henfredemars @ henfredemars @infosec.pub

This is a secondary account that sees the most usage. My first account is l

---

Read more

Posts

46

Comments

3,854

Joined

2 yr. ago

I appreciate the accurate headline.

Concentrating them, so to speak?

Would!

They could, in fact, not make it any more obvious.

Well, if they couldn’t hear the warnings, maybe they need experience to be their teacher.

Nice! I recently tried KDE Plasma and I’ve been really impressed not just with the polish but with the look and feel that still kind of reminds me of Windows without being Windows.

A tale as old as time for a budding dictatorship.

I came here just to write this -- I thought we clearly chose to leave behind cybersecurity because education and science are bad.

Seconds before disaster!

Totally unexpected! Who'd a thunk it!

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.

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.

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.

Although I don’t know much about Sandy, it has been nice casually scrolling and seeing that she is doing well.

Why the fuck would I want a browser with AI?

Some of those screams are in the form of new purchases!

This is exactly what some of my extended family uses because there’s literally no other option. Not even cellular.

This isn’t even up in the mountains or something. This is just rural Alabama where kids are struggling to do homework because they just don’t have access, and it all but guarantees that their technology skills will remain woefully outdated.

I remember when they had DSL not that long ago and I would turn off updates on everything because it was a complete waste of time to attempt.