Indie game developer 🇨🇦

Working on some games for game jams in my free time

Admin of programming.dev and frontend developer for sublinks

Account has automation for some scheduled posts

Site: https://ategon.dev Socials: https://ategon.carrd.co/

  • 59 Posts
  • 127 Comments
Joined 1 year ago
cake
Cake day: June 8th, 2023

help-circle












  • The 2m there is extremely inflated to to bot sign up spam. Back when instances were getting set up in the reddit migration there was some people that start mass signing up accounts on instances with weak security. Fediverse observer doesnt care about any of that and just shows user accounts regardless of what happens on the instance

    Fedidb has a much more accurate count at ~ 400k https://fedidb.org/software/lemmy since they exclude these bot spammed instances. They also have a monthly active user count (~ 38k) based on what instances report for that stat







  • the issue is there isnt such thing as an instance-only community

    if you mimic the actions I did above but on the community level rather than the post level you might be able to do it but new instances pulling the community for federation after you did it wouldnt be affected by that so you would need to seed it in the instances ahead of time or keep doing it

    a second way would be reaching out to other admins to remove the community from their instance but that involves talking to a ton of different instances


  • There is technically a roundabout way you can do it although it involves a bit of actions

    I havent fully tested it so may need some variation of the actions to work but:

    1. Post gets created as normal in the instance
    2. Post get removed through the lemmy ui so that it sends a removal federation action and removes the post everywhere it was federated to
    3. Post get unremoved in the database by changing the removed value to false. As this is changing the value itself rather than sending an action this does not federate and only unremoves it for the instance itself