If you’d like a spyware free alternative, you can try vs codium: https://vscodium.com

I guess I’m late to reading about this. As a 19 year old, he met a British 12 year old online, plied them with alcohol, raped them, pled guilty, and was punished for this.

What’s interesting is he was convicted in Britain, and then was sent to serve his sentence in the Netherlands. When he arrived, his sentence was reduced and the crime was changed because Dutch law didn’t recognise his crime as rape if force or violence wasn’t involved (they changed that this year).

Despite that I’m still astonished he was even considered to represent his country in this way. Even though the law and rules allowed it, surely common sense wouldn’t.

It’s still an emerging technology so it makes sense that many of the early adopters are IT nerds. Early Reddit was the same- the most active communities were IT, programming or video game related. More diversity will appear in time.

And no mention of what happens to their API but knowing google it either goes away entirely or totally changes with significant rework required.

Related, the reason I no longer use any google API: https://steve-yegge.medium.com/dear-google-cloud-your-deprecation-policy-is-killing-you-ee7525dc05dc

I don’t see a problem so long as they do so in good faith - for example publishing full event contents to ActivityPub instead of adding a link back to the Facebook Threads app, which is basically what a lot of news sites do with their RSS feeds to get advertising money.

So long as they do that, it’s not really possible to do a rug-pull. There are far more Facebook users than Fediverse users after all, so it’s going to be advertising for the Fediverse for as long as this lasts and if users would like to remain part of it they’ll have to move to another server. That is, assuming it ends.

To answer the question though, I don’t care for microblogging personally and I don’t like Meta as a company so I won’t use it. I appreciate the scepticism but I feel optimistic.

I expect it’s accurate to say; their architecture is not like a database where you can add an index on a blocked state and then join against it. You have to get a list of potential posts that the user might want to see and then eliminate any in the block list. There will be a few edge case users who have thousands of block entries and a multithreading strategy is likely required to swiftly filter it in a reasonable timeframe.

However, an architecture I’ve seen that works around this is to build this timeline in the background and present it to the user from a cache, I don’t know if this is what Twitter does as I never worked on that. However, if you want to not have a block feature but have some kind of mute feature anyway I don’t see how there is a meaningful difference.

Haha, that’s a throwback to the days when I helped to manage a phpBB board and there were a few members that would just continuously get into arguments so I edited the database so both of them had each other on their block list. It was very telling when I discovered they unblocked each other a few weeks later and got back to arguing and derailing thread topics.

What a terrible day to have the ability to imagine that in vivid detail. What a cursed image, well done OP.