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.

Now I’m thoroughly intrigued. Source would be appreciated.

Thanks - it’s a shoulder, so one of those “Either live with bone-on-bone pain for the next 30 years, or get the surgery and hope” kind of deals.

I had an unexpected… medical detour that delayed getting the shoulder done, and you’re 100% right about things being compensated for. The shoulder was planned for a couple of weeks ago, and then some other stuff happened, and I’m noticing simple things like using I can use my other hand to turn a doorknob, but then need a foot to actually push the door open - until I was recovering from something else and cognizant of additional pain, I had no idea I’d even been doing that sort of thing.

All other things being equal, after surgery and PT, I’d be happy with getting back to around 80%. At that point, the (relatively weak, apparently) joint will be able to save my tail in a pinch. - right now, I am sworn off of all alcohol and any meaningful activity if I wake up in the middle of the night because if I fall and further damage the shoulder, it gets exponentially worse. Not that I’m planning to be a falling-down-drunk post-recovery, but it’s the principle of it. Just walking outside for a smoke before going back to bed requires some thought and risk consideration. It’s a whole new world I’d never even considered.

This is incredibly interesting. Gives me a bit of future hope as well. About to have a joint replaced, and the doc was very clear the operation may well need to be “revised” in 10+ years.

I acknowledge and accept that risk, of course. But if we can regenerate cartilage (in that very specific context), revision could look more akin to removing the joint socket liner and replacing it with new cartilage by then.

Or by the 20 year mark - let’s be honest, I’m in my 40s so having a second revision is not out of the question at all, if I’m otherwise in acceptable health.

Even if the (smashed) ball side of the joint has to be straight replaced again at that time, half the surgery is better than all of it.

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.

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…

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.

A hard timeline on commit strikes me as less than ideal.

People are people. They have issues, they screw up, but they still write good code.

Seems like a brutal metric that encourages minimal commits without real change.

There’s an SOL on rape in most scenarios.

But no statute of limitations on copyright violations? WTF?

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.

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.

Open source wheelchairs; and a community of variously abled makers who can come together and build assemblies that are “not medical devices” but come together easily into something that could be used as such.

Speaking strictly for the US, and as a non-lawyer - I’m inclined to think that an open source wheelchair would probably sail right through the 510k process, but… Still doesn’t make that process cheap by any means.

I’ve had similar thoughts re: CPAP/APAP machines, neither the SW nor the HW is brutally complex / poorly understood. Pretty straightforward stuff mostly. But trying to distribute a thing like that even as plans is just asking for a C&D from the FDA, I’d expect.

Try it all. Keep good notes.

Some service names are marginally misleading, but understanding what it does and how it bills does two thing: Helps you avoid overbilling; and also ensures you “get” it.

Properly secured and understood, S3 + immutable saves my ass more than o once because could prove that as of x bi-hourly backup, PG reflected some given status.

In other words, “I did not fuck that specific thing up, and as of the last time I was in good faith awake, it looked like x. Let’s look at logs/code, bc last I saw it, it mapped perfectly to reality.”

The bit about “keep good notes,” above, is for future you.

“Oh yeah I played with that random AWS service a few years back, wish I could recall the outcome,” vs “Mind giving g me a sec to have a look at my notes, I’ve seen this before!”

That translates to execs as “Yep, I follow, and u have ref material from the last n times I solved this problem, so I’m your guy, I just need a sec to locate the details of the last round before I straight up commit to an answer.”

Appreciate you pointing out those examples - while one could argue errors in judgement, going with what one knows allows for getting stuff done NOW.

Have to say, FB and G examples resonate most with me because while Java is hardly “rapid,” given a well-defined objective I can bang out PHP or Python to accomplish it quickly, and then iterate efficiently.

That was doable long before the idea of iterating quickly / failing big / etc entered the public consciousness. Just not in Java…

So glad to hear that - it’s the humans in the process who make it possible.

I know a guy who once gave his probation officer a UPS store box, and they didn’t even blink. For the thrity bucks or so, it was well worth it. Not once did said PO knock on my friend’s door a couple states away, and all was right with the world.

Also, congrats on the giant pair it takes to sa 'yeah, homeless, but look at me, I’ve got my shit together - because I’ve a place to stay, and your def of homeless is very different from mine."

Are they based out of the PNW? Now that I think about it, I may actually have interviewed with them at one point.

ETA: Yeah, pretty sure it was them, they’re PT and have a 425 DID for sales, and the company name is wholly unrelated to the product. Had forgotten about them entirely, and would have had the same reaction as OP to getting that email now.

And it probably is the sw product the email was referencing, since Bartender is capitalized.