News for hackers. Stuff that matters.
Re:20 Hours of Tent.is by jmilloy on Wednesday September 26, 2012 @03:43PM (#4577593)
But it is a url.

I agree that it doesn't look nice. As it is, we're pretty used to links with url metadata and different visible text. Occasionally I'll hover over a link to find out the domain. Why not, similar to what alphang suggests, just ^tent (which links to https://tent.tent.is)?

Re:20 Hours of Tent.is by wahnfrieden on Wednesday September 26, 2012 @06:32PM (#4578368)
Can you reasonably expect http or https for all endpoints? Then truncate the protocol segment.

^tent is bad because whoops I copied this message to another tent server and now the identity doesn't make sense.

Re:20 Hours of Tent.is by jmilloy on Thursday September 27, 2012 @12:17AM (#4579325)
That happens if I copy text with a link in it, too: the destination gets lost. We're pretty used to that phenomenon here on the internet.

I'm just guessing here, but if mentions are in the metadata, then it would actually be incorrect to copy and paste the mention text (a representation of metadata) into the actual content of a new message anyways. I expect a mature tent microblogging app would have a mechanism for inserting mentions as well as transferring content in and out from other servers in a way that preserves metadata.

Metadata should be displayed in an easy to read format, but still be accessible in full.

Re:20 Hours of Tent.is by wahnfrieden on Thursday September 27, 2012 @10:42AM (#4580911)
If you're going to include a symbol in front of the identity like twitter does, IMO it makes it look like you can use that identity alone to refer to that person. If you can't, then maybe you shouldn't dress it up anymore than just having it be a link.

Copy/pasting is not the only issue. A screenshot of a message is also (nearly) useless for identifying anyone in it without absolute URLs. Whether or not a screenshot is "incorrect" behavior isn't really relevant if users are going to do it, which might mean your notions of correctness are leading to a bad design.

Re:20 Hours of Tent.is by jmilloy on Thursday September 27, 2012 @11:52AM (#4581224)
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!

Re:20 Hours of Tent.is by wahnfrieden on Thursday September 27, 2012 @03:40PM (#4582469)
Contextual 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.
Re:20 Hours of Tent.is by jmilloy on Friday September 28, 2012 @09:30AM (#4585358)
Aren'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.