Posts by me@chrichri.ween.de
(DIR) Post #AVoWQ8ZBkkznHFOLzM by me@chrichri.ween.de
2023-05-19T13:14:59Z
0 likes, 1 repeats
For my microblog and some other tabs I use to keep open I'm trying out Tangram - the "Browser for your pinned tabs".I tried before and failed miserably, because #Tangram didn't work on my #Librem5 (#PureOS), but worked on my notebook running the same system.This time I tried harder.FailingAfter installing the tangram #flatpak from #flathub and starting it on my #Librem5 I found a welcome screen asking me for the URL of my firsted pinned tab.I entered the URL of my blog. The next page showed me an empty address field, a go button and that's it. See the screenshots appended...DebuggingDebugging on the phones screen is a slow process if one is used to a keyboard, mouse and bigger screen. Since Tangram works on my notebook I used waypipe to log into my Librem5 via ssh using waypipe -n ssh -R /tmp/socket-way:/tmp/socket-l5 l5h. This way I can use the ssh session to debug and get Tangrams window on my desktop - so I thought…Starting Tangram from cli I got these messages:purism@pureos:~$ flatpak run re.sonny.Tangram Gjs-Message: 07:45:13.738: JS LOG: env: flatpakGjs-Message: 07:45:13.738: JS LOG: data_dir: /home/purism/.var/app/re.sonny.Tangram/data/TangramGjs-Message: 07:45:13.738: JS LOG: cache_dir: /home/purism/.var/app/re.sonny.Tangram/cache/TangramGjs-Message: 07:45:13.738: JS LOG: config_dir: /home/purism/.var/app/re.sonny.Tangram/config/TangramGjs-Message: 07:45:13.738: JS LOG: applications_dir: /home/purism/.local/share/applicationsGjs-Message: 07:45:13.738: JS LOG: keyfile_settings_path: (re.sonny.Tangram:2): Gtk-WARNING **: 07:45:13.972: Locale not supported by C library.Using the fallback 'C' locale.flatpak-spawn: Invalid byte sequence in conversion inputTry "flatpak-spawn --help" for more information.The last part about Invalid byte sequence appeared when I tried to enter an URL. Looking for information about the messages I stumbled over this flatpak issue describing a problem with flatpaks dependencies when the locales of the system are set to different values for e.g. LANG and LC_NUMERIC like on my #Librem5.When doing debugging, sharing error messages or screenshots with others I mostly need english language, but I wanted my local notations for date, numbers and time. So I'm using:purism@pureos:~$ localectl System Locale: LANG=en_US.UTF-8 LC_NUMERIC=de_DE.UTF-8 LC_TIME=de_DE.UTF-8 LC_MONETARY=de_DE.UTF-8 LC_PAPER=de_DE.UTF-8 LC_MEASUREMENT=de_DE.UTF-8 VC Keymap: de X11 Layout: de,us X11 Variant: ,As I understood this triggers the issue. To check whether this applies to my flatpak environment and the Tangram flatpak and its dependencies I did the following:purism@pureos:~$ flatpak run --command=sh re.sonny.Tangram [📦 re.sonny.Tangram ~]$ localelocale: Cannot set LC_ALL to default locale: No such file or directoryLANG=en_US.UTF-8LC_CTYPE="en_US.UTF-8"LC_NUMERIC=de_DE.UTF-8LC_TIME=de_DE.UTF-8LC_COLLATE="en_US.UTF-8"LC_MONETARY=de_DE.UTF-8LC_MESSAGES="en_US.UTF-8"LC_PAPER=de_DE.UTF-8LC_NAME=de_DE.UTF-8LC_ADDRESS=de_DE.UTF-8LC_TELEPHONE=de_DE.UTF-8LC_MEASUREMENT=de_DE.UTF-8LC_IDENTIFICATION=de_DE.UTF-8LC_ALL=[📦 re.sonny.Tangram ~]$ There again is an error saying that the locale cannot be found. Following the description in the flatpak issue I looked at the configpurism@pureos:~$ flatpak --user configlanguages: *unset* (default: en)extra-languages: *unset*and only found a default for en. I added the languages I generally want to use and might have set via environment and checked whether the setting had been saved:purism@pureos:~$ flatpak --user config --set languages 'en;es;de'purism@pureos:~$ flatpak --user configlanguages: en;es;de (default: en)extra-languages: *unset*This didn't change anything, yet and I ran an update that downloaded further components for my Locale packages:purism@pureos:~$ flatpak updateLooking for updates… ID Branch Op Remote Download 1. [✓] org.gnome.Platform.Locale 44 u flathub 241,8 kB / 340,5 MB 2. [✓] re.sonny.Tangram.Locale stable u flathub 8,4 kB / 66,1 kBUpdates complete.Repeating the check from above I found the error about the missing file or directory gone:purism@pureos:~$ flatpak run --command=sh re.sonny.Tangram [📦 re.sonny.Tangram ~]$ localeLANG=en_US.UTF-8LC_CTYPE="en_US.UTF-8"LC_NUMERIC=de_DE.UTF-8LC_TIME=de_DE.UTF-8LC_COLLATE="en_US.UTF-8"LC_MONETARY=de_DE.UTF-8LC_MESSAGES="en_US.UTF-8"LC_PAPER=de_DE.UTF-8LC_NAME=de_DE.UTF-8LC_ADDRESS=de_DE.UTF-8LC_TELEPHONE=de_DE.UTF-8LC_MEASUREMENT=de_DE.UTF-8LC_IDENTIFICATION=de_DE.UTF-8LC_ALL=[📦 re.sonny.Tangram ~]$ Running Tangram again didn't show the error message anymore…purism@pureos:~$ flatpak run re.sonny.Tangram Gjs-Message: 08:32:33.264: JS LOG: env: flatpakGjs-Message: 08:32:33.265: JS LOG: data_dir: /home/purism/.var/app/re.sonny.Tangram/data/TangramGjs-Message: 08:32:33.265: JS LOG: cache_dir: /home/purism/.var/app/re.sonny.Tangram/cache/TangramGjs-Message: 08:32:33.265: JS LOG: config_dir: /home/purism/.var/app/re.sonny.Tangram/config/TangramGjs-Message: 08:32:33.265: JS LOG: applications_dir: /home/purism/.local/share/applicationsGjs-Message: 08:32:33.265: JS LOG: keyfile_settings_path: but when I entered the URL I got these messages in exchange:(process:2): Gdk-WARNING **: 08:32:37.280: No such backend: *(process:2): Gtk-WARNING **: 08:32:37.281: Failed to open displayPoking a bit more around gave me the strong feeling that this might be an issue that Tangram or parts of it (webkitgtk?) do not find my display forwared through waypipe, so I tried on my Librem5s display and found Tangram working as expected.What nextIn Phoshs application menu Tangram does not show as mobile friendly which it should. I proposed a change of the desktop file to include the setting X-Purism-FormFactor=Workstation;Mobile;.If you do not want to wait for this to happen you can copy .local/share/flatpak/exports/share/applications/re.sonny.Tangram.desktop to .local/share/applications/ in your home directory and then edit .local/share/applications/re.sonny.Tangram.desktop to include that setting.I couldn't resolve the issue about running Tangram over waypipe, so I opened an issue. I guess it's not important that this works, but the root reason for the problem might surface in a different situation as well, so maybe the developer will help me to look into it further.One thing that I miss in Tangram is an integration for an external password store. I already asked for it and made some suggestions how it could be done.If you like the project you can support the developer @sonny@floss.social through kofi, too.
(DIR) Post #AW2UbwFFe6CplmKfCq by me@chrichri.ween.de
2023-05-26T07:01:41Z
0 likes, 0 repeats
@craftyguy@freeradical.zoneWhen I came across the topic I found that loop-devices seem not to be supported in namespaces. Access to something like losetup is always system-wide as I remember.There are other ways I could think of:the smallest possible vm running its own kernel to provide the tombs filesystem. Sounds like alpine to me :). (have to add this idea to the tomb issue...)kernel development: make loop devices usable in namespacesmake sudo more comfortable
(DIR) Post #AWPluryDSPzyl0y09I by me@chrichri.ween.de
2023-06-06T10:37:57Z
0 likes, 2 repeats
This is really a helpful life hack I read about somewhere: for temporary connections use nylon string to hold the pins to the holes in the pcb...
(DIR) Post #AWPlwN952AwpjdlUUi by me@chrichri.ween.de
2023-06-06T10:40:23Z
0 likes, 1 repeats
BTW:#ShotOnLibrem5, cut to size using #ImageRoll on my #Librem5 and send usign #microblog opened in #tangram.
(DIR) Post #AXgWlbkmWkv3L4Lb96 by me@chrichri.ween.de
2023-07-14T12:26:25Z
0 likes, 1 repeats
Letztes Jahr habe ich es nicht geschafft, aber dieses Jahr ist es fertig geworden: Unser #Gründach.Inzwischen ist schon etwas Sedum über die Angelegenheit gewachsen.#ShotOnLibrem5, bearbeitet mit #ImagePipe veröffentlicht in #microblogpub in #tangram
(DIR) Post #AXxGBPrHueIqXe3zaC by me@chrichri.ween.de
2023-07-22T14:11:04Z
0 likes, 0 repeats
@craftyguy@freeradical.zone I tried to find a sports watch with no need for online connection. Guess what...
(DIR) Post #AYYFN2LoXz0fD14thg by me@chrichri.ween.de
2023-08-09T10:25:23Z
0 likes, 1 repeats
Serial connection via breakout board to my #Librem5 using a μArt serial-usb adapter.While waiting for some press-fit headers I'm using poor mans press fit connection with nylon string.#ShotOnLibrem5
(DIR) Post #Aa4RptRw9QBI2koVYu by me@chrichri.ween.de
2023-09-23T21:08:02Z
0 likes, 1 repeats
The #yunohost running this #microblogpub instance runs on a #RockPro64 in a #Pine64 nas case.I started a year ago by installing it on an eMMC as a yunohost test, added two sata SSDs and now decided to simplify the setup by removing the eMMC boot medium.Booting of the #SoftwareRaid configured on the SATA SSDs turned out to be less easy then I'd expected and I ended up preparing a #howto about doing this remote via ssh.https://git.sr.ht/~chrichri/RockPro64_u-boot_SATA_software_RAID_howto
(DIR) Post #Aa5R2goEYMUboBjyS0 by me@chrichri.ween.de
2023-09-24T08:30:28Z
0 likes, 1 repeats
Bye, bye eMMC of my #yunohost. After letting it run a night I removed the eMMC and still found it working.I will keep the image some time - just in case…
(DIR) Post #AacjaxrwCVmAJmldqa by me@chrichri.ween.de
2023-10-10T09:05:09Z
0 likes, 2 repeats
The #GPG key I use to decrypt my harddrive and passwords and to validate my boot configuration is stored inside a #LibremKey. On a monday I had problems using the key. Since the GPG key had been generated in 2019. I decided it would be time to create a new one.created a new gpg key on an airgapped system (Raspberry Pi 2 without wifi)made a backup of that keycopied the key into a new #OpenPGPcardmade the new OpenPGPcard usable in a #ReinerSCT komfort terminalreencrypted my #pass stores content to be able to use both keysthis didn't work, because of lack of space inside the #tombextending the tomb failed, because there's still a problem with btrfs on tombsmade a new tomb and copied manually all the content overreplaced my pass-tomb with the bigger new onefinally reencrypted my passwordsreencrypted the secret to unlock my harddriveput the new public key and the re-encrypted luks secret into initramfsreplaced the OpenGPGcard inside the #LibremKey by the new one containing my new gpg keysrebooted and found #heads would only drop me to a rescue shell (instead of allowing an unsafe boot)started the system by calling #kexecdisk decryption using the new gpg key worked fineafter another reboot pressed some key to get into the #PureBoot/heads menuimported the new public gpg key into heads and wrote it to the bios areasigned my boot filesrebooted and got stopped by PureBoot, because the #bios had changedcreated a new totp secret for the bios check and wrote it to the LibremKeyused the camera on my #Librem5 to get the #totp secret into #Authenticator (in case I do not have the LibremKey around I still can check the validity of my Bios using my Phone)A reboot showed that everything works like with the former gpg key.re-encrypted my pass entries to only let the new gpg key decrypt my passwordsre-encrypted the pass-tomb to only be decryptable using the new gpg keydeleted the git information stored for the password-storeinitialized a new git repository and connected it to a newly created remote repositorypushed the contentdeleted the remote git repository containing the passwords encrypted with my old gpg keyBesides some small annoyances the process worked very well.
(DIR) Post #AbRBSRqWASNp5x4Hpo by me@chrichri.ween.de
2023-11-03T18:15:51Z
0 likes, 0 repeats
@craftyguy@freeradical.zone#cat ate #dog tail?
(DIR) Post #AbSsPR4V55Of0lNVfU by me@chrichri.ween.de
2023-11-04T13:50:12Z
0 likes, 1 repeats
Looking for an alternative to my #LibremKey usb-a I've been watching the development of #Nitrokey 3 usb-c a while.Finally I got one.a lot cooler than expectedPlaying around with the new #nitrokey 3 I found that it offers a great new feature: you have to touch the key when trying to get an otp or trying to use the gpg keys stored on it.Even if your computer might get compromised and the key is connected to it you'll not only be aware of activity (blinking led like on my former nitrokey pro), but you'll also have to touch the casing over the blue blinking led when the feature is enabled.Using firmware v1.5.0 and an actual #PureBoot it also works as a replacement for the #LibremKey to check my bios for tampering and blinking the led green if everything is o.k.new command line tool nitropyOn my notebook I run #PureOS Crimson which is based on Debian #Bookworm. I ran into two issues trying to use the new Nitrokey 3.To use the key there's a new command line tool called nitropy. Generally I like the idea of using a command line tool. The new gui Nitrokey App 2 which is based on the command line tool still doesn't support all of its options.The installation of #nitropy Gon Debian Bookworm worked flawless, but the tool showed an error when called to list all available nitrokeys.nitropy patch for bookworms openssl versionAs described in this issue one of the libs used in the new tool doesn't accept the version of openssl in bookworm. The solution is quite simple:After installing via pipx like described in the nitropy manual edit .local/pipx/venvs/pynitrokey/lib/python3.11/site-packages/oscrypto/_openssl/_libcrypto_cffi.py and find the line…version_match = re.search('\\b(\\d\\.\\d\\.\\d[a-z]*)\\b', version_string)…and change it to the following:version_match = re.search('\\b(\\d+\\.\\d+\\.\\d+[a-z]*)\\b', version_string)Now your nitropy should work even if your OpenSSL versoin is 3.0.11.otp: one time passwordsA lot of services offer the use of one time passwords to protect the login. People use their always online phones based on operating systems for which security issue after security issue becomes public, they use an authenticator app running on the same computer from which they login or they use cool gagets.The former two methods are better than nothing for sure. But having my 2nd factor generated from a device that is most of the time online and which is controlled by the big surveillance capitalism players does not correlate with my philosophy.Also having a second factor stored on the same computer I use to login is obviously not really protecting the services I use: if somehow my computer is compromised the username/password can be read from its keyboard or memory and the 2nd factor could be generated as well in the otp app I use.I use my smartphone - a #Librem5 - often docked to keyboard and monitor to do the same stuff as on my notebook. In fact it is the backup or ultra portable counterpart for my notebook. Not good as a 2nd factor neither.Some cool gadgets to use:Sensor Watch can be found on crowdsupply and offers totp as a watch facePrecursor a secure and open platformNitrokeys - open source and open hardwareSince I received a #LibremKey (#NitrokeyPro) with my notebook I ended up using it.nitrokeys otpI already had most otp slots filled on my #LibremKey. The only thing I always wondered has been if this would really be secure if my computer would get compromised. If I'd not notice activity on the token (blinking led) someone could have grabbed my pin to unlock the otp when I entered it and generate an otp on my computer to login from elsewhere with my also stolen credentials.Not that I think I'm that kind of target, but working in the field of security I'm used to ponder these possibilities.When I tried to configure otp on my new nitrokey3 for one of my accounts I stumbled over this output:$ nitropy nk3 secrets add-otp --helpCommand line tool to interact with Nitrokey devices 0.4.41Usage: nitropy nk3 secrets add-otp [OPTIONS] NAME SECRET Register OTP credential. Write credential under the NAME. Secret should be base32 encoded.Options: --digits-str [6|8] Digits count --kind [HOTP|TOTP|HOTP_REVERSE|HMAC] OTP mechanism to use. Case insensitive. --hash [SHA1|SHA256] Hash algorithm to use --counter-start INTEGER Starting value for the counter (HOTP only) --touch-button This credential requires button press before use --protect-with-pin This credential should be additionally encrypted with a PIN, which will be required before each use --help Show this message and exit.I had never read somewhere before that this new option --touch-button would be available. When trying to get an otp by nitropy nk3 secrets get-otp test I have to enter my PIN and the nitrokeys led starts blinking blue. I needed to touch the casing near the blue blinking led to get an otp otherwise Authentication failed with error: "SecretsAppException(code=6982/SecurityStatusNotSatisfied)" Please make sure the provided PIN is correct. Aborted!.Great improvement!pgp keysAfter having tested the otp generation I wondered whether there might be a similar feature to protect the use of the stored gpg keys.In Nitrokeys manual I found a chapter about User Interaction Flags. Nice.The OpenPGPcard part of the nitrokey 3 can be configured to make touching the device to allow the use of the stored pgp keys mandatory.The difficult part has been: "With GnuPG 2.3 or more recent" on Bookwork or Bullseye. Both offer a gpg version lower than 2.3.A quick look at Alpine Linux revealed that it'd bring an actual gpg version to let me at least configure UIF. Using distrobox it's fast and easy to fire up a different distribution using your home directory.I killed scdaemon and gpg-agent running on my Debian to make room for the versions coming with Alpine.This is what I had to do to make it work after installing distrobox from the repository of my distribution:distrobox create --image alpine:latest --name alpinedistrobox enter alpinegpg --versionActually I had to enter alpine twice if I remember correctly. The prompts changes to read user@alpine when it worked. O.k. here we got a new version of gpg. Let's make it work with the nitrokey:cat .gnupg/scdaemon.conf shows on my installation that scdaemon would try to use /usr/lib/x86_64-linux-gnu/libpcsclite.so.1.0.0 as pcsc-driver. This path doesn't exist in Alpine.O.k., let's install scdaemon and the driver in Alpine. A symlink in the place my Debian gnupg configuration file is pointing to makes the driver available to the scdaemon I need to start in the alpine distrobox.sudo apk add gnupg-scdaemonsudo apk add pcsc-lite-libssudo mkdir -p /usr/lib/x86_64-linux-gnu/sudo ln -s /usr/lib/libpcsclite.so /usr/lib/x86_64-linux-gnu/libpcsclite.so.1.0.0ls -l /usr/lib/x86_64-linux-gnu/libpcsclite.so.1.0.0Starting scdaemon using /usr/libexec/scdaemon --multi-server worked just fine and I put it in the background. A gpg --card-status showed that the nitrokey is already recognized by the alpines newer gpg version. If there's no pin set on the nitrokey it could already work, but I had to enter my admin pin and that needs a pinentry program.sudo apk add pinentrycat .gnupg/gpg-agent.confSame problem as with the driver - the path is different in my debians home configuration. Symlinking...sudo ln -s /usr/bin/pinentry /usr/bin/pinentry-gnome3pkill gpg-agentgpg-agent --homedir /home/cvogel/.gnupg --daemonAfter stopping and starting gpg-agent (I do not really know whether this has been necessary, I just assumed that it might not look for the pinentry program again) I could finally configure nitrokeys OpenPGPcard using gpg --card-edit.Following nitrokeys manual I linked above I enabled UIF for all uses of the OpenPGPcard part of it.After killing alpines scdaemon and gpg-agent I left the alpine distrobox to test whether my older debain bookworm gpg version < 2.3 would work with the enabled UIF: echo "test" | gpg --clearsign .Blinking blue led and after a touch of the nitrokey: yep, here we go.And the Librem5 or any other ARM device?At time of writing the documentation states "Arm Not Supported Currently, recent nitropy versions cannot be installed on Arm platforms due to a dependency issue…".After reading in the mentioned github issue that the problem should be resloved I just installed nitropy on my Librem5 and it worked. Slow. Very slow. But it worked.Would be nice to get nitropy work faster on the Librem5, but it works and is usable.Great updateNow my PGP keys and my OTP generator cannot be used without direct interaction with the device if the firmware cannot be broken into. This is close to having a #SensorWatch which isn't connected to the computer or any network at all.Anyway - sometimes I'll get around to try a Sensor Watch for the fun of it...·
(DIR) Post #Abfk5tCOWNVtsPib7A by me@chrichri.ween.de
2023-11-10T16:41:41Z
0 likes, 2 repeats
I'm migrating from a #LibremKey to a #Nitrokey 3c. One OTP made it to my new Nitrokey and the rest still sits on the LibremKey. I updated my OS and installed the new #nitropy utility which can't handle the LibremKey.#NitrokeyAuthenticator is still installed on my #Librem5 and while it is easy to use that way it is even easier from my desktop. Waypipe didn't work, but ssh librem5 NitrokeyAuthenticator -platform vnc opens an unprotected vnc port…purism@pureos:~$ netstat -pnlt | grep Nitro(Not all processes could be identified, non-owned process info will not be shown, you would have to be root to see it all.)tcp6 0 0 :::5900 :::* LISTEN 2019/NitrokeyAuthen …which I can connect to to get an otp before migrating it to the new token.#NotSoSecureAnd after disconnecting the ssh session the application keeps running and still can be connected to.#EvenLessSecure
(DIR) Post #AcKZ5IX8xuJrmZkdn6 by me@chrichri.ween.de
2023-11-30T11:27:51Z
0 likes, 1 repeats
Our battery vacuum cleaner #Xiaomi Dreame V10 (VVN5) stopped working for more than a few seconds and shows a #battery warning.I thought it'd be easy to get a new battery, but doesn't seem so. I opened up the battery pack to find 7 Samsung INR 18650 cells and a PCB.The cells are electrowelded to their connectors with two little dots. Something I couldn't do to replace them to #repair the pack.So I asked a company specialized in refurbishing batteriy packs and they told me that they wouldn't do this, because once disconnected the PCB would shut down and stop working. They wouldn't be able to bring it back to life.They can't offer me replacing the cells mechanically, because of - liability and warranty laws.#repairability #PlannedObsolescence
(DIR) Post #AiQTdf1x5ZaJGathT6 by me@chrichri.ween.de
2024-05-30T18:15:25Z
0 likes, 0 repeats
Just uploaded a new version of #flohmarkts integration into yunohost: ynh6.improved handling of the couchdb database(s)restore renames an existing database if it has been left over from a previous installationinstall re-uses an existing database if it has been left over from a previous installation--purge is respectedremoving without purging leaves the database and the data directory on the discpurging deletes theminstall and restore take care of an existing flohmarkt database userThe new version will be available for testing in the app catalogue within a few hours. Feedback is very welcome and much appreciated! 🙃https://forum.yunohost.org/t/ynh-flohmarkt-flohmarkt-as-an-app-for-yunohost/28455/6?u=chrichri
(DIR) Post #Am6RWfg5XSJgagAy12 by me@chrichri.ween.de
2024-09-17T18:16:18Z
0 likes, 1 repeats
Hm, does someone know a #sip client that works from the #cli on #arm64 with 1und1.de #voip?I triedlinphonec, but didn't get it to register on my arm64 debian installationI like baresip, but I couldn't configure it to register to register with 1und1.desipsimpleclient.org - worked somehow on my desktop, but didn't get it installed on arm64It doesn't need to be fancy, I'm just looking for a simple tool to let a phone ring. No need to connect nor for audio transmission.
(DIR) Post #AmVlmQ0MQxNieMRVEO by me@chrichri.ween.de
2024-09-29T18:13:48Z
0 likes, 1 repeats
After the release party yesterday for #flohmarkts beta 0.2.0 - first version tagged ever - we cleared out a last issue to make the beta release available for #yunohost. You'll find the yunohost soon in the app catalog - hopefully with the antifeature for alpha stage gone.Actually the yunohost version is one step ahead of the official beta 😉.
(DIR) Post #AmwafbM2wDmRyvJpOi by me@chrichri.ween.de
2024-10-12T22:19:05Z
0 likes, 0 repeats
Waking my #Librem5 from suspend when a new #matrix message triggers a notification.Starring:matrix server: #conduit#UnifiedPush and notification server: #ntfy#sip client: #pjsua#fractal: matrix client#feedbackd: rhythm & soundhttps://git.sr.ht/~chrichri/Librem5-wake-on-IM
(DIR) Post #AzCKcxBGj4lJKnRiDo by me@chrichri.ween.de
2025-10-13T09:11:06Z
1 likes, 0 repeats
https://chrichri.ween.de/o/1d2b0563ff3045ebbe36f8cb1a90aa41… so far so good. The mechanical part seemed to have gone well and #ModemManager recognizes a #5G connection. No tests, yet.#ShotOnLibrem5
(DIR) Post #AzG3oGUKMQCPoQ0Z3Q by me@chrichri.ween.de
2025-10-15T09:00:01Z
0 likes, 0 repeats
https://librephone.fsf.org/Free the last bits of "anything Android"?My positive thought about this is that #PostmarketOS and #MobileLinux in general will profit from any public knowledge about hardware it could run on.If I understood correctly the money for doing the work on the #Android blobs is donated by John Gilmore. His Money, his decision where to put it. And there is a positive effect, but there is also a negative one:Android is based on ideas by #Google. To free it we'd need to fork it and adopt it to different ideals and goals. Android is designed to maximize the profit of Google.It is not designed with the users well-being and interests as the primary goal.Just replacing blobs in Android keeps the ecosystem the same, promotes Google and their goals and leaves the control over design decisions for Android in Googles hands.Once a device is freed by hard work of a few engineers it will be old, it will be uninteresting for people looking at Android and the latest shiny hardware running it.But still - Mobile Linux will make good use of those devices as free OSes in general do when it comes to hardware left behind by commercial OSes.@fsf@hostux.social @fsfe@media.fsfe.org