You get a real IP? Its been cg-nat with every provider for the last many many years in Italy.

I got a cheap vps and just run some reverse tunnels to map ports from it to my home server going trough my cg-nat.

I am not sure that checking the time in the watch instead of on phone counts as reducing phone usage...

But anyway, any "smart" watch will not help you as they all need a phone app.

Get a cheapo analog watch, in that case...

I started with an ancient redhat, moved to Linux From Scratches, landed in Gentoo 25+ years ago and never hopped anywere else since...

Usenet is fast and very convenient, but very little content in my language, so... Not sure will renew subscriptions when they expire.

Please add support for it, it would be greatly useful

Radicale. Setup was a breeze and Just Works Fine. A piece of set and forget software for me.

Thats a good one! But I am not French.

A all my services are behind pam-auth, so nobody unless autheorized can see any subpaths. That fix it for security.

And that make it that browser will ask you to save password and login for each subdomain... But only once for a subpaths.

But beside this, is freedom of choice such difficult to grasp? My use cases are not yours, better be free to choose rather than forced, isn't it?

I do have few subdomains as well, I know perfectly how to automatize them and in fact I do, but I don't like having two ways and specially not just because some Dev don't want to look into supporting subpaths. The number of services not supporting subpaths is the vast minority, so there must be enough people wanting to use them after all. And in all cases, they don't support subpaths because framework don't support them (immich) or because devs don't care (ha).

Stuff like gitea, gerrit, WordPress, all wiki's I ever tried, arrs, jellyfin, podfetch are just the first that pops into my mind that I use and support subpaths.

The service runs as an unpriviledged user, even if, at worst, an intruder would delete or replace the wiki itself. Even the php-fpm behind it runs as that unpriviledged user and is not shared with any other service.

I doubt an attacker could do anything worse than DoS on the wiki itself.

Why?

Nginx with with over https

What do you mean?