ArchiveBox is great.

I’m big into retro computing and general old electronics shit, and I archive everything I come across that’s useful.

I just assume anything and everything on some old dude’s blog about a 30 year old whatever is subject to vanishing at any moment, and if it was useful once, it’ll be useful again later probably so fuck it, make a copy of everything.

Not like storage is expensive, anyway.

Oh, that makes sense. I was trying to mentally imagine what kind of FDM printer could possibly need that much power and was very much coming up with a blank, lol.

I’m disappointed in that writer.

Better phrasing: Sega started as a rock’n’roll breath of fresh air that did what Nintendon’t.

Perhaps it’s just me, but they’ve been releasing a good number of actually good things, though?

Persona, Yakuza, PSO, and even the fact the Sonic movies were… good? Or at least entertaining enough, which is a victory for a video game movie series, heh.

So uh, if I can ask, why?

Like what are you doing that needs this kind of uh, upgrade?

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.

Time to rename the blue shell to The Shell of Equity, I guess?

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.

The best way I’ve heard that described is that for the Bambu stuff, you spend your time fiddling with the thing you want to print, not your printer.

I love my p1p (and it’s several thousand hours and 100kg of filament into ownership and all I’ve had to do is clean the bedplate and replace a nozzle), and really wish there was anyone who was making an open-source printer that’s as reliable and fiddle-free as this thing has been.

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).

And if you fried your food in lard like God intended, this wouldn’t have happened.

(Also screw things that need phone apps to function and especially screw phone apps that then ask for every permission they possibly can hoping people just spam ‘fine whatever, i just want to make dinner’ as the response.)

(/s, kidding, etc.)

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…

It’s true, because you could in theory go play the other aspects of the game when you’re done fishing.

You won’t, but you could so that makes it a better game.

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?