Time to up the shameless product placement during eternal Caturday.
Time to up the shameless product placement during eternal Caturday.
I am definitely napping and not lying awake dreading eternal Caturday.
Just a little eternal Caturday snooze is all I need.
I’m just gonna lie down in here for a think. Then I can face eternal Caturday.
“Let the unhappy techies keep their internet of shit garbage while we repurpose their devices and designs to reveal monsters, to document abuses that should never be repeated, and to take care of one another. "
Take rest wherever you can find it during eternal Caturday.
Pretty sure I was saying something. About eternal Caturday, maybe. Enh.
Umm, it was definitely something. About eternal Caturday. Hmm.
Oops what was I saying? Something about focus? Eternal Caturday?
It takes effort to maintain focus during eternal Caturday.
Hey! Didn’t see you there. Just kidding, we’ve been sharing the same space nonstop for months. Happy eternal Caturday.
Ready to take on eternal Caturday? Okay! Uh, you go first!
Whew, recharging takes a lot of energy during eternal Caturday.
Remember to take time to recharge during eternal Caturday.
Oops, forgot to enjoy what you have yesterday? Just go twice as hard today! It’s the same during eternal Caturday.
Time to enjoy what you have!! It’s eternal Caturday!!
Don’t forget to enjoy your new goods during eternal Caturday!
I have a great fondness for IndieWeb building blocks, and Webmention is a wonderful meta-building-block that connects so many individual websites together.
Obligatory "what is Webmention?": it's a specification that describes a way to "tell" a website that some document out on the web links to one of the pages on that site.
Sound simple? It is! Perhaps even suspiciously simple. Webmention enables whole new kinds of interactions between sites (there are some great examples in this A List Apart piece). Unfortunately, almost all of the coordination to support these interactions happens outside of the "Webmention" spec itself.
So when I see blog post titles like these I am not sure exactly what to expect:
There are many more like this! I just grabbed a handful off the last few pages of news.indieweb.org.
These examples and many more are referring to the most talked-about use of Webmention: enabling site-to-site comments and responses, like a souped-up independent alternative to terrible embeds like Disqus.
This may sound like a simple feature! We might expect it to look like this:
However, for a webmention to "succeed", a lot of coordination needs to happen.
On your side:
From here, it's pretty much out of your hands. On their side:
So then they have the webmention, but to actually display it, their site must:
When I see folks posting "I added Webmentions to my site" I want to believe that they have some version of all of the bullet points above.
Unfortunately, there are lots of incompletes.
Folks in this category are collecting webmentions, probably by signing up for a receiving service like webmention.io. Their posts advertise webmention.io as the place to send mentions, webmention.io dutifully checks and stores them, and ... that's it.
This kind of "Webmention support" is often announced alongside a sentence like "Next up I'll figure out how to display them!" For me, this conjures up images of the warehouse at the end of Raiders of the Lost Ark, or a house filled to the ceiling with stacks of moldy newspapers.
There are, I recognize, lots of good reasons not to display webmentions, beyond some of the technical speedbumps and pitfalls I talk about below. For example there are a lot of unanswered questions and not-yet-built tools and services for dealing with moderation and abuse.
Static sites are back and I love it. But if there's one thing that static sites do extremely poorly it is responding dynamically to outside events. Some static sites (including my own!) will save webmentions as they come in, but won't display them until the next time a post is added or modified on the site.
From services to command line tools to fancy build hooks on your fancy hosting service, there are many ways to automate sending webmentions. But unless the receiving end can understand the content of your post, it might not show up as you intended (or at all) on the receiving end. Current best practices would have you add some extra markup to your post so that the receiver can know that your post is a reply, or a like, or an RSVP, or something else. This is a hard coordination problem between your site and theirs! In fact, there is a whole community and standards process for figuring out how to do these things!
Making sure your posts have the "correct" markup to look like you want can be difficult even for developers writing their own HTML. Tools like indiewebify.me, Monocle's preview, and microformats.io can help if you are getting your hands dirty. It's much harder for folks that just redesigned their site with a new WordPress theme.
Bridgy is an absolutely incredible suite of services provided by Ryan, also for free, for the community.
With the power of Bridgy Backfeed you can use Webmention to feed replies, likes, and reposts from your Twitter tweets to their corresponding post on your own site! This works despite the fact that twitter.com does not link to your website because Bridgy generates little "bridge" pages for which to send webmentions. And it's just a little bit of tweaking to have your Webmention display code handle the quirks.
With the power of Bridgy Publish you can use Webmention to automatically copy posts from your website directly to social media silos like Twitter! You do this by hiding a link to Bridgy in your post, which sends a Webmention to Bridgy, and then Bridgy parses your post to understand it and figure out which bits to tweet. And then Bridgy responds with info about your new tweet. And it's just a little bit of tweaking to have your Webmention sender handle those quirks and update your post with that link.
With the power of Bridgy Fed you can use Webmention to automatically copy posts from your website directly into The Fediverse where yadda yadda yadda. And it's just a bit of tweaking to have your Webmention yadda yadda yadda yadda. 😩 I've tired myself out.
These are all fantastic things that are built on top of Webmention but that I often feel are conflated with Webmention.
This one is a bit... unfair on my part. In fact, I think this setup is the best you can get for the least effort, and I encourage folks to go for it. It looks like this:
I love webmention.io and use it myself. It is an amazing community resource run by Aaron at no charge! Kevin's mention.tech is another great tool, as is VoxPelli's webmention.herokuapp.com. By configuring one of them to accept webmentions on your behalf, you save yourself a lot of self-hosting trouble. Each of these services provides APIs that let you pull out the mentions for pages across your site.
Similarly, webmention.js is a really great tool developed by fluffy (at no charge!) that hides a lot of complexity and forethought about how to display webmentions with a single JavaScript include.
All that said, I have some issues with this particular combo long-term because all the fetching and display of webmentions happens in the browser of the person viewing your post.
If 1,000 people visit your post, that's 1,000 requests to webmention.io, putting load on a service being run by one individual for free.
This setup also means that the webmentions for a post aren't included in the original HTML. So, if your site sends a webmention and wants to check back automatically to see if it's shown up, but their site only displays webmentions via JavaScript, then your site will never see it. Likewise, it becomes much harder to keep track of reply chains, for example.
Despite, apparently, being a bit salty today, I really do get excited about Webmention, how it's being used in so many ways to connect independent sites, and new ways it can be used in the future.
I'm worried, a bit, that "Webmention" is starting to lose its meaning in conversation. It's starting to feel like a shorthand that hides important details.
Maybe Webmention can be thought of as less of a "building block" and more like a glue. You can do so many things with glue, like combining a bunch of planks into a table, or building a parade float sculpture with papier-mâché, or doctoring the photo in a passport!
You wouldn't call them all "glue".
72 hours seems to be plenty of time to let your shopping sit during eternal Caturday.
Remember to check for perishable goods beforehand if you plan to let your shopping sit out during eternal Caturday.
“You see, you have to study for quite a while what others assume to be nothing to see the less obvious gears of wrong in motion.”
Some say it’s effective to let your shopping sit for a few days during eternal Caturday.
No, please. Tell me more about what the internet is saying on eternal Caturday. I’m listening!
Oh, you read Twitter and it made you sad? How about that. Close it down and enjoy eternal Caturday.
Is it, like, pretty interesting out there? Or weird? Asking because eternal Caturday.
Anybody getting out and about? What’s that like during eternal Caturday?
Yesterday I joined in the West Coast Homebrew Website Club via Zoom. I was worried I'd be too tired to join - it was held 9-10:30pm my time - but after a nice dinner and wind-down from the day I was in a pretty good place.
Jacky shared some demos, reading, and brainstorming (go check 'em out). And, as captured in Tantek's notes, we also got into some good discussion about community onboarding prompted by Sarah.
A recurring theme as new folks join the IndieWeb community is that the wiki is an amazing resource but also a source of crippling information overload. In recent years we have discussed ways to (re-)organize content for folks geting their own site started. On his own, Jason has begun writing guided intros for developers on topics like Webmention. But as Sarah pointed out, IndieWeb is much more than just developer documentation or guides for folks setting up their own websites. IndieWeb is also an active community with frequent live events, 24/7 discussions, and a long-term memory of observations and ideas and projects and participants. So, perhaps it's worth thinking about onboarding from a perspective of introducing new folks to this community, what they can expect, and how to successfully engage.
For my part, I continued research into the cursed project that I've been noodling on for years and finally started during IndieWebCamp 2020 West. My goal is to give folks a free way to dip their toes into the IndieWeb without needing to understand the building blocks first, but with on-ramps to understanding, customizing, and improving any part of it. While I am learning a lot from projects like Postr, I think I will end up actually making my own version of building blocks like authorization, token, and micropub endpoints. By way of being careful, I would like to be able to test that each one works properly. So that's how I ended up volunteering to help build out the IndieAuth.rocks test suite. 😅
I really enjoy and appreciate these meetups and I look forward to joining the next one!
Thanks to Onion Location you will now be reminded you can view your favorite loops of my cat more securely when using Tor Browser.
“Rather than waiting for comforting answers to every potential harm ahead of us, let’s run. And continue to organize, imagine, and transform this country toward freedom and justice without police and violence. Let’s run.”
Yaww-oh! Hello! Happy eternal Caturday!
Okay! Enough of that. Back to your regularly scheduled eternal Caturday programming.
wE LiVe HeRe NoW. hApPy EtErNaL cAtUrDaY.
The state of the weekend cocoon is strong. Happy eternal Caturday!
Oh, okay. I guess we live here now. Happy eternal Caturday.
You can do it! Try again! Join us in this eternal Caturday!
Yes, even in your cocoon you hear the call of eternal Caturday. Heed it!
Oh no. Are you resigned to your weekend cocoon on eternal Caturday?