I’m going to cover a lot of ground in this post, so here’s the TLDR: We built a Twitter-scale Mastodon instance from scratch in only 10k lines of code. This is 100x less code than the ~1M lines Twi…
Not your usual teaser, but still a teaser. “Look at all this techno-marketing. It shouldn’t take more than a couple of weeks. By then we’ll have some actual code to look at and toys to play with.”
In fairness, they are providing what looks like a decent overview of their underlying system (Rama) and how they used it to create their mastodon instance.
But I guess it worked :) I bookmarked their page and will check in from time to time. Maybe their toy (prototyping) system will be enough to run a personal instance…
I think the whole discussion of the architecture was pretty interesting and gives some insight into what can be done by ActivityPub platforms to facilitate scaling going forward. There’s been a lot of discussion previously whether ActivityPub creates some inherent limitations on scaling, and looks like they’ve demonstrated that it can scale pretty far.
Not your usual teaser, but still a teaser. “Look at all this techno-marketing. It shouldn’t take more than a couple of weeks. By then we’ll have some actual code to look at and toys to play with.”
In fairness, they are providing what looks like a decent overview of their underlying system (Rama) and how they used it to create their mastodon instance.
But I guess it worked :) I bookmarked their page and will check in from time to time. Maybe their toy (prototyping) system will be enough to run a personal instance…
I think the whole discussion of the architecture was pretty interesting and gives some insight into what can be done by ActivityPub platforms to facilitate scaling going forward. There’s been a lot of discussion previously whether ActivityPub creates some inherent limitations on scaling, and looks like they’ve demonstrated that it can scale pretty far.