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.

We don’t have windows, so we had to make do with this interdimensional portal.

Good point. Maybe it depends on what I want to happen when that load spike comes.

I was promised 15 years ago that cloud computing would avoid unexpected bills and provide consistent expenses that project managers love so much.

Surely. We’re doing a lot to discourage innovation, education, and the development of technical skills.

Not knowing yourself; it’s a lot like dating in that there’s big dreams and ideas but the reality of what is needed on the daily often doesn’t mesh. I find it helps to talk to other employees and ask about their job and roles to get an envelope of what the company actually needs vs. what they say they need.

Can’t really so that with dating though!

Even the cheapest most under-powered home router these days uses a multicore processor from the last decade. Uniprocessor definitely seems like the special case.

The title for this article could be much better. It should mention that SMP support code is soon becoming a mandatory kernel feature and will be included even for kernels running on truly uniprocessor systems. Kernel developers feel it’s just not worth maintaining special cases for uniprocessors.

I don’t want to fight my software being actively designed to do what some third party wants it to do. I rather it break for technical reasons rather than political ones.

I have such a shitty BIOS. It is pain, because the option ought to be there, but the software is so incredibly basic that it exposes virtually no useful settings outside of time and date + boot order.

Interesting, but I wonder who’s using F2FS. I believe some Android vendors tried it and reverted due to long term performance concerns. Much like with BTRFS, it’s going to be difficult to shake those earlier impressions.

A necessary evil for some of us. Flatpak at least tries to contain their access to the rest of the system.

The information will be evenly distributed upon its surface and some believe one day it will be be radiated back out into the rest of the system.

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.

I don’t feel like it makes a huge difference for me and I run quite a few servers. It’s mainly the cooling costs in the summer months that run up the bill.

BOINC is great. In its day, you could get an enormous amount of computing power on a shoestring budget thanks to volunteers. It also helped the volunteers feel like they were more a part of something, because they were! I used to have a small server farm crunching numbers for science.

Unfortunately, the landscape has changed. Some projects are still around, but many of the big players have left. Computing power is a lot more accessible now, and the main limitation is time spent analyzing the data rather than the computation itself. Cloud computing can make just about any computation happen fast for a reasonable price without having to own all of that hardware. GPUs have exploded in computation capacity. Just, a lot of factors came together where the need isn’t as great.

With that said, I still run it on one mini PC, but the payoff for having to write your application in a distributed fashion doesn’t have the return on investment that it used to.

Hey! My assembler is actually quite neat and compartmentalized.

A decentralized social media has 2 problems: How to store the entire world’s data on a blockchain

Stopped reading right there. I can’t take this project seriously. Even the description uses weasel words that focus more on broad concepts rather than technical clarity. I struggle to find a new idea being presented here that actually provides concrete and material benefits over other ways to put power in the hands of users.

To me this looks exactly like an academic project that was done in school and quickly forgotten. It’s great for writing papers, however.

Oh my God I didn’t see what community this was. If this was supposed to be a joke, it was quite the long one. But yeah it’s a joke project it looks like. That’s a fair comparison.

I’ll walk before I ride in a Nazi truck.

Honestly not nearly as painful reading those results as I expected it to be!