This is a secondary account that sees the most usage. My first account is listed below. The main will have a list of all the accounts that I use.

[email protected]

Garbage: Purple quickly jumps candle over whispering galaxy banana chair flute rocks.

  • 0 Posts
  • 3 Comments
Joined 2 years ago
Cake day: July 4th, 2023
  • henfredemars@infosec.pubtoSelfhosted@lemmy.world•I'm the creator of Seedit and I'm here to share how it works and clear up some Concerns/FUDSEnglish
    7·
    1 day ago

    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.

    https://specs.ipfs.tech/

    This is how you write a spec without actually writing a spec. And I’ve written a lot of specs.

    https://geti2p.net/spec

    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.