We usually hide bot communities here which would include zerobytes but my hiding system recently broke a bit due to the 0.19 update so I haven't hid any recently
I can fix that and hide the new communities that popped up
(Hiding just means they dont show on the feeds by default but show for someone if they subscribe to them)
Edit: Fixed the issues with my system and hid the main ones that appeared in the scaled feed, ill hide more as I see them
Edit #2: There is also a way to block an instance like you said by going to your user settings and then the blocks tab on web but this is one case that should be getting handled by us
yeah the interaction per content ratio is extremely high
c/programming was also considered lively last month since it got a bit of a boost from some posts but now its a bit under. Nothing else is close to these two
if it has actual content that relates to the community then its allowed
if its paywalled though or doesnt relate to programming then can be removed (programming in a general term since this was voted to be a collector community for all programming content in the instance)
The standard (I say standard but its really just the thing most sites use since it boosts their numbers) that social media uses for monthly active users is to do people who have logged in. This is what mastodon uses as well
While they aren't actively contributing content they are still actively using the site (active account as opposed to dead account)
I think lemmy should match up to the mastodon and other social media calculations so these comparisons actually make sense otherwise were just making lemmy feel dead by calling a different calculation MAU than what people are used to and since both calculations are being compared like they're equal
For communities yes due to cross instance stats but for instances themselves (which the stats above is based on) no. You can just use post read times in addition to the three which will catch anyone who has read a post. Post reads are something each instance has access to for its users so it can do the unread comments feature but it doesn't federate (but each instance self reports stats on itself).
the 2 million here includes the account bots that mass target open signup instances. (if an instance has no restrictions on signing up then they tend to make 8k accounts or something on it). fedidb detects that and excludes it
Calculation for MAU changed so the old MAU and the new MAU cant really compared
old one used to include commenters and posters while the new one has that and also voters
both are missing people who dont do any of these three actions though
1 -> yep, to make it a certain language put that language after the first three backticks. For inline you can do it using curly braces after the second backtick with a dot and then the language in it
3 -> unknown, I didnt mess around with that when implementing them and I dont think it supports it. edit: can probably be added manually by messing around with css. Ill do a pull request after my exams
There was some federation issues that are getting fixed plus a couple other bugs that need to get fixed before we update so site behavior doesnt break (e.g. show read posts not working). I assume we would update sometime after Christmas since 0.19.1 is in release clients and so we aren't dealing with maintenance over the holidays
Edit: seems like 0.19.1 released today, still likely after Christmas due to the second reason and so that can be checked to make sure there's no issues still
Heres my results, primarily around the gamedev section of the instance and here