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.

I like that a great deal, and now I wish I had set things up that way from the start - anything to ‘family.domain.com’ should always audio alert, 100% of the time, regardless of hour of day or silent mode.

The idea of going back and updating 20+ years of accounts and communications and other folks’ address books feels insurmountable, but that’s neither here nor there. No real reason I couldn’t start fresh with a nice, short, simple domain and subdomains for the purpose.

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’m not sure I fully agree with your suggestion of CloudFlare, though your point is well-taken - ten year renewals with nine to fix billing issues is a best practice. Last thing I want is to lose my primary email because I missed a billing email after replacing a card six months ago.

Catch-alls are definitely a win, especially for people who sometimes forget to write down every single ephermeral email address they’ve ever used to sign up for anything with… I like subdomains for email, but only when planned/executed in an intentional way. Has the potential to get out of hand quickly.

I’ve elsewhere mentioned my preferred provider, but it seems to be fairly common that most email providers also offer DNS as part of the package, which makes the whole process much simpler.

Migadu is relatively private, dirt cheap, and dead easy to set up. Supports both web and desktop email clients of choice.

IMHO, TLD matters and always will - the problem is that it matters to varying degrees depending on the destination host, the remainder of your setup, etc. If you’re fastidious about configuring all of the requisite DNS records, etc., it will be less of a problem.

I mostly avoid the newer non-CC TLDs for that reason, and general personal preference. Deliverability is enough of a challenge without adding more work to it, which is why ‘actually’ hosting one’s own email is mostly a toy project, and not something generally done as a serious endeavor. Useful for learning and understanding, of course, but not particularly practical to literally host one’s own email server for ongoing usage in any critical use case.

You’ll find certain providers easier to get your emails through to than others - Hotmail and variants are notoriously difficult, and tend to drop inbound mail at the gate without sending a bounce message, as if the inbound mail just disappeared.

Visible has worked well for me recently - it’s wholly owned by VZW as I recall, and exclusively uses their network. In most areas, VZW is objectively the best coverage of any carrier.

$30/mo and I have yet to see throttling, even with heavy use. It “just works”.

Yes, I’m effectively handing that data to VZW, but I have no illusions that any MVNO I chose would behave any differently. One way or another, they’re all reselling the same 3 carriers, who by definition must have some base level of access to your data.

VPNs go a long way towards mitigating that, but using a carrier is likely to leak some level of data. While I have a great deal of respect for RMS, my own life doesn’t really fit within his internet usage model and I’m forced to make choices. (Sacrifices, really, but informed ones.)

As far as function, they’ve got a nice little package all wrapped up and easy to use. Aside from the group text thing I mentioned elsewhere, it’s a pretty slick implementation. But for a user base of one, with privacy concerns, I’d rather use something that’s a bit rougher around the edges yet more configurable, and more private.

See voip.ms for voice. I can’t speak for specific non-European languages, but I’ve been quite happy with LibreTranslate for my on the fly needs. Setup was dead easy too. (And if you see a lack of coverage for particular languages, obviously your contributions to improve that would be welcome)

Seconding @Tazerface@sh.itjust.works 's suggestion of voip.ms.

I throw them a lil cash maybe once per quarter or so, they maintain a bunch of numbers that I may or may not utilize at any moment, but are just too good to give up, and anything I’m not actively using is set up to send inbound SMS to my email - that way I don’t lose access to multi-factor codes and such, but I’m not trying to juggle a bunch of numbers in some app or other either.

Dirt cheap, ‘just works,’ and they even made porting from GV easy.

Also, by the same token, to de-google your email, I’m a big fan of Migadu. Same sort of scenario - I prepay a lil bit once a quarter or so, have catch-alls set up so I don’t miss random crap from emails I’ve forgotten I created/used a decade ago, etc. A nice, simple solution that also plays well with on-the-fly outbound email addressing, Thunderbird for day to day needs, and webmail.

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.

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

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.

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

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.

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.

How about a headline that’s not pure clickbait.