Roll the credits boys 👏👏

when during job interview the recruiter ask if you code on the weekend

I think it’s more to see if you’re actually passionate about what you do and you don’t “just” do it for work, which definitely is a bit of a twisted view, when on average you’ll already be spending 40 hours a week doing that, but I think people tend to make this sort of evaluation, because people who love programming so much to also do it on their free time will usually be better, since they simply have more experience than those who only do what they’re assigned to do

I rudely agree with your opinion

Let the Zucc feel the heat

mullvad for looking shit up on ecommerce sites with new ID each time

Is it sufficient? I’d always assumed it was easily targetable with the IP so I started using TOR for that purpose

The tool presents a significant privacy risk, and shows that people may not be as anonymous in the YouTube comments sections as they may think.

I don’t understand how this makes the privacy on YouTube any worse when all the information it sources from is already public, this is just automated doxxing, which, while we’ll agree to be unethical, was never a privacy violation, it is just the consequence of the actions of who posted the information to begin with.
Also does it really violate YouTube’s privacy policy? It’s new to me that service consumers can be subject to the policy when it’s not the third parties that YouTube actively sends the information to, that sounds more to me like Terms of service, which are hardly enforceable fully (thank goodness, so we can have our yt-dlp and PipePipe)

That’s different, it’s technically possible not to comply with that statement because the location data is sent and stored, it takes just not deleting it to violate that, it just evaluates to a pinky promise that has to be verified by inspecting their systems.
This, on the other hand, is a technically verifiable claim, the code is open and it all runs locally on the same machine, the TEE will give the green light and that’s how apps will accept your biometric verification, the only thing that might be suspicious is with the implementation of the TEE, I don’t know if every manufacturer keeps the data it gets on the device or secretly communicates outside, this unknown is also a good reason to use a Google Pixel device if you care about that

Google Pixel phones use a TEE OS called Trusty which is open source, unlike many other phones.

From the Privacy Guides Mobile phones page

I’m all for not giving more data points where it’s not needed, but is this as bad it seems? All biometric data remains stored on the device, it isn’t sent to Google, or any app for that matter, that’s how the API works

Do you remember where you read that from? I thought having qi certified equipment sufficed

Guess I’ll try to see if anyone I know has it, otherwise I might buy another one and see

If we take only the battery pack into consideration, where it directly takes power from its own circuit and delivers it through the coil it has, I’ve tried with and without case on the phone and it didn’t look like it made any difference, always around that wattage, is it not strange that it wouldn’t even be able to reach half the maximum speed in pretty much optimal conditions?

Proton explicitly enabled keeping 2 free accounts on the mobile apps quite some time ago, probably more than a year, so they’re cool with you having 2 like that.

If you get more, you’ll be hampered at the application level, but, unless it’s like a load of accounts for spam purposes, having just a handful shouldn’t get you banned, I believe

Math is a human right

Oh I see, my bad, I just remembered wrongly from back when I used both repositories alongside each other

Interesting, I wonder if the 2 facts are somehow related, I don’t know what their stance was on the free software side of things, though I may have some emails saved from GitHub notifications that say something, I’ll look for those.

Edit: I don’t have any on the topic of F-droid inclusion, unfortunately, just one about language support

We are a small team and are not looking for people who can contribute to the project

This bogus argument is always big no no for me, clearly if they’d just been a small team they would not only accept, but enjoy whatever kind of contribution they can get from external people.
They just don’t want to deal with the community and do whatever they want, I’m guessing.

they don’t want our help, their loss

Spot on!

Glad to know I wasn’t alone on this, it is a shame really

Honestly if you don’t want to think too much about it, go with Briar, it’s way more battle tested, while Berty seems like it hasn’t seen much adoption since it’s younger, both have a bit of development activity I saw, so I can’t say if one is more or less maintained than the other

As for the actual question of gauging which has the better cryptographical implementation, I don’t know either, beside the most surface level information I know very little.
I believe if you want to look into it, you’ll have to start from their whitepapers

Besides the already mentioned Briar, there’s Berty, can’t speak to its quality since I never used it, but I always found the project neat in and of itself

Besides the files that are easy enough to move over, for app data there really is no other choice than to either haves ones that support their own export/import functionality or if you’re not lucky enough to have eliminated the apps that don’t have it and need their data you can only go back to papa Google and ask to politely get all your stuff for restoration on the new phone.
Takeaways:

1. If you care more about salvaging data than privacy, use a Google account on your phones, otherwise, if you still value privacy but not so much security, root a phone as soon as you get it (not always possible or desirable) so you can use other backup solutions that require root access.
2. Prefer installing apps that have an embedded backup functionality so you can be sure it’s always possible to get the data out regardless of what you did about point 1
3. (Bonus) Ask for said backup functionality to be added to apps you’d like to use with a feature request on the app’s repo when it’s open source, I’ve been doing that for the past year or so and I saw that quite a few have gone and implemented it, love these dudes :)
4. (super extra bonus) Fuck Google for artificially preventing a full backup solution that doesn’t rely on their cloud being involved

They should take you to dinner first