Not really, I don’t do GPU encoding anyway so can’t say first person.

But everybody says so on all forums so maybe its true.

I got an amazon fire stick, all the new ones support av1 and all android devices from A14 must support av1 too.

On PC vlc plays it just fine too.

Indeed, but YMMV and to me quality is still good if source was not a remix but a top quality encoding

Some notes: Don’t use GPU to reencode you will lose quality.

Don’t worry for long encoding times, specially if the objective is long term storage.

Power consumption might be significant. I run mine what the sun shine and my photovoltaic picks up the tab.

And go AV1, open source and seems pretty committed to by the big players. Much more than h265.

In my experience, you always gain space savings going av1 from 264 and 265 as well. For me its always been significant savings at the same quality level.

Ofc YMMV and use a very recent ffmpeg with the best av1 libraries.

Go AV1… In my direct experience the space saving is simply amazing at the same quality.

265 doesn’t seems to be the future since all Android are going to support AV1 by mandatory from A14.

Please add support for it, it would be greatly useful

This looks very cool and promising.

Iove that you can deploy on bare metal, immich doesn’t allow that.

Does it support base-url? I mean can I host it on xxx.mydomain.com/gallery for example?

No idea how to put a nice heart emoticon here… But assume I did!

For it to be, you need a solid paying user base. Which is not the case at hand.

Very often also at.enterprise level the big money is in training, support and courses rather than in the software licenses per se.

I am writing this https://wiki.gardiol.org feel free to take a look then ditch it and go your own way.

Its a bit of different take to today’s trends (docker and such).

Thats a good one! But I am not French.

Yes, naïve :)

Some of you guys are nahive.

The true and best open source stuff is not developed for profit. Once it is, its only a matter of time because, guess what, software development is never really profitable no matter how much you piss off your user base.

Don’t get me wrong: nothing bad in seeking profit, I do it myself too, I don’t live of thin air…

But true open source projects are not developed by seeking sustainability and profit out of it. I steer away from any such project because it’s doomed sooner or later and history is full of those projects.

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?

Not really… Your attitude is the problem.

Sub paths are simpler to deploy: need only one certificate, need only one subdomain.

In any case you need reverse proxy so security is not the matter here.

Your use cases are not mine and both ways should always be possible.

You never need a subpath over a subdomain, nor viceversa, it is (or should) always be a choice.

It’s a work in progress, but https://wiki.gardiol.org (which is OFC self-hosted)

Anyway, beefy HP laptop with 32gb ram and Xeon CPU to run all services. 3 RAID-1 (Linux sw raid) usb3 volumes to host all services and data.

Two isp’s: Vodafone FVA 5G (data capped) for general navigation and Fastweb FTTC (low speed but uncapped) for backup access and torrent/Usenet downloads.

Gentoo Linux all the way and podman, but as much limited as possible: only immich (that’s impossible to host on bare metal due to devs questionable choices).

Services: WebDAV/webcal/etc wiki, more stuff, arrs, immich, podfetch, and a few more.

All behind nginx reverse proxy.

99% bare metal.

Self developed simple dashboard

External access via ssh tunnels to vps

Why are subpaths an a anti pattern?

Why is taking away choices a problem?

Everybody has its own usage case, why should we prevent them from using their?