🔻Sleepless One🔻

Depends on what you consider taking down. The fact that the project is FOSS means anyone who wants to can fork the code, so it would be hard to eliminate one’s ability to get the source code even if the main repos got taken down and the maintainers are detained or killed.

As to whether they can control the fediverse in a way that allows them to invent reality like they do with mainstream platforms, I could see them trying to compromise admin teams for individual instances. However, unlike mainstream social media, our eggs aren’t all in one basket so to speak. They won’t be able infect the entire platform like they can do with big tech.

That sounds like a good idea generally, but it’s hard to say more without specific feature ideas in mind.

This seems like a big change that also requires a lot of brainstorming to flesh out. It sounds like it would best be made as an RFC for now.

I’m personally annoyed with how the default UI shows messages and mostly work on the frontend, so changing that is definitely on my agenda.

Bomber for me.

There was some discussion among the maintainers months ago regarding holding a contest for a new logo, but it never came up again. I think it would be a good idea.

I’m personally working a full time job in addition to this. However, I spend a lot of my free time contributing because if the only software I worked on was the corpo shit at my dayjob that ends up being cancelled before it reaches production half the time, I’d go insane.

I’ve found the people pretty good. I find it’s easier to get a sense of community on here than it is on big tech platforms.

Joy, but also panic.

Users can already block entire instances, so progress has been made on this front.

I’m curious how we’d go about automatic mod kicking. Instance admins are already able to remove and appoint mods to communities. What would a sensible trigger for auto-removing mods be?

I’ve been wanting to change how the existing admin options are organized on the admin page for awhile now to be easier to understand. As for improvements beyond that, I’m open to suggestions from instance admins for improvements.

Regarding your last point, even if an offending user is registered on another instance, banning them will prevent them from bothering users on your instance.

This is a good idea. There are currently mirrors on codeberg and a gitea instance, but I could see picking one of those platforms as the main place to host and making the github one a mirror. The main hurdle I can see for this sort of migration is that all the open issues are currently on github.

Not much that can be done to prevent them from using it. Mitigation on the maintainers’ part would be omitting them from suggested instances. The best way to combat it, I think, would be instance admins coordinating defederating from offending instances.

1. Late 20s
2. No
3. Burgerland
4. I’d try but probably fail. I’m not big on getting public attention.
5. No
6. 33%ish at the absolute max.
7. No, I like the name

Some that come to mind:

• Scaled sort, which takes community size into consideration when looking for top posts
• User will be able to block instances without the need for their home instance to defederate
• The new flow for enabling 2FA makes it harder for users to accidentally lock themselves out of their accounts
• There will be a feed option to just see posts in communities you moderate (as opposed to subscribed, local, and all)
• Controversial sort
• You can import and export account settings as JSON, making switching instances easier

I was not expecting a HexBear struggle session in the dev AMA lol.