Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changing URLs (use uid) #769

Closed
sebsel opened this issue Sep 5, 2017 · 1 comment
Closed

Changing URLs (use uid) #769

sebsel opened this issue Sep 5, 2017 · 1 comment

Comments

@sebsel
Copy link

sebsel commented Sep 5, 2017

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.)

schermafbeelding 2017-09-05 om 20 14 38

@sebsel
Copy link
Author

sebsel commented Sep 5, 2017

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.

@sebsel sebsel closed this as completed Sep 5, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant