One thing you probably need to figure out first: how are the dgpu and igpu connected to each other, and then which ports are connected to which gpu.

Everyone does funky shit with this, and you’ll sometimes have dgpus that require the igpu to do anything, or cases where the internal panel is only hooked up to the igpu (or only the dgpu), and the hdmi and display port and so on can be any damn thing.

So uh, before you get too deep in planning what gets which gpu, you probably need to see if the outputs you need support what you want to do.

It’s viable, but when you’re buying a DAS for the drives, figure out what the USB chipset is and make sure it’s not a flaky piece of crap.

Things have gotten better, but some random manufacturers are still using trash bridge chips and you’ll be in for a bad time. (By which I mean your drives will vanish in the middle of a write, and corrupt themselves.)

Am I missing something, or is this just the argo tunnel thing Cloudflare has offered for quite a while?

10000% this.

Tell me what it does, and SHOW me what it does.

Because guessing what the hell your thing looks like and behaves like is going to get me to bounce pretty much immediately because you’ve now made it where I have to figure out how to deploy your shit if I want to know. And, uh, generally, if you have no screenshots, you have no good documentation and thus it’s going to suuuuck.

It’s because of updates and who owns the support.

The postgres project makes the postgres container, the pict-rs project makes the pict-rs container, and so on.

When you make a monolithic container you’re now responsible for keeping your shit and everyone else’s updated, patched, and secured.

I don’t blame any dev for not wanting to own all that mess, and thus, you end up with seperate containers for each service.

Those both have a Ring 0 component, which is essentially presented as required for the crap to even work.

The argument being that you have to have that level of access for the anti-cheat software to be able to actually be able to do it’s thing, since if you just ran it with a normal user’s permission, it’d be subject to numerous ways you could have a cheat tool simply bypass it.

They’re probably not wrong about that, but doesn’t mean that we should have to essentially install a rootkit on our hardware to play online games.

I’d probably go with getting the ISP equipment into the dumbest mode possible, and putting your own router in it’s place, so option #2?

I know nothing about eero stuff, but can you maybe also put it into a mode that has it doing wifi-only, and no routing/bridging/whatever?

Then you can just leave the ISP router in place, and just use them for wifi (and probably turn off the wifi on the ISP router, while you’re in there).

Something that’s made shockingly unclear, for anyone who might be interested: you only need to have subscribed for a single month to have all the subscriber gated stuff unlocked.

I don’t really know how that’s a viable business model, but pay $14 or whatever, get all the expansions and inventory and whatnot unlocked, and then don’t worry about it until there’s another expansion you want.

Heh, I started another playthrough last night myself.

Never really gone through the Republic storylines, so I guess I’ve got a bit of game time ahead of me…

A generative AI company ripping everyone off? Say it ain’t so!

Then the correct answer is ‘the one you won’t screw up’, honestly.

I’m a KISS proponent with security for most things, and uh, the more complicated it gets the more likely you are to either screw up unintentionally, or get annoyed at it, and do something dumb on purpose, even though you totally were going to fix it later.

Pick the one that makes sense, is easy for you to deploy and maintain, and won’t end up being so much of a hinderance you start making edge-case exceptions because those are the things that will 100% bite you in the ass later.

Seen so many people turn off a firewall or enable port forwarding or set a weak password or change permissions to something too permissive and just end up getting owned that have otherwise sane, if maybe over-complicated, security designs and do actually know what they’re doing, but just getting burned by wandering off from standards because what they implemented originally ends up being a pain to deal with in day-to-day use.

So yeah, figure out your concerns, figure out what you’re willing to tolerate in terms of inconvenience and maintenance, and then make sure you don’t ever deviate from there without stopping and taking a good look at what you’re doing, what could happen if you do it, and coming up with a worst-case scenario first.

What’s your concern here?

Like who are you envisioning trying to hack you, and why?

Because frankly, properly configured and permissioned (that is, stop using root for everything you run) container isolation is probably good enough for anything that’s not a nation state (barring some sort of issue with your container platform and it having an escape), and if it is a nation state you’re fucked anyways.

But more to your direct question: I actually use dns scopes and nginx acls to seperate public from private. I have a *.public and a *.private cname which points to either my external or internal IP, and ACLs in the nginx site configuration to scope where access is allowed.

You can’t access a *.private host outside the network, but can access either from inside it, and so (again, barring nginx having an oopsie somewhere) it’s reasonably secure and not accessible, and leaves a very clear set of logs (and I’m pulling those logs in and parsing them for anything suspicious and doing automated alerting if I find anything I would not otherwise expect) so I’m happy enough with the level of security that this is, when paired with the services built-in authentication options.

When you say you ‘can’t access local devices’ is it just via the browser, or can you also not ping/telnet/ssh/whatever?

100% agree: I’m just saying that the guy at Funko might not have been aware of what these farms do, at least the first time because the sales powerpoints and what they actually do aren’t even in the same universe.

The next time though? Fuck 'em, they’re complicit.

If you don’t read the man pages, we’re going to ban you from the chat.

They did it at their general direction, but almost certainly not at their explicit instructions.

These takedown factories use ‘how much shit we got taken down’ as a metric, regardless of what it actually was, and LOVE spamming out thousands and thousands of reports at providers until providers do what they want and take shit down.

My personal favorite one was a bunch of morons who didn’t understand how IPFS gateways worked, and would send literal, actual, we-counted thousands of reports over pirated ebooks that were “hosted” on the gateway.

Except, of course, this isn’t how any of this works and while we did push back and argue over months and months about this, not every provider is willing to invest the time it takes to fight these shits.

Also, if you want super giggles, you should look up the standard text that Web Sheriff sends, which claims all sorts of human right volations and human slavery offenses when someone infringes a trademark for their customers. Absolutely unhinged, and there’s dozens and dozens of these companies filling up your average provider’s inbox every day knowing full well that just being annoying ENOUGH will get them a +1 in the takedown metrics.

It’s really got nothing to do with what Funko might actually really be after, and everything about how they can bill Funko more while just using automated scrapers, automated webforms, and people in the Philipines or similar making pennies to just reply to providers with pretty much the same script until the hosting provider gives up fighting and does what they want just so they’ll go away.

Better performance, but only for gay games, such as uh, well uh and um…

[Edit] I’ll have to see if I can find the video.

I can save you the time there, at least: https://youtu.be/hiwaxlttWow

There was a recent video from everyone’s favorite youtube Canadians that tested how many USB devices you can jam onto a single controller.

The takeaway they had was that modern AMD doesn’t seem to give a shit and will actually let you exceed the spec until it all crashes and dies, and Intel restricts it to where it’s guaranteed to work.

Different design philosophies, but as long as ‘might explode and die for no clear reason at some point once you have enough stuff connected’ is an acceptable outcome, AMD is the way to go.

generally replaced by systemd’s journald service

Basically this, and quite a long time ago. Anything even remotely modern (and by that I mean like, the last decade or so) is either using systemd, or in the case of debuntu, rsyslog.

Wonder what kind of funky environment is using syslog-ng, and to what scale so that there’s literally a ‘syslog-ng engineer’ job posting.