After close consideration we have come to the decision to block Threads.net instance wide on all related instances

(mstdn.social, masto.ai, mastodon.coffee, pixey.org, gram.social)

The new Meta policy goes against much we stand for and we will not allow to let it spill over to the Fediverse

I just checked the numbers and it seems Threads is the biggest 'loser' here

On all instances combined we lose just under 100 followers spread across all instances

Threads will lose over 13K total

Just a gentle boost for the blog by @TeaKayB :

https://tommaths.blogspot.com/

Well the functionality of Twitter has been strangled this afternoon, Australian time.

So poking my head back in here.

Cannot retrieve tweets at this time and being accused of being a spam account there.

Way to go, Elon #twitterdown

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

Whatever is going on right now in #Russia, I do note this: #Twitter is now useless at tracking this. Junk accounts everywhere, no verified accounts, swarms of sketchy bluechecks.

The ONE thing that place was good at was breaking global news. But not now.

See everyone here tonight.