What Google password?
I don’t intend to browse RMS-style, but I have zero need of a Google account, nor of the major search engines directly.
I just add layers between myself and that particular company. I still can get their data, but without the creep factor.
Mostly.
It’s an imperfect solution, but I’m more comfortable with access by proxy than direct access.
Content? Hardly.
Disinformation. Lies. Etc.
Sell them to someone who will test and resell them to the airline or medical industry… Manufacturing is a likely customer as well, plenty of legacy equipment there that’s airgapped and still running decades-old hw/sw.
Youtube warning, some Boeing 747s
(This is a wrong answer since you only have a single pack. If you had several cases, you might actually be able to make a buck)
Saw a post on mastodon in the last day or so that someone dug up a network card for the old 486 they had been working on getting back to life. Might be a use case there, as well as in aviation and medicine - fields that move exceptionally slowly and tend to have expensive equipment with long lifetimes.
I use Arch, btw…
Kidding, of course - but there are some of those folks out there. TBF, they’re the vocal minority, but they are vocal nonetheless.
I should have marked mine more clearly as a “first pass” from the start.
Worked with too many hotshot folks to trust future/past humans quite that much.
Once in a while, I’ve even been that hotshot guy. Definitely not excluding my own “oh that was prod…” adventures when I worry about humans, didn’t mean to come off like I think I might have.
But interesting, and certainly worth kicking around.
In green fields projects, this makes a fair bit of sense at initial reading, tentatively.
But new code becomes old code, and then builds on the quality / discipline / cowboy status of the last person to touch the code, in a complex and interlocking way.
I can’t say I’d be excited to find a partially converted existing codebase of this. But in fairness, I’m on my couch on a Sunday and haven’t actually worked through your examples (or read the original paper). I see the benefit to having both types of extensibility, obviously. Just not sure it outweighs the real world risk once actual humans start getting involved.
I don’t know a single person who can’t say they’ve never taken a single “good enough” shortcut at work, ever, and it seems this only works (efficiently) if it’s properly and fully implemented.
The value of my labor, daily.
The nominal “cost” of my healthcare, at every encounter.
Etc.
Dead on, and applicable to nearly everyone.
For me (mid-40s) from a quick glance at the SSA site, I surprisingly wouldn’t take a hit if I started at 62. That assuming it’s a) there and b) not privately invested in some shitshow tying it up, etc., of course.
Tentatively, given there’s no difference between 62 and 68 for me, and I’m not exactly in idea health already, the real motivation for me to work past 62 is the health insurance.
I have no illusion that the ACA or the Marketplace will exist in its current form nearly two decades from now; and Medicare seems to have a hard cut at 65 rather than the age range one could claim SS at.
That three years between 62 and 65, without Medicare, the Marketplace, or employer paid insurance, would be a far larger risk than I’m willing to take, barring a full and complete disability.
I walked away from reddit after Alien Blue had to get pulled, and haven’t looked back.
There are a few niche areas Lemmy hasn’t had a chance to build a community yet - AskHistorians comes to mind - that I miss, but time will hopefully solve that.
Billionaires and rent-seeking companies. There are at least three national companies I can think of who are hoarding single-family homes in major cities and renting them out.
Generally they purchase at scale via REO scenarios, and provide no value whatsoever while driving up prices drastically
One example is a company called “Progress,” no better or worse than the others but with a meaningful web presence if you’re curious.
I distinctly remember that, and the associated horror. Not to mention the risk of fatigue, health issues, and a thousand other scenarios.
I definitively walk differently in e.g., Birks, generic sandals, and generic slip-on closed-toe shoes.
Each one is quite consistent and recognizable, unfortunately, which puts me in a position of few options for working around this sort of technology. If you see me in Birks a decade ago, you’ll know me in Birks today without having to see anything above my hip.
Knew this was coming at scale sooner or later. Something of a concern to me personally, because my own gait is particularly identifiable to those who know me.
Aside from footwear, and possibly using various inserts to change the way one’s foot falls on the ground, I don’t have any obvious thoughts for defeating this unfortunately. The problem with any sort of inserts is that they’re likely to cause other problems over time for the same reason they could theoretically mask one’s gait - unnatural walking tends to be bad for the body on the whole, and to cause more widespread problems over time.
Particularly since most Lemmy instances have (IIRC) built-in image hosting (unless disabled), and there are a wide variety of alternatives as well.
Right there with you on “just works,” as well as the simple fact that the config snippets you need are readily available - either in the repo of whatever you’re putting behind the proxy, or elsewhere on the internet.
I consistently keep in mind that it’s ultimately an RU product, of course. But since it’s open source and changes relatively infrequently, that’s mitigated to a large degree from where I sit.
Nothing against Caddy, though Apache gets heavy quickly from a maintenance standpoint, IMHO. But nginx has been my go to for many, many years per the above. It drops into oddball environments without having to rip and tear existing systems out by the roots, and it doesn’t care what’s behind it.
Ages ago, I had a Tomcat app that happened to be supported indirectly by an embedded Jetty (?) app that didn’t properly support SSL certs in a sane way on its own.
That was just fine to nginx and certbot, the little-but-important Jetty app just lived off to the side and functionally didn’t matter because with nginx and certbot, nothing else gave a crap - including the browser clients and the arcane build system that depended on that random Jetty app.
I do not know why these two concepts are so frequently conflated and misunderstood, but they absolutely are.
Thanks for the solid clarification. At-will and RTW are two very different concepts, and off the top of my head, forty-nine of the fifty states are at-will. The 50th state isn’t all that different (MT), just a bit nuanced: “Montana defaults to a probationary period, after which termination is only lawful if for good cause”
IOS presently, partially to simplify de googling.