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.

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”

Haven’t seen RTFM casually dropped in conversation online in… um… a while…

You’ve been hanging out on the intartoobz at least as long as I have. Circa the paleolithic era, or so…

sed harbors no demon beasts, in my experience.

On the other hand, by default using sed -i is where the demons come in.

No, sed, NOT in place. Not the first time. Show me what you want to do based on the instructions I gave you, and then we’ll talk about letting you play with the real data.

With ya. I smoke an odd brand that’s hard to get, in a state that (rightfully) taxes the shit out of them.

Still costs me an even C-note every two weeks, same as always. Have I cut back, probably. But mostly because I’ve started to face my own bullshit instead of expecting smoking to fix it for me.

I straight up enjoy my Kamel Reds, and while I don’t want to model that to the next generation, I’m the better part of thirty pack-years in.

I can either take the risk, or downright break all the other mental health progress I’ve made. Since I have a wife and some folks I care deeply about in my life, imma go with the mental health.

For unrelated reasons, I once was an unmitigated SOB in any interaction. On the rare chances I’ve been in hospital, I’ve been miserable.

Right or wrong, I prefer to communicate with people rather than attack them, and quitting now would not help that.

RJR can have my money, they won’t get the next genration’s money. We have dispensaries, video gaming, and casinos on every corner in my state. My choice of vice could be far worse, and I’m kind of grateful that I settled on smokes, and not gambling.

As part of a much larger project that was all-in on Java to begin with, I’ve used Tomcat to serve pages and PDFs/office doc formats rendered based on a postgres backend and FreeMarker templates.

For these purposes, you don’t want that level of complexity (or Java) but the general premise and template libs should be available in nearly any sane web programming language.

She’s fallen off my feed, unfortunately. Pardon me while I go enable notifications.

It’s amazing how many companies rely on a crazy amount of FOSS libs, etc.

In the relatively recent past, a boss who I had software PMd for across numerous years had the unmitigated gall to ask me for a list of licenses for “all the software we used.”

I literally laughed in his face, explained open source and the rabbit hole such a question goes down, and he just couldn’t (wouldn’t) get it.

Unfortunately, the biz side of the house doesn’t like “yeah, it’s all legal, but fuck you if you think I’m documenting every piece of code in every library in a ten plus year old code base, allllllll the way down.”

Thank you for the TL;dw. Sincerely appreciated.

Used it in a pinch once, and realized how incredibly awesome it is. Now, it’s my go-to.

Haven’t tried data and files on same stick, but…. Now I want to.

Not aware of a FOSS 1:1, but that sounds like Ghost or your blogging platform of choice.

Except WP, if self hosting, IMHO. Wordpress == PHP == trouble and risk. I don’t mean to malign WP specifically, but if you’re a noob, you want to avoid exposing PHP to the public internet - especially if there’s any possibility you’ll eventually forget about maintaining and upgrading.

Just too damn easy for some threat actor to come along and exploit a vuln you missed, in the software or the web server or WP.

That said, years of WP taught me that, roughly, you want “pages” linking to “posts” ( == chapters). In theory, the former is a permanent reference and the latter is dynamic to some degree.

In reality, the existence of search engines before enshittification means the two have been conflated frequently.

Pages would often get links in a sidebar or menu. Posts might get buried much farther down, but can also be linked to. They’re often, but not always, time—specific.

“2023 NY [financial product] Guide” (page) might well link to a years-old post about subrogation regarding an attempted BBQ of a random wild animal that went wrong and caused a fire, because it’s a positively classic example of the same that makes a great deal of sense to most people, even if they don’t understand terms like subrogation.

Post/page are distinctions that WP makes, but are abstractly relevant to setting up abs any CMS (which is what you want, Content Management System) so that you (ideally) never have to figure out how or where to link something, its just native. Changing the structure means changing the URLs which is annoying at best, and fraught with peril at worst.

Above 2023 xxxx Guide page, would be https://example.org/NY-Xxxx-Guide and that way you DGAF about the sidebar links, for instance. Link it once, and then you only have to update 50 posts with the year and/or some change in the data, which can be done programmatically in the db as a trivial exercise. “UPDATE page SET title = (SELECT title FROM… WHERE ‘2022’ in title TO ‘2023’;”

Disclaimer: do not run that query as copypasta, it’s meant to illustrate a point and not to exhibit valid SQL on any db (Not least because I intentionally left out at least one closing paren and simplified a bit. I’m a PG guy, and I am 100% certain it would fail as written, but fully expect anything approaching the standard to reject it. But you get the idea, update 50 states at once with a fairly simple query, once a year.

Lots going on here, but go for a modern CMS and repeatable updates, not a legacy product with a bunch of tech debt accumulated. Build it clean, plan it out first, and know whatever DB is backing it fairly well.

Migadu has been amazing. It “”just works,”and there’s no reason to deal with any of the crap that comes with hosting email.

They are affordable, and provide exactly what they claim to provide.

Email is not - IMHO - worth the trouble to self host. There are too many hard stops where email is required as login, etc to bother.

I enjoy hosting and using a variety of services. But I’ve no desire to bother with something I can ship out to folks who live and breathe that particular service.

Only reason dd hasn’t bitten me is that in my head, if and of make perfect sense as input and output.

Doesn’t mean I won’t make that error tomorrow, ofc. But I tend not to alias except harmless stuff to avoid that very problem.

I have this exact use case on a work machine, because the proxy flat refuses to prompt for the login, just goes straight to deny.

I own neither the proxy, nor the steaming heap of code that lives behind it, and I’m grateful for that every single day…

The same has occurred to me numerous times. I’m not the guy to lead the project, but I’d certainly be willing to dive in and help.

Honestly, I’m somewhat surprised there isn’t one, or at least a zygote of one, already.

That’s the one I had in mind.

If the clock is off (bad CMOS battery, as others have noted); and there is a password “max age” setting that’s intended to be far, far, far in the future…

Well, your clock being off by a few hundred years might well trigger the (intended never) expiration setting.

Malware is a possibility, but I lean towards the date being the cause rather than an effect.

Gut feeling: Nope.

Further reflection, for those who remember a certain video game in the CGA error (not V, C)

“Here’s tae us, who’s like us, damn few, and they’re all dead. “

It just freakin’ works, which is a real benefit in our world.