This is what happens when you accidentally feed incorrect post data to #Blogblaze and the h-entry template rendering fails. #webdevelopment #frontend #Deno #webdesign #IndieWeb
Catching up on a couple of the sessions I missed at IndieWebCamp West. All the videos are linked on the schedule page here.
For all of y’all who make Twitter threads, now you can do that and then publish it BACK to your site using a standard in publishing content on the Web: Micropub! https://twitter.com/threadreaderapp/status/1276635958708862976
#100days 60 - Made a small but long overdue change to my site, so that it only sends me notifications about new webmentions. My notifications were filling up with duplicate mentions because of people sending them every time they build their site (which is totally fine)
Hm, advice
is interesting. I want this to signify that it’s a tag of sorts; something that can be indexed (for a negative filter search of sorts). This is making me want to lean into something like this format:
<span class="p-content-category p-category">gore</span>
<span class="p-content-category p-category">blood</span>
Leaning into what we have for tagging already would allow us to build a common way of filtering things out (or in). This is something that would have to be pushed up into the Microformats spec, IMO.
Also, I took some time to see how our friends in ActivityPub took this: https://github.com/w3c/activitypub/issues/232, some important notes there regarding overloading. One downside is that they relied on Mastodon to be the defacto representative of AP, in Microformats; the format is the leader!
A collection of truly personal sites.
This site is meant to showcase how a more personal web could look like, and hopefully give you some inspiration to make your own corner of the web a bit weirder.
Of course Cassie’s site is included!
As soon as I confirm that Webmentions work well with Lighthouse, I think I’m going to draft my backfill of content from my old Twitter account and Instagram
The more time I read and check things, the more I realize that protocols are only half of the problem. Heh, we need people working on really solid content creation tools that can match or rival what we see out there. It’s easy to publish text or an image. Video gets a bit tricky and even more dynamic content like polling, RSVPs or protected content gets more difficult.
But those are just touching the surface. I’m starting to see why the idea of being able to push a “component” of information is very attractive - by design, it can provide the necessary means for rendering things if it’s not yet supported and perhaps give users a chance to choose if they’d want to see it anyway. This is part of my hope as I begin toying with the mobile client I have in mind to be a companion to Lwa. By default, none of the post types outside of a note would be supported. It’d have to ask a Microsub server for information / tools / data on how to render it. This adds complexity to the server but it makes clients very thin.
So it’s both Lighthouse not sending the callback when it’s successful and Koype not waiting until the Webmention callback is called to then update the syndication result. Both are fine and easy to fix.
Interesting. It doesn’t look like Lighthouse is actually sending out Webmentions. Ugh.
I think I’ve successfully introduced the concept of asynchronous Webmentions to my site and Lighthouse. It does look like that’s the only kind Lighthouse might be able to accept. It relies on the sender providing a callback URL that’s sent a post of the same target and source whenever it notices a change. Usually, this shouldn’t be often but I do it to allow for slower services or passive retries.
That said, Lighthouse is successfully handling this and I think I’ll begin working on the extraction of a feed to place into a reader soon. That and having a facility to render Webmentions on one’s site will be key! Lighthouse does have a hard requirement that people leverage IndieAuth and that’s largely to reduce the number of domains / sites that one can have monitored. But I’ll have to eventually refactor that because I do want to have a per-site experience for myself (giving each of my projects their own site will be better for me to separate into my reader).
This is me testing if Webmention-based syndication works for my site. This relies on using the code in https://git.jacky.wtf/indieweb/koype/issues/202 to get that working.