
Sign up to save your podcasts
Or


Previously, previously.
There are many reasons, unrelated to artist reimbursement, why Spotify is the dirt worst of the streaming platforms. I trust by now you are aware of these.
I want to make it very clear that I am not criticising anyone for using streaming platforms. Everyone streams, living is hell and we all love music. [...]
As you can see, the vast majority of people who streamed All Hell did so using Spotify. Unfortunately, of the major streaming platforms, Spotify pays significantly less per stream than anywhere else.
If everyone who streamed All Hell on Spotify had done so using Tidal instead, we would have received an extra £31,847.38, which would double the amount we made from streaming of the album in this time period. Or if everyone used Apple Music it would have been £12,331 more.
Spotify Unwrapped:Relatedly, today is Bandcamp Friday when 100% of your money goes to the artists.
"But what do you use, jwz?" none of you are asking. I'm glad you asked! I do not use any streaming platforms. I purchase music as files that then live on my computers and computer-like devices that are backed up on hard drives that I own. I listen to them with headphones that have analog cables.
When at all possible, I purchase music from Bandcamp, because of all the options available, that is the one where the artists make the most money.
When an album is not available on Bandcamp (as often happens with bands signed to major labels who contractually prohibit the bands from making their music available on Bandcamp) I have been using Qobuz, which seems to be the least-bad second option at this time. The files are high quality and DRM-free.
Previously, previously, previously, previously.
Previously, previously, previously, previously, previously, previously.
BTW, sex dolls are alive in the Toy Story universe.
Extremely relevant previouslies:
Previously, previously, previously, previously.
I added support for PAM to XScreenSaver in 1998, when PAM itself was a little two-year-old baby. Your keyboard was still PS2 and HDMI hadn't been invented yet. For lo these many decades, nobody could agree on what went in /etc/pam.conf or /etc/pam.d/login and it was all a giant mess.
Things that used to sometimes be true:
I could not even hazard a guess as to which of these things are still true, or how many decades ago they stopped being true, or which of them are influenced by Linux versus BSD versus Solaris versus HPUX versus AIX versus Kerberos or other things that nobody cares about any more.
So I am considering making the following changes:
What I would like to know is: will this break things on your system? Particular emphasis for this question on people running weird-assed obscure systems.
But emails exchanged with Kohler's privacy contact clarified that the other "end" that can decrypt the data is Kohler themselves: "User data is encrypted at rest, when it's stored on the user's mobile phone, toilet attachment, and on our systems. Data in transit is also encrypted end-to-end, as it travels between the user's devices and our systems, where it is decrypted and processed to provide our service." [...]
And the privacy policy states data may be used "To create aggregated, de-identified and/or anonymized data, which we may use and share with third parties for our lawful business purposes, including to analyze and improve the Kohler Health Platform and our other products and services, to promote our business, and to train our AI and machine learning models."
Why would you want a toilet-cam, you almost certainly are asking. Their web site says:
Dekoda analyzes three vital areas: gut health, hydration, and the presence of blood in the bowl. Your gut health results fall into three categories: regular, hard, and loose. Your hydration status falls into one of two categories: hydrated or under hydrated. Each session unlocks deeper health insights that become the building blocks for healthy routines, notifying you if blood is detected in the bowl.Cool, cool. It notifies you if you didn't notice that you are shitting blood.
Training an AI model on literal shit is quite poetic though. Garbage in garbage out.
I'm not taking a shit, I'm unlocking deeper insights!
Previously, previously, previously, previously, previously, previously, previously, previously, previously, previously, previously, previously, previously.
Previously, previously, previously, previously, previously, previously, previously, previously, previously, previously, previously, previously, previously.
Not a lot new in this one, but it has been a while since I synchronized all 3 platforms, so here we are.
GL Slideshow does a bunch of fancier transitions when loading new images, inspired by the DNA Lounge flyer screens. So now I guess XScreenSaver can be your "Digital Signage Solution".
Endgame has a bunch of full historical chess games, and smoother piece motion.
All hacks that display images and their file names can now display their title instead, if the image originated in an RSS feed. (This is why I was asking about xattr yesterday).
On the Unix side: there are several Wayland fixes, and better diagnostics for all the shit that doesn't work under Wayland.
And "make test-wayland-lock" is a disproof-of-concept that demonstrates why the "ext-session-lock-v1" protocol does not and cannot allow a screen saver to lock the screen. Great job, everybody. Perfect, no notes. (If you think I'm wrong about this, prove it! There's a comment in the middle that says "here's where a miracle happens". Fill that part in.)
I've also written configuration files for building a non-insane .deb installer. Do "make deb" or "make rpm". (Eat shit, Debian.)
Incidentally, I am still experiencing constant crashes when just clicking around in xscreensaver-settings on Linux, as mentioned here, but apparently I'm the only one experiencing this. Just lucky, I guess. If it happens to you too... see if you can figure out why!
Previously, previously, previously, previously, previously, previously.
Previously, previously, previously, previously, previously, previously.