• 1 Post
  • 80 Comments
Joined 1 year ago
cake
Cake day: September 26th, 2023

help-circle



  • At one time, Reddit (or at least the core server) was open source. Statistically, it’s relatively likely that someone, somewhere forked and is maintaining that code for their own purposes to this day, but I’m not actively aware of any examples.

    If someone has been maintaining a fork, I’d love to see the old comment database imported into it and made available, though I don’t know offhand what license either the code or the comments were released under.

    A FOSS Reddit, without the chaos that took over America during the presidential administration installed in 2016, and branching from there, would be an interesting point of diversion to say the least.

    Edit: quickie DDG search found me one fork archived in 2023 and a further form updated a year or so ago. That’s recent enough the damn thing just might build with a little work.

    2023 fork of open source reddit

    ~2024 fork

    I’m sure there are others…






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






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