Reminder that it's #HomebrewWebsiteClub Nottingham tomorrow! See you there for some website stuff https://events.indieweb.org/2020/06/online-homebrew-website-club-nottingham-LrUgUvSF1Z23
There’s a great feature of having a live conference that people can attend! But it’s extremely difficult to do properly especially when people are ten hours away. I wonder if we, in the IndieWeb, can take this opportunity to distribute this. There’s probably prior art on this - I haven’t seen it yet.
The idea is to have people pre-record talks and information to be about 4 - 5 hours worth, total. Then we can have a live streaming server play this playlist on loop about 6 times so (ideally) everyone can see them as if they were watching it for the first time. After the loop is done for about 6 times, we could then make individual video pages, similar to how conferences publish videos after a talk.
What does the community think? I’m hoping this would reduce the pressure to agree/find on a time and distributes it out for people. We’d need people in at least 4 different zones to help make sure that the videos are looping correctly (but that shouldn’t be too hard). I think TwiT does a good job of this.
Rewriting #blogblaze drafts on #Deno. I’m having progress! The ability to load ES6 modules by URLs instead of using npm to install them is nice. I kinda miss the dev-dependencies and the tools that are usually used with Node, like #eslint etc.
#kittybox #indieweb #js
Something I think about a lot is how to prevent people from messing with the IndieWeb. It hasn’t been a huge concern as of yet because thankfully we can trust everyone in the community so far. But if we were to go 10x in size right now, how do we stop people from posting something, editing it and making it seem as if the original post changed? We give people a lot of trust into the content they publish.
I know any solution towards this would have to be backwards-compatible with how we do things now and shouldn’t impede progress but I do think that I’ll be working very hard on making this a required function for my readers. And I think I have an idea for one (as well as a way to make this work for everyone without causing too much headache - it’s a bit like DKIM but with less moving parts).
I am contemplating rewriting #blogblaze for #Deno. Well, not rewriting, rather adapting it to Deno. It looks like a promising piece of software! #kittybox #indieweb
TFW you’re teetering on the edge between using the #microformats library to find h-cards and their properties and writing an entirely new wrapper to make finding #webmention comments “easy”
~ # 16:01 ~
The Return of the 90s Web | Max Böck
Everything old is new again (thank goodness!):
Quotebacks and hypertexts (Interconnected)
What I love about the web is that it’s a hypertext. (Though in recent years it has mostly been used as a janky app delivery platform.)
I am very much enjoying Matt’s thoughts on linking, quoting, transclusion, and associative trails.
My blog is my laboratory workbench where I go through the ideas and paragraphs I’ve picked up along my way, and I twist them and turn them and I see if they fit together. I do that by narrating my way between them. And if they do fit, I try to add another piece, and then another. Writing a post is a process of experimental construction.
And then I follow the trail, and see where it takes me.
June 27-28
https://events.indieweb.org/2020/06/indiewebcamp-west-2020-ZB8zoAAu6sdN
I’m attending.
I do think that the IndieWeb community should be moving to make more services/tools that we can point to demonstrate the power of the community. A few people have been stepping up to this but it’s mostly from either a semi proof of concept thing or just to externalize and share functionality from their sites.
Back to a nerd topic: implemented some of the #webmention server in my blog software this evening, and rearchitected the storage layer with an interface to make testing easier. #golang
~ # 05:09 ~
There a LOT of error cases when writing a #webmention server implementation #indieweb #goldfrog
~ # 19:57 ~
We’re definitely in the small group of Elixir people in the IndieWeb, lol. I’ve used Mnesia mainly as a caching layer and SQLite for database stuff. I’ve been working on a IndieWeb-specific library that relies on https://wwwtech.de’s Microformats2 library actually over at https://git.jacky.wtf/indieweb/elixir/! It has a hard dependency against master for https://wwwtech.de’s project so I can’t update it in Hex but it powers all of my projects (I have like about 4 concurrent IndieWeb projects?) right now.
That’s an interesting approach to add the Bridgy Publish webmention. I’m glad it’s working well for you.
My approach is still part of the template files. I just reviewed it and it’s fairly simple, so I’m comfortable sharing it. Here is a gist. Let me know if you have any questions.
I’m excited to see more ProcessWire sites with webmention. I’ve not heard from a lot of people using the module yet. I’m definitely interested in improving the indieweb experience on ProcessWire. Bridgy Publish is an area that I have not worked on yet, partly because people can have templates set up a variety of ways and I’m not sure how to make a plugin that works with different setups.
By the way, we’ve been having weekly virtual indieweb meetups if you’d like to join. I think the closest timezone would be the London meetup. Check out events.indieweb.org for upcoming events. We have an active community chat as well: indieweb.org/discuss.
https://mxb.dev/ does it again! This time, a follow up for Webmentions!