zlacker

[parent] [thread] 3 comments
1. nsonha+(OP)[view] [source] 2023-08-16 02:39:14
did you actually get the throttle on the 10 domains? I could not even get it on one, now that it's apparently reverted.

Am I supposed to believe that Musk and his team is so dumb that they attempted to add a FIVE freaking seconds delay and thought they could get away?

replies(2): >>macki0+m >>praise+ta
◧
2. macki0+m[view] [source] 2023-08-16 02:42:08
>>nsonha+(OP)
“I can’t replicate this issue, now that the issue has been fixed” I don’t even know where to begin...
replies(1): >>nsonha+wt
◧
3. praise+ta[view] [source] 2023-08-16 04:30:43
>>nsonha+(OP)
Last night I tested the mentioned domains (bsky.social, nytimes.com, substack.com, threads.net) and a few dozen others by clicking every link I saw in my twitter feed for 20 minutes and observed the 4.5s delay on those mentioned domains but not on any others.
◧◩
4. nsonha+wt[view] [source] [discussion] 2023-08-16 08:09:33
>>macki0+m
can't even what? When you fix an issue there should still be evidence for its existence, no? Commenters of this entire thread expect everyone to read it at the exact time the issue happened?

Like what is the point of "citing" a bunch of "sources" if the "sources" are only able to provide the necessary information at one particular point in time?

[go to top]