Try with a different browser to see if it is caching the old page for some
reason.
On Wednesday, May 11, 2011 at 2:11 AM, Jason Ling wrote:
I edited my app, added a picture and saved, and now it's changed to
'read only' access.
I edit again and select 'read write' and save - and it still
So private feeds aren't indexed by Twitter at all and thus are never searchable?
--
damonp
Sent with Sparrow
On Thursday, May 12, 2011 at 8:44 AM, Rich wrote:
You can't unless you have already cached their timeline by either
being someone following that user or you are authenticated as that
of the Search API (by users with access to
the private feed).
--
damonp
On Thursday, May 12, 2011 at 9:28 AM, Taylor Singletary wrote:
Correct, the Search API's archive represents only publicly issued tweets.
@episod - Taylor Singletary
On Thu, May 12, 2011 at 7:14 AM, Damon Parker
This is from a PHP app I built using a the the twitter-async class:
$tweet = $twob-get('/statuses/show/'.$tw_id.'.json?include_entities=true');
Whatever language you are using, the url you are looking for is:
'/statuses/show/'.$tw_id.'.json?include_entities=true'
Documentation:
As an aside to this thread... In regards to changing the status of an account
from public to private or vice versa, does this only affect the tweets coming
after the change or does it change the whole user's timeline past to present?
Similarly if an account was private and is toggled to public,
I doubt it's network related. http://twitter.com/#!/carlagasparian loads a
blank page for me too from my location.
--
damonp
Sent with Sparrow
On Monday, May 16, 2011 at 10:40 PM, Mohan Arun wrote:
On May 15, 7:50 pm, Carla Gasparian Sartori
carlagaspariansart...@gmail.com wrote:
I have
In any security or permissions context the default should be the most secure
and least amount of permissions to get the job done. That is Computer and
Network Security 101.
A user must explicitly configure more loose permissions on their own after
understanding the implications. This is the
( @janole / @gravityapp )
On May 19, 2:44 pm, Damon Parker cartmet...@gmail.com wrote:
In any security or permissions context the default should be the most
secure and least amount of permissions to get the job done. That is
Computer and Network Security 101.
A user must explicitly configure
It will be interesting to see where the PR nightmare falls more squarely on
when it happens... Twitter or the app developers themselves. We will get the
tech support nightmare but if recent history is any indication (ie. Ubertwitter
ban) many users are going to ultimately blame Twitter.
--
Ole-
You make some very good points, but you can't use the tired users create poor
passwords argument as a reason to stick with outdated security protocols. By
that logic, no security upgrade is worth the time because some dumb users are
going to foil you every time.
If a user wants to chose
On that day when your users open up our various clients and see issues with
direct messages I suggest you insert your own DMs to your users with succinct
descriptions to the root of the problem and links to further info.
It looks like there is no way to prevent having to update apps for those
Frank-
Correct me if I'm wrong, but the applications won't quit working altogether.
You'll get a 403 error when trying to access DMs through the API. Everything
else should work as normal.
Has there been a better official answer if this affects Twitter's own apps
other than this:
Will
Frank-
http://dev.twitter.com/pages/application-permission-model-faq
The way I read the FAQ posted is _only_ apps requiring DM read access will be
affected under the following endpoints:
/1/direct_messages.{format}
/1/direct_messages/sent.{format}
/1/direct_messages/destroy.{format}
I thought this might interest many of you. It was written with the intent of
explaining the development issues in language our end users can understand.
http://www.mediabistro.com/alltwitter/how-private-are-your-private-messages_b9078
We are all worried of how big of a PR fiasco this could be
What are your constraints, coding language, etc.?
What do you want to do with the API?
On Tuesday, May 24, 2011 at 8:50 AM, Davinder Singh wrote:
Requesting help to find a suitable API to integrate with my Twitter
account.
Thanks in advance!
--
Twitter developer documentation and
Then why don't developers do something?
http://bit.ly/lpiADG
On Wednesday, May 25, 2011 at 10:57 AM, TJ Luoma wrote:
On Wed, May 25, 2011 at 11:34 AM, Matt Harris thematthar...@twitter.com
wrote:
When Tweetie became part of the Twitter family the user growth was huge,
creating more
Is anyone working on a choice-based or fallback permissions schema to give
users a choice which permission level they authorize?
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker:
17 matches
Mail list logo
