Jan Boddez @janboddez@mastodon.social

I'm sort of moving to @jan. Still figuring out how to correctly "back-reference," though, or make this instance notice.

Seems I may have to return to self-hosting an actual Mastodon instance after all. Was hoping for something more lightweight. Unless ... I just leave the Fediverse and go IndieWeb all the way (despite _many_ IndieWeb discussions happening _over_ [rather than _on_] Twitter, which I no longer use).

I was hoping to start crossposting to an AP-powered microblog, you see, and move away from mastodon.social after it's started blocking all of my (shared) web server's API requests.

Maybe it's mastodon.social, but interaction with my fresh microblog.pub install results in a "failed to verify" request on the latter's end, always.

Godnonde. 'Unfortunately, there was an error looking up the remote account'

Everything else, too. So, two options: I did something I shouldn't have, or someone on the same IP did. At least four possible solutions: move to another IP (no guarantee), move to another Mastodon instance (no guarantee), move off ActivityPub altogether, or find an alternative (self-host/natively support AP/Pleroma/Microblog.pub, some guarantee).

Been looking into building a "DAW" PC—my five-year-old laptop is plenty powerful for browsing, programming and running VMs, but a dedicated rig is so much tidier. Also, need more USB ports. (I'll start with cleaning up what I already have, though. Getting my eight-year-old audio interfaces to run wasn't very straightforward either.) Anyhoo, _should_ I buy, I think I'll just have it assembled for me.

Anything cURL request, regardless of its contents: "connection refused."

#notestoself Don't ever rely on functions introduced by other add-on plugins (and use `function_exists()` if you do—wouldn't have been enough, tho, but whatevs).

Who, ever, deprecated `is_woocommerce_active()` (and where the heck did I even learn about it)? *replaces with `class_exists('WooCommerce')`*

My site doesn't wanna POSSE to Mastodon anymore. Or rather, its POST requests—and possibly all attempts to connect—are refused by .social. Will implement a workaround, but can't really be bothered right now.

Feeling old. Like always.

@Gargron, any kind of issue with the API, or did my web host somehow end up on a blacklist?

But, why? "cURL error 7: Failed to connect to mastodon.social port 443: Connection refused"