3 ms·
These aren't really insurmountable design issues. I'm only imagining truncated mentions in-network, so ^daniel.tent.is is ^daniel when you are on tent.is. So wh
by jmilloy 14y ago
These aren't really insurmountable design issues. I'm only imagining truncated mentions in-network, so ^daniel.tent.is is ^daniel when you are on tent.is. So when I see a screenshot of a message which mentions ^daniel, and I see that the message is from tent.tent.is, I know daniel is on tent.is, too. If he weren't, you just wouldn't truncate.
I'm not going to be designing tent apps any time soon, but I'm finding this quite interesting!
- wahnfrieden 14y agoContextual unique identifiers seem like pretty bad UX to me, and now you also have the additional requirement that any reasonable screenshot would have the site URL contained in it.
- jmilloy 14y agoAren't all usernames are contextual? When I see a screenshot of a tweet, I assume the username and mentions are on twitter and may or may not carry over to other services. If I saw a screenshot of your message in here on hn, I would assume that wahnfrieden is your hn identifier. How is this any different? Each app/server has the power to display the data however they want. We're talking specifically about how tent.is should displays microblogging messages. On tent.is the full user identifier (with the site URL) is visible above each post, so they could safely to truncate tent.is identifiers to make mentions more readable. A different server or app could find a different solution.