Well, apparently lots of people here who are familiar with ripping and burning CDs found it confusing - so I don't think it's dumb to point out the confusing wording, especially to clarify for those who don't know that burning means writing and ripping means reading. I at least initially recoiled in horror at the thought of burning data onto the rare find.
BakedCatboy
joined 11 months ago
The least they could do is say that they burned a copy/blank or ripped the original instead of mixing it up and saying that the original was burned. It makes it sound like they were writing to the original.
Hah I wish we could ignore them. It seems to just vary from ISP to ISP in the US but our small town ISP turns off your connection and puts you behind a captive portal forcing you to click through and accept what you did wrong before your connection is turned back on.
Yes I do this. Same exact library folders so I can let my friends use whatever they prefer. If everything is named in a Plex friendly way it should just work in jellyfin.
My main complaint is when it decides to just stop casting to Chromecast in the middle of episodes randomly - then I have to open the app, reconnect, and resume.
Also I find the Chromecast controls stop responding frequently making it so I can't pause what I'm watching - it'll like disconnect from the Chromecast but keep playing.
My partner also complains about lots of bugs on the iOS app.
Our ISP sends 3 strike letters :(
I would just accept the terms and disable wifi, or if you don't want to double nat just use a switch and accept the terms / login on every device connected to the switch.
Is running a pds really equivalent to running your own instance? As I understand it, 2 friends running their own pds cannot federate without the centralized relay which still can't be self hosted.
I've done a backup swap with friends a couple times. Security wasn't much of a worry since we connected to each other's boxes over ssh or wireguard or similar and used tools that allowed encryption. The biggest challenge for us was that in my selfhosting friend group we all prefer different protocols so we had to figure out what each of us wanted to use to connect and access filesystems and set that up. The second challenge was ensuring uptime and that the remote access we set up for each other stayed up - and that's what killed the project as we all eventually stopped maintaining the remote access and nobody seemed to care - so if I were to do it again I would make sure all participants have alerts monitoring their shared endpoint.
I tried the .ps one and it worked for me
You can achieve a similar thing using vlans - usually by default they're isolated but you may add specific rules that allow traffic between vlans if it meets certain criteria (specific ports, specific types of traffic, traffic to or from specific hosts, any combination of those). So yeah you can imagine client isolation being like having each client on their own vlan - except without needing a different subnet for each client.
At least with radicle all the forks will still exist even if the authoritative copy is taken down. And even then I think because radicle is like BitTorrent, anybody who pinned the main repo would still be seeding it so it would be very hard to scrub it completely. The main challenge in using radicle is getting an active contributor with some reputation to maintain their copy on there. Otherwise there's no momentum and nobody will pin the countless mirrors published by randos.