

One bus, multiple beece?
It inherently blocks a lot of the simpler bots by requiring JavaScript as well.
Do still sign if you can, some signatures might turn out to be invalid and we need a buffer against that.
Awesome! Now let’s get the EU one as well, much closer than before now. (840’000)
Looks like they’re generally confused. The license file is GPLv3, the readme claims to be licensed under LGPLv3 and they have those terms. Potentially the terms apply only to official binaries, similar to VSCode.
I think this would require some form of CLA, or they couldn’t redistribute contributed code under their terms.
Roll with disadvantage
Upgrade notes for 10.11 RCs
It depends a lot on how physically active you are, but you don’t need 2.5l in many cases like office jobs.
Since when is there a 2 in that and what does it mean?
Maybe that’s a really bright street lamp behind the cat
Their reasoning is literally the second sentence on that page.
Note however that the
10.Y.Z
release chain represents the “cleanup” of the codebase, so it should be accepted that10.Y.Z
breaks all compatibility, at some point, with previous Emby-compatible interfaces, and may also break compatibility with previous10.Y
releases if required for later cleanup work
Any 10.Y.Z release is cleanup and can include breaking changes. That’s been the case for 10.9 and 10.10 already btw.
Yeah, I also use that, but it’s not quite as easy as the others. Either you’re open to the whole network or you need some form of external key management to add/remove peers from your network.
A bunch really, Headscale with Tailscale client, Nebula VPN, Netmaker, Zerotier.
This is the database rework that’s been in progress for a while to remove all the bad inherited database code from when the forked Emby. No more SQL statements in code or plugins, any DB access now goes through the core library. There are a few blog posts in their website with more details.
This isn’t implemented yet, sadly we also have stupid politicians like the rest of the world.
They’re doing their best though
JPEG XL would be the true future format, unfortunately Google killed it
This is fucking hilarious
Oh, that’s disappointing. I was thinking of eventually using Storj as a second s3 endpoint for backups in addition to Backblaze.