@thatEmil Taproot works almost the other way round — a “mentions” module stores incoming mentions, noting their target path after resolving redirects. Then, each content module queries the mentions module for mentions of a particular URL. That way the two are decoupled, and I can keep track of mentions of static URLs and things not represented by a “model”. Haven’t figured out how to handle redirects well yet though.

@thatemil AFAIK there’s currently no defined behaviour for HEAD requests to a webmention endpoint, so an empty 405 response is probably the safest bet at the moment.

@t excellent minimal Like implementation! Whilst your homepage performance is admirable, I don’t think you can meaningfully compare it to silo infinite scroll untill there’s some sort of pagination :) Currently, without rel-prev[ious] links, there’s no way for crawlers (e.g. readers like Shrewdness, semi-hypothetical “your year in indieweb”) tools to find your old posts other than fetching each one individually, which for many cases takes too long to provide a good experience — e.g. crawling your years worth of content takes ≈162s, verifiable with the following bash+PHP code:

curl -Ss https://getcomposer.org/installer | php

./composer.phar require taproot/subscriptions

php -a  # Start an interactive shell, paste in following code (alternatively save into file):

@(require 'vendor/autoload.php'); $start = microtime(1); echo "Starting crawl…\n"; Taproot\Subscriptions\crawl('http://tantek.com/2014/365/t1/indieweb-like-posts-2015-commitment-done', function ($r) { echo "."; if (substr($r['mf2']['items'][0]['properties']['published'][0], 0, 4) == '2013') { return false; } else { return true; } }); $total = microtime(1) - $start; echo "\nYear crawl for 2014 took {$total}s";

@parzzix silos gaining an API only means the #indieweb can become silo-friendly. For actual indieweb friendliness, see indiewebcamp.com/friendly

@acegiak that’s hilarious — OTTOMH, h-review p-rating is assumed to be between 0 and 5 as a fallback if no best/worst are given (and even if just best is given, 0 could be assumed to be “worst”). So you could totally publish something like:

<span class="p-rating">1</span>/<span class="p-best">10</span>

@elfpavlik HTTP POST urlencoded bodies are supported by every web application framework ever. For everyone to add support for not only a separate vocabulary but a completely different content type is a huge amount of (probably unnecessary) work. What benefits does it bring? Is there existing client software which would immediately work with micropub resource providers if this change was made?

@bastianallgeier given homepage, fetch; parse microformats2, look for representative h-card with photo property

• microformats.org/wiki/microformats2
• microformats.org/wiki/h-card

Webmention spam has already started to become a problem, especially thanks to Brid.gy’s backfeeding of twitter comments. For most of us it hasn’t yet been a big problem, but it inevitably will be in the future. There’s some ideas about potential spam prevention tools on the wiki: indiewebcamp.com/spam

@mapkyca good point, I hadn’t considered this problem with hotlinking profile photos before. I think some webmention implementors have started doing this, and I intend to do it within Shrewdness.

It’s worth noting that the attack is not at all limited to profile photos though, rather any photo or otherwise automatically loaded content in the comment e.g. images or audio. Whilst caching profile photos is feasible, caching any media in comments is more difficult, and therefore a good reason for text-only comments.

Text-only content is not an option in Shrewdness, but perhaps instead images could be cached, and other media loaded upon demand, removing the ability to arbitrarily spy on people.

@kartik_prabhu amazing work overall! This is one of my favourite parts though — the fact that fragmention comments fall back gracefully if they’re not supported on either side, and yet all the data required to present them is preserved, so future updates can retro-actively put old marginalia in the right place!

I wonder how tricky it would be to implement this on the comment publisher side too — detecting fragmention URLs and tailoring the reply context content…