@RealNewz247
I think it has to do a lot with the amount of people on the server. If I am not mistaken #Gab social is a fork of #mastodon even if it is #opensource so a lot of features will be built on top of it. Maybe someone can correct me like @admin or anybody else.

@pookito @RealNewz247

It's really simple actually. Gab is a fork of Mastodon and most of the 'mastodon' reffs are removed from the code but the main app is the same.

Gab runs just like Mastodon on 3 different services:

1. - gabsocial-web (mastodon-web) -- this delivers the front app for users to login (web and stuff)

2. - gabsocial-sidekiq (mastodon-sidekiq) -- this process all the actions from users local and in the fediverse (post, follow, favourite etc)

3. - gabsocial-streaming (mastodon-streaming) -- this is the API part that takes care of the endpoint for applications for example

I think #Gab has troubles with the sidekiq part (2) if you have that much users to take care of it will generate a lot of actions(!!) so you need to spread this to multiple servers to decrees loads and get all actions done (within reasonable time ofcourse)

I hope this clears up things a little!

@admin they also seem to have really screwed up the api locking things down. I think that's where all of the 500 errors were coming from that last few days @RealNewz247 @pookito

@dude @pookito @RealNewz247

Typical resource problem the 500 error :-)