I’m somewhat relieved that we MAY have more like 4 months to get these priories out the door…I wouldn’t assume more, just in case.
1 Like
I’m no moderator or AP developer but I do have a (not currently specified, to my knowledge) suggestion I’d like to throw out there as it relates to moderation:
The ability to limit new users from a remote instance could allow certain Threads users to interact with an instance, while automatically keeping out everyone else. It could also be useful during remote instance spam attacks, to allow existing people to continue interacting as normal while keeping out the wave of spam accounts.
- I don’t think this should be a “deny” but rather an “ignore,” so that once the spam attack is over, legitimate users who registered during the attack can interact once the limitation is removed.
- Admins should be able to manually approve new users even if the setting is on.
- In Mastodon, I think this would be best done as a check-box next to the existing “limit/mark media” options, so that you can combine it with “silence” for some servers and “none” for others (to allow existing users to still appear in public timelines).
- This might be useful for firehose bridges, especially if some pattern matching can be added (i.e. by domain suffix), like mostr.pub and the future Bluesky bridge(s).
2 Likes
Clearly we now have a clearer timeframe.
The idea of “what can be done in the next quarter or two” seems all the more important.
2 Likes