I'm looking to attach a SPOT Messenger to a weather balloon and track its
location throughout its flight.  SPOT sends its location to Fire Eagle.  I'm
wondering if anyone knows of an app that will continuously check Fire Eagle for
my SPOT's most recent coordinates and send a text every ten or twenty minutes to
my cell or email that includes the most recent, precise latitude/longitude
coordinates, rather than the generic location data displayed in the Fire Eagle
app.  I haven't been able to find this specific functionality in the Fire Eagle
application library.

Relax At Home ... And Get Paid For Your Opinion!

START EARNING TODAY!

$10 - $300 Per Online Survey

$50 - $300 Per Hour For Online Focus Groups

$4 - $25 Per Hour For Previewing Movie Trailers


Click here :
http://free-bizzz.com/index.php?option=com_content&view=article&id=48&Itemid=57

I created this cool friends network and added you to my friends network. Hit-up
now:
http://ladyless.zoomshare.com/files/girlfriend.htm

I have some code I wrote a while ago that runs every five minutes and querys for
the current FireEagle location.  Writen in C#, it uses the fireeaglenet
(http://code.google.com/p/fireeaglenet/) library.

Recently (within the past few months) it will occationaly throw a "Provided
nonce has been seen before" exception.  I just ignore and continue.  It seems to
work okay, but I would like to fix so that the exception is not thrown.  Is the
problem in the fireeaglenet library or my code?

I call the following once before the loop:

Token userToken = new Token(appSettings["fireeagle_usertoken"],
appSettings["fireeagle_usersecret"]);
FireEagle fireEagle = new FireEagle(appSettings["fireeagle_consumertoken"],
appSettings["fireeagle_consumersecret"], userToken);

then the following in the loop:

fireEagleUser = fireEagle.User();
bestLocation = fireEagleUser.LocationHierarchy.BestGuess;

The "fireEagle.User()" call triggers the exception.

Thanks for your help!

Started to get this recently when making initial request for request token. Not
happening on normal requests after that, which succeed as before.

Code has been working for well over 9 months, including after upgrade to 1.0a. 
Same OAuth code encoding/signature generation still works for Twitter and
Google.

We verified the error happens for both our "Snikkr v1" and "Snikkr v2" key sets.
The one we are using in production is "Snikkr v1".

As to when it started, unfortunately our error logs roll over every
three-to-four days at this point, and the operation (Get Request Token) is not
performed very often.  We have the first such error in our log is at 2010-01-02
19:21:42.010 (GMT).

Our oldest entry in our error log is 2010-01-01 07:55:57.580 (GMT).

We continue to investigate. Let us know if we can send you any param values,
etc.

Thanks!

--- In fireeagle@yahoogroups.com, Arnab Nandi <arnob.nandi@...> wrote:
>
> Since we have not made any changes during the year end moratorium, we need to
know how recent this issue is. Also, what is the concerned app that is having
the trouble getting the request token?
>
> Thx & Rgds
>
> --Arnab
>
>
>
>
> ________________________________
> From: morganbelford <morgan_public@...>
> To: fireeagle@yahoogroups.com
> Sent: Mon, 4 January, 2010 1:06:13 PM
> Subject: [fireeagle] "Invalid OAuth Signature" on Get Request Token requests.
>
>
> Started to get this recently when making initial request for request token.
Not happening on normal requests after that, which succeed as before.
>
> Code has been working for well over 9 months, including after upgrade to 1.0a.
Same OAuth code encoding/signature generation still works for Twitter and
Google.
>
>
>
>
>
>       The INTERNET now has a personality. YOURS! See your Yahoo! Homepage.
http://in.yahoo.com/
>

Looking at our oauth connections to FireEagle, it looks like the last successful
get request token would have been in October (2009-10-01 19:50:54.167).
Normally, we get a handful each month. So we might have been seeing this error,
unreported, since then.

--- In fireeagle@yahoogroups.com, Arnab Nandi <arnob.nandi@...> wrote:
>
> Since we have not made any changes during the year end moratorium, we need to
know how recent this issue is. Also, what is the concerned app that is having
the trouble getting the request token?
>
> Thx & Rgds
>
> --Arnab
>
>
>
>
> ________________________________
> From: morganbelford <morgan_public@...>
> To: fireeagle@yahoogroups.com
> Sent: Mon, 4 January, 2010 1:06:13 PM
> Subject: [fireeagle] "Invalid OAuth Signature" on Get Request Token requests.
>
>
> Started to get this recently when making initial request for request token.
Not happening on normal requests after that, which succeed as before.
>
> Code has been working for well over 9 months, including after upgrade to 1.0a.
Same OAuth code encoding/signature generation still works for Twitter and
Google.
>
>
>
>
>
>       The INTERNET now has a personality. YOURS! See your Yahoo! Homepage.
http://in.yahoo.com/
>

The problem seems to be having more than one query param in our oauth_callback:

What we use is:
http://someserver.com/AccountUI/OAuthAuthorized.aspx?uid=1&vers=1.0a&ct=1

If we only have a single param after the ? (e.g., uid=1 or ct=1), then we are
ok, but once we have more than one param in the callback, we get the
unauthorized error.

Here is an example url that we actually submit (callback server is different in
prod, consumer key changed):
https://fireeagle.yahooapis.com/oauth/request_token?oauth_callback=http%3A%2F%2F\
localhost%3A58444%2FAccountUI%2FOAuthAuthorized.aspx%3Fuid%3D1%26vers%3D1.0a%26c\
t%3D1&oauth_consumer_key=xxxyyyyzzz&oauth_nonce=545633&oauth_signature_method=HM\
AC-SHA1&oauth_timestamp=1262618030&oauth_version=1.0&oauth_signature=xG8%2BDu1LN\
LiJ0PHxGArDi1%2FwdEg%3D

Two callbacks that work:
http://someserver.com/AccountUI/OAuthAuthorized.aspx?uid=1
http://someserver.com/AccountUI/OAuthAuthorized.aspx?ct=1

--- In fireeagle@yahoogroups.com, Arnab Nandi <arnob.nandi@...> wrote:
>
> Hmmm... that may coincide with Fire Eagle cutting over to 1.0A release in
October (I need to double check the dates though, it may still be close). Can
you send a wire capture dump (or atleast a log of the POST/GET request) showing
the URL, the POST body [if any] and the HTTP headers [if you are using OAuth
through headers].
>
> If not, at least let us know if you have been using any standard Fire Eagle
library. Hint: Check if that lib has been upgraded since you deployed Snikkr v2.
Fire Eagle's Python lib had a problem I remember.
>
> Please make sure to 'xxxx' out the sensitive info like keys if you are sending
the dump.
>
> Thx & Rgds
>
> --Arnab
>
>
>
>
> ________________________________
> From: morganbelford <morgan_public@...>
> To: fireeagle@yahoogroups.com
> Sent: Mon, 4 January, 2010 8:24:07 PM
> Subject: [fireeagle] Re: "Invalid OAuth Signature" on Get Request Token
requests.
>
>
> We verified the error happens for both our "Snikkr v1" and "Snikkr v2" key
sets.  The one we are using in production is "Snikkr v1".
>
> As to when it started, unfortunately our error logs roll over every
three-to-four days at this point, and the operation (Get Request Token) is not
performed very often.  We have the first such error in our log is at 2010-01-02
19:21:42.010 (GMT).
>
> Our oldest entry in our error log is 2010-01-01 07:55:57.580 (GMT).
>
> We continue to investigate. Let us know if we can send you any param values,
etc.
>
> Thanks!
>
> --- In fireeagle@yahoogrou ps.com, Arnab Nandi <arnob.nandi@ ...> wrote:
> >
> > Since we have not made any changes during the year end moratorium, we need
to know how recent this issue is. Also, what is the concerned app that is having
the trouble getting the request token?
> >
> > Thx & Rgds
> >
> > --Arnab
> >
> >
> >
> >
> > ____________ _________ _________ __
> > From: morganbelford <morgan_public@ ...>
> > To: fireeagle@yahoogrou ps.com
> > Sent: Mon, 4 January, 2010 1:06:13 PM
> > Subject: [fireeagle] "Invalid OAuth Signature" on Get Request Token
requests.
> >
> >
> > Started to get this recently when making initial request for request token.
Not happening on normal requests after that, which succeed as before.
> >
> > Code has been working for well over 9 months, including after upgrade to
1.0a.  Same OAuth code encoding/signature generation still works for Twitter and
Google.
> >
> >
> >
> >
> >
> >       The INTERNET now has a personality. YOURS! See your Yahoo! Homepage.
http://in.yahoo. com/
> >
>
>
>
>
>
>       The INTERNET now has a personality. YOURS! See your Yahoo! Homepage.
http://in.yahoo.com/
>

Arnab,

Thanks for checking into this so quickly.

We will likely go ahead and encode our three params into one for now, per your
suggestion. Please keep us posted on any fix, though.

-Morgan

--- In fireeagle@yahoogroups.com, Arnab Nandi <arnob.nandi@...> wrote:
>
> Looks like some of the special characters are being maligned by the time they
reach the OAuth verification code. Have seen that before, but thought it was
fixed.
>
> Will take a bit of digging. In the meantime, consider the alternative of
base64 encoding the actual params for your callback to make a single param
perhaps? As per your reply, the single param seems to work.
>
> Thx & Rgds
>
> --Arnab
>
>
>
>
> ________________________________
> From: morganbelford <morgan_public@...>
> To: fireeagle@yahoogroups.com
> Sent: Mon, 4 January, 2010 10:57:57 PM
> Subject: [fireeagle] Re: "Invalid OAuth Signature" on Get Request Token
requests.
>
>
> The problem seems to be having more than one query param in our
oauth_callback:
>
> What we use is:
> http://someserver. com/AccountUI/ OAuthAuthorized. aspx?uid= 1&vers=1. 0a&ct=1
>
> If we only have a single param after the ? (e.g., uid=1 or ct=1), then we are
ok, but once we have more than one param in the callback, we get the
unauthorized error.
>
> Here is an example url that we actually submit (callback server is different
in prod, consumer key changed):
> https://fireeagle. yahooapis. com/oauth/ request_token? oauth_callback=
http%3A%2F% 2Flocalhost% 3A58444%2FAccoun tUI%2FOAuthAutho rized.aspx%
3Fuid%3D1% 26vers%3D1. 0a%26ct%3D1& oauth_consumer_ key=xxxyyyyzzz& oauth_nonce=
545633&oauth_ signature_ method=HMAC- SHA1&oauth_ timestamp= 1262618030&
oauth_version= 1.0&oauth_ signature= xG8%2BDu1LNLiJ0P HxGArDi1% 2FwdEg%3D
>
> Two callbacks that work:
> http://someserver. com/AccountUI/ OAuthAuthorized. aspx?uid= 1
> http://someserver. com/AccountUI/ OAuthAuthorized. aspx?ct=1
>
> --- In fireeagle@yahoogrou ps.com, Arnab Nandi <arnob.nandi@ ...> wrote:
> >
> > Hmmm... that may coincide with Fire Eagle cutting over to 1.0A release in
October (I need to double check the dates though, it may still be close). Can
you send a wire capture dump (or atleast a log of the POST/GET request) showing
the URL, the POST body [if any] and the HTTP headers [if you are using OAuth
through headers].
> >
> > If not, at least let us know if you have been using any standard Fire Eagle
library. Hint: Check if that lib has been upgraded since you deployed Snikkr v2.
Fire Eagle's Python lib had a problem I remember.
> >
> > Please make sure to 'xxxx' out the sensitive info like keys if you are
sending the dump.
> >
> > Thx & Rgds
> >
> > --Arnab
> >
> >
> >
> >
> > ____________ _________ _________ __
> > From: morganbelford <morgan_public@ ...>
> > To: fireeagle@yahoogrou ps.com
> > Sent: Mon, 4 January, 2010 8:24:07 PM
> > Subject: [fireeagle] Re: "Invalid OAuth Signature" on Get Request Token
requests.
> >
> >
> > We verified the error happens for both our "Snikkr v1" and "Snikkr v2" key
sets.  The one we are using in production is "Snikkr v1".
> >
> > As to when it started, unfortunately our error logs roll over every
three-to-four days at this point, and the operation (Get Request Token) is not
performed very often.  We have the first such error in our log is at 2010-01-02
19:21:42.010 (GMT).
> >
> > Our oldest entry in our error log is 2010-01-01 07:55:57.580 (GMT).
> >
> > We continue to investigate. Let us know if we can send you any param values,
etc.
> >
> > Thanks!
> >
> > --- In fireeagle@yahoogrou ps.com, Arnab Nandi <arnob.nandi@ ...> wrote:
> > >
> > > Since we have not made any changes during the year end moratorium, we need
to know how recent this issue is. Also, what is the concerned app that is having
the trouble getting the request token?
> > >
> > > Thx & Rgds
> > >
> > > --Arnab
> > >
> > >
> > >
> > >
> > > ____________ _________ _________ __
> > > From: morganbelford <morgan_public@ ...>
> > > To: fireeagle@yahoogrou ps.com
> > > Sent: Mon, 4 January, 2010 1:06:13 PM
> > > Subject: [fireeagle] "Invalid OAuth Signature" on Get Request Token
requests.
> > >
> > >
> > > Started to get this recently when making initial request for request
token. Not happening on normal requests after that, which succeed as before.
> > >
> > > Code has been working for well over 9 months, including after upgrade to
1.0a.  Same OAuth code encoding/signature generation still works for Twitter and
Google.
> > >
> > >
> > >
> > >
> > >
> > >       The INTERNET now has a personality. YOURS! See your Yahoo! Homepage.
http://in.yahoo. com/
> > >
> >
> >
> >
> >
> >
> >       The INTERNET now has a personality. YOURS! See your Yahoo! Homepage.
http://in.yahoo. com/
> >
>
>
>
>
>
>       The INTERNET now has a personality. YOURS! See your Yahoo! Homepage.
http://in.yahoo.com/
>

Send Faxes FREE

Start Faxing FREE in 2 Minutes
send faxes to 3500 cities , 46 countries and continents
Just call us at our Toll Free Number to start

Call Now : 877-375-3972

Enjoy

I continue to use Brightkite, in part because it's one of the few usable Android
updaters. But it seems that not many other folks do. Are any of the more recent
location based social networks talking to FE?

I cannot seem to find any python implementation that works with the current
FireEagle server.  Using the scripts on the FireEagle site they fail.  The ones
from mojodna fail with "Invalid OAuth signature".  It seems that the oauth
python implementation doesn't match the FE server.

Does anyone have a working script??

How to Convert Water to Gas

* Discover how to make hydrogen from water safely and inexpensively.
* Using our web-based selection guide, find professional products and
installers, from a variety of companies.
* Become a Member to help the planet and earn extra income!

  Click here : http://easylnk.com/?15440

Money making opportunity! 100% Scam-Free

I will personally give you instant unlimited access to my Video showing my
Formula of how I  earned over $14,800.00 within 14 days of starting & THE MONEY
NEVER QUITS!!

Click here : http://easylnk.com/?15439

I want to add you as a friend so you can see my profile with my pictures.Here is
the link:
http://www.ourlivespace.com/hotcoolguy/addme.htm

I do not want the entire group seeing these photos.Because some may recognize
me.
Here's the link:
http://www.ourlivespace.com/hotgirl/photos.htm

Enjoy babe :)

