The full Firehose provides two major verification features. First it includes a signature that can be validated letting you know the updates are signed by the repo owner. Second, by providing the MST proof, it makes it hard or impossible for the repo owner to omit any changes to the repo contents in the Firehose events. If some records are created or deleted without emitting events, the next event emitted will show that something's not right and you should re-sync your copy of the repo to understand what changed.
If the simulation hypothesis is real, perhaps it would follow that all the dark matter and dark energy in the universe is really just extra cycles being burned on layers of interpreters and JIT compilation of a loosely-typed scripting language.
... a reality where everything in software development that was previously established as robust foundation is discarded, only to be re-learned and re-implemented less well while burning VC cash.
One can authenticate message integrity on the client side and the server side, it doesn't have to be a trade-off. The same is true for encryption and decryption.
Neither. legal and compliance. If you hire someone in a new country you now have to comply with that country's labor and tax codes, a lot of times that means setting up a new legal entity in that jurisdiction. This can be really difficult/impractical for smaller companies.
I think that's a false myth, there are now EOR like Deel and Remote.com that make this super easy today.
There's also the "false contractors" route, i.e. hiring remote contractors but treating them like employees. Which is also a quite common setup among early
stage startups with a fully distributed DNA.
It will be because the mental image of a startup involves herman miller chairs and everyone in one room, grinding out broken code while sleep deprived against a background of colleagues fighting in a corner. With beer.
That this stereotype is self evidently absurd doesn't really detract from the psychological pressure to imitate. It's like the companies who carefully copy all the hiring practices they've heard about from Google but don't bother with the compensation or aggressively targetting specific university graduates to recruit from.
It's really easy to get a single room with a beer fridge and make everyone stressed, and some successful companies had that property, so let's copy the properties we know how to.
An alternative game plan would be to try to copy the aspects of companies that made them successful, as opposed to the aspects that are easy to copy, but that's very much harder to do.
I tried to get this working based on the other articles presented today on hn, but was unable to connect to a peer. Can anyone explain how to get this up and running?
You have to know the public key of the destination. Then it's supposed to route automatically.
Unless you know someone else using this, there's no one to talk to.
Try setting up two nodes, and get them talking to each other.
Someone could set up a directory server with a well known destination address, and then there would be a way to find destinations that will talk to you. Not finding anything like that yet.
This seems to be intended for private comms within a group, such as your militia or drug cartel. They went so far in the privacy direction that there's nobody to talk to.
Try Reddit's "r/reticulum". Maybe someone will offer to talk to you.
It’s hard to compare things that are so different like that, but I will try.
Scuttlebutt: Reticulum is a network stack for routing data in real time, not a decentralized social network.
Nostr: See Scuttlebutt
IPFS: Reticulum transfers data, it does not store it (though some protocols that work over Reticulum like LXMF optionally have functionality that allows for temporary message storage)
Yggdrasil is the closest analog to Reticulum you mentioned, but unfortunately from a cursory search I could not find any details about how it works. I can see that it currently works only over IPv6 (with IPv4 tunnels of some kind), unlike Reticulum which works over anything.