« first day (3979 days earlier)      last day (79 days later) » 

2:59 AM
-5
Q: default compression on response

LouiseI sent a request for question with no parameters to https://api.stackexchange.com/2.2/questions?order=desc&sort=activity&site=stackoverflow I received a response of 9764 bytes stored in StringBuffer. The StringBuffer was converted to byte[] to deCompress. GZIPInputStream threw exception : Not in...

 
 
7 hours later…
10:05 AM
0
Q: default compression on response

LouiseI sent a request for question with no parameters to https://api.stackexchange.com/2.2/questions?order=desc&sort=activity&site=stackoverflow I received a response of 9764 bytes stored in StringBuffer. The StringBuffer was converted to byte[] to deCompress. GZIPInputStream threw exception : Not in...

 
 
6 hours later…
4:13 PM
0
Q: Should we add review queues to the API?

AnonymousReview queues are unsupported on the Stack Exchange API, and it could be useful to write an app that would review. Should we add it to the API?

 
4:28 PM
@rene Hi! lackadaisical-appeal.glitch.me said to ping you — does that mean here? Have a question about the feed sometimes missing HNQs. Latest occurrence history.stackexchange.com/q/64377 missed in lackadaisical-appeal.glitch.me/hnq/history for a chat room on SE (shows up when now pulled into regular feed reader though).
 
@LаngLаngС any place you can find me is fine. I landed here in this room only recently ;)
@LаngLаngС which room does have that feed?
 

 HNQ History

Tracking Hot Network Questions history.stackexchange.com and c...
 
I have no idea, I'm testing in a new room now
 
4:43 PM
Thanks for looking into it. Can't put my finger on it, but it did happen a few times before. No obvious pattern.
 
might be some strange bug in the SE Chat feed reader
 
5:05 PM
@LаngLаngС well, beats me but it works for a setup in a new room: chat.stackexchange.com/rooms/111472/hnq-high-score-many-answers
I've upped the logging on lackdaisical-appeal and I see the Chat feed reader making calls so that is not the issue. It can only be that for some reason the SE Chat reader decides that the item it reads was already posted in that room.
Maybe a hash-collision if that is how its implemented.
 
5:22 PM
@rene But that observation is already made, when 'just pulling the feed now'. Could it be that me posting the link manually might trigger a posting-stop on it? (Though I'm still convinced that earlier a few HNQs wnet AWOL as well, without any manual posting.)
 
5:34 PM
@LаngLаngС yeah, that crossed my mind but I find that unlikely.
we're definitely not the first to observe that: meta.stackexchange.com/questions/276198/…
LOL I bountied that in 2019: meta.stackexchange.com/posts/276198/timeline
 
6:13 PM
@LаngLаngС posted a new bug report: meta.stackexchange.com/questions/367207
 

« first day (3979 days earlier)      last day (79 days later) »