I'd seriously consider unifi gear, like the other comments seem to have also suggested.
The only thing you don't get is ethernet drops out of the APs or anything like that, but the UAPs in a mesh configuraiton could proabbly do everything you want, unless you have a shockingly large piece of property.
underestimate how much work Mozilla does in standards and low-level shared API’s via w3c
Oh, I didn't mean to disparage the work they do: I know it's important and extensive. I've been a Firefox user since, well, it was called Netscape. It's a critical piece of software.
I was mostly just rolling my eyes at the sheer panic they're having with the only funding source they've bothered to cultivate going away, along with the fact that a good portion of that money is spent on things that aren't the browser, and frankly, don't bring a lot of value to the table or matter in the slightest.
Dumping the Corporation baggage and making the Foundation strongly independent makes a lot more sense than begging to let Google keep paying them, which seems to be their approach, at least based on that open letter.
These drives aren't for people who care how much they cost, they're for people who have a server with 16 drive bays and need to double the amount of storage they had in them.
(Enterprise gear is neat: it doesn't matter what it costs, someone will pay whatever you ask because someone somewhere desperately needs to replace 16tb drives with 32tb ones.)
But the article says they used Yahoo once! (When, I assume, Yahoo outbid Google.)
I agree we need an independent browser, but right now Firefox is about as independent as my cat, and they're both a bit deluded into thinking that's not the case.
The first thing that I have to ask: do we need Firefox-the-business providing Firefox-the-browser, or are they just dragging around a lot of Google-induced baggage that's otherwise worthless.
I have a strong feeling on that one, but hey.
What's your budget?
A $200 budget is going to get you VERY different options than a $1000 budget, especially since you're wanting to connect multiple buildings.
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.
Am I missing something, or is this just the argo tunnel thing Cloudflare has offered for quite a while?
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.
I'm sure an AI babysitter won't be immediately and utterly broken and bypassed by every single kid in these "classes".
(Seriously: we're talking about 8-12 year olds here and the absolutely are smart enough and incentivized to break the ever-loving crap out of this stupid idea.)