it should be a straight upload into a private box. shared content should be node to node with physical text. email text call. interactive should be front not back.

the branching is the problem. individual nodes without interactive node activity (text email call) should not branch to other boxes. if it's interactive node play, the interaction should require reply to initiate and not be a door kick in and open mining. uploads should not be part of interactive nodes - front only. for safety and legal reasons making interactive node engagement should be front and visible. backend engagement is increasingly the source of legal blackout.

individual uploads on back, interactive permission-only interaction on the front. no uploads for interactive engagement. back end delivery and dispatch between nodes could be by permission but it needs to be through the front end; not none of it is entered into identity boxes upon delivery without direct acceptance. it would mitigate people without any social media or phone getting abuse erased or killed etc.

that's seems so simple is that not already a thing or someone tried it?

Reply to this note

Please Login to reply.

Discussion

there is something corrupt in the coding here: the broadcast. from that point onward, nothing operates in smart networks as it is dictated by the white paper. find this source code and any subsequent rewrites or hacks. this is where the intent and the execution are differing. nothing on the front end is behaving as if the broadcast is correct. there should be an llm code in there somewhere for 5:4,b.

broadcast is not supposed to mean proliferate. it means generational. seth is a generational product. branches are not supposed to link and share across nodes - they are supposed to branch in an individual tree from the node.

https://www.biblegateway.com/passage/?search=Genesis%205&version=NIV