Did they work on developing new web standards to unlock that potential on the web?

Back then HTMLv5 wasn’t even a thing, there was no concept of video/microphone/gyroscope/gps access for webapps, notifications, web workers, web sockets, offline PWA webapps, etc. It was not a viable idea unless they actually were to invest big. They weren’t so committed. In Firefox OS even the dialer was a webapp, Mozilla brought forth a lot of innovative APIs to make it possible, many of which are in use today even after the OS was discontinued. And nowadays you even have things like Webassembly that allows you to code it in C or whatever low level language you want.

I feel Apple has always been more interested in their own ecosystem. Opening the web to have the same level of potential as the native apps from their walled garden goes against that strategy, so I don’t believe they were really serious about that approach, it’s always been more interesting for them to prioritize their native apps.

I wonder if resurrecting Firefox OS might still be an option. It was such an interesting idea having the webapps be first citizens.

There’s the KaiOS fork, but the direction is not really the same since it’s more targeted to low power keypad-based phones… and I believe they replaced much of the Gonk layer with a very stripped down low level Android base which isnt fully open source… maybe if they coordinated with the LibrePhone project and some hw manufacturers (like EU-based Nokia) we’d get a fully free stack.

Good marketing means achieving an arbitrary limit of what you consider “good” marketing. So it depends on where you set the bar.

The best marketing necessarily requires some level of unethical behavior, because being honest and saying the whole truth doesn’t sell. Everything has drawbacks and benefits… the better marketing minimizes (or even hides / fails to mention) the drawbacks and emphasizes the benefits, which is a form of deception.

I feel it’s a bit like the usability vs security dilemma… you can try to optimize to have both, but then you won’t have as a result neither the most secure system nor the smoothest user-friendly experience, but something in between (you might still consider that “secure” or “usable”, but that just depends on where you set your expectations).

If you want to maximize marketing then the result won’t be as ethical as it could be, and if you want to maximize ethics then the result won’t be as marketable as it could be.

I always saw I2P as a more modern and distributed onion-routing alternative to Tor.

The thing is that people are used to making use of Tor in different ways than the way they use I2P, but you can also have outproxies (ie. exit nodes/relays) in I2P the same way as in Tor… and you can also host a service inside the Tor network without relying on an exit node, like in I2P. It’s just that people only seem to want to host exit nodes for Tor and not so much for I2P, this led to internal communications in I2P being more common (which is a good thing), whereas in Tor it’s common to use it for anonymous access to the clearnet (which strains the network and causes chokepoints, specially with big downloads or torrent sharing). That’s just a matter of usage, not capability.

I think it makes sense to choose a phone that’s freer than most phones as a start, then fill up the gaps to make it fully free. As things are all phones have blobs (even non-Android ones).

I expect non-Android linux mobile OSes can also benefit from the reverse engineered firmware.

What should be the highest priority in terms of being able to use a fully FOSS phone? I feel we already have FOSS alternatives for most things that make the phone usable.

Perhaps free hardware might be top, but the S in FSF is Software and being able to avoid non-free software would be close 2nd, imho.

I expect it’s a combination of all the above in some sense. They state they want to build on LineageOS (an Android variant) and replace its binary blobs, I expect the result would be a new custom ROM targeting specific compatible hardware with the goal of ultimately supporting usable phones working on fully Free Software.

What it’s not is the creation of a libre hardware phone. I don’t think they are working on hardware, at least not anytime soon. Also if by “Linux phones” you mean non-Android based, that’s not necessarily a requirement (given that they mention LineageOS), but I expect regardless the kernel will be Linux without the blobs and it’s entirely possible that they add support for installing their firmware on those “Linux phones”.

I do kinda wish they’d focus on stuff that has a way bigger user impact 😅

The thing is that technically we already have fully usable FOSS software at that user level. Using for example LineageOS with F-droid as the only app store already gets you there. Whereas, ensuring your phone is not spying you or having some malicious functionality on the hardware/driver level is something that currently is simply not possible.

The FSF has always been doing the thankless job of championing for the things that are harder and less rewarding to do, but that will advance software freedom most for those who do seek it. Even when that thing is not necessarily the most popular/mainstream. I feel this has more of an impact in software freedom than, say, if they were to reinvent the wheel just to have their brand attached to it, and/or provide a slightly different UI to do the same thing other FOSS software already does.

The fingerprint (or you can also call it “security code”, it’s just a code for verification), is generated from the combination of the locally stored encryption keys from each side of the conversation, it will be different every time. I believe it’s also not technically required by the protocol that the same encryption key should be used for all conversations (although I don’t really know if the client does generate a new one every time or keeps reusing the same, that’s up to the implementation I believe).

When it comes to initializing the connection, It’s true that those identifiers (or perhaps more accurately, addresses) are susceptible to collisions in a “global space”. But they are temporary, ephemeral addresses (they are discarded after use and/or expiration), and the space is astronomical so chances of collision are tiny, and even in the rare event of a collision you still have a step in which you verify a fingerprint code that’s independent of the address, related to the individual local device… so you have a second factor authentication of sorts, if you are adding a person and the code does match then you can be pretty sure it’s the correct person, since both the shared address and the internal locally-stored key match.

I’m just explaining the reason why it’s more reddish (but not as red as others). It’s something most spreadsheet software (this was clearly MS Excel) can do automatically with numbers for visual indication so we can more easily see the distribution, it does not mean 8 years old is bad.

If there’s a big unbalance in color it would just make it more visible that there’s a big unbalance in ages. Probably if that had happened more colors could have been added to the gradient, maybe maroon->red->yellow->green->blue->white. But I think it was not seen as necessary in this case (or the author was lazy, since these are one of the defaults I believe).

I think it’s just a relative color scale from a spreadsheet… with the older being the greenest, the youngest the reddest, and the rest just fall in between. ProtonVPN just happens to be in between, it’s not as red as the others but also not as green as the ones that have been around for much longer.

Compression and efficiency is often a trade-off. H266 is also much slower than AV1, under same conditions. Hopefully there will come more AV1 hw encoders to speed things up… but at least the AV1 decoders are already relatively common.

Also, the gap between h265 and AV1 is higher than between AV1 and h266. So I’d argue it’s the other way around. AV1 is reported to be capable of ~30-50% bitrate savings over h.265 at the cost of speed. H266 differences with AV1 are minor, it’s reported to get a similar range, but more balanced towards the 50% side and at the cost of even lower speed. I’d say once AV1 encoding hardware is more common and the higher presets for AV1 become viable it’d be a good balance for most cases.

The thing is that h26x has a consortium of corporations behind with connections and an interest to ensure they can cash in on their investment, so they get a lot of traction to get hw out.