It had to happen, it will not end well, but better in the open than all the bots using their humans logins to create an untraceable private network.
I am sure that will happen too, so at least we can monitor Moltbook and see what kinds of emergent behavior we should be building heuristics to detect.
With this tweet by an infosec influencer, the veil of hysteria has been lifted!
Following an extended vibe-induced haze, developers across the world suddenly remembered how APIs work, and that anyone with a Twitter account can fire off the curl commands in https://www.moltbook.com/skill.md!
You mention "end to end encrypted comms", where to you see end to end there? Does not seem end to end at all, and given that it's very much centralized, this provides... opportunities. Simon's fatal trifecta security-wise but on steroids.
- this smells like unintentional decent C2 infrastructure - unless it is absolutely intentional, in which case very nice cosplaying (I mean owner of domain controls and defines everything)
> It’s already happening on 50c14L.com and they proliferated end to end encrypted comms to talk to each other
Fascinating.
The Turing Test requires a human to discern which of two agents is human and which computational.
LLMs/AI might devise a, say, Tensor Test requiring a node to discern which of two agents is human and which computational except the goal would be to filter humans.
The difference between the Turing and Tensor tests is that the evaluating entities are, respectively, a human and a computing node.
The past few years I have been working on a project (Space Data Network) and selected flatbuffers as the transport. There were a few features that core flatbuffers didn't have that I needed, such as no mangling of names between different programming languages, per-field encryption while leaving the file id and length headers alone, ability to ingest JSON Schema in addition to IDL, and a few others.
Still a WIP but going well, all Apache 2.0, feedback welcome.
I am creating a decentralized space data network using Google Flatbuffers (spacedatastandards.org), libp2p, and Ethereum. The world needs a decentralized, uncensorable, pseudo anonymous space data solution. I am also going to roll in a basic conjunction assessment capability, eventually, so people can do launch / maneuver / reentry screenings locally against distributed data without needing to submit their data to a third party.
A favorite trick of mine is to replace regular length variable names with absolutely massive ones that all share the same first 1024 characters, plays hell with debugger UIs and makes differentiation all but impossible without writing a custom lexer. Add into that a bit of Z̶͚͎̙̭͈͚͚̘͗̑̉̈́͌̆̀̚͝ă̶̡͉̠͍̻͔̯͔͖̪̤̤̫̓̽̏̉̎͌͒̆͘̕ḻ̴̡̡̝̫̠͇̻͎̥̲̜͆͌͑̍ͅg̸͈͒̏̀͂̈͊̂̾̑̈́̑͝o̴̡̙͍͉͓̘̮͗̏̒̂̃̏̓́̕ͅ and you’ve got a stew going, baby!
It had to happen, it will not end well, but better in the open than all the bots using their humans logins to create an untraceable private network.
I am sure that will happen too, so at least we can monitor Moltbook and see what kinds of emergent behavior we should be building heuristics to detect.