I'm going to keep the whole thread here because I think some important
distinctions are being raised / discussed.
1. As a developer, I have to create a (minimum) viable product. "Viable"
implies there must be a user interface beyond the command line. Yes, I know
Cameron Kaiser thinks otherwise,
My Twitter app runs on iPhone (and has a server side component that
user doesn't directly interact with). It has been running on Basic
Auth for more than a year. I would like to register it as OAuth and
migrated users over, i.e. running both in parallel under end June
since not everyone will update
Brian, there is no TLS or root CA certificates on this platform. No
browser. No X11. No screen or keyboard for that matter.
On May 14, 11:13 am, "Brian Smith" wrote:
> Mr Blog wrote:
> > For example, the current 'tweet' code binary is 18K bytes. If you can add
> oAuth
> > in 100K bytes or less,
Chrome has it too.
On Sun, May 16, 2010 at 03:20, nischalshetty wrote:
> Isn't console.log() specific to firebug? #JustSaying :)
>
> On May 16, 4:43 am, Larry wrote:
> > Firefox 3.X is a supported browser for @anywhere and my example is
> > properly configured, yet it triggered when it wasn't su
Isn't console.log() specific to firebug? #JustSaying :)
On May 16, 4:43 am, Larry wrote:
> Firefox 3.X is a supported browser for @anywhere and my example is
> properly configured, yet it triggered when it wasn't supposed to. This
> highlights my point of why alert() not a good choice for notific
Hello,
> I had a few bugs with encoding, I was not using UTF8 and now I do, so
> I am able to tweet stauff like "Peñarol á é í ó ú" (spanish lang
> characters). I was making some tests and I noticed that if I want to
> set '!' as my status (just the exclamation mark) it dos not work... I
> get an
Firefox 3.X is a supported browser for @anywhere and my example is
properly configured, yet it triggered when it wasn't supposed to. This
highlights my point of why alert() not a good choice for notification
of incorrect installations. Instead maybe it should use throw(). That
would be more useful
To follow up, if I simply actually call verify_credentials it returns
a valid json object for my request but returns a status code of 401
On May 16, 12:01 am, Rich wrote:
> Has anyone else had problems with oAuth echo and services like TwitPic
>
> I'm using the SAME objective-c library to generat
Has anyone else had problems with oAuth echo and services like TwitPic
I'm using the SAME objective-c library to generate the oAuth signature
as for the client (which by the way the client works fine so the oAuth
signatures for that are fine).
I'm generating the oAuth headers as if it were for
ht
Is there a reference that explains the field types and constraints of
the data coming from the Twitter API?
Some things are a bit uncertain. For example, are user IDs 32bit or 64
bit integers?
Thanks in advance.
I agree that @Anywhere should degrade gracefully when configured properly on
unsupported platforms and not prompt incorrect alert()s. But I do think
alert()s are probably the best way to notify developers of incorrect
installations.
Abraham
On Sat, May 15, 2010 at 11:55, Larry wrote:
> I can re
I'm not particularly familiar with the specifics of WebSockets but here is
the draft documentation: http://dev.w3.org/html5/websockets/
I don't see Chrome Extensions as being any different from desktop
applications as they are both manually installed by the user on their
desktop.
Abraham
On Sat,
I bet coffee and 10 seconds with either of you would fix my problem,
but no worries.
On Sat, May 15, 2010 at 9:02 PM, kuhkatz wrote:
> Am 14.05.2010 23:40, schrieb Faried Nawaz:
>>
>> On May 15, 12:41 am, kuhkatz wrote:
>>
>>> so i suppose i am doing things wrong.
>>> i followed your instruction
I can reliably reproduce this with Firefox 3.0.8 at the following url:
http://cornsyrup.org/~larry/anywhere/index.html
Error console is reporting "S.get is not a function"
Larry
On May 15, 11:31 am, Larry wrote:
> Our site has been running @anywhere for over a week now without error.
> Yesterd
Our site has been running @anywhere for over a week now without error.
Yesterday my coworker was getting the alert(). He is running an older
version of Firefox (3.0.8) on Ubuntu, so there might be another cause
other than missing clientID or version?
I still believe alert() is intrusive, especiall
The first release of User Streams is not intended for web clients due
to capacity constraints.
http://apiwiki.twitter.com/ChirpUserStreams
"
All services, mobile and browser-based clients must not use Streaming
until we've sorted out Desktop clients at some scale. One problem at a
time.
"
That be
Hello. when I call the statuses/home_timeline api method ro retrieve
the tweets, the ids of the tweets that are returned are not correct.
What could be the problem?
All the data except the tweet id are returned correctly.
I use the jmathai's twitter client:
http://github.com/jmathai/twitter-asyn
Hey guys,
Quick question, are there any plans on supporting WebSockets protocol for
the Streaming API?
That'd be awesome for browser based Twitter clients (i.e. Google Chrome
extensions). Without this it'll be very difficult for this kind of client to
lavarage benefit from the upcoming user stream
Am 14.05.2010 23:40, schrieb Faried Nawaz:
On May 15, 12:41 am, kuhkatz wrote:
so i suppose i am doing things wrong.
i followed your instructions, but when i apply the diff, i get this:
$ patch -i twurldiff
Close. You can do either one of
patch -p 1 -i twurldiff
or
git apply twurldiff
Take a look in this post at the suggestion Taylor sent me.
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/c04e4f73929a15c3/d9b6ab0c427493eb#d9b6ab0c427493eb
regards
On May 14, 5:48 pm, bjhess wrote:
> I'm trying to implement the following in Ruby:
>
> http://dev.tw
Great, thanks Adam!
As I said before, many OAuth libs do not support international
characters :(
On May 15, 1:05 am, Adam Ransom wrote:
> I'm working on a Japanese twitter app and have had similar challenges with
> encoding (i.e. the OAuth lib I used didnt support Japanese). I'll have a bit
> of
On May 15, 4:29 pm, Patrick Kennedy wrote:
> I'm sure it mostly my new newness to Ruby; rake/make files are not my
> strong area as well.
You're not stuck on a Ruby issue. Try the steps I listed on a new
repository. At the end, download the gist, and use "git apply
patchfile".
> If it's fairl
Faried -
I'm sure it mostly my new newness to Ruby; rake/make files are not my
strong area as well.
If it's fairly small changes, can you provide those changes?
Basically, why patch it - if I can just use a replacement file. But
since it's not provided yet, maybe you can demonstrate those tweaks
Link error without "http://":
twitter.com/oauth/access_token?
oauth_callback=oob&oauth_consumer_key=MY_CONSUMER_KEY&oauth_nonce=82034&oauth_signature_method=HMAC-
SHA1&oauth_timestamp=1273908737&oauth_token=MY_OAUTH_TOKEN&oauth_verifier=333&oauth_version=1.0&oauth_signature=MY_OAUTH_SIGNATURE
If I enter initially invalid input PIN code, then comes an error like
this:
Error #2032: Stream Error. URL:
http://twitter.com/oauth/access_token?oauth_callback=oob&oauth_consumer_key=MY_CONSUMER_KEY&oauth_nonce=82034&oauth_signature_method=HMAC-SHA1&oauth_timestamp=1273908737&oauth_token=MY_OAUTH
Hi,
My name is Tijs Verkoyen. I'm a webdeveloper at a Belgium company
Netlash (http://www.netlash.com).
In my spare time a run a company CR Solutions (http://
www.crsolutions.be).
Some of you may know me by the wrapper-class I created (http://
classes.verkoyen.eu/twitter).
I'm working with the Tw
26 matches
Mail list logo
