pleroma and mastodon-style content warnings (a reminder)
instead of giving the author control of how the message is processed, the *recipient* should be in control. this means tagging the message with a subject, but allowing the recipient to make their own decisions on how that message is displayed.
what we want to do is give that control to the recipient, using the keyword mute system as a basis. this is done by adding a couple of new preferences:
- [ ] collapse messages with subjects by default
- list of keywords which cause the opposite collapse behavior as an override
if you want messages with subjects to be processed as if they have a CW, you just check the box. done.
if you just want specific messages with specific keywords to be collapsed, you just do it as you would now, with a keyword mute.
if you want messages to be uncollapsed, then you just put keywords there.
everyone wins, because everyone gets what they want.
🇳🇱
@kaniini im not sure that addresses the problem. If you dont have consistency in the keywords then you cant create sane rules to take advantage of it.
in every other implementation of this system, such behaviors are emergent. it will be the same here.
@kaniini im not sure i agree, its the same reason the hash tag system isnt effective at creating topic-based lists. On any one topic there are dozens of iterations of hash tags used to describe it. So the system doesnt work too well. I dont think the solution is viable or workable without some tweaks. But could be made workable with the right considerations.
there's a secondary concept that supplements what we plan to do with the filtering rules, that allows the author to split their account into sub-feeds.
it is the combination of both features that is intended to be the ultimate solution for this type of problem (seeing what you want, but not what you don't).
@kaniini I have been giving a lot of thought on how to do sub-threads correctly as well. I think both problems are very similar. I just dont think either will work if you keep the keywords free form without some mechanism to create congruity.
that's why you allow recipients to choose their own rules for filtering on.