Re: Hello, Indieweb!


Hey there Matt, welcome aboard.

I also manually send webmentions for each link in an article, but it would be nice to make a script to do that hard work for me. Additionally, I should make accounts on more sites (like Twitter) and join a service like to sync my content between them. I would also like to experiment with owning my issues and pull requests, but that’s a thought for another day.

In addition to webmention.js which Jamie already, uh, mentioned, I’ve also written a tool called Pushl which automates the sending of webmentions. I have it set to run as part of my post-publish git hook on my site’s repository, as well as in a cron job that runs every 15 minutes. It requires an RSS or Atom feed at present (adding h-feed support is on my TODO list) but it only uses the feed for post discovery, rather than for target discovery, so it doesn’t need to be a full-content feed or whatever. It also maintains state so it can handle deletes and edits and so on.

There’s a few other automated Webmention sending things out there, like a lot of IndieWeb folks use which can be used in combination with IFTTT, although I can’t speak to the reliability of that solution.



It looks like there are some percent-20 characters I need to clean up and I should try to show your posts in chronological order—so this has already been great for catching problems.

Yep, I’d noticed you weren’t handling spaces or dt-published. Glad you caught that too. :)

One thing to keep in mind is that your posts will really only show up under the first tag in the list.

Makes sense. What happens if I change what the primary tag is, and then re-ping?

Anyway, great work on Publ. It’s cool to see what you’re doing with logins—love the idea of IndieAuth on

Just to clarify, Publ can’t run on as far as I know (it needs the ability to run WSGI apps); my mention of was specifically about people having their IndieWeb profile live on there but delegating IndieAuth to an external endpoint (e.g. IndieLogin) – in theory a user could delegate to an external endpoint which spoofs a different identity (such as AnyAuth), which is an issue with the URL validation step of the IndieAuth spec.

Authl’s URL validation already adopts my proposed change, where the validated URL must be more specific than the requested one (for example, can become or, but it can’t become or

Re: Magic auth catch-22


Ahh—ok. Makes sense. I’m not doing this in my reader—I don’t want to risk rel=“self” being wrong. Is there a compelling reason to do this? I mean if I’m able to fetch the feed, why risk it?

Because sometimes sites migrate to new platforms or new domains and RSS feeds change location, and this helps to avoid linkrot or unpleasant surprises with realizing that you’ve missed a few years of updates because the feed quietly went missing.

Incidentally, I have implemented AutoAuth on this site. Gonna make a more formal announcement shortly.



Oh hey welcome to Seattle! How long are you in town for?

Also congrats on finding the secret garden. Lots of folks I know have lived here for years without knowing that was a thing. (I only found out about it a few years ago, myself, because I was bored on a day that the rest of the market happened to be closed for a holiday.)

Re: Webmention support for static sites


Ángel Orgeta:

Oh, yes, and it’s great; I just wanted something much simpler. I took a look at it, but some requirements (like my ATOM feed needing WebSub compliance, which I didn’t know the meaning of, and other things that I sincerely didn’t understand) made me wish for something more straightforward. I run my script on the same computer that stores my atom.xml file, so I have no need for download support and/or caching further than knowing the timestamp of the file.

Ah, just to clarify, WebSub isn’t required, it’s just supported — it’s just one of the things Pushl supports. I hadn’t considered offline support as something that someone might want, so for that use case Gruta is definitely a better choice.

I’ll consider making it more clear what’s optional in the documentation, since I can see that being a point of confusion!

Re: Webmention support for static sites


Ángel Ortega:

I’ve written a script to add Webmention support for static sites. It’s available from:

That’s cool, but did you happen to see my tool Pushl that does the same thing? It has a few other features like feed autodiscovery, WebSub, and RFC5005 archive backfilling. And it’s pip-installable!