The second principle of Status is censorship resistance, so this may be a complex topic… but I’ve seen no public discussions about filtering the disproportionate amount of low quality content that is increasingly prevalent in public chat. The long term roadmap includes Tribute to Talk and Status for desktop… but today, users can’t block any content that is delivered through matterbridge without blocking it all. Has the Status Network defined and/or addressed low quality content in the past?
Almost no usage limits appear to be enforced. Users can flood/scroll a public chat with stickers that take up 1/4 of the screen… or worse, repeatedly paste and send messages that are thousands of characters long. If blocked, users can create new accounts. Repeated automated posts of enormous messages to an unnoticed public chat could silently result in a denial of service attack against nodes, and generate untenable memory/storage requirements. Do clients and mailserver nodes handle this gracefully today?
As flooding/scrolling the chat could be construed as censorship of content that came before it, I believe that addressing these concerns doesn’t compromise Status principles. Message rate and size limits would help to address this, so I’ve submitted them as feature requests… but it seems that users would also need the ability to block content itself, as opposed to blocking a specific user. Users could also potentially hide messages containing content that the community has rated as low quality in the past.
Allowing users to block messages containing specific phrases and link destinations (after their redirects complete) could potentially address this, and adding it to a context menu on a long press or selected text could make this user-friendly. Is any of this on the roadmap? If aspects of this have already been addressed, especially if there are limits in the client and/or server specifications that we can be pointed to, please point us to them.