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 published a note that (accidentally) contained a link marked up as u-bookmark-of, while my intention was to submit my note (not the article discussed within) to news.indieweb.org.
Not sure is this a bug or intentional, but there does not seem to be a means to update an earlier webmention, as IndieNews apparently registered it as a mention for the linked URL, not for my note. My expectation was that I could update a submitted webmention by fixing my markup and resending the webmention request, even if the original submission indicated a bookmark target which is no longer present in the updated version.
The text was updated successfully, but these errors were encountered:
I published a note that (accidentally) contained a link marked up as
u-bookmark-of
, while my intention was to submit my note (not the article discussed within) to news.indieweb.org.IndieNews registered the webmention as a bookmark to the URL linked in my note, but displaying the title of my note instead of the original article: https://news.indieweb.org/en/www.theatlantic.com/technology/archive/2022/01/instagram-tik-tok-link-in-bio-linktree/621365/
I subsequently fixed my markup and sent another webmention (the URL on my blog unchanged), which led to another item showing up in IndieNews: https://news.indieweb.org/en/sebastiangreger.net/2022/01/link-in-bio-platforms-new-geocities
Not sure is this a bug or intentional, but there does not seem to be a means to update an earlier webmention, as IndieNews apparently registered it as a mention for the linked URL, not for my note. My expectation was that I could update a submitted webmention by fixing my markup and resending the webmention request, even if the original submission indicated a bookmark target which is no longer present in the updated version.
The text was updated successfully, but these errors were encountered: