New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use u-url mf2 for incoming webmentions #234
Comments
Good point. That seems like something we can update. |
Now that I've looked at this I'm no longer confident about making this change without potentially breaking how Micro.blog keeps track of Webmentions. I still want to change it but need to test more first. (I'm fixing some other stuff, though, like respecting |
Not to flip this feature request back at you @snarfed, but… 🙂 I wonder if Bridgy should hide the HTML with CSS so that it avoids the refresh flicker when redirecting to Twitter? |
Hmm, maybe! Those pages aren't really intended to be user-facing at all, just computer-facing and for webmention implementer who use them for debugging...but they redirect right now in browsers anyway, so hiding with CSS does seem reasonable. Sure! Having said that, my hope with this feature request was to improve the link URLs (by removing brid.gy from them) just as much as the navigation experience. Not a big deal though, up to you! |
I agree, I'll keep this issue open until I can update Micro.blog. |
Hi @manton et all! Non urgent feature request: right now, incoming webmentions are rendered with a link to the source URL. This is ok, but ideally you'll want to override that with the
u-url
mf2 property if it's present. Often it will be the same, but not always, eg with Bridgy. See https://davidcel.is/2022/05/08/going-out-to.html for an example; the Bridgy webmentions are all linked to eg https://brid.gy/comment/twitter/davidcelis/1523434725448159233/1523471051123879936, but it'd be nicer for them to point to theiru-url
s, eg https://twitter.com/wholemilk/status/1523471051123879936.Low priority. Hope you all are good!
The text was updated successfully, but these errors were encountered: