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
The UX logic is that a link posted on its own line should be rendered as a full embed, like so:
I don’t know whether this is something that has to happen server-side (that’s how Discourse does it) or if this sort of thing can be done completely client-side nowadays (I doubt it).
There are also some security considerations when doing this type of meta-data fetching.
Aka ‘link embed’ or ‘link card’ or ‘onebox’ for use on a page like this: https://weird.one/muni.town/identity
(that is, if I had written those links on newlines instead of in a list, which I’ve only done because we don’t support embeds yet.)
The prior art I’m most familiar with is in Discourse:
The UX logic is that a link posted on its own line should be rendered as a full embed, like so:
I don’t know whether this is something that has to happen server-side (that’s how Discourse does it) or if this sort of thing can be done completely client-side nowadays (I doubt it).
There are also some security considerations when doing this type of meta-data fetching.
We could have used this if there was a JS/wasm client for it: https://github.com/EstebanBorai/link-preview
..but we just need whatever the JS/Svelte equivalent that, which I guess is metascraper.
The text was updated successfully, but these errors were encountered: