asdfasdfasdf

Sure, I didn't say they use the system browser - I said the opposite. I'm saying the OS should be able to block non-HTTPS connections. If you have control of the OS you can control what protocols are used by apps, unless I'm missing something.

What cases are there for non-HTTPS? I can't think of any.

We need a switch like Firefox has that disallows anything non-HTTPS, but from the phone level. Companies like Apple and Google could also eventually warn apps that they're going to make it the default setting.

How is DPI a problem if it's encrypted? That would only work if the attacker had installed their CA cert on your client machine, right?

Is there anything it provided you so far that was better than the guidance from the Rust compiler errors themselves? Every error ends with "run this command for a tutorial on why this error happened and how to fix it" type of info. A lot of times the error will directly tell you how to fix it too.

I like Kagi a lot. It has a Small Web feature that is results from smaller sites like the good old days. Also has a Fediverse filter.

Big creators make a ton of money from their videos. I'm fine with the Fediverse adding ads, or creators doing sponsorships. We need a separation of concerns. Fediverse is removing centralized corporate control.

We need a way to get good content creators money on the Fediverse.

IMO a very small amount of storage should be free but after that the user needs to pay. It's the right thing to do for hosts and for the environment. If content creators need massive amounts of video then that will incentivize them to make money on it.

The only people left out are small, niche channels that have quality or important content but don't make much money. Maybe they could be cut special deals by the hosts / donors.

Switch to Kagi

Why? Not making the connection.

Even Torvalds said that a lot of critical parts of the kernel are completely undocumented and only one or two devs know how they work. IMO that's completely unacceptable, especially for such an important OS. They've proven they don't want to collaborate or communicate how they work to others.

Rust encodes a LOT of things into the type system, which makes it far, far easier to maintain since you don't need docs, and since the compiler enforces these things automatically. Memory safety is only one of them.

Starting something in a modern language instead of one with so little safety is a massively important feature.

The difference is similar to gas vs electric cars. They're both ultimately cars. Gas filled the niche that horses left. Electric cars have been taken seriously for far less time than gas, but their better technology has accelerated innovation. They almost never need to be taken to the mechanic, don't need oil changes, are way better for the environment, etc. and basically the only gap is getting batteries with larger capacity and more charging stations. We'll get there soon, and then gas cars will be fully obsolete.

In the end, someone who just sees them as one car vs another doesn't understand all the benefits of the implementation.

Where do they say anything like that? I've been following them very closely for years and they've always been super transparent that there isn't one solution. They also do a lot of work to prevent trash from getting to the ocean in the first place.