@nickname and change nicknames
Reported by Johannes Schirge | May 19th, 2009 @ 06:52 AM | in 0.6
Users are able to change their own nickname. Every @nickname reply is not found anymore if the nickname has changes to @newnickname.
Is it possible to connect the @links whith the user id (as a deeplink) instead of the username? This could also be helpful if you (when this feature is availible) do remote-subscription to other users on other ombs. so the @username will link to the original profile (maybe on another omb).
Just a suggestion. maybe there are reasons to keep is at it is.
Comments and changes to this ticket
-
Brian Jesse Hendrickson May 20th, 2009 @ 03:10 PM
- State changed from “new” to “open”
i'm glad you brought this up, yes I agree using the "deeplink" would be much better, and it would preserve the old links. great idea
-
Johannes Schirge June 28th, 2009 @ 06:23 AM
- Tag changed from “@nickname, change-name” to “high-priority”
-
Brian Jesse Hendrickson June 29th, 2009 @ 06:05 PM
a status/notice/post/tweet is stored as a 140-char plain text document without any HREF links in it
so, the link has to be calculated at notice-render-time, thus, it's impossible to store the "deep link"
maybe I will add a field to the posts table, it could store a nickname->deeplink lookup table for that status/notice/post/tweet
that lookup table could be created when the tweet is posted
-
Brian Jesse Hendrickson June 30th, 2009 @ 04:12 PM
the other way to go is store a rendered copy of the original tweet, that would be a lot more simple. I believe Laconica does it like this
-
-
Johannes Schirge July 1st, 2009 @ 03:51 AM
Tested your commits.
It works if username has changed and is not in use by another user.
If another user takes the (now available) name, posts are redirecting to the new name-owner. Is it possible to assign the posting-id to the user-id?
-
Brian Jesse Hendrickson July 1st, 2009 @ 10:45 AM
The reason I did it this way so far, is because it will work the same whether you click a copy of the status on a remote server or if you click on the original on its original server.
If I save a rendered version, or create a database of posting-id to user-id (for all mentioned @nicknames in each notice) then it's hard to keep the click-behavior consistent for remote users of the Notice and local users of the Notice
or something like that
OMB 0.2 http://openmicroblogging.org might offer some help with this
-
Johannes Schirge July 5th, 2009 @ 12:58 AM
- State changed from “open” to “resolved”
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
a(nother) PHP implementation of the http://openmicroblogging.org standard for distributed microblogging. Compatible with identi.ca and laconi.ca
Brian Jesse Hendrickson
Johannes Schirge