This is hilarious. It appears that Twitter is DDOSing itself.

The Twitter home feed's been down for most of this morning. Even though nothing loads, the Twitter website never stops trying and trying.

In the first video, notice the error message that I'm being rate limited. Then notice the jiggling scrollbar on the right.

The second video shows why it's jiggling. Twitter is firing off about 10 requests a second to itself to try and fetch content that never arrives because Elon's latest genius innovation is to block people from being able to read Twitter without logging in.

This likely created some hellish conditions that the engineers never envisioned and so we get this comedy of errors resulting in the most epic of self-owns, the self-DDOS.

Unbelievable. It's amateur hour.

#TwitterDown #MastodonMigration #DDOS #TwitterFail #SelfDDOS

Are you good with Kotlin coroutines and Flow? Maybe you can help me?

https://stackoverflow.com/questions/76201558/emit-a-loading-value-from-a-flow-if-it-has-not-emitted-any-values-after-some-t

I think I will give my own Mastodon instance a real shot now. 😅 But I will not (yet) move this account away from androiddev.social.

I would really appreciate if you could follow me also at @kypeli 🙇

Now my Mastodon instance is using AWS S3 for media storage with Nginx reverse proxy as cache in front of it.

I think this is working pretty nicely now.

I feel like a young version of me, tinkering with a Linux server in 1998.

Looks like my instance is working fine! Still need to setup S3 for media and understand a bit maintenance and metrics of the server.

And of course make a decision if I want to move over here.