You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Discovered this because my site sent a 302 in reply to a webmention. The 302-error is fully on my side, but the important point is that it happened because I moved /2017/09/05/2/nblijmege to /2017/09/05/2/nblijmegen. (My site sees date+number as canonical and tries to redirect users to the right slug, which it also tried during receiving webmentions, which is a bug.)
To fix this problem temporarily, I tried to let Bridgy recrawl my site, so it could update the URL.
On my Microformats, I have both a dt-updated and a u-uid (which is https://seblog.nl/2017/248/2: year, day of year, number). Apparently, Bridgy does not use uid.
The recrawl let Bridgy find /2017/09/05/2/nblijmegen as a new post. It then saw the syndication, etc, so every tweet gets two targets, of which, for new likes, the old one (nblijmege) fails.
I think supporting uid would fix this. (And I should still fix my 302-bug.)
The text was updated successfully, but these errors were encountered:
Per discussion on #indieweb-dev, it's not really necessary for Bridgy to know every post by one URL and one URL only. People should dedupe them on their own site anyway, for Bridgy sometimes sends multiple webmentions.
Discovered this because my site sent a 302 in reply to a webmention. The 302-error is fully on my side, but the important point is that it happened because I moved /2017/09/05/2/nblijmege to /2017/09/05/2/nblijmegen. (My site sees date+number as canonical and tries to redirect users to the right slug, which it also tried during receiving webmentions, which is a bug.)
To fix this problem temporarily, I tried to let Bridgy recrawl my site, so it could update the URL.
On my Microformats, I have both a
dt-updated
and au-uid
(which ishttps://seblog.nl/2017/248/2
: year, day of year, number). Apparently, Bridgy does not useuid
.The recrawl let Bridgy find
/2017/09/05/2/nblijmegen
as a new post. It then saw the syndication, etc, so every tweet gets two targets, of which, for new likes, the old one (nblijmege
) fails.I think supporting
uid
would fix this. (And I should still fix my 302-bug.)The text was updated successfully, but these errors were encountered: