Please let me know when it's possible for average API users to access
OAuth authentication for their apps?
This page seems to be open to all:
http://twitter.com/oauth_clients/new
So just as an FYI... It's not just fast140.com that's doing this
In order of offenderness (the most spam first) its also currently:
wefollow.com (5x the spam of fast140.com)
fast140.com
tinychat.com
macheist.com
geofollow.com
... and many more I'm sure...
On Apr 15, 7:17 pm, Rod Begbie
Jesse, so what is it about mass DMs that bugs you? Just curious? You
would only recieve one DM and it would look like any other DM. So
what's the issue?
I agree with Chad though... There's already a way to do this
Update your status... I know where you're going with this feature
though
We're actually getting a different issue with the image.
When users visit our site, click on Twitter Connect or OAuth, if the
user uses Internet Explorer, they get a message that says the logo on
the Twitter login page is not secure. Do you want to download the non-
secure items. I guess that
The OAuth Beta is now open to anyone. Everyone can use OAuth services.
On Apr 16, 10:22 am, Adrian spiritpo...@gmail.com wrote:
Please let me know when it's possible for average API users to access
OAuth authentication for their apps?
This page seems to be open to
It is an open beta now. Anyone can do it.
On Thu, Apr 16, 2009 at 04:22, Adrian spiritpo...@gmail.com wrote:
Please let me know when it's possible for average API users to access
OAuth authentication for their apps?
This page seems to be open to all:
http://twitter.com/oauth_clients/new
Dittoing Cameron here, Twitterfall isn't seeing it any more, though it
was practically disabling us last night and I was getting concerned,
because I slowed things down greatly but to no avail, and I thought
I'd missed some update about it.
The HTTP status code was 403 IIRC.
Another +1 for
THANKS Peter!
It works!
On Apr 16, 12:12 pm, Peter Denton petermden...@gmail.com wrote:
and you could bump up the while loop to 15, to get 1500 results, like...
while ($page_num = 15 )
notivce in the search URL rpp=100 (results per page) and page=$page_num
(pagination), so you can get 1500
Hi,
Over at the Tipjoy blog, I'm posting free ideas on how to use our
Twitter Payments API for our API contest.
The latest is about paid protected accounts, where you pay to get
access to the stream.
Check it out:
http://tipjoys2cents.blogspot.com/2009/04/tipjoy-api-idea-2-paid-protected.html
Hi all,
The lang=XX missing in the next page URL is a bug. Please open an
issue so I remember to fix it.
Thanks;
— Matt Sanford / @mzsanford
On Apr 15, 2009, at 10:44 PM, Chad Etzel wrote:
The website uses a cookie to store your most recent language
selection.
If no lang=foo
package jtwitter;
import java.net.MalformedURLException;
import java.text.ParseException;
import java.text.SimpleDateFormat;
import java.util.Date;
import java.util.Locale;
public class TwitterEntry {
// Twitter Entry Nodes (each corresponds to a XML node with the same
name)
Hi everyone,
This error check has always existed in the search code, but most
people never see it. This is a sanity check on the since_id parameter
to prevent people using ones in the future. The problem yesterday was
specifically that several back-ends fell behind. If you hit an up-to-
Please add a section for Search API HTTP return codes and Error
Messages, and please make sure each set of codes/errors (REST v.
Search) is clearly indicated.
Also a Search Return Values page would be nice :)
-Chad
On Mon, Apr 13, 2009 at 7:11 PM, Doug Williams d...@twitter.com wrote:
Coderz,
On Wed, Apr 15, 2009 at 6:11 PM, Mario Menti mme...@gmail.com wrote:
Thanks Guan - perhaps it's an issue with the signature base string not
being encoded correctly at my end... let me dig into Net::OAuth a little
more and see what I find.
Quick update: yes, the issue in Net::OAuth was
A best practices page would be nice. Could include tips like make calls
using user_id instead of screen_name incase the screen_name changes.
On Thu, Apr 16, 2009 at 10:43, Adrian spiritpo...@gmail.com wrote:
Would love to see something about OAuth, to help in the migration
process.
On Apr
Hi Adrian,
This is caused by the same cache issue as issue 463 [1].
Thanks;
— Matt
[1] - http://code.google.com/p/twitter-api/issues/detail?id=463
On Apr 16, 2009, at 01:06 AM, Adrian wrote:
Wondering why friends count here is 791:
http://twitter.com/users/show/rssfriends.json
but
Hi there,
My initial wording for the pages was much stronger and the
biggest complaint during testing was that it scared people off … so I
obviously side with stronger language. In the light of how people are
using OAuth it seems like we need something more. I'll talk with the
I think it was the 'poll less frequently' that was throwing us all
off. Glad to hear it was just a sanity check going...insane.
-David
On Apr 16, 4:01 pm, Matt Sanford m...@twitter.com wrote:
Hi everyone,
This error check has always existed in the search code, but most
people never
What if my Google App Engine app uses the Search API instead? If I'm
not mistaken, I can't make an authenticated call to the Search API.
What should I do if I hit any limits in that case?
—Guillermo (http://twitter.com/gesteves)
On Mar 26, 12:43 pm, Alex Payne a...@twitter.com wrote:
Indeed,
Very cool!!!
I can't wait to dive in!!
Jamie
On Apr 15, 9:12 am, Nick Toumpelis nicktoumpe...@gmail.com wrote:
Hi,
Just wanted to let everyone know that I've released my (beta) Obj-C/
Cocoa twitter client (Canary) as open source
here:http://github.com/macsphere/canary
, under an
Matt has deployed our answer for one click login. It requires only a small
change to the normal Twitter OAuth workflow and is documented here:
http://apiwiki.twitter.com/Sign-in-with-Twitter
This is the perfect tool for web applications wanting to offer users the
ability to sign in with a
Zac, this can be solved just be properly modeling user accounts and
twitter accounts.
It should be one-to-many. Signing in with any of their twitter
accounts can sign in that user.
Let me know if that doesn't address your problem.
Ivan
http://tipjoy.com
On Apr 16, 1:18 pm, Zac Bowling
Thanks for that! I've also added a page in the project wiki that will
help
resolve some of the issues you may encounter when building the
project.
Nick
On 4/15/09, Alex Payne a...@twitter.com wrote:
Very nice. Added to http://apiwiki.twitter.com/Open-source (and
tweeted about - hope you get
Ivan, that doesn't solve the original problem of getting those
accounts authenticated.
Zac, you should just use the /oauth/authorize link instead. the
/oauth/authenticate link is what will do the auto-redirect.
-Chad
On Thu, Apr 16, 2009 at 1:45 PM, Ivan Kirigin ivan.kiri...@gmail.com wrote:
Sorry, a little confused by your email. :-)
It's really not directly related to twitter sign-on directly but
with OAuth authentication in general that doesn't force the user to
authenticate each time.
The problem is with all OAuth providers that shortcut the process of
associating and granting
That is why there are 2 methods:
1) Authorize that always displays prompt on Twitter.
2) Authenticate that shows nothing if already signed in and authorized.
Use them based on your needs.
Something to keep in mind that OAuth is not designed for identity
authentication. It is designed for data
On 4/16/09 12:55 PM, Doug Williams wrote:
Related: More OAuth documentation is to come throughout the day so
some of the links will be broken. It's a glaring omission in the
documentation.
Let's use this thread to fill the holes people find while implementing
Sign in with Twitter for the time
Hi Dossy,
The initial token required is a RequestToken rather than an
AccessToken. Making the request for the RequestToken requires you know
the consumer key/secret and (a) let's us know what application this is
for (callback_url alone would not) and (b) prevent the token-shooting
On Thu, Apr 16, 2009 at 13:26, Dossy Shiobara do...@panoptic.com wrote:
On 4/16/09 12:55 PM, Doug Williams wrote:
Related: More OAuth documentation is to come throughout the day so
some of the links will be broken. It's a glaring omission in the
documentation.
Let's use this thread to
On 4/16/09 2:33 PM, Matt Sanford wrote:
The initial token required is a RequestToken rather than an AccessToken.
Making the request for the RequestToken requires you know the consumer
key/secret and (a) let's us know what application this is for
(callback_url alone would not) and (b) prevent
I would definitely support greater disclosure here, but would avoid
the checkbox model of authorizing different levels of access (http://
www.flickr.com/photos/factoryjoe/2601626420/sizes/o/).
Instead, you should allow the application developer to pick the
appropriate API access level it needs
Marlo,
You should currently only have one working token per user per application.
There is an open issue [1] that will allow multiple tokens per user per
application.
1. http://code.google.com/p/twitter-api/issues/detail?id=372
Doug Williams
Twitter API Support
http://twitter.com/dougw
On Thu,
Awesome this will definitely improve the process. In particular the
users will only have to face the question of Deny or Allow access
only once.
The only problem I foresee is if multiple users use the same computer.
This way if USERA is already signed in to Twitter and USERB attempts
to log into
On Thu, Apr 16, 2009 at 3:03 PM, Chris Messina chris.mess...@gmail.com wrote:
2. layer in social awareness into the authorization screen so people
have a better sense whether to trust an app
Here's my mockup for #2:
http://www.flickr.com/photos/factoryjoe/3448360090/
Oooh, I really like
On 4/16/09 2:33 PM, Matt Sanford wrote:
The initial token required is a RequestToken rather than an
AccessToken. Making the request for the RequestToken requires you know
the consumer key/secret and (a) let's us know what application this is
for (callback_url alone would not) and (b)
How are you posting the user's credentials to the
/favorites/(create/destroy) calls? And how are you avoiding the
cross-domain ajax limitation?
-Chad
On Thu, Apr 16, 2009 at 2:35 PM, Dr. Drang drdr...@gmail.com wrote:
I'm writing a Twitter webapp using jQuery. One of the features is the
Our users continue to complain about hitting API limits for our app. I
applied to get whitelisted, but got rejected. I'm thinking of creating
several test accounts that run the more intensive API call
procedures as cron jobs, to not use our users' api calls.
Any idea why we got rejected? (app
Great stuff, Chris. Thanks for taking the time to mock it up.
On Thu, Apr 16, 2009 at 12:03, Chris Messina chris.mess...@gmail.com wrote:
I would definitely support greater disclosure here, but would avoid
the checkbox model of authorizing different levels of access (http://
We always supply a reason when rejecting whitelisting requests. That
reason should be in the body of the rejection email.
If you create a bunch of accounts, our spam team is likely to suspend
them. Please address the issues mentioned in the rejection email and
re-apply.
On Thu, Apr 16, 2009 at
We provide you the ability to programmatically throttle your API usage on
the client side. I've documented it here [1]. If your users are complaining,
then you should take the time to use the tools described in the
documentation to gracefully handle API usage.
1.
I see it now, I'm all over it. First one to get single signin working
wins. :)
On Apr 15, 5:56 pm, Doug Williams d...@twitter.com wrote:
Yes, we are working on something that will make what you are asking for,
djMax, a working feature. I'm writing the documentation now.
Doug Williams
Yeah, but I think giving people a little bit of a scare is exactly the right
thing to do. It wasn't until I was writing my first email that I realised
that an authorized app could change my display name and avatar, or block
followers!
Ideally, I would like there to be finer-grained permissions
On Thu, Apr 16, 2009 at 12:21 PM, Chad Etzel jazzyc...@gmail.com wrote:
Thinking along these lines... what if, in the Connections tab, each
user were able to rate each app they've authorized on a 1-5 star
scale? Then the auth page could show the average rating by users, or
something like
Looks like it's working perfectly now. Thanks guys.
-Isaac
On Apr 14, 11:53 am, Matt Sanford m...@twitter.com wrote:
Hey Abraham,
Checkout the dreaded issue 433 as we found out there is a bug in
that RESERVED_CHARACTERS depending on the $KCODE variable.
Thanks;
— Matt
On Apr
On Thu, Apr 16, 2009 at 8:17 PM, Doug Williams d...@twitter.com wrote:
Marlo,
You should currently only have one working token per user per application.
There is an open issue [1] that will allow multiple tokens per user per
application.
1.
On Apr 16, 9:52 am, Doug Williams d...@twitter.com wrote:
Matt has deployed our answer for one click login. It requires only a small
change to the normal Twitter OAuth workflow and is documented here:
http://apiwiki.twitter.com/Sign-in-with-Twitter
This is the perfect tool for web
I'm adding my opinion to this thread after a little bit of back-and-
forth with @simX and @KuraFire on Twitter the other day. 140
characters is just not enough to convey a complete argument.
This change of functionality has turned a feature that was in a
definite gray area, to black and white.
There are plenty of available media sources that support mass
advertising and there is no need to add Twitter to the list.
Please bury this idea.
@emergingtech
On Apr 14, 4:24 pm, Alex aybarb...@gmail.com wrote:
I'm wondering if there is a way - or if you would consider adding a
way - to send
I'm with Jesse on this one
On Apr 16, 10:03 pm, Jesse Stay jesses...@gmail.com wrote:
stevenic, after so many followers, that one DM cascades into hundreds. I
don't want my DM box filled with people wanting to sell me stuff. I want
the choice to control that - I don't want the marketers
Sorry if this is a noob question, but how can we verify the
screen_name of an OAuth token? It would seem that having it only out
of band as a query arg means it's subject to spoofing right? Not sure
how I build secure site login with the core identifier may not match
the token I'm given.
Thank you Doug. That is where I was wrong. Is there anyway to excuse
the HTML and just get the Application Name?
On Apr 16, 12:01 pm, Doug Williams d...@twitter.com wrote:
Source parameters that come from outside apps are encoded HTML. Are you
accounting for this Travis? See the source heading
Dont follow the person, they can DM you. Dossy already said this. Twitter
has built in preventative controls called un follow.
The cost of losing a followers is greater the gain of DM'ing them. If
someone wants to DM all of their followers, their should be a relative value
to the user. I have done
Hello again,
We've discussed OpenID but adding it is not something we can do
in the near-term. With OAuth just out the door we felt like this was a
better user experience than have to continually re-display the Accept/
Deny dialog. I'm looking into a few issues raised in this thread
Allen,
OAuth is the third-party authorization protocol that we have decided to
embrace. You can search the group's archives [1] for past discussion on
OpenID and the Twitter API.
1.
Hi there,
I recommend calling verify_credentials with your new token to
verify the user in question. The screen_name was added as a
convenience method because there were a great many complaints about
have to do yet another round trip for the screen_name.
Thanks;
— Matt Sanford
On
On Thu, Apr 16, 2009 at 11:12 PM, ray ray.pig...@gmail.com wrote:
I'm with Jesse on this one
This is like giving somebody the key to the house and then complain
that people can 'just' get into the house.
If you don't want to be DMed by certain people, dont follow them.
If you do get
For me Twitter is a *person* to *person* communication service. Mass DMs
don't fit into that model in a useful way. To stray from this would in my
view be the beginning of the end.
Abraham
On Thu, Apr 16, 2009 at 16:35, Nicole Simon nee...@gmail.com wrote:
On Thu, Apr 16, 2009 at 11:12 PM,
On Thu, Apr 16, 2009 at 5:35 PM, Nicole Simon nee...@gmail.com wrote:
If you don't want to be DMed by certain people, dont follow them.
If you do get something from them, unfollow.
I'm fine with getting DM'd by *people* I follow. But I don't expect to get
DM'd by @cnnbrk or @jetblue unless
On 4/16/09 5:11 PM, djMax wrote:
Sorry if this is a noob question, but how can we verify the
screen_name of an OAuth token? It would seem that having it only out
of band as a query arg means it's subject to spoofing right? Not sure
how I build secure site login with the core identifier may
On Thu, Apr 16, 2009 at 11:42 PM, Ed Costello epcoste...@gmail.com wrote:
I'm fine with getting DM'd by *people* I follow. But I don't expect to get
DM'd by @cnnbrk or @jetblue unless I'm directly engaging them. There's no
granularity to separate getting DM'd by a friend I follow from DM'd
On Thu, Apr 16, 2009 at 5:11 PM, Travis James
deadscene...@hyperhack.com wrote:
Thank you Doug. That is where I was wrong. Is there anyway to excuse
the HTML and just get the Application Name?
I believe they've stated that will happen in API v2. Right now you
just have to parse through the
Yeah, I have to agree with the above post by Nicole.
Believe it or not, the fact that some people don't want this is an
argument for it, because it demonstrates that there is a difference
between simply updating your status (as others have suggested as an
alternative) and DMing all followers.
Even as a marketer, and someone who uses social media in marketing
efforts I am not in favor of mass DMing. If people are actively
interested in what I have to say they will follow me (or my company) -
if I have an event, webinar, product release, whatever to promote I
update my status and it is
Doug,
What kind of use case do you think that would be acceptable in? I
simply can't imagine one that's not going to be spam.
On Apr 14, 7:46 pm, Doug Williams d...@twitter.com wrote:
Alex,
That sounds very spamish although there are certainly some use cases where
it is acceptable. Proceed
Please don't do this in any way shape or form. It's bad manners, bad
form, and straight up spamming.
On Apr 14, 7:24 pm, Alex aybarb...@gmail.com wrote:
I'm wondering if there is a way - or if you would consider adding a
way - to send a DM to all followers via the API?
Obviously we could
http://apiwiki.twitter.com/REST+API+Documentation#account/updateprofileimage
says
image. Required. Must be a valid GIF, JPG, or PNG image
So it's safe to assume that anything I pull out of profile_image_url
is going to be either .gif or .jpg or .png?
TjL
Stevenic,
If I received one, just one tiny little DM from each one of my
followers, every day, I would get more than 30 times the amount of
spam that my email gets. And I've had that same email account (not
this one) for over 10years. Why should I be subjected to every
twitter secrets marketing
An idea is to have the oauth/authorize page display login/don't login
instead of accept/deny if the user has already approved the application.
On Thu, Apr 16, 2009 at 16:29, djMax djm...@gmail.com wrote:
Did this stop working? All of the sudden I'm getting 500 server
errors back. Was
Apps that provide this capability have the responsibility to let us opt-out.
I don't see the problem here. If people don't want to receive DMs from your
app, why should they have to. Plain and simple. I follow people not to
receive marketing DMs from them, but rather so they can communicate with
The current language to access and update your data on Twitter is so
vague as to be meaningless.
Agreed.
I would definitely support greater disclosure here, but would avoid
the checkbox model of authorizing different levels of access (http://
On Thu, Apr 16, 2009 at 11:34 PM, guruvan guru...@gmail.com wrote:
Dossy, not this doesn't work for me. I don't really a) have time or b)
want to unfollow a new follower (and likely new user of twitter)
because of poor first judgement. I would like to simply opt-out of
those types of
Please don't mess with Twitter and turn it into just another
communication tool. We don't want to mass DM our followers, and we
certainly don't want them mass DM-ing us. If they can't say what they
want to say to us in 140 characters or less, they can go to the
website and contact us that way.
the oauth_token you are returned is only good for getting an access token
from oauth/access_token. that access token is what lets you act as the user.
On Thu, Apr 16, 2009 at 16:36, djMax djm...@gmail.com wrote:
Ok got it. This explains more. So when I call authenticate (rather
than
On Thu, Apr 16, 2009 at 11:59 PM, Jesse Stay jesses...@gmail.com wrote:
Apps have an ethical responsibility to provide opt-out, plain and simple if
they're going to enable the sending of mass-DMs in any way. I didn't
opt-into getting sales advertisements from the people I follow when I joined
On Thu, Apr 16, 2009 at 4:00 PM, Nicole Simon nee...@gmail.com wrote:
On Thu, Apr 16, 2009 at 11:34 PM, guruvan guru...@gmail.com wrote:
Dossy, not this doesn't work for me. I don't really a) have time or b)
want to unfollow a new follower (and likely new user of twitter)
because of poor
@TwitReport has, until today, auto-followed anyone who followed it,
for functionality of the app (basically, being able to get a DM with
some basic information about your new follower).
In the last few days apparently it ended up on some list of
auto-followers, and I saw about 50 new followers,
On Thu, Apr 16, 2009 at 5:59 PM, Jesse Stay jesses...@gmail.com wrote:
I didn't opt-into getting sales advertisements from the
people I follow when I joined Twitter.
Uh, yes you did. Following somebody = opt-in to receive *whatever*
they want to send you. If the value of the crap they DM
On Thu, Apr 16, 2009 at 4:02 PM, Nicole Simon nee...@gmail.com wrote:
On Thu, Apr 16, 2009 at 11:59 PM, Jesse Stay jesses...@gmail.com wrote:
Apps have an ethical responsibility to provide opt-out, plain and simple
if they're going to enable the sending of mass-DMs in any way. I didn't
On Fri, Apr 17, 2009 at 12:04 AM, Jesse Stay jesses...@gmail.com wrote:
If you don't have the time to do it, then hire somebody to do it.
Am I really hearing this right? So now *I* have to lose money because I'm
getting spam??? Yeah right.
If you do not know how to use the tools, then
On 4/16/09 6:02 PM, Abraham Williams wrote:
the oauth_token you are returned is only good for getting an access
token from oauth/access_token. that access token is what lets you act as
the user.
Wait, what? The oauth_token that's returned from the
_oauth/authenticate_ method is already an
On Thu, Apr 16, 2009 at 4:14 PM, Nicole Simon nee...@gmail.com wrote:
On Fri, Apr 17, 2009 at 12:04 AM, Jesse Stay jesses...@gmail.com wrote:
If you don't have the time to do it, then hire somebody to do it.
Am I really hearing this right? So now *I* have to lose money because I'm
getting
Jesse,
If I may ask (and I promise I'm not trying to make this personal, I
really am just curious), what is the value of following 14,000 people?
Surely you know anyone of them could send you a DM at any time? How
do you keep up with them all?
Basically, what is your reason for following a
I think this thread has run its course.
--
Abraham Williams | http://the.hackerconundrum.com
Hacker | http://abrah.am | http://twitter.com/abraham
Web608 | Community Evangelist | http://web608.org
This email is: [ ] blogable [x] ask first [ ] private.
Sent from Madison, Wisconsin, United States
Got several complaints about this from TweetGrid users:
http://twitter.com/VoxAZ/status/1537143626
This can't be good...
-Chad
Chad, the value is 1) I get to show a token of appreciation for them
following me - even if I can't listen to everyone I am at least willing to
give them the opportunity to be discovered, and most importantly, 2) I want
them to have the ability to communicate with me via DM if they want to.
Note
Thanks for the reply Matt...
Just as an FYI...
I updated my code to track duplicates and then did a sample run over a
5 minute period that once a minute paged in new results for the query
http filter:links This resulted in about 11 pages of results each
minute and over the 11 pages I saw
OK, will pursue with my hosted server admins. Thanks!
On Apr 15, 8:06 pm, Alex Payne a...@twitter.com wrote:
You're probably better off writing the firewall rule by domain, if
possible. Our IP ranges are going to change and grow, and they'll be
hard to keep track of.
On Tue, Apr 14, 2009
On Thu, Apr 16, 2009 at 6:53 PM, Jesse Stay jesses...@gmail.com wrote:
Chad, the value is 1) I get to show a token of appreciation for them
following me - even if I can't listen to everyone I am at least willing to
give them the opportunity to be discovered, and most importantly, 2) I want
the query http filter:links (which is a bit redundant) is such a
high volume query that I would doubt that the search servers would
ever be able to keep in sync even when things were running up to
speed.
Try with a less traffic'd query like twitter
-Chad
On Thu, Apr 16, 2009 at 6:55 PM,
Matt... Did you already fix this? I was going to file a bug on it and
I just noticed that now the next and previous links contain the
lang param.
So do you still need a bug on it for tracking purposes or did you
already add one?
-steve
On Apr 16, 1:02 pm, Rod Begbie rodbeg...@gmail.com wrote:
On Thu, Apr 16, 2009 at 12:03 PM, Chris Messina
chris.mess...@gmail.comwrote:
1. create a directory of known/good apps and promote the ones that are
safe (see Facebook)
I would not necessarily hold Facebook up as a good example
On Thu, Apr 16, 2009 at 4:58 PM, Chad Etzel jazzyc...@gmail.com wrote:
On Thu, Apr 16, 2009 at 6:53 PM, Jesse Stay jesses...@gmail.com wrote:
Chad, the value is 1) I get to show a token of appreciation for them
following me - even if I can't listen to everyone I am at least willing
to
It was a bug. Someone brought up a new host and it snuck into the
network configurations. We have removed it and the problem should be
gone.
— Matt
On Apr 16, 2009, at 04:04 PM, Chad Etzel wrote:
Ditto my previous post. eek.
-Chad
On Thu, Apr 16, 2009 at 6:57 PM, stephane
Fixed it in a deploy today, yes. No need for a bug report.
— Matt
On Apr 16, 2009, at 04:03 PM, stevenic wrote:
Matt... Did you already fix this? I was going to file a bug on it and
I just noticed that now the next and previous links contain the
lang param.
So do you still need a bug on
On Apr 16, 12:21 pm, Chad Etzel jazzyc...@gmail.com wrote:
Regarding my buyer beware comment:
I do agree that some/most of the onus is on Twitter to communicate
what exactly is happening (I'm also for stronger language), but users
do have to use their brains at some point and quit blindly
Yes, and going forward, even GIFs won't be allowed, though some remain
in our system.
On Thu, Apr 16, 2009 at 14:55, TjL luo...@gmail.com wrote:
http://apiwiki.twitter.com/REST+API+Documentation#account/updateprofileimage
says
image. Required. Must be a valid GIF, JPG, or PNG image
So
On Apr 16, 2:59 pm, Lachlan Hardy lach...@lachstock.com.au wrote:
I would definitely support greater disclosure here, but would avoid
the checkbox model of authorizing different levels of access (http://
www.flickr.com/photos/factoryjoe/2601626420/sizes/o/).
Why is that? Do you have any
On Thu, Apr 16, 2009 at 7:19 PM, Chris Messina chris.mess...@gmail.com wrote:
On Apr 16, 2:59 pm, Lachlan Hardy lach...@lachstock.com.au wrote:
I would definitely support greater disclosure here, but would avoid
the checkbox model of authorizing different levels of access (http://
So my project is a sort of tweetmeme or twitturly type thing where I'm
looking to collect a sample of the links being shared through
Twitter. Unlike those projects I don't have a firehose so I have to
rely on search. Fortunatly, I don't really need to see every link for
my project just a
Consider this code snippet who's task is to display the first page of
a user's tweets:
const double tweetsPerPage = 20;
string screenName = Dimebrain;
double updatesCount = 821;
double pages = updatesCount / tweetsPerPage;
int last =
1 - 100 of 115 matches
Mail list logo
