Hi Matt,
thanks for your feedback. I think the following paragraph can't be
generalized, though:
> > Why will you not grandfather existing applications into DM access?
>
> Grandfathering all existing read/write tokens assumes they all wanted
> access to DMs. The feedback we’ve had from users and
I can see no reason for Twitter to do this other than to put all other
Twitter clients at a disadvantage. I've been wondering for quite a
while why I should use Twitter.
I guess you don't really care about user experience... only control.
--
Twitter developer documentation and resources: https:
OK, I spent the last hour searching for "incorrect signature" posts
and did not solve my issue.
When trying to post with oAuth I get "Incorrect Signature." It works
fine if I log in first, my script works perfectly, but if I rely on
the oAuth to log me in it does not work, "Incorrect Signature."
Matt,
Could you Advocate that they do so?
:-)
Thanks,
BB
On May 18, 5:45 pm, Matt Harris wrote:
> Hi BB,
>
> I don't have anymore information i'm afraid.
> All I know is they are not accepting any more applications right now.
>
> Best,
> @themattharris
> Developer Advocate, Twitterhttp://twitt
Thanks Matt,
Two important implementation questions that aren't 100% clear from
that announcement or any supporting docs at this point;
1) "we are also restricting this permission to the OAuth /authorize
web flow only"
To be clear, does this include using the OAuth "/authenticate" method
as well
Thanks for the clarification and bug link Matt!
I understand how big of a pain supporting this legacy method must be,
especially given the fundamental changes in #newtwitter. I just wanted
to emphasize how many sites still use this and probably aren't in a
position to easily figure out how to fix
Hi Jonathan,
This is being investigated by our engineers at the moment. We'll be posting
updates to this ticket on our issue tracker:
http://code.google.com/p/twitter-api/issues/detail?id=1650
Best,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
On Wed, May 18,
> Please continue to send
> us your feedback about the permission model and what you would like to
> see it offer.
Why?
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.
Hi BB,
I don't have anymore information i'm afraid.
All I know is they are not accepting any more applications right now.
Best,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
On Wed, May 18, 2011 at 5:10 PM, BB wrote:
> Matt,
>
> Thank you very much for the prompt
Interesting ideas. I have started to do that a little by setting up a
php proxy script on another webserver and checking to see if my
remaining hits are really low, and switch over to querying through the
proxy if it's low. The #1 problem with that method is that I'm using
shared hosting which can
I'm totally with you guys on the value of switching to web intents,
and we recommend all our customers doing new implementations use them.
However, there are just too many legacy implementations against the
"old hack", as Taylor deemed it, for you to expect everyone to switch
over in such a timefra
Thanks Matt!
I still urge you to reconsider the mass breakage of older existing apps, and
crippling of the mobile/desktop app user experiences going forward.
My own judgement is that yes, maybe the user didn't realize that they didn't
want to give that level of access and maybe the web flow c
Thanks Matt!
I still urge you to reconsider the mass breakage of older and existing apps
and the crippling mobile/desktop user experiences apps going forward.
My own judgement is that yes, maybe user didn't realize that didn't want to
give that level of access and matbe the web flow can help
Twitter is just wrapping your link in t.co. When it gets displayed in
Twitter, it will show the link on your domain as you passed it in.
On May 18, 12:35 pm, Mo wrote:
> Since switching to the new "Intents" linking, by URLs are being
> shortened. I have a registered Twitter application, and a rel
Hi BB - it looks like Matt has answered this question in another
thread:
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/6b37774d6db29b9
Thanks,
@jasoncosta
On May 18, 3:46 pm, BB wrote:
> Hello Jason and other folks that made it to #devnestSF,
>
> I did not make i
Hey everyone,
Thank you for all the feedback on the list, email and through Tweets.
We've been responding throughout the day to many of the Tweets but
wanted to group the questions together and respond here as well.
> Two weeks is not enough time to implement a web OAuth flow and have the app
>
Matt,
Thank you very much for the prompt reply.
2 follow ups though:
Do you ever foresee this happening?
And if so do you have an approximate time-frame?
Or if you tell me would you have to kill me?
:-)
Thanks,
BB
On May 18, 4:54 pm, Matt Harris wrote:
> Hi BB,
>
> We're not accepting any n
On May 18, 2011, at 12:01 , Matt Harris wrote:
> We know this will take some time so we are allowing a transition period until
> the end of this month.
Gentlefolk,
This is way too short an amount of time to implement OAuth and
transition mobile users off of an xAuth based client.
Hi BB,
We're not accepting any new applications for the details pane at the moment.
Should this change we will let everyone know.
Best
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
On Wed, May 18, 2011 at 4:02 PM, BB wrote:
> Does anyone know when (if ever) twitt
Please exclude xAuth mobile clients from this, logically and from the
usability point of view, it doesn't make any sense, the user authorize my
app to use his account, why i ask for his authorization again to view his
Direct messages, why you insist on making our life very hard :(
--
Twitter
Matt,
This maybe a harder architectural shift, but a better solution would be to
move permissions from being per application, but instead a per
authentication token method, wherein that each token stores the permissions
that the app requested and was granted at the time they authorized.
So i
Does anyone know when (if ever) twitter will open up the details pane
to new companies?
Thanks,
BB
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-
Hello Jason and other folks that made it to #devnestSF,
I did not make it out. I had one huge question and I wonder if any of
the other folks had it:
When (if ever) will twitter open up embedding in the details pane to
new companies? (specifically video players)
Did anyone else ask this? What
nevermind, i must have been out of the loop.. i was using the old form
so use http://dev.twitter.com/apps
and DO NOT USE http://twitter.com/apps (which, should be deleted or
auto-forwarded or something)
caramba,
-chad
On Wed, May 18, 2011 at 3:47 PM, Chad Etzel wrote:
> Aside from all the
Aside from all the emotional/philosophical stuff in this thread, I am
concerned about a major possible bug:
I have updated my apps to use Read/Write/DM permissions, and then it
saves it as Read-Only... I tried to change it back to just Read/Write,
and again it is saved as Read-Only.
Is anyone els
I agree this nice idea.
On 5月19日, 午前2:30, Fabien Penso wrote:
> Another one :
>
> It would be nice to have those events in the stream (new blocked user
> / removal of a blocked user) so we don't need to fetch those through
> the REST API once our streaming process is running.
>
>
>
> On Wed, May
Hi,
I'm trying to put a tweet button in a Spanish site, but when the URL
being sent has accents in it (for example, using an á char -%E1-), I
get a "Malformed URI sequence" error. I've tried the button and it
works for every other case.
Is there anything I can do about this?
Thanks!
Micaela.
--
Quick question and a comment.
1) I see the new Default Access type as "Read, Write & Private
Message" not "Read, Write & Direct Messages." Is there a typo
somewhere?.
2) I just have to agree with everyone here that having all of our
users re-auth our app to give them access to a feature they've
thats because it was my birthday
From: timw4mail
To: Twitter Development Talk
Sent: Wednesday, 18 May, 2011 21:10:31
Subject: [twitter-dev] Problem getting request tokens on REST API
As of yesterday, May 17, I've been unable to get request tokens to
login via
On Wed, May 18, 2011 at 11:37 AM, Jon Colverson wrote:
>
> Also on the subject of granularity, it would be great if the app could
> request DM access but make it optional, such that users can turn it
> off on the authorization page. If the user declines it then the app
> would be able to ask them
The more I think about this, the less it makes any sense whatsoever to
force everyone through a re-authentication if DM access is required.
Here's why:
1) For existing user tokens, the users have already granted access
with the knowledge that it is to their DMs as well. In other words,
they have
As of yesterday, May 17, I've been unable to get request tokens to
login via the API for my web-based Twitter client.
Now, whenever I try to get a request token, I get a 401 HTTP code,
"Failed to validate oauth signature and token"
The url in question:
https://timshomepage.net/twitter/login
The a
On Wed, May 18, 2011 at 12:50:30PM -0700, Derek Gathright wrote:
>I agree with Scott. A token should simply be a bond between the user
>and the app, it should not contain any knowledge of
>permissions/restrictions. A token simply represents "Hi, I'm making a
>call on behalf of Joe
I agree with Scott. A token should simply be a bond between the user and
the app, it should not contain any knowledge of permissions/restrictions. A
token simply represents "Hi, I'm making a call on behalf of Joe User.
Attached is the request I want to make. Make sure I'm allowed to do this
befo
Since switching to the new "Intents" linking, by URLs are being
shortened. I have a registered Twitter application, and a relatively
short URL already ( http://TagsBy.me ).
I'd like to continue using my own URLs, even if it means I have to
build a shortener with an even shorter domain. However, I'
Hello,
There have been a lot of opinions voiced about how this is being implemented.
This not only proves troublesome for xAuth clients, but it lends me to worry
about how the future of permissions will evolve. Effectively now, every single
Twitter user needs to get their application re-authed
I had most of the same thoughts already mentioned in this thread so
wont reiterate everyone, except to add that this seems like a rather
sudden and disruptive change coming just after #devnestsf where
Twitter made a point that it was trying to provide better guidance so
companies that rely on the p
Hello.
For my app, it's inconvenient that the DM permission is only available
lumped in with the write permission, because now I have to request
both even though my app has no facility for posting (it's a
notification-only app), and I expect users will (rightly) be
suspicious about that.
Also on
I very much agree. To get xAuth, we all had to apply and undergo some
sort of verification process.
Also, if I take my app Gravity as an example, I am using xAuth (and
previously Basic Auth) since the very beginning and there have been
zero complaints from users that Gravity has been misusing the
Hi, Jigs,
You're probably best off running your regex search and doing any replacing
within your own application, before you send the tweets off to Twitter --
once the tweet's been tweeted, there's no way to modify it.
You could probably follow your users, search for suspicious tweets, delete
the
Hi Matt,
1. xAuth apps are already approved by you guys and have a (I'm assuming)
higher threshold to get access to. I'd really ask you guys to re-consider and
allow xAuth access to DMs. Or at the very least allow clients to apply for
exceptions to this rule.
2. Under 2 weeks is way too short
Hi Matt,
I understand the change need to happen. In regards to xAuth though and
finding an upgrade path, the assumption is that those that got access to
that were developing desktop/mobile clients (not centralized services) so
there is no centralized storage of tokens or user data (only in stan
Matt,
Ultimately I understand the issues with xAuth and granularity. Frankly, if
you just ditched xAuth entirely, I can see decent arguments for it.
However, we've made a significant investment in the xAuth UX. If we have to
change it, 13 days is simply not sufficient for most devs. It will be
--
http://twitter.com/znmeb http://borasky-research.net
"A mathematician is a device for turning coffee into theorems." -- Paul
Erdos
Quoting Matt Harris :
Hey everyone,
We recently updated our OAuth screens to give users greater transparency
about the level of access applications have to t
Matt,
If I understand correctly, activate the new permission, all Read and
Read/Write user_tokens issued to third-party applications will lose
their ability to read direct messages.
That is a HUGE and MAJOR headache for existing apps and their
thousands of users who are currently using any of the
Hi Matt,
can you please give us more time to adapt to this. It is impossible to
make the appropriate changes and submit to appstore within this
timeframe.
Thanks,
Ole, Gravity Twitter Client for Symbian
On May 18, 7:01 pm, Matt Harris wrote:
> Hey everyone,
>
> We recently updated our OAuth scr
Sounds good! Also sounds like you folks are finally trying to get rid of
xAuth :-)
Of course, for desktop (and mobile) applications this will mean that
they will have to integrate the normal OAuth flow. "Yay!".
In the past, I've seen several occurrences where popular clients weren't
affected
Another one :
It would be nice to have those events in the stream (new blocked user
/ removal of a blocked user) so we don't need to fetch those through
the REST API once our streaming process is running.
On Wed, May 18, 2011 at 10:27 AM, Fabien Penso wrote:
> Thanks Taylor,
>
> I wish the strea
"We know this will take some time so we are allowing a transition period
until the end of this month."
This is such a short timeframe for people to rebuild, QA and resubmit their
apps that it will certainly mean some peoples apps will stop working while
they are waiting for them to be 'approved
Thanks Taylor,
I wish the streaming did, is that planned at all in the future? Don't
want to code something if you guys are planning it soon :)
On Wed, May 18, 2011 at 7:30 AM, Taylor Singletary
wrote:
> Hi Fabien,
> The Streaming API/Site Streams/User Streams don't support certain kinds of
> po
The new permissions level is welcomed by me and a good idea. Removing
the ability for xAuth to access DMs is insanity, pure and simple.
I presume your iOS and Mac clients will be switching off xAuth access
as well then?
On May 18, 6:19 pm, Jim Cortez wrote:
> Matt,
> You say:> This means ap
Matt,
You say:
This means applications which use xAuth and want to access direct
messages must send a user through the full OAuth flow.
What if the client using xAuth has no browser and therefore cannot go
through oAuth? Does this mean that direct messages cannot be accessed?
Is there a pro
Hey everyone,
We recently updated our OAuth screens to give users greater transparency
about the level of access applications have to their accounts. The valuable
feedback Twitter users and developers have given us played a large part in
that redesign and helped us identify where we can do more.
Hey Anand,
I'm not sure to understand what you're exactly doing? If you're using the
API to update a user's status behind a proxy, did you specify in the code /
lib you're using the HTTP proxy to tunnel requests through? Are you sure
it's not a DNS issue?
Try to provide us more details, please. O
Hey Journey,
There is no dedicated API method to retrieve the most retweeted tweet
in a given time window. However, every status object comes with a
"retweet_count" attribute that you can for example use to curate the
most retweeted tweets of a timeline, a list...
Hope that helps!
Arnaud / @rno
Hi Omar,
Sorry for the confusion -- we recommend Web Intents as we've developed the
Tweet Intent specifically for this purpose -- let us know what tweaks you
think the display needs to "look good" in a full browser tab. Intents are
optimized to load quickly and service the user's intent as efficie
For a case of single-account use like this, you're totally fine using the
API to programmatically follow. Most of the terms around automated following
are clarified here:
http://support.twitter.com/entries/76915-automation-rules-and-best-practiceswith
some more general information on the limits of
Hi Fabien,
The Streaming API/Site Streams/User Streams don't support certain kinds of
post-filter user settings like blocked users/"no retweets from this
user"/etc. -- if you want to provide that filtering, you can keep an index
of the users they block and filter in real time.
http://dev.twitter.
Matt, what happened to the mobile version of these new OAuth screens?
Is there no mobile version at all?
There used to be automatic mobile detection (based on user agent) and
rendering of mobile friendly screens:
http://mashable.com/2010/02/03/twitter-oauth-mobile/
This all stopped working when
Hi
I'm working on a website how expose interesting things about cooking and
food.
We have created a service how use the stream API to get information about
people on twitter talking about our subject of interest.
In our website, if our administrator thinks that content is good enough, he
mark the
Hi All,
I recently launched this website: http://makesmyjobeasy.com
I have had a few people tell me that the scroll bar visible on the
right of the twitter search widget used to move the tweets up and down
so you can see the rest doesnt appear on the Safari iPad2 browser
(unsure about ipad1).
An
No, twitter doesn't filter any tweets text. Low quality users will be excluded
from search results.
On 18 May 2011, at 07:17, journey wrote:
> hi guys,
>
> does any can give me a guideline of how does Twitter handle this
> filtering - Spam, obscenity, questionable content, etc.
> After go throu
Hello,
I need one help regarding encryption or masking certain keywords when
a user accidently keys in sensitive information e.g. SSN (XXX-yy-)
to anyone (as opposed to DM) which gets displayed on the time line
e.g. i tweet as per
@jigsb my SSN # is XXX-yy-.
When it gets displayed on the
hi guys,
does any can give me a guideline of how does Twitter handle this
filtering - Spam, obscenity, questionable content, etc.
After go through the api, i didn't find any information about it. does
that means twitter does not do any filter for obscenity,questionable
content?
thanks,
Journey
-
Hi guys,
I want to get a tweet which has the highest retweet count number
during the last five minutes. Does the api support this? if not
support, is there a plan to support it in the future?
thanks,
Journey
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API update
Hi,
While posting the Messages on the mapped user wall we are getting
below show error
"The remote name could not be resolved: 'api.twitter.com'"
Please advice us to over come this issue.
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: htt
+1. Thanks for the update Arnaud. This is affecting all of our customers at
the moment.
Cheers,
Omar
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitt
Hey There,
+1. This issue is affecting all of our products at the moment. I can't
find any notification anywhere about this being deprecated today.
Please restore this functionality. And allow us some time to migrate
w/ a date in mind. If it's no longer going to be supported, we need to
know soone
Me too. What I was able to figure out is managing your application
through https://twitter.com/apps/edit/ does not save the read-write
property, but dev.twitter.com/apps does.
On May 14, 12:29 pm, Ciarán McCann
wrote:
> I currently have the same problem. Very strange.
--
Twitter developer docu
This is a follow up to an existing thread (which I am unable to reply
to):
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/5a287ab379497e97/321508b2463573d7?lnk=gst&q=block#321508b2463573d7
Our application is experiencing the exact same problem. The block API
call ofte
70 matches
Mail list logo
