Skip to main content


Misskey just softlocked my browser wtf
JavaScript be like that
its not even JS its just misskey is bad
what makes misskey bad genuine question
its slow it is bad at federating its slow its bad at federating the api is bad its slow it doesnt federate well at all
oh I had no idea. I've been considering it as my choice for instance software against Mastodon. Not looking at Pleroma due to scalability and caching since we're interested in infrastructure to handle up to 500 users. Misskey seemed a lot more modern and simple afa dependencies vs. Mastodon.
why the hell are you making a 500 user instance
an instance *capable of supporting a proposed maximum* of 500 users. my group already has like 130 people. if we're going to re-deploy and invest in the hardware + time to spin everything up then we want the overhead and capabilities to be able to reliably handle up to 500 active users. @neko
@neko
just use mastodong
does mastodon actually scale better than pleroma

that seems unlikely
mastodon and misskey, yeah, from everything ive looked into. pleroma is great for single user instances and smaller instances but doesnt scale like the other two do @neko
@neko
pleroma scales insanely good are you insane
mastodon can scale horizontally across multiple servers, has better caching, utilizes redis and compression, has good documentation, and is under active development.

Misskey is similar afaik but also has a fuckton of other features and nifty things like user drives but also at the cost of heavily heabily JS dependent.

Idk maybe @alex can shed some light onto this topic @getindor
Mastodon is built on tech that is inherently expensive to scale, but its architecture allows for scaling it pretty much infinitely if you can throw money at it.

Pleroma is built on a way better software stack and has potential to scale cheaply, but gets easily bottlenecked by the Postgres database.
Also the reason Soapbox is good is because you don’t have to choose between Pleroma or Mastodon. You can use either is both with Soapbox.

The reason Misskey is bad is because it doesn’t work with Soapbox.
>soap
>Good
Gonna be very difficult convincing the fedi of this
its better than pleromaFE performance and feature wise but i want full emojo reacts still
What are ur thoughts on revolver btw?
Sounds great conceptually. I wanna see the code.
we have 2 dell r630s to play with. Can you provide some information re the differences in scalability and how pleroma gets bottlenecked? @neko@getindor
20,000 users all hitting the Home timeline at once. Every request is an SQL query with different parameters and there’s no cache. Even though Elixir can handle a fuckton of http requests, the database can’t handle the load.

There’s no way to shard the database, and CockroachDB doesn’t work either. I tried all the easy solutions. What it needs is pregenerated timelines in a cache like Redis. That’s why Mastodon doesn’t have this problem.
Postgres supports connection pooling and load balancing. Should be able to scale up the database just fine.
You can add read replicas, which makes writes slower. And we’d need a lot of them because the home timeline is an expensive query.