joseph8th

Since ICE List is a MediaWiki site, it can have an API. I asked various AIs to write a web app that would scrape and mirror the data on the ICE List wiki.

The AI made a fast, bare-bones interface to the cloned data. I prompted it to make a nice README with instructions on how to host your own clone.

Once data is distributed, it's hard to destroy.

Disclaimer: I just prompted this. I didn't actually write it.

Not being snarky, but if you believe that, then you clearly are not an artist.

If it's not normal, then we can't extrapolate generalities from it, either. It's just an anecdote. One dude's anecdote. On the internet.

We used to call "solo poly"... "single".

The cinema industry in general is woefully way behind the curve in some respects... Cutting edge in others (like security).

No, the projector is never connected to the internet. It's connected to a cinema server. In the case of Sony, it's always a Sony server. This is not usually connected to the internet either. Instead, the usual topology is to have a Theater Management System (TMS) that pre-ingests content in the form of Digital Cinema Packages (DCPs) and then propagates it to each auditorium's server.

This TMS is also not connected to the internet in most cases. Digital cinema is locked down tight as an ATM. Most theaters have pretty meager on-site IT, so email and thumb-drives and hard-drives still rule.

I work in cinema IoT including KDM and DCP delivery and ingestion to TMS or cinema server, and our solution is to have a separate agent inside the private cinema network that can broker communication with cinema devices like projectors, calibrators, and audio processors. Some of these have their own UIs in the local network, or if you've got the company VPN, but in general for monitoring we just rely on SNMP or server API.

The cinema servers are different. They all have APIs that provide varying levels of monitoring, control, and automation for the server, itself, as well as connected devices including limited monitoring and control of projectors and audio. They all support RDP or VNC, so if you're behind the same firewall you can get to their UI. Same with TMSes... they have UIs that you can access remotely, if you're on the company VPN.

But the projector itself? Never on the internet. It's "married" to the cinema server, and will only work with that particular server, based on their respective certs.

In Sony's case, it sounds like the projector certs have expired, so now they are invalid when used with the updated server certs.

It hasn't changed much. Most features are still delivered on drives. They're just too damn BIG otherwise.

Keys are sent separately, and are valid only for a certain date-range, and for a specific cinema server. In this case, Sony servers only work with Sony projectors, and vice-versa. Each device has its own certs, but for encrypted feature encoding, the standard is Key Delivery Messages, which unlock the feature Digital Cinema Package (DCP). DCPs are a general purpose cinema package, and is also used to deliver unencrypted clips like ads and trailers.

But the key is the Key. It's only valid for the specific cinema server, and the cinema server is "married" to the projector by encryption. This protects against on-site MITM attacks.

If there's a server update that doesn't update the certs on either the server itself, or the projector (in Sony's case), then the marriage breaks, and the silver screen stays dark.

Nothing anyone else can do about it, either, since any valid certs would have to be issued by Sony, and nobody has the private keys except Sony.

This is the most likely, yup. The certs are unlikely to have a precise end-of-year expiration. It will be whatever the expiration is for the last certs loaded.

10 years in cinema IoT, here. Features are encrypted by Key Delivery Messages (KDM), and those are per cinema server/projector "marriage". No KDM will be considered valid if the server certs are expired.

This should make 2024 interesting for me.

Same. And since I chose the SDF instance, I went ahead and finally got myself an sdf.org shell. A new toy to me, though it's been around since 1987.

Yah it does. Pretty fast too! Mastodon I think suffers from running on RoR. Lemmy is written in Rust.

Having run a Mastodon solo instance for a while now, I disagree on several points...

Mastodon has very few federation blocks built-in. Truth Social and Gab are about it. In both cases, the defederation is mutual, because even those two cesspools don't wanna mix effluence with each other, never mind the rest of the "libtards" in the wildly diverse and worldly Fediverse. They've chosen to be siloed.

So that pretty much demolishes the idea that even Mastodon is somehow intrinsically "echo-chambery". There are, again, no other built-in domain blocks.

If Mastodon is "echo-chambery" it's because the alternative is to remain federated with absolute cesspools. I made it 3 months running my instance before I had to start banning whole domains. There's multiple websites to help Mastodon admins curb the incessant shitstorm that exists in the Fediverse. Whole troll farms do nothing but pump out juvenile invective at innocent users... hundreds of posts with nothing but the N-word, K-word, F-word and detailed rape threats.

Again... this is happening on ActivityPub, right now.

You tell me... is it creating an echo chamber to ban Nazi scum?

Interestingly, I've found Lemmy to be surprisingly engaging and active after just a day of Reddit Migration. Sure, there's still a lot of "Reddit sucks" posts, but certainly not all, or even close to the majority.

I was on Mastodon for the Great Twitter Migration of Nov. 2022, and yeah... it was pretty hard to watch. Never have used Twitter, but I saw a lot of Twits struggling with Mastodon. I don't think the migration went well. The Twitter experience didn't translate.

Reddit, I think is a more traditional forum. And that does translate well. There are hundreds of threads with hundreds of comments on Lemmy, and it's really the same experience as Reddit. Reddit users find Lemmy familiar in a way that Twitter users did not find on Mastodon.