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
I have mistitled a blog post so I changed the title and the slug. I load my profile in mastodon and it has the old title and url. so if I click the link it 404's because I changed it. if I search the updated url from mastodon it does not show the new data.
Version or last commit:
scream.today running
writefreely v0.11.2
social.wake.st running
mastodon 3.0.1
The text was updated successfully, but these errors were encountered:
I'm not sure if fediverse platforms support updating post URIs (most completely ignore the Update activity), so the right fix could mean sending out ugly ID-based URLs for posts in the fediverse instead of their slug-based URLs.
Another solution (probably a good middle-ground) would be to send out ID + slug (Medium style) URLs to the fediverse, and only parse the ID on the WF end to retrieve the post. That would keep semi-pretty URLs, at least.
Otherwise, the least-ideal solution would be to just track slug changes and redirect people on the WF side. This isn't ideal, because as soon as a new post uses an old (redirecting) slug, that redirect gets removed.
We'll need to see how much work this'll involve and then we can get it in.
I have the same problem on a story with a changed title/url
writefreely can do like medium: it keeps live the old url with a canonical url to the updated address, just to avoid duplicated pages.
easiest just to show this as a screenshot.
I am following my blog scream.today/daily from my mastodon instance social.wake.st/@liaizon
I have mistitled a blog post so I changed the title and the slug. I load my profile in mastodon and it has the old title and url. so if I click the link it 404's because I changed it. if I search the updated url from mastodon it does not show the new data.
Version or last commit:
scream.today running
writefreely v0.11.2
social.wake.st running
mastodon 3.0.1
The text was updated successfully, but these errors were encountered: