The year is 2006. I’m complaining on my blog about businesses training their customers to fall for phishing attacks.

The year is 2011. I’m complaining on my blog about businesses training their customers to fall for phishing attacks.

The year is 2022. I’m complaining on my blog about businesses training their customers to fall for phishing attacks.

Corporations haven’t learned. Unfortunately, their customers have learned from all this training. And so has the fraud industry. Even if you’re usually savvy about this sort of thing, you can get caught up if the circumstances put you just off-balance enough to line up the holes in each overlapping layer of security.

I trusted this fraudster specifically because I knew that the outsource, out-of-hours contractors my bank uses have crummy headsets, don’t know how to pronounce my bank’s name, and have long-ass, tedious, and pointless standardized questionnaires they run through when taking fraud reports. All of this created cover for the fraudster, whose plausibility was enhanced by the rough edges in his pitch – they didn’t raise red flags. Cory Doctorow on “Swiss-cheese security.”

And here I am, in 2024, complaining on my blog about…well…you know.

Option 1: will do some things you want, and some things you don’t.

Option 2: won’t do anything you want, will do all the same things you don’t want that option 1 will do, has promised to do more things you don’t want, undo the things you wanted that have already happened, make it more difficult for you to even have these choices in the future, and has previously demonstrated that they’re willing to go through with all of the above.

And yet I keep seeing people say they’re the same picture???

Really????

It’s like…you need to hire someone to fix your heater. One contractor will fix your heater for the advertised price, but break some of your windows in the process and stop taking your phone calls. The other will rip out your entire heating system and your plumbing, and steal the copper phone lines to make it hard for you to call someone else (I know, outdated metaphor), insist that you broke it yourself and charge extra. And they’ll break your windows too.

A bunch of reviews point out that both of them will break your windows, so they can’t be all that different, right?

It would be great to find someone who would fix your heat without breaking your windows! But there’s a glass factory in town that wants more business and gives all the local contractors kickbacks, so your best bet for that is to hire someone from out of town…but they’re booked until summer.

So you can either go with the one who’ll break things even more, or the one who will fix some things and break others, and then deal with the breakage while you still have heating, plumbing, and a working phone.

The “bipartisan” immigration bill currently in Congress is a right-winger’s dream, but since Trump wants to run on anti-immigration, the GOP is suddenly opposed to it, arguing that it’s not draconian enough.

Nothing will ever be cruel enough for them, no matter how much Democrats do to appease them. Biden could do everything they asked for, and they’d still insist he was being soft on border control. They need it as a wedge issue. Appeasing them won’t win any points with their base, and it’ll alienate those on the left who want asylum seekers and immigrants in general treated like the actual human beings they are.

This bill is probably DOA at this point. But just in case, I sent a message to my rep advocating for more protections for asylum seekers, not less.

Since I started converting parts of my website to use 11ty as a static site generator, I’ve been able to automatically generate tag and category pages that are *just there* as plain html files. And since they’re plain HTML, the old local site search engine I have on there still finds all the Eleventy-generated pages. And again since it’s all static, it doesn’t go down when the database does (which has been happening on an annoyingly frequent basis lately).

And this would be perfect if I was using a single Eleventy instance to build the entire site, but I’m not. I’ve got separate instances building the Les Misérables blog, the reviews, the tech tips, the creative writing collection, and so on, plus I have this WordPress blog and a bunch of hand-coded HTML from the old days.

Which leads to a few problems:

  1. Tags are per-section, not universal.
  2. The site search, which indexes html files on the server, sees everything except the WordPress posts, and the WordPress search *only* sees the WordPress posts.

Some ideas I’ve had to combine the tag pages:

  • Rebuild everything in a single Eleventy instance with a deeper hierarchy. Upside: Still static pages for everything except WordPress. Downside: Time-consuming, still leaves the main blog separate.
  • Write a post-build script that combines all the the tag pages from each subsite. Upside: Same. Downside: Need to either run on the server or make sure my local copies of the *other* subsites are current.
  • Write a server-side page that combines the backend HTML pages into a dynamic frontend for only the tag being viewed. Upside: simple. Downside: tag pages now depend on PHP.
  • Write some client-side JavaScript for the tag pages that will check whether other subsites have tag pages, and add those to the end of the list in a “See also…” section. Upside: simple, and the “local” tag pages are still usable as long as I make sure the script doesn’t block anything. I could even have it check the other static subsites first and then check the blog, so if the blog times out I still display everything else. Downside: requires JavaScript and additional network requests. But as long as I stick to vanilla JS, I can make it pretty small.

And for unifying the search:

  • Write a post-site-indexing script that adds the WordPress posts to the index. Could be done with direct DB access.
  • Write a pre-site-indexing script that generates a bunch of files for it to index. Seems like overkill.
  • Update the search code to send the same search terms to WordPress and combine the results.
  • Use a new search engine that indexes the served pages instead of the files on the server.
  • Point the search box at a remote search engine like Googl…yeah, never mind.

I haven’t settled on anything. I’m just kind of writing down ideas in public. If you have any suggestions, please let me know!