• 0 Posts
  • 17 Comments
Joined 9 months ago
cake
Cake day: September 26th, 2023

help-circle



  • That source is garbage.

    Seems to be based on what amounts to a single “does not currently appear that the procedure itself killed him” statement from MGH, which is generally respected.

    I will wait for the actual journal article that (I sincerely hope) is yet to come.

    Five years, and an additional two months following consent from a highly experimental and unique procedure that he appears to have given informed consent for because he would otherwise have died sooner beats the hell out of five years without the two months.

    I could make a hell of a lot of amends in sixty days, knowing it was all I had, that I’ve had trouble making in four plus decades…. Which would make the end exponentially more peaceful and pleasant.

    Anything that gives me that much time is a net positive. Not going to bother with some of the usual surgical recovery stuff if I am fully informed at that point but… Don’t want to die wishing I had had time to make that one phone call or txt that I didn’t quite get to make because we don’t get to choose the moment.

    Ten yrs from now hewill be a hero for undergoing the procedure that leads to real progress.


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




  • Boxes that physically live in my home are mostly Manjaro. They’re also not externally accessible from the internet.

    Anything in the cloud I standardize on Debian. Two distros and consistency makes maintenance much easier.

    Anything in a container runs whatever it was built on because porting a docker compose file from, say, Alpine to anything else is just not worth the time and energy.





  • While my primary masto is a single user instance, basically anywhere else I exist on the fedi is a subset of infosec dot *.

    Those instances are all run by someone who a) is cool with spinning up a whole bunch of instances, b) is willing to risk the costs, and c) is excellent at delineating policy. There’s a “no fucking threads full stop” instance, and a “no threads by default, but user can flip switch” instance, for example.

    That’s a method of operation that works from my pov but doesn’t suit everyone’s needs. Personally, I want nothing to do with threads but am more able to express my anti corp tendencies than I was in my twenties, and I’m more willing to accept that “it’s just bandwidth, find the instance that meets your needs.”

    My needs involve no threads at all, but I can accomplish that with a very small amount of effort given. My circles.





  • When Borat was fresh, I was in a new hire class for a major telecom you’ve heard of if you’re in the US.

    Somehow, the chatter came around to Borat, and someone challenged me on the existence of Kazakhstan.

    I’m not always great with people , so I did a double take - they were serious. I shipped them a GMaps link via chat…

    …and they proceeded to argue with me that said country couldn’t possibly actually exist.

    Once in a while, I wonder where that person ended up - no Ill will towards the misinformed, but I’m certainly curious.