Not sure about Facebook since authenticating for private videos is a hurdle, but for my partner who uses a mac I downloaded open video downloader which is just a foss GUI for ytdl, it also keeps ytdl up to date which is a requirement for me since I don’t want to be called when it stops working. I think on windows you have to manually install msvc2010redist but besides that it seems to just work out of the box.
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.
It should be safe, using fstab is how I do a network mount to a specific folder also so it doesn’t change or anything.
Somebody should make an api shim that proxies openapi compatible requests to this. And since Microsoft is forcing copilot on windows 10 they’re on the shit list too. Load balance all the AI workloads onto both of them through API adapters.
One game I used to play recently started working suddenly in the latest proton major release (I think 9), it wasn’t mentioned in the release notes and it has no community around the game since it was released around windows vista, as well as being pulled from stores for many years (I still have it on steam) so I don’t think anyone intentionally fixed it but probably just a result of some system call being implemented or tweaked to behave closer to correct.
So yeah, it’s very good to test your broken wine apps every 6 months to a year because slowly anything I ever had issues with in wine is starting to work.
I don’t think it’s completely true to say it’s not accurate in any way. You can still get a rough estimate based on the proportion of likes to dislikes coming from people with the extension installed, then extrapolate that out based on the public number of likes provided by YouTube.
Of course it’s not going to be anything more than a ballpark number, but being able to tell the difference between “almost nobody is disliking this” and “like half of viewers are disliking this” is super useful information. If nothing else it serves as a third party keeping a dislike count for users who installed the extension. They’re not claiming to access the real YouTube data, so I think it’s unnecessarily dismissive of what it does to call it bullshit.
Isn’t Miracast for sending video data? The thing I like about Chromecast is that the phone or remote app just tells the Chromecast where to load the media directly from, and then only sends playback control commands. That makes it a lot lighter resource wise because you don’t need to proxy the stream through a device like a phone that wants to go to sleep to save battery.
Note that the 2x10G is SFP+ not SFP. I was briefly confused. I have tons of SFP+ stuff but no SFP gear whatsoever
I went with the DS1621xs+, the main driving factors being:
If I remember correctly only the 1621xs+ met those requirements, though if I was willing to go without ECC (which requires going with xeon) then the DS620slim would have given me 6 bays and integrated graphics which includes quicksync and would have allowed me to do power efficient transcoding and thus running Plex/jf right on the nas. So there’s tradeoffs, but I tend to lean towards overkill.
If you know what level of redundancy you want and how many drives you want to be running considering how much the drives will cost, whether you want an extra level of redundancy while rebuilds are happening after 1 failure, how much space is sacrificed to parity, then that’s a good way to narrow down off the shelf nases if you go that way. Newegg’s NAS builder comes in handy if you just select “All” capacities and then use the nas filters by number of drive bays, then you can compare whats left.
And since the 1621xs+ has a pretty powerful xeon, I run most things on the nas itself. Synology supports docker and docker compose out of the box (once the container app is installed), so I just ssh into the box and keep my compose folders somewhere in the btrfs volume. Docker nicely allows anything to be run without worrying about dependencies being available on the host OS, the only gotcha is kernel stuff since docker containers share the host kernel - for example wire guard which relies on kernel support I could only get to work using a user space wire guard docker container (using boringtun) and after the VPN/tail scale app is installed (presumably because that adds tap/tun interfaces that’s needed for vpn containers to work.
Only jellyfin/Plex is on my NUC. On the nas I run:
Adguard
Sonarr/radarr/lidarr/prowlarr/transmission/overseerr
Castblock
Grocy
Nextcloud
A few nginx instances for websites
Uptime-kuma
Vaultwarden
Traefik and wire guard which connects to a vps as a reverse proxy for anything that needs to be accessible from the public internet
Just want to second this - I use an Intel nuc10i7 that has quicksync for Plex/jellyfin, can transcode at least 8 streams simultaneously without breaking a sweat, probably more if you don’t have 4K, and a separate synology nas that mainly handles storage. I run docker containers on both and the nuc has my media mounted using a network share via a dedicated direct gigabit Ethernet connecting the two so I can keep all the filesystem access traffic off of my switch /LAN.
This strategy was to be able to pick the best nas based on my redundancy needs (raidz2 / btrfs with double redundancy for my irreplaceable personal family memories) while being able to get a cost effective low power quicksync device for transcoding my media collection, which is the strategy I chose over pre-transcoding or keeping multiple qualities in order to save HDD space and be flexible to the low bandwidth requirements of whoever I share with who has a slow connection.
My primary use case is safeguarding my important personal artifacts (family photos, digitized paperwork, encryption key / account recovery / 2FA backups) against drive failure (~2TB), followed by my decently sized Plex server (23TB), immich, nextcloud, and various other small things like selfhosted bitwarden, grocy, ollama, and stuff like that.
I run all of my stuff off of a 6 bay Synology (more drives helps with capacity efficiency as double redundancy with 6 drives costs you 30% and I wanted to be protected against drive failures during rebuilding) with an Intel nuc on top to run plex/jellyfin transcoding using quicksync instead of loading the poor nas with cpu transcoding, I also run ollama on the nuc since it has faster cores than the nas.