Totally unexpected! Who'd a thunk it!
henfredemars
joined 2 years ago
People's minds are growing numb to the madness. This is very similar to what happened in Soviet Russia in the five years leading up to the collapse of the government.
Then use decentralized links or hashes, which is what IPFS uses to identify content. A character limit doesn't solve this problem fundamentally. Indeed, it's been a tough problem to solve for decentralized services.
I'm concerned about the large amount of low quality, vaporware/crypto applications built on IPFS which is the same core technology used here. It's concerning how many clicks it takes to get technical specs for the underlying work, like libp2p for the network layer, which itself espouses only vague ideas on its main website that seems to focus a lot more on presentation than technical merit. Even the GitHub admits that the spec that most of these apps are relying upon is, well, unspecified.
Your project source downloads and runs an executable. That's a little bit SUS; it would be much better if you compiled/built this core code as part of your build process, else, it's not much in the way of source code, no? But, it works. It seems to delegate just fine, and few understand how to actually talk IPFS directly. But, this is the most important part!
I think the biggest tell that IPFS borders on vaporware is that there's very little discussion about concrete specifications and the main problem faced by all DHTs: how you get your data to actually stay hosted on the network over time. These ideas are not new, and you may be better served building your app on technology that has spent vastly more time understanding the fundamental problems.
This is how you write a spec without actually writing a spec. And I've written a lot of specs.
This is how you write a spec. Excruciating detail of what actually gets sent over the wire at different levels of the design starting from the very bottom.
Anyway, just my 2c. It's cool you've got functionality at this level and that's commendable, but I feel it's built on shoddy foundation of an immature technology. At least it should be easy to migrate to something else in the future as the distributed technology is offload to a separate binary anyway.
Note: Various edits for clarification and to ensure I focus on the code and not the human.
I saw this post on Reddit but it was taken down.
Excellent source of plant-based protein and fiber.
Me maintaining packages that depend on Java and discovering all the bizarre ways that you can install different versions of Java and have environment variables misconfigured or missing.
A classic Casio wristwatch.
Gentlemen, terrorist, or the best engineer you’ve ever met.
Not necessarily. You might be confusing it with a Tor exit node.
The Snowflake project provides people who live under an oppressive regime the ability to connect to the Tor network. You can’t observe their traffic and you are not an exit to the open Internet. Generally, you shouldn’t be able to connect the activities of any user with traffic on an exit relay.
Tor Snowflake proxy. Learn FreeBSD/pf which works great with those specifications. Try to overclock it and see how much you can get away with before failure. SSH honeypot. Low-spec server for a simple site. If you have bandwidth, you could contribute some to SyncThing by hosting a public relay.
Although I don’t know much about Sandy, it has been nice casually scrolling and seeing that she is doing well.
Seconds before disaster!