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.

Sure, but the way this usually works is that the government tells you to do something and if you don’t, they’ll find someone (or a couple of someones) on that list, arrest them, and charge them with a crime.

Doesn’t matter if they did the crime, and it doesn’t matter if they’d be convicted, but the play is to keep your friends in jail until you capitulate to what they want. This is actually something that’s happened with tech companies before, like what they did with GoDaddy’s C-level in India.

The problem is that there’s no damn way I’d want to be arrested by the upcoming US administration, because I’d bet $100 that their playbook will portray not doing what they’re demanding as a national security or terrorism offense, and if you’ve been watching ANYTHING for the last damn near 25 years, that’s a free pass for them to basically just vanish you until they feel like doing otherwise.

It’s fantastic leverage against organizations that have US people and are, presumably, not willing to just let their friends spend who-knows amount of time in prison, and could probably result in some cooperation.

And I’m about to both get downvoted and WELL AKSHULLY’d about how you can’t just vanish people under the US justice system, and sure, you’re technically correct. Except we’ve passed law after law after law since 9/11 that have basically given the government the ability to do any damn thing they please if they call you a national security risk or terrorist, up to and including Gitmo, in case you’ve forgotten that existed: which you shouldn’t have, because we STILL have prisoners sitting there.

This is doomer as fuck, and horribly unlikely, but so is a demand to stuff backdoors into everything. But, if we head down that road, the only safe software will be ones that can’t be blackmailed like this which is essentially none of the major projects.

Well, yes, it does: https://www.debian.org/intro/organization

But the corporation that handles all their funding and owns their trademarks is in the US, so they’re possibly subject to the same pressure. And of course a good number of those people in that org tree are in the US, so again, same issue.

My point was more ‘this is silly, because if you REALLY think that, there’s nobody and no project that’s got any ties at all to the US that can be considered safe, and you should maybe get rid of all your computing devices now’, rather than an intent to say that Debian or anyone there is at more or less risk.

So uh, if I can ask, why?

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

I mean, if you want to carry that line of reasoning out, the Linux kernel is governed under a US-based foundation, so should the kernel itself be suspect?

How about FreeBSD? Or something like Debian? Or Ubuntu, which isn’t US-based but they’re in a typically cooperating jurisdiction?

You’re def being paranoid and somewhat irrational, since it’s unlikely to happen and if it did, it’s not like you could trust anything at all anyways.

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.

you may see your mom

I hope not. I’ve got a strict no-zombies policy, and I’m certainly not violating it for her.

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

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?

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

I’m on year 5 with 6 of them and they’re all fine.

RTSP stream to frigate, and then frigate does the magic AI and recording shit.

They’re also not allowed outside the LAN and don’t seem to care about not being all internet connect-y, though YMMV on newer models.

I can’t think of a single case of being annoyed with them other than the mounting pressure is a little wonky and a sufficiently fat corvid can land on them and change the angle on one of the ones in the backyard but I’m not sure I’d blame the camera manufacturer because of a fat crow.

I’m a big fan of using model paint, like you’d go buy for, well, models or your Warhammer stuff.

Small bottles, literally any color you could ever possibly want, and it’s easy to work with because it’s designed to be used on tiny little plastic things anyway.