Canonical post images with a relative src attribute are syndicated on GitHub with a relative path (i.e. ![alt text](/path/to/thre/image.png)).

This can be seen in https://github.com/snarfed/bridgy/issues/985 and it’s canonical post.

I suggest we convert image paths to absolute URL during the syndication.

Hello, I noticed that my twitter account no longer receives webmentions from bridgy.

It picks the reply but shows the “no webmention support” text, followed by my canonical post (both shortlink and permalink).

Today I was able to get a screenshot of when bridgy fetched replies for the first time:

But nothing was received on webmention.io and now bridgy tells me “no webmention support”

The reply in the screenshots is this tweet.

I already checked https://brid.gy/about#missing but it seems not relevant in my case as the original post is discovered.

Could someone help me figure out if it’s a problem on my side or a legitimate bug? :pray:

Hello, when I tested brid.gy GitHub publish integration I got a strange webmention that I didn’t expected.

This is my original content https://abisso.org/stream/2020/10/19/tor-in-vagrant/ and it received 2 reply webmentions.

One is the legitimate reply from the issue author (shown as comment on my original post) and another one that is a reply pointing to my own comment (that I filtered out on the web page).

Is this behavior expected?

Thank you for this wonderful project :pray: