Again? But we spent all day yesterday doing the exact same thing.

I hope this gets its own Wikipedia article.

It’s always going to be a subjective process. The difference is I try to base it on effort and value for time. I’m not a computer but I can influence what I value. I can appreciate a good argument or an opinion I don’t like. I’m not perfect, but I think I can strive for that.

If that feels like the same thing as approval, then I perhaps a moment of self-reflection on whether things can have value that one dislikes is in order. I hope Lemmy won’t become more of an echo chamber than it already is.

Upvote: any insightful contribution even if I don’t agree with it.

Downvote: Remove this. Don’t show it to others. Was not worth my time to read this content because it contains false information, trolling, etc.

I’d like to encourage others not to use down votes for simple disagreement. Lemmy needs participation from thinking people.

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.

A classic Casio wristwatch.

Gentlemen, terrorist, or the best engineer you’ve ever met.

Why the fuck would I want a browser with AI?

We’re not really a first world country. I’m not sure that we ever were.

It’s truly amazing how stupid Americans can be. I was hoping better for my fellow citizens but I guess not.

I suspect for a lot of their members, the goal was achieved. The guns may have been secondary.

This looks fake. Real events provide event information before you provide your personal information.

For example, many attendees might want to look up requirements or details about the event. It’s also really suspect that you can only get one ticket per mobile number. What if you have a child who doesn’t have a phone number? What about accessibility? Just follow the instructions we text you?

I understand that being a bumbling idiot makes one their preferred candidate for leadership.

I have returned printers for requiring an internet connection out of spite.

If you’re willing to donate bandwidth, I suggest I2P or a public SyncThing node. My server chews through a terabyte of bandwidth helping people securely access their files. I also run Tor’s Snowflake proxy which helps users reach the network.

I2P is Java. SyncThing and Snowflake are written in Go which means you can’t pull off typical memory corruption attacks in these relatively safe languages, and it’s fairly easy to run them in a container.

With enough confidence, everyone will roll with it and nobody will notice! Right?

Just about half as twice as much.

Inaction figure.

Beautiful. Thank you for sharing.

They’re in the business of selling the illusion of security to university administrators.