wgroeneveld
/
brainbaking
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

fix sentence that didnt end

This commit is contained in:
Wouter Groeneveld 2022-11-20 13:34:09 +01:00
parent 5af490d22d
commit 73c4d74513
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
content/post/2022/11/the-great-mastodon-influx.md
View File

@ -17,7 +17,7 @@ Meanwhile, Sebastiaan fiddles with ActivityPub [trying to connect](https://seblo
[^act]: I recognize this might come across as a bit harsh. In a way, ActivityPub is amazing---can you imagine an _open_ protocol making it possible to use your site as your personal Twitter handle? That seamlessly integrates with the system? If you're up for a hefty development phase, that is.
Even more scary is perhaps Aral Balkan's _why every toot is also [a potential denial of service attack](https://ar.al/2022/11/09/is-the-fediverse-about-to-get-fryed-or-why-every-toot-is-also-a-potential-denial-of-service-attack/)_ post, where he proposes one solution: everyone should be on an instance-of-one. Except that doesn't help, as Aral is on one, and his host had to upscale quickly because he has 23K followers, having to pay `€50`/month now. That means there's technical knowledge involved, even if you let someone else manage it---yet another
Even more scary is perhaps Aral Balkan's _why every toot is also [a potential denial of service attack](https://ar.al/2022/11/09/is-the-fediverse-about-to-get-fryed-or-why-every-toot-is-also-a-potential-denial-of-service-attack/)_ post, where he proposes one solution: everyone should be on an instance-of-one. Except that doesn't help, as Aral is on one, and his host had to upscale quickly because he has 23K followers, having to pay `€50`/month now. That means that not only it's expensive to "be an influencer", there's also technical knowledge involved, even if you let someone else manage it.
Twitter once ran on Ruby on Rails and used a single MySQL database as a backend. It notoriously had a lot of performance issues. Mastodon is built on Ruby on Rails as well, and guess what: it's struggling to keep up, even with Ruby's "fast job system" called [Sidekiq](https://sidekiq.org/). Pleroma on the other hand runs on Elixir and claims to be using [significantly less resources](https://soapbox.pub/2021/10/10/choosing-a-backend-for-soapbox-fediverse-mastodon-pleroma/). But you can't go around ActivityPub's required message-passing system that Sebastiaan is also experiencing difficulties with---as soon as a few other servers pick up your endpoint, your server is dragged along in the message maelstrom. The Beam server on my VPS that serves Elixir processes consistently takes up the most CPU load and I'm currently wondering whether or not it's worth it. The Postgres DB is about 800 MB right now.