cheeseburger
Comparing GET requests for the next page between logged-in and logged-out, the only difference in the request headers is the addition of an Authorization field in the logged-in GET.
The response from the server for my logged-in requests is a 504 gateway timeout page from Cloudflare telling me to try again in a few minutes, and providing a unique Cloudflare Ray ID each time. Same thing on Windows/Chrome when logged in.
Example ray id: 8a92cf221ff78431
On the Chrome browser the console spits this error out after each timeout, complaining about client.js:
edit: Removed irrelevant console dump.
GET https://lemmy.ca/api/v3/post/list?page_cursor=P188614a&limit=20&sort=Hot&saved_only=false&type_=All&show_hidden=false 504 (Gateway Timeout)
I'm on a bridge still while we wait for Bitlocker recovery keys, so we can actually boot into safemode, but the Bitkocker key server is down as well...
But that would make it hydrogenated! I guess it's back to the drawing board, Bill.
Super interesting. You make me think back to The Chemical Workers Song about guys with jobs like you had. The song always gives me goose bumps.
Holy shit, it's Manhattan!
Around here tailors say, "which way do you hang" (or they used to, it's been a while) and it's because extra room is required in tailored pants. Generally junk at rest prefers one side to the other.
Why is the Saskatoon Museum of Military Artifacts posting about ancient Nubian pyramids?
I didn't realize where I was and was laughing while watching in anticipation of a pot-bellied old man shuffling through the shot.
Anyway, still a good video.