ShortN0te

Consumer Hardware has feature enterprise/datacenter Hardware does not have and the otherway around.

High End Consumer CPUs for example clock way higher and therefore have better single core performance, which can be a benefit.

Non ECC memory and overclocked memory like on Consumer Hardware is often faster, especially when you compare price to performance.

Especially when things like a minecraft server is not optimized for a 128-core CPU or even 32-core CPU.

Firstly, wildcards are convenient but they break your functionality of to which you are connecting which is half of what TLS does. That may or may not be important to you.

You are implying that https is supposed to be done by the individual server and not reverse proxy. Since otherwise you could not “authenticating the server”

Short answer, it should work as you describe, everything local, no need to expose anything.

More information is needed to help.

Its either the caddy setup, maybe proxmox internal networking? Or most likely DNS, its almost always DNS.

Its good practice to handle https on a reverse proxy. Also who actually does cert pinning?

My guess, auto updates for major versions is not good practice. Installations potentially corrupt and users come screaming to the project maintainers instead of searching the blame by themselfe.

forgejo defined the lifecycle for every version so just add a calendar entry for when the supports runs out and then update the 3 characters in the docker compose file.

netbird uses wireguard as vpn protocol

To my knowledge:

• File Versions only 30 days available.
• -> Everything older and deleted than 30 days gone.
• Slow and manual Restore Process
• -> Web downloads max. 500 GB manual selection.

B2 is data storage, Backblaze Personal is a service. 2 Completely different things.

You can share albums with other users, or even with a public link.

That is not what i have asked.

I doubt that this applies to files smaller than the pack size or a for example bitwise unique 17MB file would result in a (overly simplified) 16 MB and a 1 MB chunk or am i wrong here?

I use B2 for my restic Backup. Currently i have about 100GB stored there and it says i have about 100,000 files stored.

With the adjusted calculation of the blog you posted for 10TB of 50KB files, adjusted to the mean file size of my restic repository 10 TB of 1MB files:

Transaction fees: 10,000,000 / 10,000 x $0.004 = $4

My Laptop has a mean file size of about 16 MB per file on the local restic repository.

It actually does both. Not really tested the multimonitor features but its there and it works, not sure if to the same degree as in rdp.

No, you have not understood anything. Assuming Jellyfin would go closed source, (ignoring the GPL license and so on) you would not notice anything. Your server and service would be unchanged by this.

Emby is the best example, the community will fork it and you server lives on. Even if not, then the server and software is still yours.

If it becomes an issue, then you’re in the exact same position you’d be in today if you decided to move away from Plex now.

I disagree. Right now you got time to do the research, plan the move and test it out with a demo setup. You do not know if you got the time if Plex decides to screw their lifetime users.

Yes this is hypothetical.

… and may also break compatibility with previous 10.Y releases if required for later cleanup work.

If you read through the whole paragraph, it is clear that they mean the compatibility of previous jellyfin versions.

Also, again:

Note however that the 10.Y.Z release chain represents the “cleanup” of the codebase, so it should be accepted that 10.Y.Z breaks all compatibility,

That means that the code is not cleaned up with that release.

If you would release 11 before the code is considered cleaned up, you would basically break your own defined versioning convention. That is best decided by the active maintainers.

Consider the 10.y.z simply to be 0.y.z and everything works out.

Jellyfin inherited a lot of shitty code and architecture from emby. They simply cannot guarantee anything across patches until it is sorted out.

imho much better then releasing major version after major version because the break stuff regularly.

Also for internal use. The original emby source used not within the code base standardized database access.

Basically changes to the database were not possible since finding references across the code base which part uses which values was impossible.

Note however that the 10.Y.Z release chain represents the “cleanup” of the codebase, so it should be accepted that 10.Y.Z breaks all compatibility,

Its right there at the link you posted.