Noa Himesaka

Also keep in mind cached requests don’t count so it’d be cheaper.

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.

Your “reverse situation” is exactly what happened to Kakao. Started as small messenger, expanding into other businesses as such.

Quite a lot. Those DMCAed titles from Kakao are all from them (originally published on their platform in Korea) so yeah they’re quite big. And they do all sorts of other biz like KakaoTalk (de facto messaging service in Korea) and even a fucking bank.

Ah, of course it’s South Korean cybersecurity agency. They suck at everything and only thing they do is trying to hide this country’s system’s vulnerabilities.

They did explicitly said that it’s completely unsupported scenario. It’s only for multiarch usage so even kernel isn’t provided.

Users running i386 systems should not upgrade to trixie.

From https://www.debian.org/releases/trixie/release-notes/issues.en.html#reduced-support-for-i386

It won’t work since there’s no RHEL10 repo. You can however use CentOS (Stream) 10 repo, I use it that way and it works!

deleted by creator

deleted by creator

BTW one of the maintainer forked it so if you need upgrade path, it exists. (at least for now)

https://github.com/matrix-construct/tuwunel

Note that you still need t2linux-specific patches to make it work on your Intel MacBooks with T2 chip.

GPL does not restrict you from selling the software, though you can’t stop getting distributed by someone who bought it. Even RMS himself sold Emacs back in the day.

EDIT: I’m not saying it’s justified in moral sense, I think it sucks ass. But it’s not against the license.

You can selfhost Ghost, but hosting different APub service with same domain messes up federation.

Me using Threadripper 7960X and R5 6600H for my servers: 🤭

I run a Arch Linux tier 1 mirror. Somehow mine’s one of the few.

The main server. Specs:

• Ryzen Threadripper 7960X
• 256GiB (4x64GiB quad-channel) of DDR5 REG/ECC running at 4800MT/s
• 256GB SATA for Proxmox boot disk, 2TB WD BLACK SN850X NVMe for VM data
• NVIDIA RTX 4080 Super for workstation use, AMD Radeon Pro WX 3100 for Proxmox console
• Proxmox VE
• RHEL 9 for server (14c, 160GiB RAM, 800GB SSD), Arch for workstation (10c, 80GiB RAM, 1.6TB SSD)

Server runs:

• Mastodon
• Minio for S3 bucket
• Lemmy
• Four Minecraft server, two modded and two vanilla
• Jellyfin
• Roon
• Komga
• Nextcloud AIO
• Pi-Hole
• Bluesky PDS

Bonus: I use Oracle Cloud server for:

• Mirror
• Ghost blog
• Synapse
• Vaultwarden
• Wikiless

He did pass the repo to the community (thus the repo not being on tteck) before he passed away so it will be maintained.

https://www.nytimes.com/2024/02/03/us/book-bans-librarians.html?unlocked_article_code=1.1k0.2DLu.z4XyKBb-92s6 Here’s the gift link without the paywall. I got the sub for free because my university has one for students.

The newest Threadripper 7000 series not only support ECC, but require it to work. It only accepts DDR5 registered ECC RAM.

From mangas of course!

• YuruYuri San☆Hai! - Proxmox host replacing old YuruYuri bare-metal RHEL server, now with 24-core Threadripper and registered ECC RAM!
• Nanamori-chu☆Goraku-bu (VM on Proxmox) - Replacement of my personal rig, has GPU passthrough
• Nanamori-chu☆Seitokai (VM on Proxmox) - Direct replacement of old YuruYuri working as my primary server
• I Think I Turned My Childhood Friend Into a Girl - Oracle Cloud VM, for high bandwidth and speed applications (e.g. mirror)
• WATATEN!: An Angel Flew Down to Me - Old personal rig (MacBook Pro 16" 2019 with Arch) which is still used for managing Proxmox