However, it could go one better and "forward" this by sending it natively to the original target. Ie, it could send a webmention from my like (https://snarfed.org/2023-08-11_gregor-morrill-this-is-awesome-a-right-wing-indieweb-social ) to the original target. Those posts are both native web, but sending that webmention arguably matches my intent in spirit. Maybe ok?
There are equivalents in other same-protocol delivery too, eg BF could do AP inbox delivery for original AP posts, even when neither the post nor the inbox(es) are on BF. Same with Nostr, Bluesky, etc.
Hit an interesting edge case just now. I tried to like https://indieweb.social/@gregorlove.com@gregorlove.com/110794731120430327 via BF, but it correctly detected that that post was bridged, and the source and original target (https://gregorlove.com/2023/07/this-is-awesome/ ) were on the same protocol, web/webmention, so it declined to do anything. Good, ok.
However, it could go one better and "forward" this by sending it natively to the original target. Ie, it could send a webmention from my like (https://snarfed.org/2023-08-11_gregor-morrill-this-is-awesome-a-right-wing-indieweb-social ) to the original target. Those posts are both native web, but sending that webmention arguably matches my intent in spirit. Maybe ok?
There are equivalents in other same-protocol delivery too, eg BF could do AP inbox delivery for original AP posts, even when neither the post nor the inbox(es) are on BF. Same with Nostr, Bluesky, etc.