Sandy is beautiful.

The start menu is a Web app as I understand.

Please don’t support the regime. Thanks.

Unironically, yes. That’s not nearly as common sense as you may think. There’s no such thing as idiot-proof steps. To some you may very well be a pro from that alone.

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.

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.

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

Pathetic. Take off your masks, pussies. I wanna see the faces of the people who kidnap my friends.

And here I am adopting abandoned ports on FreeBSD and packaging applications that I didn’t even write as a hobby.

Who cares. It’s effectively shut down, assholes. You know what you did.

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

Google’s decision to now discontinue the Pixel as an AOSP reference device is unfortunate, as it has pulled the rug from under developers like the teams at LineageOS and GrapheneOS who build Android for Pixel devices. These developers will still be able to build AOSP for Pixel devices, but it will now be more difficult and painful to do so than before, as they will need to build their own device trees from scratch. This also brings Pixels down to the same level as other Android devices[.]

Yep, looks like Pixel is just another Android to ROM developers. A sorry shame indeed. There goes another reason to bother with the Pixel. Just go buy Samsung if support was your reason. They bench better anyway.

I always remove the eggs in the Fibonacci sequence first until I run out of indices, and then I remove them in order by index.

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.