This one is edgy.

• Arch Linux announcement
• Ubuntu discourse announcement
• RedHat/Fedora security alert
• Debian security announcement

I tried both Lidarr and Beets before, but their automation tended to pick matches with a “eh, close enough” attitude, so I just decided I’d do it properly myself.

I tag metadata on everything with MusicBrainz Picard, and then store it in a /{Album Artist}/{Album}/{Track} hierarchy.

Dead Products (Death Date)

• Mentioned in article:
  • Google Podcasts (Later in 2024)
  • YouTube Premium Lite (Oct 2023)
  • Gmail’s “Basic HTML” view (Jan 2024)
• Not mentioned in article:
  • Google Optimize (30 Sept 2023)
  • Google Domains (30 Sept 2023)

If you’ve never heard of this, that’s because it got a very small rollout to only Belgium, Denmark, Finland, Luxembourg, the Netherlands, Norway, and Sweden.

This is in relation to YouTube Premium Lite, and not, as this shortened article implies, Google Podcasts.

I think it’s getting down-voted purely because OP’s title is essentially “mIcRo$oFt bAd!” instead of describing the issue. It’s not getting down-voted anywhere else this article was cross-posted to, where they used the article’s actual title.

VS Code has an optional feature that can allow remote access, which could be [used/abused] to [access/breach] otherwise secure networks. Because the executable is signed by Microsoft, it won’t be flagged as malicious by antivirus/malware scanners even though it could easily be used as such. The article shows the steps the author attempted to detect and block this tunnel functionality, with limited success.

I swapped to Chrome a long time ago, probably around Firefox 7 or so, and never really looked back. I didn’t really have an issue with being part of the Google ecosystem, and they were still in their embrace phase. It’s been a while.

I have both browsers installed at the moment and under Linux/Wayland/Nvidia, Firefox definitely performs miles better (actual HW acceleration!) but Chrome still feels more practical to use, in my opinion. I think my main hang-up is that Chrome’s “Tab Groups” suit my approach to web browsing better than Firefox “Tab Containers”, even factoring in how Multi-Account Containers can make them more useful.

Meta can do whatever they want with Threads, in the exact same way that mastodon.social is it’s own independent instance and can do as it pleases.

If Mastodon users want to follow or even see content on Threads, it’s entirely optional, depending on your current instance’s stance. You can always move to another instance that shares your views (and there will be plenty that do) and has defederated from Threads, or you could roll your own instance and be in control of what instances you interact/federate with for yourself.