💬 Re: Intelligent webmention sending

Comments

In reply to: Re: Intelligent webmention sending

FWIW, Pushl also handles incremental webmention updates, including support for removals of targets and deletions of articles. Right now the only thing I feel like it’s missing for most IndieWeb folks is h-feed support, which should be fairly easy to add (I just need to get around to it).

It also could do with some better retry logic (namely saving failures in a queue for next time), which is also On The List.

💬 Re: Hello, Indieweb!

Comments

In reply to: 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 brid.gy 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 webmention.app which can be used in combination with IFTTT, although I can’t speak to the reliability of that solution.

💬 Re: Auto-XYZ

Comments

In reply to: Re: Auto-XYZ

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 tilde.club.

Just to clarify, Publ can’t run on tilde.club as far as I know (it needs the ability to run WSGI apps); my mention of tilde.club was specifically about people having their IndieWeb profile live on there but delegating IndieAuth to an external endpoint (e.g. IndieLogin) – in theory a tilde.club user could delegate to an external endpoint which spoofs a different tilde.club 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, http://tilde.club/~fluffy can become http://tilde.club/~fluffy/ or http://tilde.club/~fluffy/blog/, but it can’t become http://tilde.club/~root or http://tilde.club).

💬 Re: Magic auth catch-22

Comments

In reply to: 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.