PyBitmessage
PyBitmessage copied to clipboard
unencrypted/raw broadcast tab
As a crude method of creating a network wide shared public space (unlike the more private chans), have a tab for messaging that everyone can view. Since it is unencrypted, it provides minimal burden to the network. But to avoid abuse to such a public system (and to keep the UI simple), you can only post short single line messages to a single channel.
Messages for human consumption, doesn't have to be as structured, but should at least specify the previous message in the chain, and the message content, as well as a single channel (Structured like usenet discussion categories). Should also be ideally be crypo signed, unless anonymous post.
Messages for automated consumption (public chan announcements) should ideally be structured (json etc...), so that it will be easy to add plugins (e.g. public chan list collators). Could be usually hidden to avoid flooding users, but should be viewable if requested.
( Higher PoW if humans are expected to look at it. Also higher PoW if its to stay persistent more than a few days. )
Pros:
- Announcing new rooms.
- Semi real time (sorta IRC) chat
- Avoid balkanization of the bitmessage community.
- Helps make bitmessages feel more active to newcomers, without scaring them off.
- Minimal load due to no encryption.
Cons:
- Filtering spam : Thus higher PoW required, and single line IRC style.
- Unsavory posters (e.g. terrorist) : Thus no images, short text post only. (proper discussion meant to be in chans)
- Retrieval of older message : Thus, could keep some older messages around bit longer if replied to often.
https://www.reddit.com/r/bitmessage/comments/3ty1uo/network_announcements/
The lazy "raw" tab method. Is to have a "debug" tab, where you can view every packet coming in (matrix style lol?) even if its encrypted (depending on your filter options). An optional field for sending unencrypted packets just needs to be added, and you can still sorta clunkly do most of what this idea is about anyway.