Ategon

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 [email protected]

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

I just transferred the community over to ericjmorey due to them posting in the mod thread so ill try to not manage this as much but I can give my opinion on this community

With all of the question communities ive found that the posting rate is much lower but the engagement on each post is relatively high. If the scope is widened the high activity could be flooded out due to people unsubscribing due to it not being focused on the question topic anymore

(for articles formatted as a question) With articles the focus tends to be more about the article rather than the question itself and you get people talking about things discussed within the article rather than it being open ended

Feel like best thing would be having a new community for career articles

edit: If having a new community for career articles is what you guys want after this discussion just let me know and I can set one up

Yeah sure, both cscareerquestions and data engineering are solely admin run currently so starting to move them into dedicated mod teams would be great

For cscareerquestions you just need a post or comment in the community I can use to mod you from

Theres some other sources like monkeyuser and abstrusegoose. Also encourages the creation of new comics

For some reason it doesn't like when instances running 0.19 are hooked up to the latest release. Manually specified a version and the issues were fixed

Latest release works fine on 0.18 instances like lemmy.world though

Might be something to do with 0.19, Seems like same is true across my mastodon instances. Assume that would be a bug with lemmy

Anyone's free to comment here. Meta decisions apply to any users of the instance regardless of where your account is hosted

Hexbear we are federated with but its a half federation where a bunch of their communities have been hidden by default in all of the feeds (including the community youre referring to). Usually things are fine with them interacting in the threads here locally and we haven't had any issues due to it being a specific niche

(Theres out of instance stuff but that should be up to that instance to handle them)

Also going to try to get a better instance block in at some point that allows people to block users if they want that level of control rather than just the communities. Just want these sorts of things to be determinable at the user level rather than instance level defederations since ultimately things are mostly fine

For the first paragraph: year fair. I'll likely do some more additions to our admin guidelines for expected conduct on non admin accounts and I can do a general expected conduct when participating in the instance (for all instance users) for behaviors that anyone shouldn't do regardless of whether they're an admin or not. Can add that to the support site im making

Most of the pronoun situation just stems from discrepancies in different frontends where the "main" frontend shows it but most people are on mobile apps that don't show it leading to people assuming visibility when that isnt the case. In your second paragraph people who don't realize the discrepancy in these frontends may think they're making it clear as you say

But yeah overall things in the conversation wasnt done maliciously and was able to be resolved fine

There was some other branches other than the pronoun situation although that was one of the main ones pointed out to me for defederation reasons

Dev of said fork here, not technically established, just has been in development. There is a much larger project in the works but it hasn't been announced publicly yet and its also in development

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

btw I made a post in our instance meta community if you want to read it. Been trying to resolve the situation [email protected]