Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion in_reply_to_status_id

Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Received: by 10.90.84.17 with SMTP id h17mr174209agb.20.1218992845860; Sun, 17 
	Aug 2008 10:07:25 -0700 (PDT)
Date: Sun, 17 Aug 2008 10:07:25 -0700 (PDT)
In-Reply-To: <ca1278640808141034w2de556a6v3f5adf400abb624f@mail.gmail.com>
X-IP: 70.104.205.13
References: <ca1278640808141034w2de556a6v3f5adf400abb624f@mail.gmail.com>
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; 
	rv:1.9.0.2pre) Gecko/2008081604 Firefox/3.0.1pre,gzip(gfe),gzip(gfe)
Message-ID: <1b589dd8-d713-458b-bce5-9bd23f5156c9@t54g2000hsg.googlegroups.com>
Subject: Re: in_reply_to_status_id
From: me at work <me.at.w...@gmail.com>
To: Twitter Development Talk <twitter-development-talk@googlegroups.com>

I think this is totally awesome and great and I love you for having
implemented it.  The next thing would be a way to update an old
update's in_reply_to in the API, mainly so that sites like quotably
which implement a way to fix which tweet you're replying to (sorta)
could post back updates to the user.  Of course, I'd support it in a
certain implementation (but these are not for twitter, but for
quotably and just general discussion of how this API could be useful)

Changes made by the logged in user to his own tweets would happen
instantly.

Changes made by logged in trusted users to a users tweets (i.e. your
friends), or by the person the SPECIFIC TWEET is in reply to (so I
could fix, for example, a newbie friend of mine's tweet to be in reply
to the correct tweet of mine) would happen instantly, but would show
up in a user's control panel on quotably and they could review and
undo (quotably would have to store the original in_reply_to for this).

Changes made by untrusted users would go to a queue which trusted
users, the person who made the specific tweet, and the user himself
could check and approve.

Of course, those are the default settings, some users may want to have
complete control so that everything would go to a queue.  I just like
the idea of crowdsourcing retro-reply-repairs.