Hey, pretty cool idea. So, if I understood your specifics correctly the bot's functionalities would essentially be twofold:
- starting new megathreads
- adding links to existing megathreads
About 1. I think you should seriously consider the idea of restricting the allowed megathread starters in a way. An easy solution would be only allowing community mods to start megathreads (and maybe instance admins? not really necessary, though, imo). So in your example only a moderator of [email protected] could start new megathreads. I think this would be preferable instead of an array of trusted users, because it would reduce the amount of configuration necessary.
- would be comparatively easier on a permission side and unless any incidents happen it could probably be beneficial to allow everyone to partecipate in the megathread. However removing stuff from the megathread should definitely be restricted to mods and/or admins. Giving everyone the possibility to remove sources they disagree with in a public discussion sounds dangerous.
The biggest challenge would be designing a clear interface for users. What you have proposed:
@[email protected] add to Farm section Market
sounds a bit too long winded and possibly hard to remember.
Furthermore, you might want to assign some sort of unique identifier to your megathreads, as just giving them a title (like "Farm") will likely generate conflicts in the future. The "add link to megathread" action should somehow uniquely identify a megathread, both within a certain community as well as instance wide. Asking the user to provide a link to the megathread they wish to contribute to would be an easy and unambiguous solution, but it might be a bit too difficult on the UX side (bear in mind, users are LAZY).
All in all the idea sounds great, you (we?) should just discuss the specifics in detail before any code is written.
Great idea, we really needed a more specific community. Usually any time I build something I post it to [email protected] , but the scope of that community is so broad it sometimes feels out of place. Plus, as an instance admin I feel it will probably be convenient having a single community to consult for all the extensions and integrations we might want to opt our instances in.