20 Hours of Tent.is(tent.is) |
20 Hours of Tent.is(tent.is) |
Well, ^https://tent.tent.is looks like an URL which is also confusing. What if I want to mention an URL to somebody?
I'm sorry, but this looks horrible. At least remove the https so it doesn't look like a URL: ^tent.tent.is
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)?
^tent is bad because whoops I copied this message to another tent server and now the identity doesn't make sense.
There's a strong convention for using @ to refer to someone, not just in email addresses, so I think it will be quite intuitive, especially if the http(s) is removed: @daniel.tent.is works pretty well I think.
- Open and Decentralized (Tent)
- Open and Centralized (App.net)
- Closed and Centralized (Facebook)
Did Diaspora go anywhere after the security flaws were pointed out?
In any case, don't forget to remind me sooner rather than later that I signed up with you and I should come back.
Looking forward to being ^alanhogan.com or ^ajh.us one day :)
I think Diaspora sort of fizzled out due to a plethora of issues--not the least of which was the suicide of one of its founders.[1]
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.
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.
I'm not going to be designing tent apps any time soon, but I'm finding this quite interesting!
But yeah, Google support, although it would compete with Google+, might not be as far-fetched as it seems. Google Talk and Facebook Chat both use the open, distributed XMPP protocol. In the same way, it would be great to see commercial services that get mass use built over Tent.
Google would love for the walled-garden social networks to give way to open social networks -- closed social networks are probably the number one threat to their position as the center of the web.
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.