Yeah “dd if=/dev/mmcblk0 of=$HOSTNAME.$(date +%Y.%m.%d).img” and while its running. (!!! Make sure the output is NOT going to the sd card you are backing up…)

I deliberately chose a time when it’s not very active to perform the backup. Never had an issue, going on 6 years now.

I used to wonder why porn sites aren’t required to use ‘.cum’ instead of ‘.com’…

I’ve always used dd + sshfs to backup the entire sd card daily at midnight to an ssh server; retaining 2 weeks of backups.

Should the card die, I’ve just gotta write the last backup to a new card and pop it in. If that one’s not good, I’ve got 13 others I can try.

I’ve only had to use it once and that went smoothly. I’ve tested half a dozen backups though and no issues there either.

I wish I’d actually chosen a file system instead of just letting window’s at the time default to NTFS for external drives.

Moving from Windows to Debian; NTFS has been nothing but a headache. I’ve actually had to setup a windows machine to serve that drive pool via SAMBA as Linux just won’t play nicely with it.

Pretty sure the media itself is stored in ram, or similar volatile memory; so it wipes automatically on powerloss.

Last time I looked at the topic (several years ago in a now deleted reddit post); someone had posted info on the projector system.

The media is delivered on a battery backed up rack-mount pc with proprietary connectors and a dozen anti-tamper switches in the case. If it detects meddling; it wipes itself. You’re not likely to grab a copy from there.

As the other commenter mentioned; the projector and media are heavily protected with DRM, encrypting the stream all the way up to the projector itself. You can pull an audio feed off the sound board; but you’re stuck with a camera for video.

deleted by creator

I hope exhibit A of the defences evidence is Elon telling them all to go fuck themselves.

They’ve gotta do something in the face of ballooning expenses…

Ooo spicy… I’ll have to keep an eye on that.

Thanks!

I’m rather OOTL with intel. Mind giving me a short summary? What’d they do this time?

Https://reddit.com/robots.txt

They literally are, and attempting to block those that don’t.

I haven’t actually tried myself; but I’ve read many DRMs can be defeated by simply running the service in a VM, then screen recording the VM from the host.

Try to directly screen capture Netflix for example, and the webpage will appear as a solid black box in the recording; but not if the capture is done from outside the VM.

Yeah… Becoming a public-facing file host for others to use seem rather irresponsible.

If/when a user’s given a means of uploading files to my server, there’s no method/permissions for them to share those files with others; it’s really just for them to send files to me. (Filebrowser is pretty good for that)

That and almost nothing is public access; auth or gtfo.

Not worth the storage space. I’ll wait for digital/physical release.

That’s just the statistics pluggin on Emby server.

Configuring input/output paths are only really necessary when you have multiple systems that don’t see the media at the same paths. Such as a Linux server and a Windows node working together.

Honestly, I just wish I’d have known about and set it up sooner:

Get me a 3d printer big enough…

https://home.tdarr.io/

I used to use the built in convert options in Emby server, but recently switched to Tdarr to manage all my conversions. It’s got far more control/configurablity to encode your files exactly how you’d like.

It can also ‘health check’ files by transcoding them, but not saving the output; checking for errors during that process to ensure the file can actually be played through successfully. With 41k+ files to manage, that made it much easier to find and replace the dozen or so broken files I had, before I found them by trying to play them.

Fore warning; this is a long and intensive process. Converting my entire library to HEVC using an RTX 2080 took me over 2 months non-stop. (not including health checks)