lemm.ee I dont know (probably their politics compared to hexbear's), aussie.zone was due to some comments by their admin. programming.dev was due to the situation with snowe thats a bit back in meta. The votes for aussie.zone and us were tied half for federation half against
Pangora is getting merged into sublinks-ui. Ive been moving over stuff I made for it and adapting it to their codebase. Was planning on soft forking sublinks into a new version of pangora but might not need to tbh, all my stuff I wanted is getting added into sublinks
Alternative to lemmy being developed (but is also using activitypub so the two federate and its compatible with the lemmy api so frontends like sync, boost, photon, etc. will still work). When version 0.1 releases itll essentially have parity with lemmy features but with a better UI and then the next updates will be adding more things for moderation, federation, etc.
People from our instance, discuss.online, lemmy.world, etc. have been working on it
Will mostly be decided when that happens (and sublinks should be giving a lot more tools to work with for federation and moderation). Within the instance itself we didnt have any issues with hexbear users though
Its already been fixed (if I remember the patch notes correctly from 0.19 base), they just havent upgraded yet. Been seeing cross instance moderation working better in my queue
Yeah. Shows people in a list with an up or down arrow beside each of them (downvotes hoisted to the top). Helps make it easier to stop vote manipulation. People can theoretically spin up an instance to get who upvoted or downvoted but they could anyways in the database
Probably soon, just been making sure nothing major broke in the 0.19.3 update before we move over
The 0.19.1 version isnt ideal but its still usable if the server is restarted every day so gives us some time and after the situation with 0.19 0.19.1 were being more cautious
Theres a link to the community for it in the comment above. Basically will be primarily about making and guessing passwords (but also have some idle game stuff in there as well but no spoilers until I start testing which might be today edit: auths taking longer, testing this week)
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)
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
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:
Post gets created as normal in the instance
Post get removed through the lemmy ui so that it sends a removal federation action and removes the post everywhere it was federated to
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
https://programming.dev/post/8399272