pfefferle
Getting "Der Ziel-Link konnte nicht gefunden werden"
Hi!
Out of the blue I get the error "Der Ziel-Link konnte nicht gefunden werden" from bird.gy - see here
When I try it to add it manually via https://jascha.wtf/wp-json/webmention/1.0/endpoint I get the same error:
Any idea what I could do to further debug this issue? The destination of course exists
The destination exists, but the plugin can't find a link to your post in the brid.gy html.
See: https://pin13.net/mf2/?url=https%3A%2F%2Fbrid.gy%2Fcomment%2Fmastodon%2F%40jascha%40ohai.social%2F111681444048580159%2F111681453109020359
/cc @snarfed
Perhaps we need to change the error message a little to make this clearer!
But it was an answer to a comment. So it might be in the side of Brid.gy to name the parent comment
Oh is this a threaded comment thing? An answer to a comment to your post, not your post directly?
If so, then this is not supported by the Webmention plugin (yet)!
The plugin checks for URLs with the same domain and rejects any other request. When we started working on Webmentions we have not thought about bridges to other social network protocols like ActivityPub.
So to support that we would have to think about how to implement that properly.
The plugin checks for URLs with the same domain and rejects any other request. When we started working on Webmentions we have not thought about bridges to other social network protocols like ActivityPub.
So to support that we would have to think about how to implement that properly.
I thought Bridgy was supposed to convert the syndicated copy of a post to their website link for that reason. Maybe I'm confused about that. @snarfed
I jfound out that the parent comment is empty: 681444048580159\\/111681453109020359","comment_parent":"","comment_autho
I thought Bridgy was supposed to convert the syndicated copy of a post to their website link for that reason. Maybe I'm confused about that. @snarfed
Right. The root problem here, or at least one, is that https://brid.gy/comment/mastodon/@[email protected]/111681444048580159/111681453109020359 should have u-in-reply-to link pointing to https://jascha.wtf/angels-at-chaos-about-volunteering-and-fitting-in/ , but doesn't.
That post is both a direct reply to https://chaos.social/@[email protected]/111681444071267594 and an indirect reply to the root post https://chaos.social/@[email protected]/111679915834398325 . The original post https://jascha.wtf/angels-at-chaos-about-volunteering-and-fitting-in/ is in the latter. Bridgy should still find it, but my guess is that the immediate parent is overriding it somehow. Maybe related to https://github.com/snarfed/bridgy/issues/1617 . I'll add these details there.
Thanks for the report, all!