All,

     this issue is (hopefully) fixed in the maintenance release of 27th Jan.
Please let us know if this is still causing issues.

Thx & Rgds

--Arnab

--- In fireeagle@yahoogroups.com, "morganbelford" <morgan_public@...> wrote:
>
> Arnab,
>
> Thanks for checking into this so quickly.
>
> We will likely go ahead and encode our three params into one for now, per your
suggestion. Please keep us posted on any fix, though.
>
> -Morgan
>
> --- In fireeagle@yahoogroups.com, Arnab Nandi <arnob.nandi@> wrote:
> >
> > Looks like some of the special characters are being maligned by the time
they reach the OAuth verification code. Have seen that before, but thought it
was fixed.
> >
> > Will take a bit of digging. In the meantime, consider the alternative of
base64 encoding the actual params for your callback to make a single param
perhaps? As per your reply, the single param seems to work.
> >
> > Thx & Rgds
> >
> > --Arnab
> >
> >
> >
> >
> > ________________________________
> > From: morganbelford <morgan_public@>
> > To: fireeagle@yahoogroups.com
> > Sent: Mon, 4 January, 2010 10:57:57 PM
> > Subject: [fireeagle] Re: "Invalid OAuth Signature" on Get Request Token
requests.
> >
> >
> > The problem seems to be having more than one query param in our
oauth_callback:
> >
> > What we use is:
> > http://someserver. com/AccountUI/ OAuthAuthorized. aspx?uid= 1&vers=1.
0a&ct=1
> >
> > If we only have a single param after the ? (e.g., uid=1 or ct=1), then we
are ok, but once we have more than one param in the callback, we get the
unauthorized error.
> >
> > Here is an example url that we actually submit (callback server is different
in prod, consumer key changed):
> > https://fireeagle. yahooapis. com/oauth/ request_token? oauth_callback=
http%3A%2F% 2Flocalhost% 3A58444%2FAccoun tUI%2FOAuthAutho rized.aspx%
3Fuid%3D1% 26vers%3D1. 0a%26ct%3D1& oauth_consumer_ key=xxxyyyyzzz& oauth_nonce=
545633&oauth_ signature_ method=HMAC- SHA1&oauth_ timestamp= 1262618030&
oauth_version= 1.0&oauth_ signature= xG8%2BDu1LNLiJ0P HxGArDi1% 2FwdEg%3D
> >
> > Two callbacks that work:
> > http://someserver. com/AccountUI/ OAuthAuthorized. aspx?uid= 1
> > http://someserver. com/AccountUI/ OAuthAuthorized. aspx?ct=1
> >
> > --- In fireeagle@yahoogrou ps.com, Arnab Nandi <arnob.nandi@ ...> wrote:
> > >
> > > Hmmm... that may coincide with Fire Eagle cutting over to 1.0A release in
October (I need to double check the dates though, it may still be close). Can
you send a wire capture dump (or atleast a log of the POST/GET request) showing
the URL, the POST body [if any] and the HTTP headers [if you are using OAuth
through headers].
> > >
> > > If not, at least let us know if you have been using any standard Fire
Eagle library. Hint: Check if that lib has been upgraded since you deployed
Snikkr v2. Fire Eagle's Python lib had a problem I remember.
> > >
> > > Please make sure to 'xxxx' out the sensitive info like keys if you are
sending the dump.
> > >
> > > Thx & Rgds
> > >
> > > --Arnab
> > >
> > >
> > >
> > >
> > > ____________ _________ _________ __
> > > From: morganbelford <morgan_public@ ...>
> > > To: fireeagle@yahoogrou ps.com
> > > Sent: Mon, 4 January, 2010 8:24:07 PM
> > > Subject: [fireeagle] Re: "Invalid OAuth Signature" on Get Request Token
requests.
> > >
> > >
> > > We verified the error happens for both our "Snikkr v1" and "Snikkr v2" key
sets.  The one we are using in production is "Snikkr v1".
> > >
> > > As to when it started, unfortunately our error logs roll over every
three-to-four days at this point, and the operation (Get Request Token) is not
performed very often.  We have the first such error in our log is at 2010-01-02
19:21:42.010 (GMT).
> > >
> > > Our oldest entry in our error log is 2010-01-01 07:55:57.580 (GMT).
> > >
> > > We continue to investigate. Let us know if we can send you any param
values, etc.
> > >
> > > Thanks!
> > >
> > > --- In fireeagle@yahoogrou ps.com, Arnab Nandi <arnob.nandi@ ...> wrote:
> > > >
> > > > Since we have not made any changes during the year end moratorium, we
need to know how recent this issue is. Also, what is the concerned app that is
having the trouble getting the request token?
> > > >
> > > > Thx & Rgds
> > > >
> > > > --Arnab
> > > >
> > > >
> > > >
> > > >
> > > > ____________ _________ _________ __
> > > > From: morganbelford <morgan_public@ ...>
> > > > To: fireeagle@yahoogrou ps.com
> > > > Sent: Mon, 4 January, 2010 1:06:13 PM
> > > > Subject: [fireeagle] "Invalid OAuth Signature" on Get Request Token
requests.
> > > >
> > > >
> > > > Started to get this recently when making initial request for request
token. Not happening on normal requests after that, which succeed as before.
> > > >
> > > > Code has been working for well over 9 months, including after upgrade to
1.0a.  Same OAuth code encoding/signature generation still works for Twitter and
Google.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >       The INTERNET now has a personality. YOURS! See your Yahoo!
Homepage. http://in.yahoo. com/
> > > >
> > >
> > >
> > >
> > >
> > >
> > >       The INTERNET now has a personality. YOURS! See your Yahoo! Homepage.
http://in.yahoo. com/
> > >
> >
> >
> >
> >
> >
> >       The INTERNET now has a personality. YOURS! See your Yahoo! Homepage.
http://in.yahoo.com/
> >
>

10GB Web Hosting For FREE

10 GB Space | 300 GB Transfer
100 Email Accounts
10 MySQL Databases
support PHP and ASP
+ $130 of advertising credits on Google, Facebook and MySpace and more....


Click here : http://easylnk.com/?15457

Send Faxes For FREE

Start Faxing FREE in 2 minuties
Send faxes to 3500 cities and 46 countries.

Start Now : http://easylnk.com/?15468

Enjoy