@ru That would be possible, but kind of goes against what other people do.
@chris Oh, wait. Looks like it is in fact dynamic. In that case, I might take another look. Been looking for a sort of “pre-made” Laravel CMS, though. Ended up settling for … WordPress. 🙃
@chris Not yet. Mr. McDade’s designs are awesome. His politics … not so much. (I mean, not that it matters, I think. I use M$ products all the time, after all.) But, more importantly, I’m becoming increasingly fond of _dynamic_ sites.
@jle One benefit (or burden, it really depends) of Microsub could be the explicit server/client split. (I kind of prefer “integrated” _web_ apps, so I don’t really care for it.) The other is that most clients—there’s maybe three or four of them, but whatever—are also _Micropub_ clients, so you can react to a post (e.g., create a reply on your site [and have it “webmention” the post’s author]) with two clicks or so. @wouter
In reply to https://deeden.co.uk/notes/2022/05/18/094125/.
Hehe. What I do is file a million tiny GitHub issues, like, during lunch breaks and stuff, ~~to revisit later~~ and then totally forget about them.
Note to self: I don’t think Pixelfed’s API supports revoking access tokens, or a `since_id` parameter (like, when getting the most recent statuses).
@cdevroe
Email: multiple times a day
RSS: multiple times a day
Micro.blog: never
Mastodon: multiple times a day
Twitter: I'll browse a few known profiles (all while logged out, I don't maintain an active presence); but, a few times a week?
Facebook: never
TikTok: never
> Weaver’s Iron Law of Blockchain: _When somebody says you can solve X with blockchain, they don’t understand X, and you can ignore them._
Engineer, web designer, and amateur guitarist. Likes web standards, accessibility, #PHP, #PunkRock, and the #IndieWeb. #nobot