CrazyDuck

joined 1 year ago
[–] CrazyDuck@lemmy.world 7 points 1 year ago (3 children)

This is an article from March 2021...

[–] CrazyDuck@lemmy.world 3 points 1 year ago (1 children)

I hope you like clutter because gitlab's interface is atrocious...

[–] CrazyDuck@lemmy.world 2 points 1 year ago

Thanks! It's extremely insightful to get a peek behind the scenes like this. Stuff like this always happens behind closed doors and threads like yours really help shine some light :)

[–] CrazyDuck@lemmy.world 6 points 1 year ago (5 children)

Do you remember/are at liberty to elaborate on the reasoning and course of events at the time that lead to defederating?

[–] CrazyDuck@lemmy.world 5 points 1 year ago

It's a secret nefarious feature to keep you sucked in, just like how there's no clocks in casino's :p

[–] CrazyDuck@lemmy.world 17 points 1 year ago* (last edited 1 year ago) (12 children)

Wasn't XMPP EEE'd by Google? Not to say that Meta is any better of course

[–] CrazyDuck@lemmy.world 2 points 1 year ago

Didn't twitter just default on a massive google cloud bill on the first of July? This is pure speculation, but it wouldn't surprise me if the rate limiting is a direct consequence of them having to massively scale back infra because of getting kicked from Google cloud

[–] CrazyDuck@lemmy.world 3 points 1 year ago

Lots of instances are waiting for 0.18.1 to be released, which will bring back captchas, which got removed in 0.18.0. The devs pushed out 0.18.0 to fix a bunch of annoying bugs and to make their api more sustainable (http vs websockets), but changing api technologies meant that captchas needed to be entirely reimplemented. They didn't want to wait for that to push the bug fixes and the new api, hence why you're seeing the discrepancy. The new jerboa app using the new api got pushed together with the new api, but isn't compatible with the 0.17.4 version