I would add that you can follow this guide for building Caddy with DNS Provider modules. For Docker you can start from the instructions for Caddy Docker Proxy

I actually switched from Action Laucnher to Nova because the former kept crashing.

Does anyone have recommendations to replace Nova?

While I agree with you, I wished that Mehta would entertain the idea of spinning Chrome into an independent company, even though it is still unclear to me how a browser company can generate revenue, especially to pay the salaries of the army of engineers working on Blink.

Aw, chucks

I’m a Sumeria customer and they do not offer an alternative to Google Pay, in fact their cards can be used with it. You can send money to sellers and individuals (much like Wero) but I have yet to meet any seller that accepts Sumeria payments.

The author did not mention that you as a end user can customize rankings for every website and build custom searches (lenses), which are in my opinion the features that make Kagi unique and more useful than other meta search engines. And to my knowledge you cannot replicate those in SearNXG.

I think the more damning part is the fact that OpenAI’s automated moderation system flagged the messages for self-harm but no human moderator ever intervened.

OpenAI claims that its moderation technology can detect self-harm content with up to 99.8 percent accuracy, the lawsuit noted, and that tech was tracking Adam’s chats in real time. In total, OpenAI flagged “213 mentions of suicide, 42 discussions of hanging, 17 references to nooses,” on Adam’s side of the conversation alone.

[…]

Ultimately, OpenAI’s system flagged “377 messages for self-harm content, with 181 scoring over 50 percent confidence and 23 over 90 percent confidence.” Over time, these flags became more frequent, the lawsuit noted, jumping from two to three “flagged messages per week in December 2024 to over 20 messages per week by April 2025.” And “beyond text analysis, OpenAI’s image recognition processed visual evidence of Adam’s crisis.” Some images were flagged as “consistent with attempted strangulation” or “fresh self-harm wounds,” but the system scored Adam’s final image of the noose as 0 percent for self-harm risk, the lawsuit alleged.

Had a human been in the loop monitoring Adam’s conversations, they may have recognized “textbook warning signs” like “increasing isolation, detailed method research, practice attempts, farewell behaviors, and explicit timeline planning.” But OpenAI’s tracking instead “never stopped any conversations with Adam” or flagged any chats for human review.

I use unbound as an upstream resolver for Pi-hole, not directly on my machines. Be aware that resolving new domains can incur some delay (about 1s), but once cached, it’s pretty quick, even for additional entries on the same domain.

Every developer wishing to offer applications on F-Droid will have to register their identities and package names to Google for Android devices to install their apps, regardless of the distribution platform (F-Droid, Obtainium, GitHub releases, etc.)

From my understanding, it will only allow apps that were registered, so since ReVanced uses identical package names to the patched apps, it probably won’t work unless they start using ReVanced-specific package names that are tied to their identity. But that would allow Google to block these package names (or ban ReVanced completely) if say, Spotify or YouTube complain about them.

Hopefully, the EU and other jurisdictions block this.

This is very similar to the notarization process Apple introduced to comply with the EU requirement of allowing third-party stores, and yet the EU doesn’t seem concerned (maybe because Apple did not allow third-party stores in the first place, will it be different for Google?)

I first read the original report from Android Authority thinking it would only be an additional hurdle for third-party stores and developers, but I’m now thinking that it would potentially block the use of ReVanced

1: I’m assuming (hoping) this wouldn’t be a full wipe and start over? It should just upgrade right?

Yes, you can upgrade in-place. If I recall correctly, you just have to change the release channel from LTS to non-LTS in the Sources app, then trigger an update (I don’t quite remember how to do)

2: Do I need to do the whole USB route, and if so is there an option to keep everything (I’m hoping, I put a LOT of work into this so far and I don’t remember if that was an option on first install).

No, as I said above. But it’s always a good idea to have backups if you ever need to wipe and re-install.

3: I remember a few apps I installed were specific to Noble, will this break those apps?

Hard to be 100% sure without knowing which apps and how they were installed, but most likely yes as their dependencies might no longer be available on Plucky.

4: It seems like there should be an option to upgrade from the desktop, but I don’t have that option. If I run plasma-distro-release-notifier I should get an update notification right? In which case I can just say “hell yeah!” and it’ll do its thing?

Refer to my first answer

deleted by creator

Considering that my outlook on the future is grim, I would say that I do, yes.

But on the other hand, when I look at my 3yo nephew and how my sister raises him, teaching him inclusiveness, limiting his exposure to screens as much as possible, and encouraging him to draw and go outdoors, it gives me some hope that maybe not all is lost.

What’s your issue exactly?

Personally, I set up Caddy with subdomains like radarr.local.example.tld, added a DNS entry on my domain so that *.local.example.tld points to the local IP of Caddy, then followed this guide so that Caddy issues TLS certificates using the DNS challenge (since the subdomains don’t point to anything accessible from Internet) along with the caddy-docker-proxy plug-in to easily manage upstreams.

Don’t you have any off-site backup? It would help keeping some peace of mind knowing you have a copy somewhere else.

You can long press the tab icon to open a new tab. Still 2 taps.

In my experience with unbound, it tends to return expired records in the hope that they are still valid, causing issues with services hosted in the cloud, where IP addresses rotate regularly. What I did was update the serve-expired-ttl setting in unbound’s configuration to 3 hours (down from the default 24h)