Aaron Parecki

I finally got around to reading @timbray 's "Bye, Twitter" blog post that everyone's rightfully sharing, and the last paragraph of this section resonated.

Full post here, if you haven't seen it yet: https://www.tbray.org/ongoing/When/202x/2022/11/26/Bye-Twitter

Apparently, it’s rude to poke someone in the forehead and say, “skip intro,” when they start talking to you.

someone on Twitter asked why we think ActivityPub sucks from a protocol and implementation standpoint, and we're porting it over here with minor cleanups:

several things — from a server perspective, the most popular implementation requires that you become an SRE for Nginx, Rails, Postgres, Redis, Sidekiq, and possibly ElasticSearch. IMO, these (especially postgres) are nontrivial services to maintain over the long term.

once you pick a piece of Activitypub-compatible software, as far as we can tell, you're locked into that particular branch — you cannot simply export a Mastodon database into the GotoSocial implementation, you have to set up GotoSocial brand new, and make everyone refollow you

protocol-wise, we keep finding shocking ways in which activitypub is worse than email; the biggest pecadillo (IMO) is that if i follow 100 people on 3 servers and make a post, my server has to make 100 requests, one per follower, instead of 3 posts, one per server

the way the protocol works is that if two large instances defederate each other, it causes a notification storm for everyone downstream that can overwhelm smaller instances

so! if you run your own, you pretty much have to become a cache SRE, web-tier SRE, DB SRE, queue SRE, Rails SRE, you have to know how to secure unix systems, mitigate attacks, and if you're responsible, you have to do replication and backups.

sure, Docker has made it so that you can stand up all of this easily, but long-term maintenance? are you really confident that you know what you're doing here? Oh, sure, you've offloaded a lot of this to your cloud provider, but then you're now dependent on that provider continuing to work. Unless you're a large corporation with a secure contract, your cloud provider most likely doesn't care about you.

in short, standing up our own mastondong is signing up for a whole lot of Actual Work that we don't really want to do just to talk with friends, and we absolutely must stress that we both worked for twitter for 6 years and run our own **email server* for 21*

#We_Are_Plural_Not_An_Entire_SRE_Org

This whole Federated idea used in Mastodon is pretty neat.

Now imagine applying this to your social media profile page.

Except, with the ability to customize it however you want.

Add sub-pages.

Put your own images anywhere, and link to whatever you like.

All through some kind of language, all on your own server or paid service, accessible by anyone.

I think I'm on to something here. This could be the killer app for the Internet.

Just read a story about all the new social networks popping up/off right now and decided to look at Hive. The stark contrast between what they're doing and Mastodon is really something. Hive feels like a cheap knock-off of every network you already hate. Bad content suggestions, no interesting discourse, tons of people posting for clout... and just a terrible vibe. No thanks.