schizo

Yeah, seriously. If they had only shown things that actually existed, I'm pretty sure all the negative press would have been totally avoided since even at release it was a solid enough story-driven RPG.

Mostly just the amount of my power bill.

I mean all the usual arrs and overseerr and jellyseerr and such are already on github, so it's... probably fine?

60% of the time, it works every time.

Of course, 60% was a hell of a lot more than 95 managed, so still impressive?

Two things, I think, that are making your view and mine different.

First, the value of time. I like self-hosting things, but it's not a 40 hour a week job. Docker lets me invest minimal time in maintenance and upkeep and restricts the blowback of a bad update to the stack it's in. Yes, I'm using a little bit more hardware to accomplish this, but hardware is vastly cheaper than my time.

Second, uh, this is a hobby yeah? I don't think anyone posting here needs to optimize their Nextcloud or whatever install to scale to 100,000 concurrent users that required 99.999999% uptime SLAs or anything. I mean yes, you'd certainly do things differently in those environments, but that's really not what this is.

Using containers simplifies maintaining and deploying, and a few percent of cpu usage or a little bit of ram is unlikely to matter, unless you're big into running everything on a Raspberry Pi Zero or something.

All of this is investor driven, and a lot of the announcements are 'Yes, people giving us millions of dollars to do things, we're going to make a 2nd game in this series'. You need to announce what you're doing so you can get people to give you the money to fund doing the thing you want to do, since I'm entirely certain CDPR isn't sitting on funding to go off for 5 years and make a game without telling anyone anything.

The hype train is mostly driven by game journalists that see that a company is going to make a game, and then do the clickbait 'GameCo announces Game 2! Here's 10 things that we think will be in it!' listicles for the next few years, which skews everyone's expectations and can drown out more tame discussion since who doesn't like hype?

Things can be true and also be misleading.

This is just shitty clickbait journalism. A more accurate headline "Anticipated Fallout 4 mod won't work on current Fallout 4 versions" wouldn't get the engagement and clicks that a more provocative bullshit title that indicates that Epic won't let you play it does.

It more sounds like the mod won't work on the most current version of FO4, and because you can't install older versions on Epic, it won't work.

That's a shockingly misleading title, even for vidya game "journalism".

Eh, I'd be fine with them taking however long they need to release a fully complete and working game, rather than shove out a half-baked one.

See: 2077 at release vs 2077 patch 2.0

In fairness the motherboard not restricting power usage isn't a bad thing: it's not like it's shoving 4000w through the cpu, it's just letting the cpu pull as much as it wants which, with a non-defective piece of silicon, is probably fine.

A modern CPU shouldn't pull enough power that it kills itself, unless there's a major failure in design or manufacturing.

Sure, the CPU gets hotter with more power and sure, the last 5% of performance is a third of the total power usage and probably not worth chasing, but them's the design decisions x86 vendors are making right now and the motherboard (assuming it can deliver enough clean power) shrugging and saying 'whatever' is, outside factors aside, fine.

Also, that 253w TDP limit on a i7 or i9 is a bit low. Yes Intel's spec says that, but intel lies like crazy on power usage, and pretty much always has. These are chips that will happily gain performance up to about 400w of total draw, so capping at half that is a bit of a kneecapping, though it MIGHT keep them from failing as fast, but who knows.

I'd argue the opposite: it's made it where I care very little about the dependencies of anything I'm running and it's LESS of a delicate balancing act.

I don't care what version of postgres or php or nginx or mysql or rust or node or python or whatever a given app needs, because it's in the container or stack and doesn't impact anything else running on the system.

All that matters at that point is 'does the stack work' and you then don't need to spend any time thinking about dependencies or interactions.

I also treat EACH stack as it's own thing: if it needs a database, I stand one up. If it needs some nosql it gets it's own.

Makes maintenance of and upgrades to everything super simple, since each of the ~30 stacks with ~120 containers I'm running doesn't in any way impact, screw with, or have dependency issues that impact anything else I'm running.

Though, in fairness, if you're only running two or three things, then I could see how the management of the docker layer MIGHT be more time than management of the applications.

The Cloudflare certs CN are yourdomain.com and *.yourdomain.com, so enumeration via that means is not really going to lead anywhere.

Cloudflare is resistant to, but not totally immune from, DNS enumeration. But, frankly, the attack profile you're concerned about isn't likely to have the resources to do proper enumeration: automated bots are going to guess a static list of hosts, not spend time trying to scrape data out of DNS.

TLDR: don't use common service names, don't use common activity (don't use jellyfin. or movies. or media. or tv. and so forth) and make sure your host responds with something aggressively fuck-off for non-matched requests. For nginx, the default_server site configuration I'm using sends what's likely real humans to a rickroll, and everybot else gets a 444 which is nginx for go fuck yourself.