How much you pay the cell phone over there mr marx lol. Or did you barter it up. What a joke. You are a little capitalist too

literally https://thenib.com/mister-gotcha/

How much you pay the cell phone over there mr marx lol. Or did you barter it up. What a joke. You are a little capitalist too

twitter (via cloudflare) is serving HTTP 403 {"error_code":2,"error_response":"Dmcaed"}

thanks, i edited the post to link that instead

I didn’t say that they should be thrown away?

Sorry that I interpreted your comment as suggesting that anything less than a Pixel is not worth trying to improve the security of.

What’s with the hostility?

No hostility intended. But I still don’t understand why you think that omitting Graphene’s Pixel-requiring hardening features would cause Graphite to be less secure than other Android distributions which also lack those features.

Are there any other options with a feature set comparable to GrapheneOS(-minus-pixel-only-hardening-features) ?

Should the world just throw away the billions of non-Pixel devices in use today?

And/or should everyone just give up on improving security at all for the vast majority of phone users who cannot afford Pixels, since they can’t ever be as secure as a Pixel?

see my other comment in this thread

those benefits rely on the Pixel’s hardware

Doesn’t GrapheneOS have a lot of benefits besides the 3 pixel-requiring hardening features which are removed in Graphite (and the 3 others which are disabled by default but can be re-enabled on some devices)?

I’m not disputing that those hardening features are worthwhile! Pixels with Graphene are obviously much more difficult to exploit than phones without those features.

But there are billions of non-Pixel phones in the world which aren’t about to be thrown away, and the vast majority of phone users absolutely cannot afford a Pixel. GraphiteOS (if it actually works?) seems to me like it is probably a major improvement over the other options available for them.

At that point I’d just use something like Lineage

My impression is that Graphene-without-the-features-requiring-Pixel-hardware would still be a much more secure operating system than Lineage (or the other options available).

Reading that FAQ I get the impression that it should/could run on a very large number of devices, but maybe there is some caveat I’m missing? 🤔

so that many non-pixel devices can have an OS with most of the benefits of GrapheneOS?

unfortunately, like its predecessor (Nokia’s Maemo/Meego), Jolla’s SailfishOS has never been (and has never had plans to be) fully free/libre open source software.

many components of it are freely licensed, but not nearly enough to constitute an actual mobile operating system you can use.

what happened next? (do the terms actually allow you to cancel it immediately for no cost, or is their $10-per-month-for-nothing offer an alternative to paying a cancellation fee?)

Activity lights are useful

in even more ways than one might think.

(see also this and this later work from the same author…)

based on the other comments here i had to double check if this thread was in !shittyasklemmy@lemmy.ml smh my head

some of them are built so that the front doesn’t fall off at all

You’re correct on both points (🤦‍♂️ indeed).

I’ve now edited this post to link to their advisory text file instead of their advertising-heavy blog post about it which I had initially linked when the above comment was posted. Thanks.

Sparkles? (bookmark groups?)

Nice, thanks.

It would certainly be nice to be able to pre-download language pair models without selecting to and from and then actually initiating a translation using the model i don’t have yet.

re: getting uBlock externally, i also see the attraction of that approach but unfortunately Debian’s package was last updated in October (from 1.62 to 1.67) while AMO has a release from January (1.69) :/

imo it would be better to bundle UBO and ship its updates along with browser updates.

are there plans to distribute Konform via flathub?