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.
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!
“trade secret” lol. lmao even.
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:
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.
Same with taking your top of the line iphone to Korea where Samsungs grow on trees and so forth.
Fun fact: iPhones are really popular in South Korea, especially for younger generations and considered more cool than boomer’s Samsung, though Samsung is gaining some traction with newer flagship models recently, so yeah it won’t make you stand out.
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
Though surprisingly, it was unarchived in 23/7, the deprecation notice removed, and some development activities are ongoing!
So they’re still denying they’re zionists. How disgusting. My fediseer censure + defed are 100% worth it.
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!
It was a now defunct Korean Mastodon instance. Actually it was the biggest Korean fediverse instance. (Now that record is superseded by planet.moe.)
It shut down sometime in 2023 after some moderation drama. It was a Korean Mastodon instance, the biggest one at that. (Now planet.moe is the largest Korean fediverse instance.)
The old 410 gone page available on IA says:
이 서버는 운영을 종료하였습니다 HTTP 410 Gone
요청하신 리소스는 더 이상 제공되지 않습니다.
twingyeo.kr Mastodon 서버는 2023년 10월 10일에 서비스를 종료하였습니다. 그동안 twingyeo.kr을 이용해주신 사용자 분들과 운영을 도와주신 주변 서버 관리자 분들께 감사드립니다. 새롭게 Mastodon을 이용하고자 하시는 분들께
여기서 다른 한국어권 연합우주 서버 목록을 확인하실 수 있습니다.
UPDATE: It got revived as the original owner’s personal instance.
That’s why I buy Macs! /hj (Though I do install and use Arch BTW on my M2 MacBook Air)