Well, seeing that Insurgency: Sandstorm was on a sale, I just picked it up for him (and myself). Seems to have a lot in the map making scene, and that's a really important factor for him.
It also helps that the prior Insurgency game has the most hours on his profile, by far. Gave me a good hint that he should enjoy this one.
Thanks so much!
EDIT: My dad just got back to me, and loves the gift. Apparently that's where most of his online buddies went and still are. Nailed it!
I understand the sentiment... But... This is a terribly reasoned and researched article. We only need to look at the NASA to see how this is flawed.
Blown Capacitors/Resistors, Solder failing over time and through various conditions, failing RAM/ROM/NAND chips. Just because the technology has less "moving parts" doesn't mean its any less susceptible to environmental and age based degradation. And we only get around those challenges by necessity and really smart engineers.
The article uses an example of a 2014 Model S - but I don't think it's fair to conflate 2 Million Kilometers in the span of 10 years, vs the same distance in the span of the quoted 74 years. It's just not the same. Time brings seasonal changes which happen regardless if you drive the vehicle or not. Further, in many cases, the car computers never completely turn off, meaning that these computers are running 24/7/365. Not to mention how Tesla's in general have poor reliability as tracked by multiple third parties.
Perhaps if there was an easy-access panel that allowed replacement of 90% of the car's electronics through standardized cards, that would go a long way to realizing a "Buy it for Life" vehicle. Assuming that we can just build 80 year, "all-condition" capacitors, resistors, and other components isn't realistic or scalable.
Whats weird is that they seem to concede the repairability aspect at the end, without any thought whatsoever as to how that impacts reliability.
In Conclusion: A poor article, with a surface level view of reliability, using bad examples (One person's Tesla) to prop up a narrative that EVs - as they exist - could last forever if companies wanted.
Well that's pretty compelling!
Ever since the failure of Windows mixed reality, there hasn't been many non-Meta HMD's worth buying. At least with inside out tracking.
Maybe this will finally pressure Valve to lower the price on the venerable Index? Probably not. But one can hope!
Huh, now that's a classic I never thought would get a remaster/re-release! I played this a ton when I was a little kid in the 90s on my Sega Genesis.
Though I'll probably stick to purchasing on Steam. I'm steering clear of Nintendo where possible.
It's just my client. Boost for Reddit doesn't appear to show it correctly. It's the opposite though. It just shows the text. Spoiling it for me.
yeah…
They asked for easy, or newbie friendly - and didn't particularly mention privacy concerns.
Other than that, if they don't have a port 80/433 ingress from their ISP there are scarce simple solutions that don't require another server that also needs management, either by them or a corporate entity.
back when i was on a DOCSIS modem, i noticed concurrent downloads would disrupt uploads and vice versa. i think this may depend on the type of connection OP has.
I used to work at a cable company, that was either a problem that people with low SNR had. Either from external factors (tree branch on a cable line) or in-home ones (bad splitter). A modem will ramp up it's gain in order to offset this (to a point), and in so doing, create a lot more interference between channels. OR they were hitting their ingress rate limit (which is quite agressive on residential plans because DDOS'es). It's surprisingly easy to hit your ingress rate limit for modern http/https webservers hosting complex web apps. Lots of concurrent connections open up to try to download all the resources when you go to any website in a modern browser and while it's not a TON of data, the short period of time causes the traffic to easily hit the PPS/BPS rate limit that ISPs employ.
But yeah, it all depends on the ISP.
I'd argue that the cloudflared daemon is even easier to use than a static wire guard or openvpn tunnel. It's basically set and forget. The downside is that you must use cloudflare. This may, or may not be a big deal depending on OPs needs.
I moved from a place with symmetrical gigabit to "gigabit cable" with 30mbps upload, it definitely wasn't good enough for my small family. Photos are quite large these days - not to mention videos. Though it likely has a lot more to do with the bandwidth shaping my ISP does than the 30mbps rate.
Also agree that it's not perfect, but very likely the most newbie friendly solution at the moment. Especially from a deployment scenario vs going piecemeal.
The best "bang for the buck" in your use-case is to use Nextcloud - Nextcloud Talk is your Jitsi replacement, and the files feature can be extended with the Nextcloud Photos plugin (https://github.com/nextcloud/photos).
As for your domain question:
You should use any computer you'd like that meets the Nextcloud recommendations, the key is of course isolating this machine on your home network so any "funny business" stays on the server. You can do this with VLANs or an entirely separate LAN connected to a different WAN (ISP).
Many places, I like porkbun.com for real custom domains for cheap, but for your use case, you might be able to use a Dynamic DNS provider for free. It just likely won't be an easy to remember URL (or at least, as easy as a root domain only). If you have a newer ASUS or Netgear router/modem they both have Dynamic DNS built in and you can select from a few different providers that have both free and paid tiers. ALSO it might be better to use Google Domains (now squarespace domains) since, IIRC, many DynDNS configs for routers support Google Domains too. Cloudflare can also be a decent registrar, and I'd recommend using them if you use any other cloudflare services (see below).
Other things to consider: Your ISP may block port 80, meaning lots of issues. If this is the case, you might want to use a tunnel of some sort. Cloudflare has a great solution here. Even if they don't block port 80, they may aggressively throttle and shape your incoming traffic - causing issues. Again, the tunnel is a good solution here. And, of course, your upload bandwidth matters a lot, you'll need something around 100Mbps upload for a decent experience when accessing your stuff over the internet. The 30Mbps that's typical of DOCSIS modems won't cut it. Outside of these concerns it's all about making sure you isolate your server from your "home stuff" to keep things secure.
With today's announcement, I'm super happy you did this 4 days ago. Time to make a few clones myself.
Even on Windows, Proton drive is hot garbage. It never syncs my files correctly. Has a tendency to leave half encrypted uploads just lying around. Eating up desk space.
Don't even get me started on how long it takes to upload anything. Got a 1 GB file? Good luck!
And that's before getting into the fact that it's proton's third product. It was announced in 2019. 5 years and they still don't have proton drive as a working product.
Another gripe I have is that the Linux VPN client still doesn't support wireguard. Sure, you can download wireguard configuration files. And they work just fine. But changing servers is a pain in the ass because of it.
It's made me seriously consider dropping my visionary plan and moving to a more competent provider.
That being said, proton mail has been fantastic. And I have a ton of domains on it. So it would be a pain to move. I guess I'm just in a stalemate.