Oh hey look, that thing they warned us about would happen is happening and will continue to keep happening for the foreseeable future.
henfredemars
joined 2 years ago
The moment was yesterday. The second best moment is today.
At some point I wonder if the crazies will kill me to proudly proclaim that they were right about the vaccine all along.
Some voted to destroy the United States. Others were failed by the educational system and the media. Irrespective of cause, there's no going back. We're now in a place where "fuck you I've got mine" and "make me" is the basis of our formal society that only recognizes power in all its forms. I do not know what the future holds. I can only say that if this year were a taro card, it's Death, as what was changes into something new an unrecognizable.
Seconds before disaster!
Totally unexpected! Who'd a thunk it!
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.
I came here just to write this -- I thought we clearly chose to leave behind cybersecurity because education and science are bad.