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.
Garbage: Purple quickly jumps candle over whispering galaxy banana chair flute rocks.
I never understand this mindset because a person who is technically skilled like this is exactly the kind of person who wouldn’t struggle with Linux.
They’re already the kind of person who would be an excellent Linux user. I can only imagine that, for whatever reason, they’ve grown emotionally attached and are simply too stubborn to consider anything else.
Until the next re-bloating update where your settings get reverted and services re-installed.
Being good at de-bloating (as you may very well be to do that in a few minutes!) is an anti-skill that shouldn’t have to exist.
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.
And here I am adopting abandoned ports on FreeBSD and packaging applications that I didn’t even write as a hobby.
Discord has become really annoying to use with all the ads. I confine it to my browser because I don’t trust it.
With that said, I used to run Flatpak version and it never had this issue.
There would be people on Lemmy still using a 386. Of course.
Definitely needs to be posted more frequently. Especially if you can connect this to public transportation. I love public transportation.
Sort of. There’s realtime builds, but the Linux definition of real time is more relaxed than dedicated RTOS’s in exchange for a much more feature-filled OS. You should not use Linux if people could die when you miss a deadline. You want a simple system where it’s easier to prove that can never happen.
Pretty much the only place it doesn’t run is where you have hard real-time requirements and on extremely small embedded micro controllers.
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.
I just installed a new Linux system on my laptop and I feel called out.
And don’t forget to actually test your backups once in a while. It doesn’t count if you can’t use it.
Same I just throw it in a desk at work. It’s encrypted anyway.
Things are getting so bad I fear for being labeled a troublemaker and sent to the gulag over declining.
It can always be a weird self-extracting shell script.
I find you still have to fuss with partitions. There isn’t a simple wipe everything and install option. You have to manually select the partitions on the disk, delete them and create a new one which somehow triggers it to create several partitions.
There is an upgrade option.
And then they tell you they don’t want a Microsoft account and you have to look up what’s the current hack to get around that if possible.
That said, I think the Linux install experience is very clear about what it’s going to do.
Unironically, yes. That’s not nearly as common sense as you may think. There’s no such thing as idiotic-proof steps. To some to may very well be a pro from that alone.