If I decide to start blogging again (it's been years), what's more #screenreader#accessible: ghost or micro.blog or something else? Don't even mention #wordpress; my desire to run a PHP app for any reason is zero. Plus the gutenberg stuff. #a11y
Never mind, I thought you could #selfhost micro.blog. Apparently not. I don't do business with American companies when I could host myself. So they're out.
@MostlyBlindGamer That requires both Google Firebase and something called versal that I've never heard of and can't host myself. If I'm doing business with big american tech I might as well just use micro.blog directly.
@MostlyBlindGamer Oh my God I'm so glad I didn't try to build an entire thing in hugo by myself. I find hugo utterly, utterly baffling and incomprehensible. I've spent like four hours trying to figure out how to get this shortcode to paginate...or at least only display 50 books or something...and not dump 500 book links on the page where I put it. It might actually be impossible. Google Gemini fixed the bookmarks shortcode, but I just copied the magic letters. I have no idea why that worked. Or why it won't work for this shortcode. github.com/kottkrig/microdotblog-bookshelf-shortcode/
there’s a recent breaking change in pagination that LLMs won’t know about. I handle those myself when my pipelines break and that’s how I understand how things work.
Mind you, this might be a totally different issue. My main point is the software is in active development. If you don’t want to keep up with it when things break - which is fair and understandable - it may not be the best fit. I assumed you were looking for the same kind of hint instability I am.
@MostlyBlindGamer I don't mind well documented instability. But Hugo is written in go, a language I'm entirely ignorant of, so I can't even consult the code. Also, it's dealing with my least favourite part of development: the user interface. When something in the backend goes wrong, consulting the logs and figuring it out can be kind of fun. But for front-end stuff, it's just frustration.
@thelonelyghost I find NodeJS is better at being self-contained and dockerized than PHP, where random things explode for no reason known to men or Gods. And I want fediverse integration, with the ability to pull in replies as comments. A static site won't get me that.
there's an option involving webmentions, either hosted for you as webmention.io or self-hosted with the same software.
You can rebuild the static site periodically pulling in comments for each page using code specific to your generator. It's yet another data source, and allows you to approve comments before they appear on your site. In the end, it's still a static site (for caching and security purposes).
for federation of your posts, there are any number of RSS to Fedi automations, either as a discrete bot or queueing content to post under your main account like Buffer or Hootsuite tend to do.
@thelonelyghost Right, but by the time I'm running my own webmentions service, my own RSS to federation automation system, etc, what's the point of a static website? Now I have four or five things to manage, all of whom use different languages and platforms, and update instead of just one.
Ongoing investigation: * #fedipage looks good, but depends on firebase and versal, so doesn't let me avoid big tech * #ghost requires mailgun, more big american tech
Can we literally not host a federated blog on our own servers without big American tech companies involved? At least micro.blog is a small American tech company, so they might be the way I have to go. Or just, you know, not do this at all.
So I ended up going with micro.blog. I don't love that it's American. But it stores my stuff in Europe, it's easy to export and back-up the blog if I have to move elsewhere, it does cross-posting, and it lets me centralize a bunch of other stuff (like my bookmarks formerly on tinygem and my to-read list formerly on goodreads). Hence the name: stuff.interfree.ca
@phillycodehound But requires mailgun, needs an account to comment (comments don't seem federated), and has a bunch of other annoying issues. I'll use #microblog until it inevitably enshitifies.
🇨🇦Samuel Proulx🇨🇦
in reply to 🇨🇦Samuel Proulx🇨🇦 • • •MostlyBlindGamer
in reply to 🇨🇦Samuel Proulx🇨🇦 • • •🇨🇦Samuel Proulx🇨🇦
in reply to MostlyBlindGamer • • •MostlyBlindGamer
in reply to 🇨🇦Samuel Proulx🇨🇦 • • •🇨🇦Samuel Proulx🇨🇦
in reply to MostlyBlindGamer • • •MostlyBlindGamer
in reply to 🇨🇦Samuel Proulx🇨🇦 • • •🇨🇦Samuel Proulx🇨🇦
in reply to MostlyBlindGamer • • •GitHub - kottkrig/microdotblog-bookshelf-shortcode: A Hugo shortcode to embed micro.blog bookshelves on any page
GitHubMostlyBlindGamer
in reply to 🇨🇦Samuel Proulx🇨🇦 • • •there’s a recent breaking change in pagination that LLMs won’t know about. I handle those myself when my pipelines break and that’s how I understand how things work.
Mind you, this might be a totally different issue. My main point is the software is in active development. If you don’t want to keep up with it when things break - which is fair and understandable - it may not be the best fit. I assumed you were looking for the same kind of hint instability I am.
🇨🇦Samuel Proulx🇨🇦
in reply to MostlyBlindGamer • • •They Might Be Stupid
in reply to 🇨🇦Samuel Proulx🇨🇦 • • •do you really want to run a NodeJS thing instead? that's how ghost is built, FWIW.
Since you're techy, you might try one of the static site generators like Hugo or Jekyll. Depends on if you want a comments section.
🇨🇦Samuel Proulx🇨🇦
in reply to They Might Be Stupid • • •They Might Be Stupid
in reply to 🇨🇦Samuel Proulx🇨🇦 • • •there's an option involving webmentions, either hosted for you as webmention.io or self-hosted with the same software.
You can rebuild the static site periodically pulling in comments for each page using code specific to your generator. It's yet another data source, and allows you to approve comments before they appear on your site. In the end, it's still a static site (for caching and security purposes).
They Might Be Stupid
in reply to They Might Be Stupid • • •🇨🇦Samuel Proulx🇨🇦
in reply to They Might Be Stupid • • •Brandon
in reply to 🇨🇦Samuel Proulx🇨🇦 • • •🇨🇦Samuel Proulx🇨🇦
in reply to Brandon • • •Drew
in reply to 🇨🇦Samuel Proulx🇨🇦 • • •🇨🇦Samuel Proulx🇨🇦
in reply to Drew • • •🇨🇦Samuel Proulx🇨🇦
in reply to 🇨🇦Samuel Proulx🇨🇦 • • •Ongoing investigation:
* #fedipage looks good, but depends on firebase and versal, so doesn't let me avoid big tech
* #ghost requires mailgun, more big american tech
Can we literally not host a federated blog on our own servers without big American tech companies involved? At least micro.blog is a small American tech company, so they might be the way I have to go. Or just, you know, not do this at all.
🇨🇦Samuel Proulx🇨🇦
in reply to 🇨🇦Samuel Proulx🇨🇦 • • •Samuel Proulx
stuff.interfree.caAndré Polykanine
in reply to 🇨🇦Samuel Proulx🇨🇦 • • •🇨🇦Samuel Proulx🇨🇦
in reply to André Polykanine • • •Seth is a Perpetual Startup ⁂
in reply to 🇨🇦Samuel Proulx🇨🇦 • • •🇨🇦Samuel Proulx🇨🇦
in reply to Seth is a Perpetual Startup ⁂ • • •