Hi, I’m new here, so I apologize if I get anything wrong, or am not detailed enough in any way.
I am told that @DGeddes can help me here since the RFC process is being updated.
I am also aware that this is not a v1 goal, and am fine with it being a post-v1 goal (patch?), or a v2 goal.
I am working on an imageboard , and I hope that liveposting  can be a possibility with SAFE.
1. Network Push Notifications
- Example: A client is typing in a post form, we want the other clients to see what it’s typing.
A way to do this would be to have client A send a network push notification along with related data (PUT index 46 (containing the string “some”) of post 4262?), in which client B and C are watching for a network push notification, to then display the new post text on their display.
How can we ensure that this doesn’t leak IP addresses or other user information in the process
How would this be achieved in safe_vault or perhaps safe_client_libs?
How can we structure an RFC to provide detailed information on a specification for this?
2. Streaming Chunks (Possibly off-topic)
I’m not entirely sure what @dirvine meant by this, so if applicable here (or needed) as a feature RFC, please clarify.
A “commit signal” was also mentioned, so perhaps having the network stream the chunks to clients without actually finalizing to the network yet, but having the network host it as mutable data until finalized?
: An imageboard is like a text BBS, but with images.
: Liveposting is where you type in the post form, and it shows what you’re typing, only in the post form, to the other clients.