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 edit form of a submission (talk or workshop) has a "Mastodon handle" input field.
As someone becoming less experienced with social media every day, I'm tempted to enter only - what I think is - my user name in that field (in my case peterbittner). Interestingly, this results in a URL https://undefined/@peterbittner on the public page of my talk (https://pycon.it/it/event/... below the speaker photo).
Parsing of Mastodon handle
I failed to find the related code in this repository, but it looks like the "handle" content is expected to be of:
either https://<platform>@<username>
or <username>@<platform>
or @<username>@<platform> (which is what is displayed on Mastodon.social below one's name in the user profile)
... and the two parts <platform> and <username> are being parsed out of that string accordingly to then construct the target URL.
Can we add form validation?
Unfortunately, the form doesn't warn you about your potentially wrong handle. It were nice if it would, to avoid https://undefined/@username for everyone.
The text was updated successfully, but these errors were encountered:
The edit form of a submission (talk or workshop) has a "Mastodon handle" input field.
As someone becoming less experienced with social media every day, I'm tempted to enter only - what I think is - my user name in that field (in my case
peterbittner
). Interestingly, this results in a URLhttps://undefined/@peterbittner
on the public page of my talk (https://pycon.it/it/event/... below the speaker photo).Parsing of Mastodon handle
I failed to find the related code in this repository, but it looks like the "handle" content is expected to be of:
https://<platform>@<username>
<username>@<platform>
@<username>@<platform>
(which is what is displayed on Mastodon.social below one's name in the user profile)... and the two parts
<platform>
and<username>
are being parsed out of that string accordingly to then construct the target URL.Can we add form validation?
Unfortunately, the form doesn't warn you about your potentially wrong handle. It were nice if it would, to avoid
https://undefined/@username
for everyone.The text was updated successfully, but these errors were encountered: