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

Yeah, I remember the ‘grandma wanted to die for the economy!’ ghouls.

And the ‘it’s just a flu!’ people pissed me the fuck off. Like have you morons never HAD the flu? It’s not like the flu is somehow pleasant and fun. You don’t want the flu! Nobody wants the flu! You idiots got a flu shot, get your damn covid shot.

Okay so you’re able to access it via the IP it’s hosted on, but NOT via the domain name in the tunnel?

Is the working IP a public or private one?

My $5 is that you don’t have the tunnel configured properly and that’s why you’re having issues, but maybe not.

Also, what specifically did you put in the config file? Usually they’re not asking for an IP, but the FQDN of the site.

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

Are you using Cloudflare as DNS, proxy, or via their argo tunnels? (I know you said tunnel, but then mention accessing via IP address, so I’m not entirely sure what you’ve done.)

Kinda changes what you should be looking at.

The problem was it was too quick: if you died of COVID, you were dead. You could be memory-holed and everyone would simply forget you and move on.

If you had Polio, though, you were paralyzed and stuck in a metal tube and kept alive.

Can’t forget your not-dead kid who lives in a tube, and thus it was treated as more of a thing that should be fought because there was a clear and visible reminder of what this disease was doing to everyone’s kids.

If COVID left a couple million people living in tubes, then we absolutely would have treated it differently, but it didn’t.

(Alternately, if COVID had killed 10 or 20 million people, we would have also treated it seriously: it just wasn’t sufficiently deadly OR left a wake of broken, but living, people.)

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?

Or if you prefer to be a lot more cynical, he Old Yeller’d it, but he burned it’s equity to get himself elected Co-President, and is worth like a hundred billion dollars more than he was before he did that.

So really, it was a Very Wise and bigly Smart business move.

I’m in the same boat, with a Quest 2.

My plan is to use it until it’s no longer working, and then replace it with something from someone else, assuming civilization still exists by then and my desire for higher-resolution Beat Saber is still a concern and not scavenging for food, or fighting the raiders or whatever the hell.

I don’t get the ‘oh throw it out and buy a thing that’s not from that bad company!’ responses: that’s the same dumb shit that led to people breaking beer and burning Nikes, which I can assure you nobody gives a shit about as they already have your money.

As I’m not a subject of the British Empire, I went and read what that law does and wow, is that a flaming pile of shit.

They basically said anyone who has a thing online that allows “user to user” communications is now subject to all sorts of bullshit, which includes social media companies, but also catches your blog because it has a comment section because they didn’t even remotely try to carve out an exception for an individual doing a thing.

Can’t imagine this’ll do anything other than make people who can bail on the UK to do so (hosting is pretty fungible, and it’s not like you can’t host elsewhere that’s still close enough to the UK to be fine) and screw with UK citizens and residents access to and ability to provide online shit.

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.

You kinda missed the most important detail: they’re competing with the mid-range (and yes, a 4060 is the midrange) for substantially less money than the competition wants.

I know game nerd types don’t care about that, but if you’re trying to build a $500 gaming system, Intel just dropped the most compelling gpu on the market and, yes, while there’s an upcoming generation, the 60-series cards don’t come out immediately, and when they do, I doubt they’re going to be competing on price.

Intel really does have a six month to a year window here to buy market share with a sufficiently performant, properly priced, and by all accounts good product.

Head to the lemmy github and subscribe to the releases email and you’ll get one when a new version is out.

(And, unlike SOME projects I’m subbed to, they don’t do anything that generates a ton of spam, so it really is just one-email-per-release.)

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

I’ve become a fan of staying one version behind for a month or two, unless there’s a security issue that is involved in which case I’ll patch.

I like it when someone who isn’t me finds out the catastrophic breaking issues and has to do the cleanup, and I’ll wait for the fixed version. :P

You mean “Fuck you, getting my full bonus” right?

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.