This is super neat even though it’s basically just running the main board plugged into peripherals - I already knew the main board was pretty small but it’s still surprising seeing it sitting on a table.
Makes me wonder what you could do with a case the size of a wii (or even a mini wii). Plenty of space for cooling, a 2.5" SSD bay, and I’m sure you could fit lots of other goodies in it too.
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.
Brb uploading a 5GiB file from /dev/urandom to make sure there isn’t a byte of space left in OneDrive for them to do this to me.
I’m not sure how you figure that I’m “so angry”, I thought my reply was pretty calm. All I’m pointing out is that valve treats their own employees very well, and that if you have an issue with how developers working for other companies are treated / paid, your beef lies with those companies.
Hell valve doesn’t even charge their cut on steam key sales on other storefronts even though activating the key / downloading the game still uses steam infrastructure.
Then maybe you should complain about the game company that employs those developers, not valve…?
Has anybody made a matrix app that looks like a discord clone? That sounds easier since the federated rich text chat is already made, the current clients don’t really appeal to the discord crowd.
Moonlight is Nvidia game stream so it’ll be using the Nvidia server or sunshine which implements the Nvidia game stream protocol for AMD/Intel/Nvidia server hardware.
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 think that text is from melroy, so according to him. From seeing his interactions in the kbin issue tracker I get somewhat of an egotistical impression of him, because he would often take an issue that has just been opened and not triaged or discussed what the best fix is, and he would open a PR with how he thinks it should be fixed, and it sounds like his frustration is that his hasty PRs weren’t getting merged quickly because people wanted to come to a consensus.
Maybe I’m just reading into it but it felt like he just wanted his name on something and it wasn’t happening with kbin.
Edit: I want to add that I don’t mean to shit on him as a dev or as a person - it’s possible that I’ve only seen a one-sided view of his interactions as a busy contributor who just wants to whittle down the issue list as fast as possible and that he’s got good intentions, and regardless he seems like a very capable dev. It’s just that based on my perusing of issues and discussions I’ve come across, it doesn’t seem fun to work with him to contribute, and if I were to treat the contributors list as a scoreboard and had the goal of having my name on as many commits as possible, I think it would be hard to tell us apart. I was just going to keep my thoughts about this to myself but I’ve seen some other people comment similar things in other threads about mbin so maybe it’s worth sharing my skepticism about mbin. Take from it what you will.
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.
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.