Nomadnet private group messages #287
Replies: 3 comments 4 replies
-
Yes, I think there is a use case for what you describe. I attend various meetups & festivals around the country and public msg boards for groups are very useful for attendees to post things for sale, talks being given etc. Having a wide open and readily available msg board to post such things provides a dynamic, on-the-fly public schedule of what & where things are going on in real time. Authentication for such a use case is actually not required and in fact is a barrier to its' use & success. Last year a public mesh network was implemented at Jackelope in AZ and Porcfest in NH for exactly this purpose. They would be much more useful if available through Sideband installed on smartphones. |
Beta Was this translation helpful? Give feedback.
-
The message board is a real good solution. |
Beta Was this translation helpful? Give feedback.
-
Closed groups natively within LXMF are not hard to make, per se. But they are really hard to make bandwidth efficient while still preserving privacy. I think there can be an optimal solution, but it's something I need to lock myself in a room for a week to figure out, and I haven't had the oppertunity to do so yet ;) One of these days, hopefully. |
Beta Was this translation helpful? Give feedback.
-
Please note, I said private, not secure. I'll get to that.
I had an idea while going through the NN message board code (which is amazing by the way). By combining the .allowed feature with the message board you could create an ad-hoc private message board to allow group chats. However, this is insecure in so far as there exists a plain-text version of the page on the server (which is typical of old BBS and phpBB implementations, but largely unacceptable today).
Is there any real call for this sort of private message board? It is, at the very least, very simple to implement.
The other concept is a server side repeater. Get a core page with a .allowed that would allow configuring a user name and options, but have that linked to a server script that would take a message sent to RepeaterIdent and send it back to everyone except the original recipient, tagged with : . It would be processed in the clear on the server, but would otherwise be protected by the standard encryption methods. This provides the benefits of not only a single identity to broadcast to, but also full compatibility with LXMF. It may actually be secure if you count the time in memory for the repeater as trusted.
I strongly prefer the second idea, but it is more effort. Since it's server side, it could eventually be expanded to be configured outside of NN and, if proven, possibly rolled into NN itself. I'm happy to try to implement it myself, but I don't want to step on toes, miss a major problem, or build something nobody wants. Thoughts?
Beta Was this translation helpful? Give feedback.
All reactions