After tweets are deleted, are their IDs ever reused?
1 view
Skip to first unread message
Hans Engel
Jul 20, 2008, 7:33:25 PM7/20/08
to twitter-deve...@googlegroups.com
Just a quick question here. (See subject).
-Hans
Abraham Williams
Jul 20, 2008, 7:39:35 PM7/20/08
to twitter-deve...@googlegroups.com
No. IDs are incremental.
On Sun, Jul 20, 2008 at 18:33, Hans Engel <en...@engel.uk.to> wrote:
Just a quick question here. (See subject).
-Hans
--
| Abraham Williams | Web Developer | Lothlórien Coop | Madison WI
| http://abrah.am | http://web608.org | http://barcampmadison2.org
| This email is: [] blogable [x] ask first [] private
| Abraham Williams | Web Developer | Lothlórien Coop | Madison WI
| http://abrah.am | http://web608.org | http://barcampmadison2.org
| This email is: [] blogable [x] ask first [] private
Alex Payne
Jul 21, 2008, 1:47:51 PM7/21/08
to twitter-deve...@googlegroups.com
Confirming the below.
--
Alex Payne
http://twitter.com/al3x
Richard
Jul 21, 2008, 6:48:20 PM7/21/08
to Twitter Development Talk
I notice that there is no way to get a list of deleted message ids
from your friends or a individual user or everyone, which makes
actually deleting them from your cache after you have received them
fairly difficult if not completely impractical. It seems that without
this feature, 'deleted' tweets will live on around the web in various
places forever.
from your friends or a individual user or everyone, which makes
actually deleting them from your cache after you have received them
fairly difficult if not completely impractical. It seems that without
this feature, 'deleted' tweets will live on around the web in various
places forever.
Chris Meller
Jul 21, 2008, 9:40:45 PM7/21/08
to twitter-deve...@googlegroups.com
On Mon, Jul 21, 2008 at 6:48 PM, Richard <ryt...@gmail.com> wrote:
I notice that there is no way to get a list of deleted message ids
from your friends or a individual user or everyone, which makes
actually deleting them from your cache after you have received them
fairly difficult if not completely impractical. It seems that without
this feature, 'deleted' tweets will live on around the web in various
places forever.
I would say that there should probably always be some sort of timeline for expiring tweets from any cache, as it's probably not feasible to convey which tweets have been deleted. Either expire them and re-fetch them after x interval, or accept the fact that you're always going to have deleted tweets that haven't been accounted for.
Given API limitations and the volume of tweets vs. deletions, I'd say living with deleted tweets is probably going to be the end result.
Hans Engel
Jul 21, 2008, 11:08:00 PM7/21/08
to twitter-deve...@googlegroups.com
This is why I was asking the question - currently when a user deletes a
tweet in the timeline of my app, it shows up again due to caching. I was
thinking of storing a local array of deleted tweets, the keys being the
deleted tweet's ID - and checking if each tweet shown in the timeline is
mentioned in the deleted-tweets array. But, if these IDs are reused, I
probably shouldn't pursue this method, right?
tweet in the timeline of my app, it shows up again due to caching. I was
thinking of storing a local array of deleted tweets, the keys being the
deleted tweet's ID - and checking if each tweet shown in the timeline is
mentioned in the deleted-tweets array. But, if these IDs are reused, I
probably shouldn't pursue this method, right?
Damon Clinkscales
Jul 22, 2008, 3:14:31 AM7/22/08
to twitter-deve...@googlegroups.com
On Mon, Jul 21, 2008 at 10:08 PM, Hans Engel <en...@engel.uk.to> wrote:
> But, if these IDs are reused, I probably shouldn't pursue this method, right?
> But, if these IDs are reused, I probably shouldn't pursue this method, right?
They aren't reused.
-damon
Richard
Jul 22, 2008, 5:57:06 AM7/22/08
to Twitter Development Talk
Well I think given the API limitations, I can see just living with
deleted tweets. What I think is odd is, that the Twitter site lets you
delete tweets even though behind the scenes the toothpaste is out of
the tube so to speak.
In the last 2 weeks my friends have created around 9000 tweets, which
would take 45 requests to check for deletions and I only have around
100 friends. When you consider some people have 20,000 friends and you
might want to store their entire history too then so doing this is
impractical at the very least because of the 100 request limit of
Twitter's side and the amount of resource needed on the client side.
deleted tweets. What I think is odd is, that the Twitter site lets you
delete tweets even though behind the scenes the toothpaste is out of
the tube so to speak.
In the last 2 weeks my friends have created around 9000 tweets, which
would take 45 requests to check for deletions and I only have around
100 friends. When you consider some people have 20,000 friends and you
might want to store their entire history too then so doing this is
impractical at the very least because of the 100 request limit of
Twitter's side and the amount of resource needed on the client side.
Reply all
Reply to author
Forward
0 new messages