You’d just print the photo on the paper instead of that. Use the benefits of the medium to your advantage. Physical copies of photos has a history of working which is waaaaay longer than any current digital medium could ever match.

This is likely more for things which require digital data storage, programs, longer form text that space constraints mean you can’t just print as a book, security codes, etc.

It’s all read only, yes, but I just use a group specifically for NAS access and put users that need it in there.

I use the NFS version from the debian repository; not actually sure which one, and didn’t even know that it mattered.

I had issues streaming directly from one device to the other without transcoding on WiFi. (I know you’re wired! Heard me out.)

I found that, although it didn’t fix the issue, it did help to switch from using SMB to NFS. Something about the way the protocol works meant that SMB had enough of an overhead that it worsened my stuttering issues outside of the spotty WiFi connection. For sure it significantly sped up scrubbing access times as well.

It may not be the issue, but it may be a step worth checking just to see if it is a part of the issue.

For what it’s worth, 4k remuxes can have bitrate spikes well exceeding the limits of a single gbps wire. If you have a player with limited memory, or just limited cache settings, this may also be a part of the problem.

I use https://file.pizza/. It’s open source and has password protection options and everything.

It’s very much a thing. https://getcrankshaft.com/

Terramaster had some pretty gnarly security issues that they badly handled in the past. No big deal if you keep it walled off from the internet, but their software would never let you know it should be kept away from any internet access.

Also, if you get one of their units that has an ARM chip inside instead of an intel one, there is basically no chance you’re ever going to be able to use anything other than the software that they have by default. This makes the security issues impossible to resolve without completely removing internet access to the device.

I too was unsatisfied with jellyfin’s music handling. Not only was the website disorganized and bad at using the built-in album art, but all the android music players i could find for it were also barely usable as well.

I can’t use musicbee because it’s windows only. I still want synchronized play history, metadata updates, and everything between my phone, pc, and mp3 player so a single OS software was out of the question.

I use a combination of beets, navidrome, and tempo. Beets is the metadata manager; once i’ve beet imported an album, it’s ready for navidrome to pick it up and serve it to any of my devices. (I have a custom sync script for my mp3 player that does the same). Navidome serves the music to any connected devices, converts it on the fly to lower quality (for low speed phone network situations) and also keeps track of my play counts, and my playlists for me. It’s not nearly as complicated as some of the other setups, which I also prefer.

I use tempo on my phone to connect to navidrome on the go and it has worked out incredibly well so far.

Craft Computing on YouTube does these videos semi-regularly as well. Makes something from weird and cheap parts and then gives the results of how well it works or doesn’t, as well as what quirks you take as trade. For example; https://youtube.com/watch?v=VTWaRBcOsBE

Counterpoint; it required gigabit internet and still had noticable delay to my eyes. It also had compression artifacts as well as low-medium graphics settings. It also hitched semi-regularly for no apparent reason.

All the above meant that stadia was only good for people with the money to spend on it and located in an area with fast internet and didn’t play any FPSes. It was too many requirements to be a popular thing, kinda like VR is.

It also suffered from the “games get removed straight from my library” problem. They also couldn’t support every game, or even the bare minimum if most popular right now, simply because they had to make sure it’s supported on their backend.

It should have stuck around, but I don’t think it would be a big thing until much later when internet is actually decent in most places, instead of a very select few.

I’ve found navidrome, tempo, and beets to be a pretty solid combo for that. Jellyfin technically has support for music, but I was not impressed with any of the players or library management that had to go with it.

Yes, but it still works. So long as you don’t overdo it, like someone who isn’t new to this, it’ll work just fine for a start.

Step 1: download the free ProtonVPN app; https://protonvpn.com/download

Step 2: download the free qbittorrent app; https://www.qbittorrent.org/

Step 3: download vlc media player; https://www.videolan.org/vlc/

Step 4: install and connect ProtonVPN to a free server.

Step 5: Pick a public torrent website from the wiki and look for a movie you want to watch.

Step 6: copy the magnet link the website lists and add it to bittorrent. Wait for it to connect and download.

Step 7: enable showing extensions if you use windows; https://www.howtogeek.com/205086/beginner-how-to-make-windows-show-file-extensions/

Step 8: make sure that all your downloaded files only ever play in vlc, and that they arent .exe files.

Step 9: leave qbittorrent running (and seeding!) On your computer after your movies are downloaded.

That’s androids fault. Their login input detection is spotty, and has been for a while now. https://9to5google.com/2024/10/06/android-autofill-password-manager-problems/

Honestly, this one. Handbrake was made as a wrapper for ffmpeg anyways.

Probably the latter. Doesn’t matter which it is though; they advertise both on their website.

Because I told them I used torrents. Their FAQ literally has a page with instructions for setting up torrents. Still does. I didn’t think it’d be an issue for them.

I don’t know about ‘locked’ so much as ‘hard to get running with headless linux’. I looked into it two or three times and was stymied by the various ways it went wrong.

In comparison, windscribe had me choose a port on their website, and then I used that in my docker run command and it just worked.

The strong other half of my reasoning was port forwarding being locked to GUI. I use a lot of scripts to keep my server restart process simple.

The unban was just to check if the refund process would go through. Since it didn’t then I did a chargeback.

About 8TiB upload and 2TiB download over the course of this whole mess. I don’t have exact numbers because WRT stopped counting for some reason, but I can infer based on January numbers.