[ ] Make name/value pair orientations consistent between editor (currently vertical) and profile (currently horizontal).
[ ] Guard against accidentally swapping names and values.
"Some people add them with the site names and values swapped. The labels aren’t totally obvious enough, and it’s possible auto-recognizing URLs and splitting/moving them as they’re entered would help. Also, if the UI does auto-recognize pasted URLs and autofill the corresponding site names, how do we expose that functionality to the user? Putting the URL field first implies this flow, but then how do we support usernames? Do we need to? Predefined fields, like how FA does it, with the option to relabel and add multiples might help." - charmander
[ ] If a full URL to a recognized service is inserted, extract just the identifier.
"The result is cleaner and more trustworthy. This also means stripping tracking parameters, mostly Twitter’s." - charmander
Mastodon might be an issue. @username@example.com format is preferred to support author metadata (see below), but since anyone can be running any Fediverse software, we likely can't assume this will always map to https://example.com/@username. However, if we require a URL for Fediverse accounts, it might not be possible to always map back to the username-at-domain format.
[x] Add rel="me" to outgoing links. (#1472)
[ ] Add Mastodon-recognized author metadata to Weasyl embeds.
This seems to involve taking <head> and putting <meta name="fediverse:creator" content="@username@example.com" /> in there. Assorted blog posts suggest this is a new feature added in Mastodon 4.3.
Future goals from discussion
[ ] Add icons to recognized services.
"we do have a set of icons from weasyl3, but that needs discussion." - charmander
[ ] Better present contact links; they are currently small and not prominent.
[ ] Support bidirectional verification.
This could potentially lead to an opt-in "last resort" option for password resets.
[ ] Detect broken links.
[ ] "permalinking by user id to avoid impersonation on outdated links"
[ ] Potentially sync with linktree-like services for use with bidirectional verification?
Capturing a discussion from 2024-11-10 in the developer chatroom.
Possible enhancements from discussion
@username@example.com
format is preferred to support author metadata (see below), but since anyone can be running any Fediverse software, we likely can't assume this will always map tohttps://example.com/@username
. However, if we require a URL for Fediverse accounts, it might not be possible to always map back to the username-at-domain format.rel="me"
to outgoing links. (#1472)<head>
and putting<meta name="fediverse:creator" content="@username@example.com" />
in there. Assorted blog posts suggest this is a new feature added in Mastodon 4.3.Future goals from discussion