[twitter-dev] logout page redirecting (http://api.twitter.com/logout) to other page
I making android twitter app. I want to add log-out funtion in my app, but oAuth has no log-out. So I open web-view with 'http://api.twitter.com/logout' for log-out, but twitter logout page redirecting automatically 'http:// mobile.twitter.com/', so i cant see logout page. Is this normal redireting? -- 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-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Re: Post from C#
Al, Be sure to get the 2.1 beta that was just recently posted. Andrew, I'm not sure what you mean saying that the .NET OAuth stuff is out of date/incomplete "on the Twitter side." On May 26, 3:15 pm, Andrew Badera wrote: > Cool. Just keep in mind a lot of the .NET OAuth stuff, especially on the > Twitter side, is somewhat out of date or incomplete. > > --ab > > > > On Wed, May 26, 2010 at 2:51 PM, Al wrote: > > Thanks for the link. > > I also found this page: http://apiwiki.twitter.com/OAuth-Examples > > AL. > > > On May 26, 9:29 am, Al wrote: > > > I am a new to programming, what I want to do is post a comment to my > > > twitter page > > > using C#. Something simple amd direct, I have started my C# app with > > > the > > > Twitterizer api. Is this api a good place to start? I just want to > > > contact my Twitter page and post a message. > > > > Thanks AL.
[twitter-dev] Re: Deleted status still in JSON, not in XML
Has anyone seen this behavior before? Is this a once in a lifetime
event? I (still) haven't found any mention of this anywhere.
Ricky
On Apr 20, 2:47 pm, Ricky wrote:
> I've had a bug submitted by a user of the Twitterizer .NET library,
> and it appears to be a possible bug with the Twitter API.
>
> After destroying a status, the /users/show/screen_name.json result
> still contained the destroyed status, while the /users/show/
> screen_name.xml results (correctly, I think) contains the previous
> status.
>
> Below is the example, both from the user "ronneylovely". The status
> "wow" has been deleted.
>
> Thanks in advance for any insight or attention you give,
> Ricky
>
> JSON (api.twitter.com/1/users/show/ronneylovely.json):
> {"favourites_count":1,"created_at":"Thu Apr 15 15:23:35 +
> 2010","profile_sidebar_fill_color":"e0ff92","description":null,"contributor
> s_enabled":false,"time_zone":null,"status":
> {"in_reply_to_status_id":null,"created_at":"Mon Apr 19 22:05:12 +
> 2010","in_reply_to_user_id":null,"truncated":false,"source":"web","favorite
> d":false,"id":
> 12478411850,"in_reply_to_screen_name":null,"text":"wow"},"following":false,
> "geo_enabled":false,"profile_sidebar_border_color":"87bc44","url":null,"ver
> ified":false,"profile_background_color":"9ae4e8","location":null,"profile_b
> ackground_image_url":"http://
> s.twimg.com/a/1271213136/images/themes/theme1/
> bg.png","profile_text_color":"00","followers_count":
> 0,"protected":false,"profile_image_url":"http://s.twimg.com/a/
> 1271213136/images/
> default_profile_3_normal.png","notifications":false,"profile_background_til
> e":false,"name":"ronneylovely","friends_count":
> 4,"profile_link_color":"ff","screen_name":"ronneylovely","id":
> 133348295,"lang":"en","statuses_count":2,"utc_offset":null}
>
> XML (api.twitter.com/1/users/show/ronneylovely.xml):
>
> 133348295
> ronneylovely
> ronneylovely
>
>
> http://s.twimg.com/a/1271725794/images/
> default_profile_3_normal.png
>
> false
> 0
> 9ae4e8
> 00
> ff
> e0ff92
> 87bc44
> 4
> Thu Apr 15 15:23:35 + 2010
> 1
>
>
> http://s.twimg.com/a/1271725794/images/
> themes/theme1/bg.png
> false
>
> false
> false
>
> 1
> en
> false
>
> Thu Apr 15 15:25:38 + 2010
> 12228846134
> testing this thing
> web
> false
>
>
> false
>
>
>
>
>
>
>
>
> --
> Subscription
> settings:http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Deleted status still in JSON, not in XML
I've had a bug submitted by a user of the Twitterizer .NET library,
and it appears to be a possible bug with the Twitter API.
After destroying a status, the /users/show/screen_name.json result
still contained the destroyed status, while the /users/show/
screen_name.xml results (correctly, I think) contains the previous
status.
Below is the example, both from the user "ronneylovely". The status
"wow" has been deleted.
Thanks in advance for any insight or attention you give,
Ricky
JSON (api.twitter.com/1/users/show/ronneylovely.json):
{"favourites_count":1,"created_at":"Thu Apr 15 15:23:35 +
2010","profile_sidebar_fill_color":"e0ff92","description":null,"contributors_enabled":false,"time_zone":null,"status":
{"in_reply_to_status_id":null,"created_at":"Mon Apr 19 22:05:12 +
2010","in_reply_to_user_id":null,"truncated":false,"source":"web","favorited":false,"id":
12478411850,"in_reply_to_screen_name":null,"text":"wow"},"following":false,"geo_enabled":false,"profile_sidebar_border_color":"87bc44","url":null,"verified":false,"profile_background_color":"9ae4e8","location":null,"profile_background_image_url":"http://
s.twimg.com/a/1271213136/images/themes/theme1/
bg.png","profile_text_color":"00","followers_count":
0,"protected":false,"profile_image_url":"http://s.twimg.com/a/
1271213136/images/
default_profile_3_normal.png","notifications":false,"profile_background_tile":false,"name":"ronneylovely","friends_count":
4,"profile_link_color":"ff","screen_name":"ronneylovely","id":
133348295,"lang":"en","statuses_count":2,"utc_offset":null}
XML (api.twitter.com/1/users/show/ronneylovely.xml):
133348295
ronneylovely
ronneylovely
http://s.twimg.com/a/1271725794/images/
default_profile_3_normal.png
false
0
9ae4e8
00
ff
e0ff92
87bc44
4
Thu Apr 15 15:23:35 + 2010
1
http://s.twimg.com/a/1271725794/images/
themes/theme1/bg.png
false
false
false
1
en
false
Thu Apr 15 15:25:38 + 2010
12228846134
testing this thing
web
false
false
--
Subscription settings:
http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Re: Open Source Project website
@Mark: Sorry to bother you a second time, but you missed the link on the open source page. http://apiwiki.twitter.com/Open+source#NET Thanks again, Ricky On Mar 22, 1:15 pm, Mark McBride wrote: > Done > ---Mark > > http://twitter.com/mccv > > > > On Mon, Mar 22, 2010 at 9:38 AM, IanQuigley wrote: > > Are you sure they check this forum for update requests? You might want > > to email them directly. I did. > > > Ian > > > To unsubscribe from this group, send email to twitter-development-talk+ > > unsubscribegooglegroups.com or reply to this email with the words "REMOVE > > ME" as the subject. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
[twitter-dev] Re: Open Source Project website
@Ian: I think we have our answer. @Mark: Thanks! Ricky On Mar 22, 1:15 pm, Mark McBride wrote: > Done > ---Mark > > http://twitter.com/mccv > > > > On Mon, Mar 22, 2010 at 9:38 AM, IanQuigley wrote: > > Are you sure they check this forum for update requests? You might want > > to email them directly. I did. > > > Ian > > > To unsubscribe from this group, send email to twitter-development-talk+ > > unsubscribegooglegroups.com or reply to this email with the words "REMOVE > > ME" as the subject. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
[twitter-dev] Open Source Project website
Can some one at Twitter please update the address of the Twitterizer open source project on the libraries and open source pages under C#/.NET and .NET, respectively. Also, it is now written for .NET 3.5. The new web address is: www.twitterizer.net. Thanks, Ricky To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
[twitter-dev] Re: Pin-based authorization via .NET
TwitterVB is actually a port of version 1 of Twitterizer. (I'm named in the source :D) Ricky On Mar 7, 6:34 pm, John Meyer wrote: > Take a look athttp://twittervb.codeplex.com/for some examples. > > John Meyer > Freelance Consultanthttp://www.pueblonative.com/blog > > If something goes wrong at the plant, blame the guy who can t speak > English. > */Homer Simpson/* > > --- @ WiseStamp Signature > <http://my.wisestamp.com/link?u=42bgx5rfnpr43zfj&site=www.wisestamp.co...>. > Get it now > <http://my.wisestamp.com/link?u=42bgx5rfnpr43zfj&site=www.wisestamp.co...> > On 3/7/2010 4:19 PM, Ricky wrote: > > > > > I'm developing a library that can be used with either web or desktop. > > Since I had code already going in a web application, I use it to do my > > initial development. > > > Ricky > > > On Mar 7, 5:03 pm, Ryan Alford wrote: > >> Why are you using PIN based authorization for web applications? Web > >> applications don't use PINs. > > >> Ryan > > >> Sent from my DROID > > >> On Mar 7, 2010 4:59 PM, "Ricky" wrote: > > >> I'm working on version 2 of Twitterizer, a .NET library for using the > >> Twitter API, but I've run into a weird issue with pin-based OAuth. I > >> have a sample web application and a sample desktop application. From > >> the web application I am able to perform pin-based authentication > >> without any issues, but through the desktop application every call for > >> access tokens are refused with "Invalid oauth_verifier parameter." > >> I've stepped through the code (non-stop for an hour) and I'm sure that > >> the exact code is executing for each call. I've tried changing the > >> calls to GET, instead of POST, and the results are the same. From the > >> web app it works great, from the desktop app, not so much. > > >> Using fiddler, I've captured the HTTP request/response from each, and > >> they look exactly the same (to me). > > >> Here is the call from the web application (works): > >> POSThttp://twitter.com/oauth/access_token?oauth_verifier=2068385HTTP/ > >> 1.1 > >> Content-Type: application/x-www-form-urlencoded > >> Authorization: OAuth realm="Twitter > >> API",oauth_consumer_key="Ds8w95QVNTITV16pqMwtHA",oauth_nonce="6E723378",oau > >> th_signature_method="HMAC- > >> SHA1",oauth_timestamp="1267995036",oauth_token="Vy5cCHkomrAKocY9c8J18hAEf1P > >> J2ONwBtQxmdGGaI",oauth_version="1.0",oauth_signature="OU3Qfi2tq > >> %2Fwyaij0NezCARqLVCA%3D" > >> User-Agent: Twitterizer/2.0.0.0 > >> Host: twitter.com > > >> And here is the call from the desktop application (does not work): > >> POSThttp://twitter.com/oauth/access_token?oauth_verifier=541907HTTP/ > >> 1.1 > >> Content-Type: application/x-www-form-urlencoded > >> Authorization: OAuth realm="Twitter > >> API",oauth_consumer_key="Ds8w95QVNTITV16pqMwtHA",oauth_nonce="7F8D82E3",oau > >> th_signature_method="HMAC- > >> SHA1",oauth_timestamp="1267995086",oauth_token="uTcERUybyJF0WKi77w5dPCTZbwO > >> 7DZJX1hQuJK0fg",oauth_version="1.0",oauth_signature="iUUcdVtM > >> %2B4nxfDKrqPqElE9IPgY%3D" > >> User-Agent: Twitterizer/2.0.0.0 > >> Host: twitter.com > > >> The response body is: > >> > >> > >> /oauth/access_token?oauth_verifier=541907 > >> Invalid oauth_verifier parameter > >> > > >> This may be more of a .NET question, as there may be some kind of > >> nuance when making requests through a windows application, but I > >> thought it might be worth my time to ask everyone, in case I'm doing > >> something dumb (it happens). > > >> Thanks for your time, > >> Rickywww.twitterizer.net
[twitter-dev] Re: Pin-based authorization via .NET
Actually, ignore me. You were totally right. I accidentally limited the text box in the desktop app to 6 chars, so it was truncating them. I need a nap. Thanks, Ricky On Mar 7, 5:07 pm, Abraham Williams <4bra...@gmail.com> wrote: > You are missing a digit from the desktop PIN. It should always be 7 digits. > > Abraham > > > > > > On Sun, Mar 7, 2010 at 12:57, Ricky wrote: > > I'm working on version 2 of Twitterizer, a .NET library for using the > > Twitter API, but I've run into a weird issue with pin-based OAuth. I > > have a sample web application and a sample desktop application. From > > the web application I am able to perform pin-based authentication > > without any issues, but through the desktop application every call for > > access tokens are refused with "Invalid oauth_verifier parameter." > > I've stepped through the code (non-stop for an hour) and I'm sure that > > the exact code is executing for each call. I've tried changing the > > calls to GET, instead of POST, and the results are the same. From the > > web app it works great, from the desktop app, not so much. > > > Using fiddler, I've captured the HTTP request/response from each, and > > they look exactly the same (to me). > > > Here is the call from the web application (works): > > POSThttp://twitter.com/oauth/access_token?oauth_verifier=2068385HTTP/ > > 1.1 > > Content-Type: application/x-www-form-urlencoded > > Authorization: OAuth realm="Twitter > > > API",oauth_consumer_key="Ds8w95QVNTITV16pqMwtHA",oauth_nonce="6E723378",oau > > th_signature_method="HMAC- > > > SHA1",oauth_timestamp="1267995036",oauth_token="Vy5cCHkomrAKocY9c8J18hAEf1P > > J2ONwBtQxmdGGaI",oauth_version="1.0",oauth_signature="OU3Qfi2tq > > %2Fwyaij0NezCARqLVCA%3D" > > User-Agent: Twitterizer/2.0.0.0 > > Host: twitter.com > > > And here is the call from the desktop application (does not work): > > POSThttp://twitter.com/oauth/access_token?oauth_verifier=541907HTTP/ > > 1.1 > > Content-Type: application/x-www-form-urlencoded > > Authorization: OAuth realm="Twitter > > > API",oauth_consumer_key="Ds8w95QVNTITV16pqMwtHA",oauth_nonce="7F8D82E3",oau > > th_signature_method="HMAC- > > > SHA1",oauth_timestamp="1267995086",oauth_token="uTcERUybyJF0WKi77w5dPCTZbwO > > 7DZJX1hQuJK0fg",oauth_version="1.0",oauth_signature="iUUcdVtM > > %2B4nxfDKrqPqElE9IPgY%3D" > > User-Agent: Twitterizer/2.0.0.0 > > Host: twitter.com > > > The response body is: > > > > > > /oauth/access_token?oauth_verifier=541907 > > Invalid oauth_verifier parameter > > > > > This may be more of a .NET question, as there may be some kind of > > nuance when making requests through a windows application, but I > > thought it might be worth my time to ask everyone, in case I'm doing > > something dumb (it happens). > > > Thanks for your time, > > Ricky > >www.twitterizer.net > > -- > Abraham Williams | Community Advocate |http://abrah.am > TwitterOAuth |http://github.com/abraham/twitteroauth > This email is: [ ] shareable [x] ask first [ ] private.
[twitter-dev] Re: Pin-based authorization via .NET
I thought the same thing, but Twitter has absolutely given me 6 digit pins. Ricky On Mar 7, 5:07 pm, Abraham Williams <4bra...@gmail.com> wrote: > You are missing a digit from the desktop PIN. It should always be 7 digits. > > Abraham > > > > > > On Sun, Mar 7, 2010 at 12:57, Ricky wrote: > > I'm working on version 2 of Twitterizer, a .NET library for using the > > Twitter API, but I've run into a weird issue with pin-based OAuth. I > > have a sample web application and a sample desktop application. From > > the web application I am able to perform pin-based authentication > > without any issues, but through the desktop application every call for > > access tokens are refused with "Invalid oauth_verifier parameter." > > I've stepped through the code (non-stop for an hour) and I'm sure that > > the exact code is executing for each call. I've tried changing the > > calls to GET, instead of POST, and the results are the same. From the > > web app it works great, from the desktop app, not so much. > > > Using fiddler, I've captured the HTTP request/response from each, and > > they look exactly the same (to me). > > > Here is the call from the web application (works): > > POSThttp://twitter.com/oauth/access_token?oauth_verifier=2068385HTTP/ > > 1.1 > > Content-Type: application/x-www-form-urlencoded > > Authorization: OAuth realm="Twitter > > > API",oauth_consumer_key="Ds8w95QVNTITV16pqMwtHA",oauth_nonce="6E723378",oau > > th_signature_method="HMAC- > > > SHA1",oauth_timestamp="1267995036",oauth_token="Vy5cCHkomrAKocY9c8J18hAEf1P > > J2ONwBtQxmdGGaI",oauth_version="1.0",oauth_signature="OU3Qfi2tq > > %2Fwyaij0NezCARqLVCA%3D" > > User-Agent: Twitterizer/2.0.0.0 > > Host: twitter.com > > > And here is the call from the desktop application (does not work): > > POSThttp://twitter.com/oauth/access_token?oauth_verifier=541907HTTP/ > > 1.1 > > Content-Type: application/x-www-form-urlencoded > > Authorization: OAuth realm="Twitter > > > API",oauth_consumer_key="Ds8w95QVNTITV16pqMwtHA",oauth_nonce="7F8D82E3",oau > > th_signature_method="HMAC- > > > SHA1",oauth_timestamp="1267995086",oauth_token="uTcERUybyJF0WKi77w5dPCTZbwO > > 7DZJX1hQuJK0fg",oauth_version="1.0",oauth_signature="iUUcdVtM > > %2B4nxfDKrqPqElE9IPgY%3D" > > User-Agent: Twitterizer/2.0.0.0 > > Host: twitter.com > > > The response body is: > > > > > > /oauth/access_token?oauth_verifier=541907 > > Invalid oauth_verifier parameter > > > > > This may be more of a .NET question, as there may be some kind of > > nuance when making requests through a windows application, but I > > thought it might be worth my time to ask everyone, in case I'm doing > > something dumb (it happens). > > > Thanks for your time, > > Ricky > >www.twitterizer.net > > -- > Abraham Williams | Community Advocate |http://abrah.am > TwitterOAuth |http://github.com/abraham/twitteroauth > This email is: [ ] shareable [x] ask first [ ] private.
[twitter-dev] Re: Pin-based authorization via .NET
I'm developing a library that can be used with either web or desktop. Since I had code already going in a web application, I use it to do my initial development. Ricky On Mar 7, 5:03 pm, Ryan Alford wrote: > Why are you using PIN based authorization for web applications? Web > applications don't use PINs. > > Ryan > > Sent from my DROID > > On Mar 7, 2010 4:59 PM, "Ricky" wrote: > > I'm working on version 2 of Twitterizer, a .NET library for using the > Twitter API, but I've run into a weird issue with pin-based OAuth. I > have a sample web application and a sample desktop application. From > the web application I am able to perform pin-based authentication > without any issues, but through the desktop application every call for > access tokens are refused with "Invalid oauth_verifier parameter." > I've stepped through the code (non-stop for an hour) and I'm sure that > the exact code is executing for each call. I've tried changing the > calls to GET, instead of POST, and the results are the same. From the > web app it works great, from the desktop app, not so much. > > Using fiddler, I've captured the HTTP request/response from each, and > they look exactly the same (to me). > > Here is the call from the web application (works): > POSThttp://twitter.com/oauth/access_token?oauth_verifier=2068385HTTP/ > 1.1 > Content-Type: application/x-www-form-urlencoded > Authorization: OAuth realm="Twitter > API",oauth_consumer_key="Ds8w95QVNTITV16pqMwtHA",oauth_nonce="6E723378",oau > th_signature_method="HMAC- > SHA1",oauth_timestamp="1267995036",oauth_token="Vy5cCHkomrAKocY9c8J18hAEf1P > J2ONwBtQxmdGGaI",oauth_version="1.0",oauth_signature="OU3Qfi2tq > %2Fwyaij0NezCARqLVCA%3D" > User-Agent: Twitterizer/2.0.0.0 > Host: twitter.com > > And here is the call from the desktop application (does not work): > POSThttp://twitter.com/oauth/access_token?oauth_verifier=541907HTTP/ > 1.1 > Content-Type: application/x-www-form-urlencoded > Authorization: OAuth realm="Twitter > API",oauth_consumer_key="Ds8w95QVNTITV16pqMwtHA",oauth_nonce="7F8D82E3",oau > th_signature_method="HMAC- > SHA1",oauth_timestamp="1267995086",oauth_token="uTcERUybyJF0WKi77w5dPCTZbwO > 7DZJX1hQuJK0fg",oauth_version="1.0",oauth_signature="iUUcdVtM > %2B4nxfDKrqPqElE9IPgY%3D" > User-Agent: Twitterizer/2.0.0.0 > Host: twitter.com > > The response body is: > > > /oauth/access_token?oauth_verifier=541907 > Invalid oauth_verifier parameter > > > This may be more of a .NET question, as there may be some kind of > nuance when making requests through a windows application, but I > thought it might be worth my time to ask everyone, in case I'm doing > something dumb (it happens). > > Thanks for your time, > Rickywww.twitterizer.net
[twitter-dev] Pin-based authorization via .NET
I'm working on version 2 of Twitterizer, a .NET library for using the Twitter API, but I've run into a weird issue with pin-based OAuth. I have a sample web application and a sample desktop application. From the web application I am able to perform pin-based authentication without any issues, but through the desktop application every call for access tokens are refused with "Invalid oauth_verifier parameter." I've stepped through the code (non-stop for an hour) and I'm sure that the exact code is executing for each call. I've tried changing the calls to GET, instead of POST, and the results are the same. From the web app it works great, from the desktop app, not so much. Using fiddler, I've captured the HTTP request/response from each, and they look exactly the same (to me). Here is the call from the web application (works): POST http://twitter.com/oauth/access_token?oauth_verifier=2068385 HTTP/ 1.1 Content-Type: application/x-www-form-urlencoded Authorization: OAuth realm="Twitter API",oauth_consumer_key="Ds8w95QVNTITV16pqMwtHA",oauth_nonce="6E723378",oauth_signature_method="HMAC- SHA1",oauth_timestamp="1267995036",oauth_token="Vy5cCHkomrAKocY9c8J18hAEf1PJ2ONwBtQxmdGGaI",oauth_version="1.0",oauth_signature="OU3Qfi2tq %2Fwyaij0NezCARqLVCA%3D" User-Agent: Twitterizer/2.0.0.0 Host: twitter.com And here is the call from the desktop application (does not work): POST http://twitter.com/oauth/access_token?oauth_verifier=541907 HTTP/ 1.1 Content-Type: application/x-www-form-urlencoded Authorization: OAuth realm="Twitter API",oauth_consumer_key="Ds8w95QVNTITV16pqMwtHA",oauth_nonce="7F8D82E3",oauth_signature_method="HMAC- SHA1",oauth_timestamp="1267995086",oauth_token="uTcERUybyJF0WKi77w5dPCTZbwO7DZJX1hQuJK0fg",oauth_version="1.0",oauth_signature="iUUcdVtM %2B4nxfDKrqPqElE9IPgY%3D" User-Agent: Twitterizer/2.0.0.0 Host: twitter.com The response body is: /oauth/access_token?oauth_verifier=541907 Invalid oauth_verifier parameter This may be more of a .NET question, as there may be some kind of nuance when making requests through a windows application, but I thought it might be worth my time to ask everyone, in case I'm doing something dumb (it happens). Thanks for your time, Ricky www.twitterizer.net
[twitter-dev] Re: How to change Source name to Client tool Source?
After it has been approved, do we need to add source parameter to all twitter status updates? Or does twitter do it automatically? On Mar 12, 1:45 am, Cameron Kaiser wrote: > > You probably missed it the same way i missed it. The term Twitter uses > > is not what my mind assumed it would be. > > > I googled "Custom Twitter Client Name" and "Change Twitter Client > > Name" and "Twitter Client Name" and nothing came up... I forget what > > finally brought me to this page. And the part in the Twitter docs is > > "How do I get _from [MyApp]_ which is like documentation but not human > > friendly :) > > Oh, I don't know, "just fill out this handy form[1]" seems pretty > straightforward to me. :-P > > [1]http://twitter.com/help/request_source > > -- > personal:http://www.cameronkaiser.com/-- > Cameron Kaiser * Floodgap Systems *www.floodgap.com* ckai...@floodgap.com > -- FOOLS! I WILL DESTROY YOU ALL! ASK ME HOW! -- "Girl Genius" 8/29/07 >
