They know. They’re OK with it. In fact, many millions of Americans are OK with it.

This is going to turn out to be the lead of our time isn’t it?

Throuple of 7 years here. It absolutely can work, but please exercise extreme caution. It requires a level of discipline and security that just isn’t realistic for most people.

Many people will tell you it doesn’t work out, but the same can be said for relationships in general. There’s always risks. There’s no life worth living without risk. If you want to do this, you need to ask yourself some deep questions and answer honestly before you get hurt.

In the same way relationships aren’t just about sex, you need to know as sure as you can be if you can handle a relationship of three. It’s all the trouble of two and then a huge scoop more. It has got to be worth it, and a lot of it isn’t glamorous.

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

A surging deficit sounds like a double negative. It’s a little confusing what exactly they mean by the title.

No.

You do realize you’re in a Linux gaming community?

You can quickly and easily filter this community out from being shown to you.

Sure, for six months pay up front and a severance clause for your untrustworthy ass.

The word you’re looking for is corruption.

Not everything is Chrome just yet. We still have Gecko and Webkit holding on.

It was fun! It worked well when compared with IE back in the day which isn’t saying much, but it was a sensible bedfellow with iTunes and all the Apple mobile support software that was common to run alongside for your iPod. I enjoyed using it as my main browser because it was aesthetically pleasing.

Apple used rigged demos and made false claims about their own technology so outstanding that their own project managers were taken aback by how far behind the features actually were vs. what was pushed. There’s already informal documentaries on the massive internal disconnects within Apple that have lead to poor product testing and stagnation.

I did use Safari for Windows back in the day. It was a product they indeed shipped.

I appreciate the accurate headline.

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.

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.