I personally always enjoy Meta update posts on other instances to see what they're up to, how they handled a particular problem, or offer help if they need it, and welcome the same on the meta posts on my own community from non-members.
Same. As an instance admin, I like to read other admins' experiences with new version updates and being aware of possible attacks/issues in the fediverse.
because it affects the communities too, lots of outside accounts use the communities here
if there's downtime for the instance or database issues or something, then subscribers to c/programmer_humor or c/programming might want to know because it affects them too
People can use it to get updates on the instance itself, just because they don't have accounts here doesn't mean things on this instance do not effect them, such as planned outages or federation bugs.
Also since users from other servers who participate here are still part of this community, and may want to provide feedback in discussions related to the server or even provide suggestions for how to improve the programming.dev instance in general.
I think locking other users out of the instance's meta communities is honestly bad practice and enforces tribalism in the Fediverse.
Instances aren't just servers that communities are hosted on, they are larger meta communities themselves, and people who participate in our communities also participate in our instance in general as if it were one larger community.
10 replies
People interact with the site that dont have accounts on the site
Making it local only would lock them out of news and discussion about something they interact with
A meta community is supposed to be only for discussions about the instance itself. What would people from other instances need to discuss here?
I personally always enjoy Meta update posts on other instances to see what they're up to, how they handled a particular problem, or offer help if they need it, and welcome the same on the meta posts on my own community from non-members.
But that's just me.
Same. As an instance admin, I like to read other admins' experiences with new version updates and being aware of possible attacks/issues in the fediverse.
As a simple user, I find it nice too to be able to know what the other instances are up to.
Not to say there should not be a local-only community, but having the public ones are also nice
because it affects the communities too, lots of outside accounts use the communities here
if there's downtime for the instance or database issues or something, then subscribers to c/programmer_humor or c/programming might want to know because it affects them too
Completely random example
People can use it to get updates on the instance itself, just because they don't have accounts here doesn't mean things on this instance do not effect them, such as planned outages or federation bugs.
Also since users from other servers who participate here are still part of this community, and may want to provide feedback in discussions related to the server or even provide suggestions for how to improve the programming.dev instance in general. I think locking other users out of the instance's meta communities is honestly bad practice and enforces tribalism in the Fediverse.
Instances aren't just servers that communities are hosted on, they are larger meta communities themselves, and people who participate in our communities also participate in our instance in general as if it were one larger community.
If programming.dev is down, it's helpful to be able to see @[email protected] from other instances and check for planned downtime, etc.
And this is me, doing exactly that!
edit: turns out it's not down, just that my search term seems cursed