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.

It is mostly professional/office use where this make sense. I’ve implemented this (well, a similar thing that does the same thing) for clients that want versioning and compliance.

I’ve worked with/for a lot of places that keep everything because disks are cheap enough that they’ve decided it’s better to have a copy of every git version than not have one and need it some day.

Or places that have compliance reasons to have to keep copies of every email, document, spreadsheet, picture and so on. You’ll almost never touch “old” data, but you have to hold on to it for a decade somewhere.

It’s basically cold storage that can immediately pull the data into a fast cache if/when someone needs the older data, but otherwise it just sits there forever on a slow drive.

…depends what your use pattern is, but I doubt you’d enjoy it.

The problem is the cached data will be fast, but the uncached will, well, be on a hard drive.

If you have enough cached space to keep your OS and your used data on it, it’s great, but if you have enough disk space to keep your OS and used data on it, why are you doing this in the first place?

If you don’t have enough cache drive to keep your commonly used data on it, then it’s going to absolutely perform worse than just buying another SSD.

So I guess if this is ‘I keep my whole steam library installed, but only play 3 games at a time’ kinda usecase, it’ll probably work fine.

For everything else, eh, I probably wouldn’t.

Edit: a good usecase for this is more the ‘I have 800TB of data, but 99% of it is historical and the daily working set of it is just a couple hundred gigs’ on a NAS type thing.

I’ll admit to having no opinion on windowing systems.

If the distro ships with X, I use X, and if it ships with Wayland, I use Wayland.

I’d honestly probably not be able tell you which systems I’ve been using use one or the other, and that’s a good thing: if you can’t tell, then it probably doesn’t matter anymore.

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.

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.

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

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?

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.

Might have been unclear; I listen basically exclusively to spoken word stuff. Podcasts, audobooks, “raido” plays, etc.

The Airpods actually sound remarkably good and clear (and ANC helps a lot with ensuring clarity anywhere even slightly noisy) with voices, so for my uses, they sound perfectly fine.

I have a pile of Chi-Fi earbuds that absolutely destroy them in sound quality for music, but it’s very much a 99.9% of the time it’s not music situation.

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

They really do.

The sound great, and the ANC is great, but the “official” battery life for a brand new one (which these are not) is “up to 4.5 hours” with ANC on, and 5 without it.

It ends up being 2-3 charge cycles basically every day, plus a full recharge of the charging case.

They do, however, work amazingly well if you’re in the Apple ecosystem; for example they’ll swap between my iPad and Mac Mini if audio starts on one or the other.

But for actually sitting down with something and listening to a thing, I’d rather just plug in some headphones (via the lovely USB-C dongle) and not have to think about if the stupid things are going to die before I’m ready to stop listening.

(Disclaimer: I’m also a weirdo who doesn’t carry a smartphone, and still uses an iPod for listening to stuff outside of the house, so feel free to roll your eyes and disregard my obviously bad opinions :P )

My complaint has always been that the stupid things need to endlessly be recharged.

I’ve got some AirPod Pros and they’re great… for about 4 hours.

Then you’re stopping what you’re doing, recharging for half an hour, and then you’re good for uh, another 3 hours because that wasn’t a full charge.

And after the 2nd or 3rd time you’ve done that, your case is dead and you get to throw everything on a charger for a couple of hours.

Ooooooooor I can put in my wired headphones, and not give a shit about any of that, because that’s not how those work at all.

I suppose most people don’t spend most of their day listening to podcasts and audiobooks and thus 4 hours is fine, but good lord is it annoying as crap.

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?