There’s a lot of these out there. They mostly work by using tricks to reduce the layers in the results image with known tweaks to how they are built. They remove things included in the final image that aren’t used, essentially. Dockerslim is another that is popular. They don’t impact security in a negative way.

https://github.com/patchy-oss/fwdl

Then why did you comment? 😂

That’s exactly what VLC’s main purpose is. Have you even looked at it? It’s one of the most intuitive front-ends to transcoding out there. Desktop, mobile, and web.

I did. You’ve been told no such thing exists multiple times already. I’m just giving you options for what DOES exist. Fuck me, right?

VLC does all of these things and does it locally for the client it’s installed on if pulling from a source.

I’m not “trying to do” anything but explain the different workflows. Again, I’ve given you solutions, but there isn’t any self-hosted thing in the way you’re asking about. Just find a handbrake UI or an ffmpeg frontend if that’s all you’re looking for.

The question is more about the WHY you need to transcode anything when you already have many better options available to you?

Again, this is why you’re misunderstanding transcoding. Let me explain…

So you want a workflow where you upload files and then they get transcoded…to what exactly? Do you have specific sizes, formats, and codecs in mind? Are you planning on keeping multiple copies of transcoded files around for use in the future? Do you have a set list of devices it needs to work for? This is why you have a pipeline to take an input, and make multiple outputs that cover the outputs for different devices.

Now…if you’re just talking about some files you take on your phone, and then you want them to play on any device anywhere on-demand? This is what Jellyfin is good for.

There is no such thing as transcoding files that aren’t available on a server. It’s never going to be a thing, because the server needs those files to transcode them.

If you’re looking for a tool where you once in awhile may choose a certain video to transcode into something else, setup a pipeline service, and send the files to that service to transcode them, but you’ll be limited by needing to know where and what it needs to processed as input, and then the outputs.

It doesn’t quite work like that.

Are you just looking to view these files on different devices? Run Jellyfin and get live transcoding when the files are accessed.

If you’re sure you want a transcoding pipeline, check out Encore, or one of the handbrake webUI’s available.

Windows uses the system registry to control other aspects of interaction with runtimes and linked libraries, so it can be confusing to people newer to Linux to just realize that flat files don’t have some hidden interaction elsewhere in the system (usually).

I feel like this is just a thing with PDF viewers that don’t paginate their views properly. Try LibreOffice or Xournal as a test to see if they perform better. I never have a problem.

Defaults are usually fine for most users. People who know they are going to distro hop or need to move data later should have a separate /home, but that’s about it until you get into special purpose installs.

Tailscale is both a client and server. If you use only Tailscale, you have to pay for the service after so many devices are connected, which by all means support the company and do so and avoid using Headscale.

Headscale is an open source implementation of the Tailscale service, so it’s free to use with all the usual Tailscale clients published. You setup Headscale somewhere, register your Tailscale clients to it, and use it like usual. It’s just skipping the need to pay for Tailscale servers as a service, and gives you greater control over how traffic routed. Completely optional.

Tailscale+Headscale or Zerotier, use whatever backup software you want for the local backups. Simple script to rsync backups to other sites and remove copies past a certain age.

Pretty simple, and no need to expose machines in any less than safe ways.

The GitHub repo IS the source code. That’s what open source means. All of the code is right there, and the releases ARE the FOSS version. There is no closed-source code for this project.

You don’t need to use Apache if that’s confusing you. The project seems to include a full Caddyfile so that’s probably going to be easier for you.

It’s really just personal preference, and either way is fine.

Cache commitment is not a memory leak. Hard commit is.

Think about limiting the resources it can see/use and move forward.

Everything in Linux is flat files. Don’t panic.

Back up ~/home, do a clean install, then drop your stuff back in.

Well if it doesn’t show as a valid output devices there’s your problem. You might want to start searching on how to use pipewire configs to force it into being a properly advertised output device.