Music. Photography. Thoughts.
Bobby Borisov wrote a nice article called “Debian Unveiled: The Gold Standard of Linux Stability” on his linuxiac web site, and Ankush Das summarized in his “Focusrite Extends Help to Linux Developer to Enable Driver Support” article on It’s FOSS News how Geoffrey Bennett and Focusrite are getting together since he started writing driver and GUI software for their audio interfaces (and reported about that on LinuxMusicians).
So both articles are good and recommended reading.
Got Gnome 45 on Arch today, and – as expected and even announced – none of the former extensions kept working. Looked like this:
The workspace switcher still worked, but is redundant now because they made another pill-shaped one on the top left (not movable). Freon and Openweather extensions don’t have version 45 yet, and even Vitals – at least the one packaged in Arch’s User Repository (AUR) was too old. And GSConnect, the most important one for integrating your phone(s), is gone as well.
My solution, for the moment? Go to XFCE. I’ve tried Budgie but didn’t like it, and I never became friends with KDE again since leaving it 20+ years ago. So for now my Arch desktop looks like this:
So still no GSConnect (or KDE Connect), but still better than this forced-into-your face behaviour of Gnome. Seems like Linus was right, that is cancerous behaviour, thanks but no thanks.
Edit/Update:
I gave KDE another try. No love yet, but it’s growing on me. And KDE Connect works as well (that small phone icon in the lower right):
So let’s see…
Edit/Update from later the same day:
Back to Gnome by now. Like I said, I tried to love KDE or XFCE or other desktop environments, but just can’t. So for the moment I installed the latest nightly build of GSConnect from Github, and for a bit of weather info, I used another extension from AUR’s git. That relies on the installed weather app from Gnome which isn’t as good as OpenWeather, but it works (showing Frankfurt, not the place we live but close enough). For the moment, I can do without Vitals or Freon, I know that my CPU temp and fans speeds are good no matter what I’ll do. So back to minmalistic Gnome:
Like always, thanks for viewing.
During the last month or so, quite a number of bugs have been found, some of them prominent, and some severe ones which are actively exploited already, meaning that more or less everyone is affected, no matter what operating system(s) they use. That’s why more or less every operating system and program vendor(s) are offering updates at the moment, and you should install all of them.
For instance: the webp image and vp8 video formats from Google, they are used in every major browser and even in programs you wouldn’t think of, like the Signal desktop and mobile clients which are basically Chrome browsers as well (just with another look). Or in-OS updates like libvpx on Linux and the equivalent ones on Windows, Macs, and so on – even “stable” operating systems like Debian 12 “Bookworm” are offering updates on almost a daily basis at the moment, and you should really care.
On Android phones, look for updates as well – the original Google Pixel devices which are still supported just got Android 14 (which has bug fixes), but ones on A13 or older should still get updates as well – and don’t forget to check the Google Play Store or its alternatives like F-Droid & Co. Play services as well in case you’re on standard Android. And for iPhones and the Apple iOS/MacOS world the same applies.
So do yourselves and us all a favour, and update your engines, ladies & gents. Thanks.
P.S.: older devices are potentially greater risks than newer ones, which is why Apple or Google and also 3rd party vendors like GrapheneOS only support their devices for a certain amount of time. Luckily, for the new Google Pixel 8 phones that supported time frame was now extended to 7 years, for these and older ones see here.
Older ones could still run at home with some risks accepted, and with OSs like DivestOS, like for instance our 11 year old Nexus 10 tablet or the Pixel 3a phone. That Pixel 3a for instance has Android 13 (which Google never gave it), and while the Nexus 10 tablet ist still on Android 7 (which Google also never gave it), it still can have the latest security patches at least for the software side (but not for Qualcomm, ARM, or any other 3rd party hardware vendors of course, blame it upon them):
At least a bit more peace of mind, and even if that’s not a 100% solution, it’s still better than nothing, so we have to thank people like Tad (DivestOS) or Daniel (GrapheneOS) for all of their work. Please support them if you can. And see a comparison table of Android ROMs at eylenburg. Thanks.
Just saw the first little parts of what will become Gnome 45 trickling in, like in:
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...
Packages (2) gnome-disk-utility-45.0-1 openpmix-4.2.6-1
Total Download Size: 1.87 MiB
Total Installed Size: 9.83 MiB
Net Upgrade Size: 0.03 MiBAnd why does that make me sigh, you might ask? Well, because the guys at Gnome think they know better again, and will again break existing and working desktops for you, me, or everyone (worst will be for “the big guys” who make desktops like Unity based upon Gnome). See this article in The Register:
GNOME 45 formalizes extensions module system
I’m using four Gnome extensions which I’d really like to keep, which are OpenWeather, Freon, the built-in Workspace Indicator, and GSConnect, so I looked up https://extensions.gnome.org/ to search for version numbers, and as expected, none of them has a 45 version yet. And while it’s all documented from the Gnome developers, I’d like to wait until all these – for me – important things have updates before I’ll get a desktop which again throws out the baby with the bath water, many thanks.
Looking for / thinking about alternatives? Nah, not really. I never really loved KDE, and XFCE isn’t an option for me either, nor are others which mostly mimic Windows (like Cinnamon & Co.), or Enlightenment. So let’s see how this turns out.
But there are worse news, especially for those of us who are using Android phones, namely Google’s planned “Privacy Sandbox”. See this article:
Google Chrome Privacy Sandbox open to all: Now websites can tap into your habits directly for ads
Time to look out for another browser, see also in https://www.androidauthority.com/chrome-ad-topics-rollout-3362364/ – and it’s getting worse, since this will probably end up in AOSP. Chatted a bit about that with Tad who is the lead developer of DivestOS, and he assured me that neither DivestOS nor GrapheneOS would include these bits. But Google with its former infamous “Don’t be evil” mantra seems to turn to Orwell’s Newspeak lately, which is really bad. There’s nothing “private” about their sandbox anymore, so dump these Chrome browsers, and get Mulch or Vanadium (or better, Firefox) instead. Best solution for Android phone users: install GrapheneOS in case you have a current Pixel phone, or DivestOS for those whose devices would also be covered by LineageOS, or whose devices are too old for GrapheneOS.
And no, Apple is not an alternative. Security based upon obscurity never worked, I’m only dealing with Open Source here, no time for walled garden crap.
Like always, thanks for reading.
Update, from September 12th, 2023:
Here are some more links, some new some old, but take your pick or read them all if you care for real privacy:
https://www.theregister.com/2023/09/07/google_privacy_sandbox/
https://lifehacker.com/how-to-disable-google-chromes-new-privacy-sandbox-track-1847276073
https://www.zdnet.com/article/heres-how-to-opt-out-of-google-chromes-privacy-sandbox-floc-trials/
https://techcrunch.com/2023/01/17/privacy-sandbox-topics-api-criticism/
https://en.wikipedia.org/wiki/Privacy_Sandbox
https://www.eff.org/deeplinks/2021/03/googles-floc-terrible-idea
https://www.howtogeek.com/724783/how-to-opt-out-of-google-floc-in-chrome/
By far not the only sites and articles I’ve found, but enough to give you an idea why this is bad. And as I wrote above, it could be even worse on Android phones, where Google almost always has the ‘WebView’ authority, which means that any link you’ll click will be opened in WebView (aka Chrome), no matter if you have Firefox or other browsers set as your default. Only way to mitigate that is to use more private operating systems on your phones, like GrapheneOS (which uses their hardened Vanadium WebView), or DivestOS (which uses their hardened Mulch WebView, partly based upon GrapheneOS’s Vanadium (plus a few other goodies like an ad-fighting hosts file)).
Like always, thanks for reading, and for considering in helping to make the web a safer place to be.
Update, from September 30th, 2023:
Here’s another one. Do yourselves and us all a favour, and don’t use that browser.
Due to several newly discovered and closed bugs in recent times, it’s advisable to update your browsers, both Firefox and everything based upon Google’s Chrome and Chromium engines.
See here and here for Firefox, here and this and that for Chrome.
The fastest of my systems to update these (or their hardened derivates) were DivestOS with updates for their Mull and Mulch browsers, and Arch Linux with the new Firefox and Chromium browsers – thanks for all of your work, it’s really appreciated!
Thanks to you for reading, and for considering to staying safe.
And thanks for everything ladies & gents, and of course to Debra and to Ian!
Update, from Sat 19 Aug (as shown on my monitor): here are some very good reads about Debian, Google’s in-house version of a rolling release Debian, and some message from a no-name-yet variant of it which is about three and a half months older than our daughter. Excellent read, so recommended…
If you’re reading this blog regularly, you might have asked yourselves why all the thoughts about security, privacy, freedom, and so on lately? And you might be one of those who say “I have nothing to hide”. Well…
This one is a must see. It helps if you understand English, French, and German at least a bit, but even if you don’t, watch it to the end:
This comes from the PeerTube, and it promotes those free and decentralised services, and for good reason as you will hear. So please do yourself and us all a favour and stop using Facebook, Whatsapp, and all of that – and replace it with something like Signal or even better, XMPP. We will all profit from it.
Oh, and in case you have an old Android phone which isn’t supported with regular updates anymore, try DivestOS. And if you have a new one from Google, try GrapheneOS (or else, DivestOS again). Sure you can’t live without that intrusive Play Store? Have a look at F-Droid instead. Or are you using Apple instead? Maybe think again… and please start encrypting. You can at least do that even if you stay with a standard Google or Samsung or Apple device.
As always, thanks for reading, and for viewing.
In my recent discussion in one of the GrapheneOS forum threads I was reminded not to encourage people to use that system on devices which aren’t supported anymore, like for instance our Pixel 3a. My follow-up question on how to best preserve such older but perfectly working hardware from becoming landfills, one of the suggestions were that if your tasks don’t really need the highest security, one should probably have a look at DivestOS instead.
And yes, I have read good things about it already, both in the German-speaking blog of Mike Kuketz, and also on the blog of a photographer friend from Florida, US of A. Mike pointed to the About page which states:
DivestOS is a full-time passion project (not a company) maintained solely by Tad (SkewedZeppelin) since 2014. It has many goals, but primarily: prolonging the life-span of discontinued devices, enhancing user privacy, and providing a modest increase of security where/when possible. The devices DivestOS supports are not fully free (as-in-freedom) and there are many security issues we cannot solve such as insecure proprietary blobs, insecure firmware, insecure bootloaders, and insecure ancient kernels. We are also fully aware of our “off-the-rails” approach, however mostly attribute it to the sheer effectiveness provided by “80%” solutions instead of mulling around and not doing anything. We genuinely believe that what DivestOS offers is something unlike any other project, especially with regards to the project scope and our persistence. We hope you find some benefit in our fruits, and remind you to have fun!
And just like the guys from GrapheneOS recommended DivestOS, Tad also writes in the Patch Levely page:
If you want a reasonably secure and well-maintained device, please acquire a newer Pixel (6/6a/7) that is fully supported by GrapheneOS and use it instead.
And that is true. GrapheneOS is probably the most secure system I’ve seen so far, and DivestOS does all they can to provide system updates for devices which aren’t even supported by the hardware vendors (and therefore, also by GrapheneOS) anymore. They even have monthly updates for our 11 year old Google Nexus 10 (Codename “manta”) tablet and its Android version 7 “Nougat”, can you believe that? So it’s this 80% effort Tad writes about which goes a long way, and which helps us all a lot – thanks man!
I’ve made three screenshots of the Pixel 3a running it, still unaltered by me (that came later). Looks like this out of the proverbial box:
So that seems to be the system for older devices. For newer ones, it depends on you or me: stock Android with all its AI goodies like Live Translate from the Google Assistant, or a much more spartan but really more secure GrapheneOS? Only you can decide. At least the Graphene web installer makes it easy in case you want to have a look…
So it’s a big “Thank You!” to people like Daniel and Tad. And like always, thanks to you for reading.
Update, from Sun 20 Aug: here’s an updated version of my home screen on the Google Pixel 3a with DivestOS as the operating system, Lawnchair as an alternative system launcher, itself being updated by Obtainium and directly through GitHub. So it now looks like this:
Themed icons and all, very cool. Almost like a stock Android, but better.
Like always, thanks for viewing, and for reading.
Over in the discussion forum of GrapheneOS, there was an interesting topic, or so I thought, titled: “Brave vs Vanadium“. In it, someone asked about how the Brave browser did seemingly offer better protection against tracking and fingerprinting vs. the hardened Vanadium browser of GrapheneOS, tho this one might be more secure. Some others mentioned tests I hadn’t seen before, so my interest was piqued, I got curious myself, and wanted to see results. So here we go.
First, the Brave browser on my Arch Linux, with a test from fingerprint.com:
Aha. As expected, I saw my IP (that comes from the router, not my machine), the slightly false geolocation (our IPs always resolve way too far East for some reason), and a unique visitor ID. So there’s no “hiding”, trackers and advertisers always know exactly where you are as long as you don’t use VPNs or the onion routing network.
Second test, same browser, with EFF:
And yes, this is where Brave shines in my opinion. Randomized fingerprint plus ads and trackers blocked, that’s what I expected to see.
Third test, also found recently, the real blocking of ads:
Ouch. 72% or 108 of 150 tests blocked, here I expected something better…
Ok, someone in that discussion thread mentioned Edge, so same tests with that one:
Ouch again, this one’s definitely out. A unique fingerprint and no ad and tracker blocking whatsoever, this is one of the worst I’ve seen.
Onto my main operating system and browser of choice, Firefox (with uBlock Origin) on Debian:
Wow, far better than I had expected! A unique fingerprint according to EFF, okay, but that’s probably due to some extensions like WindowSizer and so on… but that it was 10% better than Brave in the real world ad & tracker tests, I must say that I’m impressed!
Ok, now it gets interesting – we’re on a phone operating system’s discussion forum, so let’s take phones into the equation, shan’t we? I have a Google Pixel 6a with stock Android from Google on which I normally use Firefox (also with uBlock Origin), so let’s see:
Cool… we’re down to “nearly unique”, and to 87% blocking of real ads & trackers… the best so far, isn’t it?
Wait, what about Vanadium? That I have on a Pixel 3a with GrapheneOS, so let’s see:
Also strong protection with a nearly unique fingerprint, but these 90% blockings of ads and trackers, that’s what I wanted to see, wow…
Subjectively, I see less ads in other browsers, so I guess I still have to continue reading and understanding it all – but kudos to the team over at GrapheneOS, you did a marvelous job!
As always, thanks for reading.
Update, from August 3rd, in the evening back at home:
Some people in the mentioned discussion forum over at GrapheneOS asked if I had an ad-blocking DNS provider configured in the Vanadium browser on that Pixel 3a phone, and another one asked to please also repeat a test using the Brave browser on a phone instead of a Linux machine.
Point 1: doh… (me silly, mea culpa, and so on) – of course I had set up a more or less secure environment with Graphene on that older Pixel phone, and that included setting up a secure DNS which also uses ad-blocking. So I had to repeat that test, could do it only today as I haven’t been home for a few days. So here you go, with:
Vanadium on GrapheneOS on a Pixel 3a, *without* an ad-blocking DNS configured:
Ouch! 4% block rate only, that wasn’t good… interestingly, with the same secure DNS configured again, at the first try it was raised to about 29 or 30% only, but that could have been session-related I guess; a later test with the browser newly opened went back to the 90% which I had before.
Point 2: the test with Brave on a phone. Did that while I was away, so here you go:
The fingerprint test, as you can see that was from a different location and IP address…
EFF’s Coveryourtracks test again, as good as before, and
The real world blocking test, exactly the same as on the desktop with Arch.
Now the *real* question was/is still unanswered, namely how both would compare under the same conditions, and from mobile phones. So to be fair to the Brave browser, I set up the same ad-blocking secure DNS provider in its settings, et voilà:
95%, and only 7 of the 150 tested “attacks” left unblocked, that’s the top position of my tests so far.
So how to answer that initial question about which one to choose? Hard to say, maybe I will install and leave both on that Pixel 3a with GrapheneOS, for me Vanadium will most likely always stay the default browser on Graphene (and its web view part anyway), but I will further test Brave when in doubt, or when I see something unusual and/or new.
I’m sorry that my first test attempt was a bit misleading, and I hope this additional one could clear up things a bit? In any case, and as usual, thanks very much for reading.
Still trying to figure out GrapheneOS on my late brother Willi’s old Pixel 3a phone. Turns out that with the sandboxed Google services activated, you can have the best of both worlds – one profile with free and open source apps, one with all the usual Google Android Apps in case you want these. With the same background picture of our late cat Tuna from 2020, that looks like this:
As you can see, you can even have the famous Google camera. What I have not found yet is the original Pixel launcher, guess you’d have to use a lookalike like Lawnchair2 or so to get the same look and functionality like on a Pixel with only the Google Android on it.
But this here is way more secure, as all of these apps are sandboxed and don’t have system-wide privileges, unlike with Google’s version of Android. I’m tempted to use it on my main cellphone as well…
Oh, and although installing GrapheneOS is easy especially with the web based installer, there are still some nice video howtos from people like Side Of Burritos, Cozy Living Machine, or Naomi Brockwell. Just in case you want more than just *my* opinions…
As always, thanks for reading.