Jyte should parse Jyte profiles to reveal names when making claims or comments: mylid.net/scoobyfoo vs. jyte.com/profile/mylid.net/scoobyfoo
By
Dave Chiu
on February 11, 2007
This is done for OpenIDs, viz. you enter an OpenID into the claim and Jyte replaces it with the person's name.
Why can't Jyte parse Jyte URLs to reveal names?
http://jyte.com/profile/mylid.net/scoobyfoo
v.
http://mylid.net/scoobyfoo
For that matter, Jyte doesn't parse URLs in the Description or Comments, as shown by the previous urls.
Agreed
12
1
92.3% 7.7%
Embed Claim
Make a related claim
Similar claims
- 26-1 It is helpful when people who disagree with claims about improvements to Jyte explain why they don't agree
- 36-0 The Jyte Blog, and any other JanRain blog or web property should take full advantage of OpenID.
- 50-0 When using a Jyte user's OpenID in your comments it should be automatically linked to their profiles, like claims about users.
- 6-0 I'd like to see Jyte work well with coComment or similar service.
- 25-1 Jyte should allow us to use a user's OpenID in comments as well as in claims.
Discussion (1)
That would make it quicker to make claims about people. However, they need to distinguish the openid URL from the profile URL, so you can't redirect all local navigation to the profile page. Also, I wonder if the user lookup button could have a paste button for the openid returned. I'm getting lazy in my old age, and highlighting the whole openid takes like 750 milliseconds too long. If I had any productivity, the process would be cutting into it.