

Hear hear. Knowledge should be communicated in an easily shareable way that can also be archived as easily, in contrast to a video requiring hundreds of MB:s.


Hear hear. Knowledge should be communicated in an easily shareable way that can also be archived as easily, in contrast to a video requiring hundreds of MB:s.
The fact that they do not store any customer data was put to the test in 2023, when the Swedish police raided their offices and left with nothing.
They also spend a lot of time and resources into researching and advancing technology around measured boot and running as much as possible in memory, without having to use disk storage.
Absolutely love it, in all forms. Yerba mate to start my morning and Club-Mate to extend the night!
Aperture Science - We do what we must, because we can.
@fossilesque@mander.xyz Please do.
I kinda imagined the person seemingly sitting down as being mid-fall, thrusted backwards by the blast. Somehow captured with arms and legs in perfect right angles at the time of being pictured, by accident


I really like the idea of relevant + flag as additional (more weighted) attributes compared to just agree/disagree, as you might disagree with a poster but still want to mark the comment as valuable for the discussion (which can’t be done on Reddit since you’ll downvote them to the gutters).
I’m hoping it won’t result in too much micromanagement of different attributes for each post, but am curious to see how it turns out.


In fact, trust isn’t manually handled, it’s handled based on how similarly you act vs others (i.e. you both upvote/downvote similarly, flag posts similarly, etc), and I’m deciding whether making this based on community makes sense (i.e. you trust user A on community X, but not on community Y).
Wouldn’t this just create an impenetrable filter bubble/echo chamber where you see nothing else than content you 100% agree with?
But shouldn’t it be 8 < 1
That would be a pair of scissors, on its way to cut the number 1.
GP probably asked whether Mull was shortname for the Mullvad browser.
I think we should call “football” exactly what it is. Unassociated soccer.
A tip is to host your own domain at an e-mail provider that allow you to receive e-mail for any recipient in a single mailbox (i.e. catch-all or wildcard), and use the following alias format when signing up at different websites or services:
<website>@<yourdomain.tld>
This allows you to filter incoming e-mail by which website/service you signed up for, regardless of what domain they send e-mail from (it can be different for account notifications vs newsletters etc.).
It will also help you detect if they have sold your contact details or had a data breach without announcing it publicly, since you wouldn’t use that specific e-mail alias elsewhere.


Good point! The details for each app are crowdsourced and can be submitted via the instructions here. However, the default templates does not include any mention of root status.
The maintainer of the site can be reached via any medium listed here if anyone would like to suggest updating the templates to include root status.


Thank you! Updated the post with a link to this resource.
DivestOS sounds interesting but I am wary of any “mission-critical” software project (such as the firmware for my primary phone) that relies on a single person, for multiple reasons. Burnout and potential for social engineering by malicious actors being two of them.
GP:s comment made me curious as well. Usually, if multiple hardware vendors are supported there are separate branches with different maintainers. It doesn’t necessarily mean that the main codebase is bloated as a result.
For those that are looking to install GrapheneOS and want to ensure that their banking apps work as intended, here is a curated list of supported apps per country:
https://privsec.dev/posts/android/banking-applications-compatibility-with-grapheneos/
Rest assured, he won’t get fooled again
I believe it’s usually that they attempt to use some of the parts in the Google Play framework that is (currently) not fully supported by the Google compability layer in GrapheneOS, but the developers does an amazing job on trying to keep up with stock AOSP changes and make apps work equally good as on a stock Google image.
That, and sometimes just checking whether the phone is running an image signed by Google and refuses to run if not.
Personally, I’ve only had issues with one app, and that’s Pushover (a push notification service). It tries to use Google Play for notifications and I refuse to install that for this single app.