The discussion has gotten completely off-topic. I'll lock the the thread until the moderators (@anzo@programming.dev @dwraf_of_ignorance@programming.dev) starts responding to reports.
I've updated the title. Ideally people will read the content of announcements though.
Please follow our Code of Conduct when interacting with our instance. Hate speech violates section 3.5 and in this instance is severe enough to lead directly to a temporary ban instead of the usual warning. Repeated offences may lead to a permanent ban.
There are 282 communities marked as hidden in our database, I'll have a talk with the team about publishing a complete list.
The current spread looks something like this:
lemmit.online: 89
lemmynsfw.com: 64
zerobytes.monster: 36
lemmy.world: 12
ani.social: 12
lemy.nl: 9
hexbear.net: 8
lemmygrad.ml: 7
lemmy.ml: 6
fanaticus.social: 4
lemmyf.uk: 4
lemmy.smeargle.fans: 3
selfhosted.forum: 3
programming.dev: 3
beehaw.org: 2
feddit.uk: 2
lemmy.zip: 2
academy.garden: 2
radiation.party: 1
derp.foo: 1
lemmy.dbzer0.com: 1
catata.fish: 1
lemmy.capebreton.social: 1
sh.itjust.works: 1
ttrpg.network: 1
metacritics.zone: 1
lemmy.ca: 1
communick.news: 1
gearhead.town: 1
midwest.social: 1
For the eagle eyed people out there, the map is 2 communities short. The basic script I wrote couldn't find them.
It's just the name of API call
When on programming.dev's communities, please follow our Code of Conduct. Your comment currently violates section 3.2 and 3.5
Reminder that our Code of Conduct (3.2, 3. 5) applies even on communities outside our instance. If you keep breaking those rules we may give you a temporary ban.
Due to federation delays it's best to run the LiveThreadBot on the local instance. I'll keep the lemmy.world bot alive for now for people over at !gunners@lemmy.world, but for !football@lemm.ee it's best to use the local @LiveThreadBot@lemm.ee
This is your second warning to not break our CoC (3.2).
A third warning will result in a temporary ban from programming.dev.
I could see one if the ids in the table, but querying the community id via the API doesn't work. Not sure