If user AAAA is no longer the same user as the one that posted status
id 1111, then the link http://twitter.com/AAAA/statuses/1111 would no
longer be valid (as the NEW user AAAA is not the owner of the status
id).
On Jan 30, 2010, at 11:40 PM, Ivan Glushkov <gli.w...@gmail.com> wrote:
Actually i can't.
For example, i get some link like
http://twitter.com/AAA/statuses/111111, for the message that was
posted month ago. I can't be sure if the current user AAA has the same
guid as the AAA month ago.
If i had the link like http://twitter.com/redirect?id=111&status=222 i
would be sure that it's the same user and the same status for that
user.
Ivan.
On Sun, Jan 31, 2010 at 9:36 AM, Michael Ivey
<michael.i...@gmail.com> wrote:
You could do this internally in your application, using statuses/
show to
make sure you have the correct user info before redirecting.
-- ivey
On Sat, Jan 30, 2010 at 4:06 AM, Ivan Glushkov <gli.w...@gmail.com>
wrote:
Oh, thanks, Abraham! That's great!
But why isn't it documented anywhere?
And is there any way to redirect to some status of this user?
I mean smth like
http://twitter.com/account/redirect_by_id?id=9436992&status=33333
???
Thanks once more,
Ivan.
On Fri, Jan 29, 2010 at 11:37 PM, Abraham Williams <4bra...@gmail.com
>
wrote:
Actually Twitter does support it.
http://twitter.com/account/redirect_by_id?id=9436992
Abraham
On Wed, Jan 27, 2010 at 06:42, Ivan <gli.w...@gmail.com> wrote:
Hi.
I don't need an application that is able to handle this. Instead i
need changes in the twitter API so i can refer to the users and
their
statuses using the user id, not the username. This is a problem
for
the aggregator, and there users (so it become also a problem for
the
twitter users).
Is there any plan in this direction?
Ivan.
On 21 янв, 06:03, Abraham Williams <4bra...@gmail.com> wrote:
I remember this topic coming up before and it seems like someone
built
an
application that handled this but I can't find any references
to it.
Maybe
somebody else can?
Abraham
On Wed, Jan 20, 2010 at 06:29, Ivan <gli.w...@gmail.com> wrote:
Hi.
I tried to find the similar question here (in google groups), in
the
FAQ and in the API, but couldn't find anything.
The problem:
Cross-posting the links to the user page and to some his
statuses
in
the web become more and more popular. But, as i understood, you
can't
guarantee that this links not long after would not change the
logical
destination. For example I create some post about some twitter-
user
"aaa" and give the link "twitter.com/aaa"
After that user “aaa” changed name to "bbb" and user "dd
d" changed
name to "aaa". So my old link now points to the different
person.
This problem becomes more serious for the aggregators that don't
know
what content they might approve after a while.
The simplest decision would be providing the possibility to
link to
the user not by name but also by id. That pages might be just
redirections to the original user pages, it doesn't matter.
For example
if the user “aaa” have id 111111, the following two link
s should
point
to the same page:
twitter.com/aaa and twitter.com/id/111111
This mechanism should also be applied for the statuses:
twitter.com/id/111111/statuses/222222
Ivan.
--
Abraham Williams | Moved to Seattle | May cause email delays
Project | Intersect |http://intersect.labs.poseurtech.com
Hacker |http://abrah.am|http://twitter.com/abraham
This email is: [ ] shareable [x] ask first [ ] private.
Sent from Seattle, WA, United States
--
Abraham Williams | Moved to Seattle | May cause email delays
Project | Out Loud | http://outloud.labs.poseurtech.com
Hacker | http://abrah.am | http://twitter.com/abraham
This email is: [ ] shareable [x] ask first [ ] private.
Sent from Seattle, WA, United States
