Nope, db0 fork is based on the latest release, it just got relocated because of how GitHub works. (If you delete the repo, fork's parents get assigned to another fork.)
100% their fault since there's a way to ad-hoc sign and run, and they're removing it and sucking Apple's dick.
EDIT: and there's even an example found in one of this post's comment of a 3rd party cask doing that in preparation of complete flag removal from Homebrew!
Yes and no. Yes, it has to be signed, but no, it doesn't have to be Apple's signing, it can be ad-hoc signed for the device programmatically. What they're doing is that removing that ability to remove quarantine bits and ad-hoc signing on installation and forcing everything to be Apple-signed.
EDIT: Ad-hoc signing is compile-time. Quarantine bit just has to be removed at install-time.
The changelog says it'll keep a copy of old database so you could start migration again with that copy.
EDIT: exact text from the blog:
The upgrade will make a backup of your existing library.db file named library.db.old. This file can be used to recover should the upgrade fail. Once you have successfully upgraded and Jellyfin 10.11.0 is running smoothly, you may delete this backup. If you need to try the migrations again due to a failure, stop Jellyfin, rename this file back to library.db, then start Jellyfin again, and the migration will be re-attempted.
That's explicitly metadata-only. No mention of DeDRMing.
AFAIK no public DeDRM methods exist for Korean eBook stores. You're sadly on your own. This country fucking sucks.
Nope, db0 fork is based on the latest release, it just got relocated because of how GitHub works. (If you delete the repo, fork's parents get assigned to another fork.)
Aye from YuruLemmy! We'll gonna block l.w when they block you all!
Deep Packet Inspection
This time it's a (permanent?) profile badge. (also it's their april fools stuff but still it's annoying.)
GNOME runs GJS which is based on SpiderMonkey (Firefox's JavaScript engine).
Because it's about RAM. It requires 8GB of RAM which iPhone 15 doesn't. (But 15 Pro does.)
KOReader the GOAT.
Also keep in mind cached requests don't count so it'd be cheaper.
That's Korean education for you!
MakeMKV thankfully exists, though 4k is a hassle even with that.
That's why I buy Macs! /hj (Though I do install and use Arch BTW on my M2 MacBook Air)
100% their fault since there's a way to ad-hoc sign and run, and they're removing it and sucking Apple's dick.
EDIT: and there's even an example found in one of this post's comment of a 3rd party cask doing that in preparation of complete flag removal from Homebrew!
Yes and no. Yes, it has to be signed, but no, it doesn't have to be Apple's signing, it can be ad-hoc signed for the device programmatically. What they're doing is that removing that ability to remove quarantine bits and ad-hoc signing
on installationand forcing everything to be Apple-signed.EDIT: Ad-hoc signing is compile-time. Quarantine bit just has to be removed at install-time.
Lighting talks will be the last sessions from 17:40 in the main hall.
Dang, I got selected for lighting talk! Come see me talk about t2linux!
Just bought the ticket! See you there!
The changelog says it'll keep a copy of old database so you could start migration again with that copy.
EDIT: exact text from the blog: