Thanks to everyone who joined me last night at #TechNott for my talk about the #IndieWeb - you can find the recording of the video at https://www.youtube.com/watch?v=qFXOZww5mmE - I'll also look at getting it uploaded to Archive.org for longevity!
Not long now till you'll be able to hear me talking about the #IndieWeb at tonight's #TechNott - hope to see some of you there to learn what it is, why some of us want to own our data and be our own platforms, and more!
Happy #TechNott day all! Looking forward to seeing you later to hear a bit more about what the #IndieWeb is, and the ways you can get involved owning your data and building cool things for yourself https://www.technottingham.com/events/tech-nottingham-april-2021
In the midst of a re-write of how my site works and in passing conversation in the IndieWeb chat, I think about how to 'show' the IndieWeb as something people can invest in versus a collection of things that...
In the midst of a re-write of how my site works and in passing conversation in the IndieWeb chat, I think about how to 'show' the IndieWeb as something people can invest in versus a collection of things that...
Now that you know why posting for âfreeâ on MySpaceBook isnât a good idea. Check out Micro.blog. I just paid for another year, again. Totally worth it. Micro.blog is the easy way to #indieweb.
The Healing Power of Javascript | WIRED
I can very much relate to what Craig is saying here.
Woop woop! Very excited for this đ looking forward to sharing a bit more about what the #IndieWeb is, why you may be interested and what folks can do to get involved!
Reminder that it's #HomebrewWebsiteClub Nottingham tomorrow! I hope to see you there at 1730 for some website stuff! https://events.indieweb.org/2021/03/homebrew-website-club-nottingham-VSpbmyQEbxQZ
Tantek Ăelik (tantek.com)
Foreword A couple of weeks ago I noticed one of our newer IndieWeb community participants found an example on the IndieWeb wiki that no longer worked, and it was from someone who hasnât been around for a while. I knew that person had various things come up in their personal life, thus left without...
As part of my attempt to work on something IndieWeb every weekend, I decided to do a bit of a dive into the code for https://github.com/kylewm/silo.pub. Itâs known as being a (working) example of using Micropub as a means of syndication. Conventionally, people do this using Webmentions via brid.gy - but I am curious about having such a system automatically add syndication back-links to my posts as well as being able to dynamically use it back-fill posts to my site (since it can do the former with potentially less magic than Webmention parsing).
I notice that in order to use silo.pub, you forward the entire incoming Micropub request to the remote endpoint (we can call it âsyndication endpointâ). This feels a bit tricky to implement because I can see it being simpler as the originating site of the request to only just send a URL of the post that needed to be syndicated - part of the appeal of Bridgy is that. But having to forward the whole thing feels interesting. But it also allows for a means of insuring that a particular syndication location only gets what it can support or whatâs appropriate for that destination (bookmarks could be formatted more differently on Twitter or how reading progress is reflected).
I think I can âgetâ with this approach but Iâm going to take a bit of a different approach. Instead of forwarding the whole body, Iâm going to send it a request to update a post. Something like the following:
POST /syndication/twitter
{
"action": "update",
"url": "https://jacky.wtf/a-post-to-share"
}With no other arguments, this would tell the Micropub-powered syndication endpoint that it should update the provided post. Being that this one is optimized for Twitter, it could do the work of sending the tweet (or replying, or liking) and then sending a Micropub update to the original post with the change in the syndication URL. A server noticing that could use that as a way to determine that the syndication was successful with no extra need to add asynchronous processing - we get it for free.
Okay, finally ready to make https://jacky.wtf a static site powered by this new Micropub server. You can peek at the code at https://git.jacky.wtf/indieweb/koype-next but Iâll be aiming to use it to redo a lot of sites (like even https://koype.net because if I canât use it there then Iâm kidding myself, lol)