#android

379 posts
flo
@fasnix

Anscheinend ist http://keepandroidopen.org nicht mal im IT-Umfeld besonders bekannt 🤔

#KeepAndroidOpen #Google #Android

flo
@fasnix

Oh, Privamatic sieht mir nach einer sehr interessanten App aus, gerade für diejenigen von euch, die zB viele Apps installiert haben und prüfen wollen, wie es eigentlich um ihre Privatsphäre bestellt ist (über F-Droid).

"Privamatic
Your phone's privacy, scored 0–100. 50 checks, no internet permission.
Neu in Version 1.5.2

  • Privamatic no longer copies any of its data into backups or to a new phone. On a new phone, set up your trusted apps and settings again.
  • Widget: easier to read on any wallpaper. The background is now at least 76 % opaque, or you can switch it off completely.
  • Widget: the score is coloured by its rating, and a change shows as ↓6 in red or ↑6 in green in the middle of the widget.
  • Widget: the score and its change no longer overlap with large text.
    Privamatic audits your Android device and gives you a clear 0–100 privacy score based on your actual settings — not guesswork.

Whether you're just starting to take privacy seriously or you're already running GrapheneOS, Privamatic shows you exactly what's exposing your data and how to fix it, step by step.
(...)
Privacy is built in:

  • Fully offline — no network requests, ever. Privamatic never requests the INTERNET permission, so Android will not let it connect even if it tried; check F-Droid's permission list or the open source code yourself.
  • No accounts, no cloud sync, no analytics
  • All data stays on your device, and none of it goes into backups or transfers to a new phone
  • Open source (GPLv3)

Works on any Android 8.0+ device. Made with GrapheneOS in mind, and just as useful on CalyxOS, LineageOS or stock Android."

https://f-droid.org/packages/com.techtrest.privamatic/

#Privamatic #Android #Privacy #AntiTracking

Dendrobatus Azureus
@dendrobatus_azureus

Software updates

Update your software on all your platforms regularly

This is the golden rule.

  • We often do it in a work environment and get paid for that
  • We do it for ourselves because it is good for our devices.
  • We are careful doing it on our devices which can be bricked remotely by the factory (TV's treadmills trainers)
  • We install piehole and other ad blackholes to protect our devices from pesky ads
  • There are so many repositories to follow
  • Auto updates are stupid, IMHO, even for workstations
  • On servers with PHP, we need manual granular tested updates, if we used PHP (old version) because we are slow to implement PHP (new major version)

Manual updates can be a pain

What can happen?

We forget one or two full manual updates

I've just had to do this

$ sudo ./Ventoy2Disk.sh -g -u /dev/sdx


  Ventoy: 1.1.17  x86_64
  longpanda admin@ventoy.net
  https://www.ventoy.net

Upgrade operation is safe, all the data in the 1st partition (iso files and other) will be unchanged!

Update Ventoy 1.1.12 ===> 1.1.17 Continue? (y/n) y
esp partition processing ...
update esp partition attribute

Update Ventoy on /dev/sdc successfully finished.

Did I forget something else?

Probably. Is it critical?

Lets see

$ ~/bin/yt-dlp -U Current version: stable@2026.07.04 from yt-dlp/yt-dlp Latest version: stable@2026.08.19 from yt-dlp/yt-dlp Current Build Hash: 495be29ff4d9d4e9be7eabdfef225221e5d5282e77f2f505abc6dca80349f3fd Updating to stable@2026.08.19 from yt-dlp/yt-dlp ... Updated yt-dlp to stable@2026.08.19 from yt-dlp/yt-dlp

It was not critical, but important none the less

Happy updating!

Sources

https://github.com/yt-dlp/yt-dlp/blob/master/README.md#installation

https://ventoy.net

#programming #infosec #updates #Linux #Android #repositories #BSD

Load older posts