How is the hosting changed when needed (e.g., a different IPFS address)? What happens in a coordinated attack by someone with 51% of the seeds, can they overwrite all of the content? Is there any cryptographic way to ensure the content hasn’t been maliciously altered?
“You pay for how many streaming services??? You could start building a decent DVD/BRD collection that you own forever.”
“Yea but I hate swapping disks and I watch on my phone.”
“Gather around, let me tell you the story of a fin made of jelly.”
I’m running Proxmox and hate it. I still recommend it for what you are trying to do. I think it would work quite nicely. Three of my four nodes have llama.cpp VMs hosting OpenAI-compatible LLM endpoints (llama-server) and I run Claude Code against that using a simple translation proxy.
Proxmox is very opinionated on certain aspects and I much prefer bare metal k8s for my needs.
I’m really not sure. I’ve heard of people using Ceph across datacenters. Presumably that’s with a fast-ish connection, and it’s like joining separate clusters, so you’d likely need local ceph cluster at each site then replicate between datacenters. Probably not what you’re looking for.
I’ve heard good things about Garbage S3 and that it’s usable across the internet on slow-ish connections. Combined with JuiceFS is what I was looking at using before I landed on Ceph.
I know Ceph would work for this use case, but it’s not a lighthearted choice, kind of an investment and a steep learning curve (at least it was, and still is, for me).
I went and edited my hosts file and added all of my devices, but I only have a handful. Tailscale on macOS has a lot of bugs, this being one of many.
This is a feature that Jellyfin natively has already. So now Jellyfin exceeds Plex in some areas.
Yea that’s the whole trusting trust thing. You can theoretically set up hour browser to only trust your private CA and not trust any of the publicly trusted CAs. Depends on your threat model I suppose.
Because a private CA allows you to create a certificate and nobody else has the ability to create certificates unless you give them the keys or a signing CA. With Let’s Encrypt, you are trusting every major certificate authority to not create a cert on your domain; coupled with DNS poisoning means you would end up on a legit-looking but counterfeit website of yours.
You’ll have to explain that one to me.
Just my 2 cents.
I would argue that shopping for a person is different than straight delivery. Depending on the shopping, I could be convinced that tipping could be appropriate.
According to the manual, you can do PC connection using Bluetooth, so give that a try. I found a teardown video and at least the top side of the PCB connector doesn’t have too many connection points. Some high quality pictures of both sides could help identify the likely pinout, and a breakout board would confirm. I would give Bluetooth a shot first.
This is normalizing tipping drivers and pretty soon it will be expected. Resist this enshittification.
Not sure why I’m being downvoted. If your only other option is desolder the NAND chips, you can build a cable for probably $10 in parts. Ask me how I know. That shit is easy. Get you a breakout board and find the connector or a close enough one that you can solder or crimp and get to it.
Way easier and less work than messing with the board level components, FFS people.
There are also people who will build you one as a service if it is beyond you.
Downvotes for adding to the discussion giving a real alternative to a stated problem is asinine.
Edit: also, if you’re willing to desolder the fucking NAND chips, just solder directly on the connector header on the PCB. Fucking duh!
Build your own USB cable?
David Birkin did a pretty good job as young Picard.
I love these games. Apparently some of the artwork has been changed instead of enhanced leading some to scream censorship. I wonder if a naked statue is really the thing to get up in arms about.
deleted by creator
Jellyfin is finally moving to the new version scheme. With [major].[minor] having breaking changes between major versions and commitment to non breaking changes for minor bumps.
This release looks to be mostly house keeping, bug fixes, few minor features, and breaking changes being the legacy api key auth removal, best I can tell it’s just the name of the key is changed from api_key to ApiKey.