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

help-circle





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


  • I grind and have other issues, use CPAP, and use semi disposable mouthguards to help w the grinding at same time.

    Invasive is a pretty strong term for this case, I would class neither one as such. The Inspire implant is “invasive,” by definition, given context.

    OTOH, the mask was difficult to adjust to for me, and my wife’s “encouragement” and justifiable pushiness is big part of why I’m a reasonably successful mask wearer.

    On my own, I would have tossed it out the window quickly! But I’d say the same thing re the disposable mouth guards, TBH. She intro’d me to them and I wasn’t a huge fan initially. But the difference it made after a few days was significant.

    Ultimately, all three solutions exist because none are perfect for everyone.

    Worth noting there are a handful of large dental practices shilling those mouthguards because $$$, but same is probably true for both the mask and the implant.

    Incidentally, I’m currently in physical therapy recovering from an unrelated issue and it’s really made clear to me that for me, the mask is way better than implant. PT is a bitch, and that’s for an injury rather than surgery. But that’s me personally - it seems mildly disingenuous to throw around terms like “invasive” here, though CPAP is certainly a major adjustment and takes real work to get used to.



  • ____@infosec.pubtoSelfhosted@lemmy.worldCustom Domain Email
    link
    fedilink
    English
    arrow-up
    5
    ·
    2 months ago

    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.





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


  • Yes - you’ll be well-served by the ThinkPad line in general. My first permanently dedicated Linux machine was a T430 and true to form things largely “just worked.”

    That was enough years ago that I might well have needed to seed the network drivers on the usb key, and that was the worst of it.

    They’re tanks, and the hw is generally easy and fairly intuitive to swap out the usual memory and HDD.

    IIRC my first distro on that was Debian, had plenty of docs about the intersection of the distro and ThinkPad line.

    Mint should be perfectly fine given that.

    I will say that I try not to do fresh installs on unfamiliar hardware w/o some other available form of connectivity, my phone mostly is quite sufficient for the purpose. It’s just easier not to risk putting myself in a difficult position in the first place.

    You’re in for some fun.


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


  • No harm enjoying a distro and being stable.

    I’m a fan of Arch and derivatives but I need better odds of shit just working. Been running Mankato on desktop for some time to get both stable ish packages and also AUR as/where needed.

    For servers, it’s Debian all the way for me. Ubuntu does some things I don’t personally love - no offense to the distro, it’s well constructed - and the recent ish changes in the RPM world didn’t sit well with me - strictly personal opinion.

    Anything in a container generally runs on whatever the image was built with. It’s only a minimal pain to port simple dockerfiles, but when you get into multiple linked containers, that risks edge case bugs down the road.

    Honestly, between the lot of it, I use a pretty representative sample - I think alpine on desktop would be kind of pointless to say the least, doesn’t mean I’m going to forego any container built on it.

    Use case is a huge factor here, as is ability to grok multiple distros concurrently. I find that easy, but plenty of people don’t. For them, maybe rebuilding that image makes more sense.

    Linux is all about doing what works for you and your use case.

    FWIW, pacman doesn’t resonate nearly as well as pamac does with me. Probably because I haven’t had to dive deep into it. All about what works for an individual. If that’s stability on an Ubuntu derivative, great - Linux is Linux, in that context.





  • For my use cases at workstation level, Manjaro makes it really easy to work with whatever tooling I need - but I’m comfortable on CLI and aware of the risks/benefits.

    Wouldn’t suggest it to a noob, ofc, but for me it’s a good middle ground where I can get things done, and also easily work with edge cases.

    Not that I can’t build whatever I need to in the deb world, but I prefer to work with instead of against a distro’s packaging.