I dont

⠀⠀⠀⠀know what you're

talking

⠀⠀ab out

.ml and hexbear have been around much longer than the other instances so have built up more subscribers

Programming.Dev

Im going to be trying to set up a tech corner similar to what Programming.Dev did last year with the dark theme zone. Any groups who want to join on around the area feel free to reach out and we can do stuff like merge templates

One to one: https://canvas.fediverse.events/#x=378&y=423&zoom=27&tu=https%3A%2F%2Fbytes.programming.dev%2Ffiles%2F1b2ba85c-98c7-4f5c-bb5e-47840aa24f1f&tw=66&tx=320&ty=420&ts=ONE_TO_ONE

Dotted: https://canvas.fediverse.events/#x=378&y=423&zoom=27&tu=https%3A%2F%2Fbytes.programming.dev%2Ffiles%2F1b2ba85c-98c7-4f5c-bb5e-47840aa24f1f&tw=66&tx=320&ty=420&ts=DOTTED_BIG

• Matrix Space
• Discord Server

I mainly use linkstack https://linkstack.org/, git repo: https://github.com/LinkStackOrg/LinkStack

Theres an instance for the programming.dev instance if you want an example of how it looks https://me.programming.dev (weve got a space-like theme on it)

Its happening once a year so likely in the summer

Im working on another event that may happen next month though depending on if I finish the rest of the things to do in my queue of projects !safe_crackers@programming.dev

(so this and canvas will be 6 months apart from each other)

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

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

Starting off banner submissions with a quick banner generated from midjourney

Example view of it in lemmy explorer

This is a collecting community that gets every topic in the instance (so people can go to it and then be naturally sent into the other ones in the instance) so questions in here are fine.

The main question communities in the instance though are:
!no_stupid_questions@programming.dev
!ask_experienced_devs@programming.dev
!cs_career_questions@programming.dev

they do an allowlist rather than a blocklist (defederate with everyone by default, explicitly allow certain ones). the two were removed from their allowlist

They defederated from both programming.dev and sh.itjust.works recently since they held a vote and they had enough upvotes to do so. Reasoning for programming.dev was due to people in our instance coming in there with supposedly bad takes but I feel like thats a major overreaction to block an entire instance of people with different views (with the different views appearing due to it not being political at all inside the instance) due to a couple people going in there instead of just moderating the individual users. The message to defederate from us also only has 13 upvotes and was both programming.dev and sh.itjust.works which I feel isnt really a majority opinion of their instance if they want one since it confounds the upvotes of two different instances and is a relatively low amount for their monthly active users

Lemmy itself has had some bugs that are bringing down a bunch of instances at once. Should hopefully be resolved in a future update