Check this repository at #codeberg , it will do the job for you.
Episode 57: F-Droid (featuring Sylvia van Os & Hans-Christoph Steiner!) https://fossandcrafts.org/episodes/057-f-droid.html
Let's be clear: $1.8b for "AI" translates to ~$1.8b handed to Big Tech companies to license infrastructure, data, and APIs.
AI is a corporate technology.
This is a subsidy to the richest companies in the world, justified via rewarmed cold war imaginaries.
Putin’s energy blackmail has failed.
One year after presenting #REPowerEU, we have reduced our dependency on Russian gas by three-quarters.
Everyone has played their part in building a more independent 🇪🇺 and we are more united and stronger than ever in preparing for next winter.
I'm often surprised to hear that many people believe that #OpenSource was this new radical idea in software development that came about in the 80s. That is actually backwards. Open Source was the default way software was developed before the 80s, and #proprietary development changed that. The #FreeSoftware movement was a direct response to software going #proprietary. It put #UserFreedom front and center as the reason why #software should be free and open.
Mullvad VPN and the Tor Project today present the release of the Mullvad Browser.
A privacy-focused web browser designed to be used with a trustworthy VPN instead of the Tor Network.
Read the full story and download the browser here.
Tik Tok ist zwar lustig, kann aber zum echten Sicherheitsrisiko werden, wenn man die User:innendaten aggregiert & analysiert. Thomas Lohninger war dazu in der ZIB 1:
Which means, you can only use that if your app's minSDK is >= Android 9. (At least that's what I remember from when this feature was originally introduced)
Wireguard's minSDK is Android 5.0.
F-Droid might start to look into this though, it's only a few years off until this can can be reaslistically used in the wild.
The Wireguard android app is now Reproducible and distributed with Jasons own signing key.
#WhatsApp implementing #KeyTransparency is pretty nice, and definitely an excellent step in the right direction against shadow accounts and the service provider trust problem. However, without the client being #OpenSource, it is not that meaningful. Yes, of course somebody could implement an independent monitor for the transparency log to check keys registered for an identity, but what percentage of the user base will actually do that when the only realistic way to use the service is to rely on the #proprietary client, which can still be used to maliciously target (groups of) users to break #E2EE?
Secure messenger clients should both use identity security protections like #KeyTransparency and have a *default* implementation that is #OpenSource and, ideally, be distributed with #BinaryTransparency and verified through #ReproducibleBuilds. Oh, and allow other identifiers than just phone numbers (still looking at you, @signalapp - which is otherwise ticking a lot of the right checkboxes).
Mastodon made a change to the version they provided to F-Droid (the GitHub version) that broke policy. F-Droid even went out of their way to tweak policy in Mastodon'a favour to not require complete removal of the in-app updater, just a good explanation.
Help needed: are there any graphic designers who could help create matching #FDroid category images for missing categories? My "quick hack" doesn't really fit: https://gitlab.com/fdroid/fdroiddata/-/merge_requests/13059
Thanks in advance!
PS: if the same could be done for the additional categories in the #IzzySoftRepo that would be great
@iThreepwood @fdroidorg this whole drama actually went down exactly because F-Droid distributed the developer signed version at the beginning, but for this to work, F-Droid needs a reference APK that complies with F-Droid policy, which then in turn became to much work for the Mastodon team to upload, so they asked to get switched to the F-Droid owned signing key.
In other words: F-Droid tries their best, but sometimes upstream developers won't/can't cooperate
This turning so much #FreeSoftware #Android work towards this huge focus on locking everything down and limiting things. #Android started out as a much more hackable mobile OS than any major one before it, and that's why it became so popular. Locked down devices have their use cases, like for journalists and whistleblowers. And computing devices should not be easy to abuse. Locking down devices is also useful for maintaining monopolies. All this is also limiting the promise of mobile computing.
I see a shift in how people think about #privacy in #software. Now that people are aware of how bad software can be for privacy, I see a lot of pressure to not include useful functions because they might appear to be invading privacy. #Android permissions are a good example: so many people are rightly concerned about location tracking, as represented by location permissions. The first question is ask when seeing a suspicious one is: do I trust that app's people and process to do the right thing?
🤔 What are your favorite #OpenSource / #FreeSoftware projects on the #Fediverse that we should collectively try to convince to move away from mastodon.social and toward other instances, so more people can easily see and interact with them?
📋 Give them an @-mention in this thread!