I'm sorry, it took *how* many servers to post a single long message from Ghost to 5k fediverse accounts and handle some replies?
-
@Viss @kissane @fediversereport might be more networking intensive than compute intensive, fwiw
-
@by_caballero @kissane @fediversereport yeah the issue here isn't the front end js stuff - its whats running under the hood, powering any given mastodon instance. its a ton of ruby on rails, which twitter showed the world "isnt exactly the best language/framework to do huge, high volume. small bandwidth transactions and queueing systems". its why twitter scrambled to get off RoR and moved to scala as they grew.
i was VERY SURPRISED, to say the least, learning that mastodon still uses RoR.
-
@Viss @kissane @fediversereport right but ghost doesn't run mastodon, it runs fedify which interoperable with mastodon API. the 10 servers in question are fedify servers:
https://fedify.dev/ -
@pete @fediversereport @thisismissem I think that's a reasonable take!
It's also partly the information that to federate Ghost posts to a group that's equivalent in size to the number of people who follow me on Mastodon will cost at least $155/month—not counting email subscribers—is somewhat startling to me.
Like, I fully understand that infra isn't free, but Wordpress (which I am not going to use) charges $25/mo for a plan that includes AP federation.
-
@by_caballero @kissane @fediversereport the repo that project links to appears to be a node/npm project with dirs indicating it runs inside a docker container.
so this is javascript running 'as a server' inside docker, which is very different than ruby on rails, but in its own way, super topheavy in terms of layers of abstraction, and also entirely unsurprising it gets loaded down easily.
-
@by_caballero @kissane Did it support comments sections, notifications &c?
-
@polotek @kissane @fediversereport I remember when twitter first launched and everyone in that community were discovering the work needed to get RoR to scale to a global “firehose” size. Feels like we're back there again but in different ways.
-
Ziggy the Hamster :whyfox:🐹🌻replied to Viss on last edited by
@Viss @by_caballero @kissane @fediversereport
That was literally 16 years ago.
Most of the world still ran Windows XP and Internet Explorer.
Ruby and Rails are plenty fast today, and one could argue was when Twitter changed, but they were unwilling to make large changes to their code to be able to upgrade.
If you use GitHub, buy something with Shopify, or listen to a lot of podcasts, you are using Rails apps that perform just fine.
-
@kissane @fediversereport @thisismissem Yeah, that’s a downer. I wonder (based on total ignorance!) if there’s an incremental way to do this sort of thing? Like RSS broadcast at one end, full Masto ping-fest at the other, and Ghost could be somewhere inbetween?
-
Ziggy the Hamster :whyfox:🐹🌻replied to Ziggy the Hamster :whyfox:🐹🌻 on last edited by
@Viss @by_caballero @kissane @fediversereport oh shit, I also forgot about GitLab.
Mastodon isn’t a resource hog due to Rails, it’s a resource hog due to ActivityPub being somewhat badly implemented across the board, meaning that most actions result in amplification (ping N servers about a reply) and this amplification can sometimes be severe.
-
@pete @kissane @fediversereport many activitypub servers use queues for processing incoming activities, along with caches
-
@poswald @kissane @fediversereport I should be more clear about which issue I'm referring to. There are many technical issues to solve. I'm talking specifically about an issue that is specific to the decentralized nature of the fediverse. There are many optimizations that a company like twitter can do to scale fanouts, because they control both the source and the destination. Fediverse servers do not have that advantage. And more so, many servers are likely to be under resourced.
-
@poswald @kissane @fediversereport As far as I understand, mastodon's implementation is particularly naive today. If you have 5000 followers, every post creates 5000 jobs. There are many optimizations they can make today that will help. But I believe the problem of scaling of decentralized message delivery is going to be a huge bugbear if the fediverse keeps growing.
-
@kissane @pete @fediversereport @thisismissem You can federate with all of our WordPress.com plans, including the free plan! I assure you our infra can handle a lot more than the fediverse has been able to throw at it thus far.
-
@mattwiebe @pete @fediversereport @thisismissem Ah, I must have been reading old docs!
-
@kissane You do need that plan for installing plugins but many features, like ActivityPub, are available on all plans.
-
@mattwiebe So I went back to see what docs I'd run into as I searched while making dinner, in case it's useful: I googled "activitypub wordpress free" (not in quotes) bc I thought I remembered that it was free. The first few results offered no obvious answer, but the fourth had one that was accurate at the time, but isn't now.
(Might I have checked another post if I hadn't been stirring multiple pots of noodles? Very likely yes.)
-
@kissane Aha! That was the post from when we acquired the plugin and brought @pfefferle on board. This is when we launched it for everyone: https://wordpress.com/blog/2023/10/11/activitypub/
We should probably add a follow-up note to the older post
-
Jenniferplusplusreplied to Erin Kissane on last edited by
@kissane @fediversereport @thisismissem
This is armchair engineering, but I suspect there's an architecture issue here. I suspect ghost is organized around the assumption that secondary work is fast and easy. Like sending emails is mostly an API call to mailgun for them. But there's no mailgun for activitypub, so they're doing it themselves, and it happens in a blocking way. -
@mattwiebe @pfefferle Honestly this largely is a search results problem, but that's a problem we all live with forever somehow. I keep meaning to check out your implementation!
