[twitter-dev] Re: Questions about opening the firehose

[M. Edward (Ed) Borasky]

On Dec 18, 9:23 am, Raffi Krikorian  wrote:
> > Will the geo-hose streaming API return only those tweets which are geo-
> > tagged, or will it also return tweets for users whose location (in
> > profile) falls within the lat, lon specified
>
> the geo-hose will only return tweets that are geotagged.
>
> while the volume may be low (comparably) now, its definitely growing.

Given the realities of social networking, media, privacy, word-of-
mouth, attention spans, user laziness, etc., those people who want
users to geo-tag will need to offer those users incentive to do so,
for example, discounts on goods and services. Or you could do what
Facebook did - make geo-tagging the default and then send out a
complicated set of instructions on how to make your location private
again. ;-)
>
> --
> Raffi Krikorian
> Twitter Platform Teamhttp://twitter.com/raffi

[twitter-dev] When to Cache search api

[Jamie Dolan]

Hello;

Would it be best practice to create a local cache when accessing the
search api in a streaming fashion.

Using the site www.monitter.com as an example, the data is only
present for such a short amount of time, additional users are not very
likely to hit the cache.  I suspect it isn't even worth the overhead
to cache data in that situation.

Does a site that is pulling data the way monitter.com is have any
problems with access limits from the search api?

I am looking for search & read only access to data.  If I understand
correctly, at this point, that is best accomplished using just the
search api?

Thank You

-- 
Jamie Dolan
Neenah, WI 54956
http://jamiedolan.com
@akivathedog on twitter

Re: [twitter-dev] Re: The remote name could not be resolved: 'twitter.com' problem

[Mark McBride]

This looks like a networking issue more than a Twitter issue.  Can you
ping twitter.com from the machine that's trying to make this call?

   ---Mark

http://twitter.com/mccv



2009/12/20 Emre KIYAK :
> yes I try but couldn't solve this problem
>
> On 20 Aralık, 10:00, Ken Dobruskin  wrote:
>> You might want to try the Twitterizer API Google group 
>> here:http://groups.google.com/group/twitterizer
>>
>> hth,
>>
>> Ken
>>
>>
>>
>>
>>
>> > Date: Sat, 19 Dec 2009 17:53:05 -0800
>> > Subject: [twitter-dev] The remote name could not be resolved: 
>> > 'twitter.com'        problem
>> > From: mr.ki...@gmail.com
>> > To: twitter-development-talk@googlegroups.com
>>
>> > Hi there
>>
>> > I started to use twitterizer API for my blog. I post my tweet from my
>> > cms system. I get this error
>>
>> > The remote name could not be resolved: 'twitter.com'
>>
>> > In the .cs file my code goes here
>>
>> > Twitter t = new Twitter("emrekiyak", "*");
>> >             t.Status.Update(textbox1.Text);
>>
>> > and web.config configuration is that :
>>
>> > 
>>
>> > How can i solve this problem.
>>
>> > Thank you all
>>
>> _
>> Windows Live Hotmail: Your friends can get your Facebook updates, right from 
>> Hotmail®.http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-act...-
>>  Alıntıyı gizle -
>>
>> - Alıntıyı göster -
>

Re: [twitter-dev] Server blacklisted? Not sure how to explain this

[Christopher Becker]

We are back on, turns out we just needed to restart apache?  Have no idea how 
that fixed it but we're all good now.


On Dec 20, 2009, at 11:37 AM, Abraham Williams wrote:

> Do any of the other API calls work from your production server?
> 
> Such as http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-help%C2%A0test
> 
> On Sun, Dec 20, 2009 at 13:20, chrisLiveFyre  wrote:
> The twitter integration on our site stopped working a couple days ago,
> it was unclear what caused this.  Some investigation revealed that the
> getAccessToken() call was coming back with blank tokens.
> 
> 1. Tried on dev server (different IP) with the same twitter app
> credentials and confirmed broken
> 2. Tried on dev server with new twitter app credentials and it worked
> 3. Tried on live server with new twitter app credentials, still broken
> 
> Seems like the IP has been blocked somehow, no?  We're trying to get
> in touch with Twitter engineers right now to solve this but any help
> would be much appreciated.
> 
> 
> 
> -- 
> Abraham Williams | Awesome Lists | http://awesomeli.st
> Project | Intersect | http://intersect.labs.poseurtech.com
> Hacker | http://abrah.am | http://twitter.com/abraham
> This email is: [ ] shareable [x] ask first [ ] private.
> Sent from Bloomington, IN, United States

Re: [twitter-dev] 168.143.162.36... Connection timed out

[shiplu]

On Mon, Dec 21, 2009 at 2:52 AM, Andrew Badera  wrote:
> Probably better to email your IP address directly and not display it
> publicly ...

Dont worry. I dont own them.

I just check some of my peers of same ISP.
None of them is having the problem.
It seems somewhere something is broken.

-- 
Shiplu Mokaddim
My talks, http://talk.cmyweb.net
Follow me, http://twitter.com/shiplu
SUST Programmers, http://groups.google.com/group/p2psust
Innovation distinguishes bet ... ... (ask Steve Jobs the rest)

Re: [twitter-dev] Re: Tweet length plain text or urlencoded?

[Raffi Krikorian]

This is a known issue on the bug tracker, I believe, thatis assigned  
to me.  I'll try to get it taken care of soon.




On Dec 20, 2009, at 12:41 AM, mndasher  wrote:




On Dec 20, 12:22 am, Cameron Kaiser  wrote:

Tweets are limited to 140 characters. If I am sending the tweet from
an API which requires the characters to be urlencoded is there a  
limit

there? Or is it the un-encoded length that must be <= 140?


The un-encoded length must be <= 140. It is still not clear to me  
if this

is fixed for UTF-8 characters, though; Matt Sanford was going to post
something about that and I never heard anything about it later.

--
 personal:http:// 
www.cameronkaiser.com/--
  Cameron Kaiser * Floodgap Systems *www.floodgap.com*  
ckai...@floodgap.com
-- This message will self-destruct in five seconds. Good luck, Jim.  
-- M:I 


Ok - I need to sort this out.. it seems if a posting is >140 it just
doesn't get posted, and the API does not complain, i.e. no error
reported.  Using PHP and cURL for the API.

Re: [twitter-dev] 168.143.162.36... Connection timed out

[Christopher Becker]

I was confused, expecting an email from someone else and misread this.

But the IP address is umm...pretty public already wouldn't you say? just try:
ping livefyre.com 

On Dec 20, 2009, at 11:52 AM, Andrew Badera wrote:

> Probably better to email your IP address directly and not display it
> publicly ...
> 
> ∞ Andy Badera
> ∞ +1 518-641-1280 Google Voice
> ∞ This email is: [ ] bloggable [x] ask first [ ] private
> ∞ Google me: http://www.google.com/search?q=andrew%20badera
> 
> 
> 
> On Sun, Dec 20, 2009 at 2:51 PM, shiplu  wrote:
>> My external IP address is 202.56.7.116
>> Its dynamic. 202.56.7.* part is fixed.
>> 
>> --
>> Shiplu Mokaddim
>> My talks, http://talk.cmyweb.net
>> Follow me, http://twitter.com/shiplu
>> SUST Programmers, http://groups.google.com/group/p2psust
>> Innovation distinguishes bet ... ... (ask Steve Jobs the rest)
>> 

Re: [twitter-dev] 168.143.162.36... Connection timed out

[Christopher Becker]

We are @ 75.101.136.182

I just tried the help/test api call using curl and the result came back ok, so 
it now seems unlikely that its a blacklisted IP.

Thanks for your help,
Chris

On Dec 20, 2009, at 11:45 AM, John Adams wrote:

> On Dec 20, 2009, at 9:17 AM, shiplu wrote:
> 
>> Used all these ips.
>> 
>> 128.121.146.100
>> 128.121.146.228
>> 128.121.243.228
>> 168.143.161.20
>> 168.143.162.116
>> 168.143.162.36
>> 168.143.162.52
>> 168.143.162.68
>> 168.143.171.84
> 
> 
> It is possible your IP or network was blacklisted on our routers or firwealls.
> 
> Could you email me your source IP and I can check in our lists for you? 
> Thanks.
> 
> chrisLiveFyre, post your IP as well and we'll research.
> 
> -john
> Twitter Operations
> 

Re: [twitter-dev] 168.143.162.36... Connection timed out

[Andrew Badera]

Probably better to email your IP address directly and not display it
publicly ...

∞ Andy Badera
∞ +1 518-641-1280 Google Voice
∞ This email is: [ ] bloggable [x] ask first [ ] private
∞ Google me: http://www.google.com/search?q=andrew%20badera



On Sun, Dec 20, 2009 at 2:51 PM, shiplu  wrote:
> My external IP address is 202.56.7.116
> Its dynamic. 202.56.7.* part is fixed.
>
> --
> Shiplu Mokaddim
> My talks, http://talk.cmyweb.net
> Follow me, http://twitter.com/shiplu
> SUST Programmers, http://groups.google.com/group/p2psust
> Innovation distinguishes bet ... ... (ask Steve Jobs the rest)
>

Re: [twitter-dev] 168.143.162.36... Connection timed out

[shiplu]

My external IP address is 202.56.7.116
Its dynamic. 202.56.7.* part is fixed.

-- 
Shiplu Mokaddim
My talks, http://talk.cmyweb.net
Follow me, http://twitter.com/shiplu
SUST Programmers, http://groups.google.com/group/p2psust
Innovation distinguishes bet ... ... (ask Steve Jobs the rest)

Re: [twitter-dev] 168.143.162.36... Connection timed out

[John Adams]

On Dec 20, 2009, at 9:17 AM, shiplu wrote:


Used all these ips.

128.121.146.100
128.121.146.228
128.121.243.228
168.143.161.20
168.143.162.116
168.143.162.36
168.143.162.52
168.143.162.68
168.143.171.84



It is possible your IP or network was blacklisted on our routers or  
firwealls.


Could you email me your source IP and I can check in our lists for  
you? Thanks.


chrisLiveFyre, post your IP as well and we'll research.

-john
Twitter Operations

Re: [twitter-dev] Server blacklisted? Not sure how to explain this

[Abraham Williams]

Do any of the other API calls work from your production server?

Such as http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-help%C2%A0test

On Sun, Dec 20, 2009 at 13:20, chrisLiveFyre  wrote:

> The twitter integration on our site stopped working a couple days ago,
> it was unclear what caused this.  Some investigation revealed that the
> getAccessToken() call was coming back with blank tokens.
>
> 1. Tried on dev server (different IP) with the same twitter app
> credentials and confirmed broken
> 2. Tried on dev server with new twitter app credentials and it worked
> 3. Tried on live server with new twitter app credentials, still broken
>
> Seems like the IP has been blocked somehow, no?  We're trying to get
> in touch with Twitter engineers right now to solve this but any help
> would be much appreciated.
>



-- 
Abraham Williams | Awesome Lists | http://awesomeli.st
Project | Intersect | http://intersect.labs.poseurtech.com
Hacker | http://abrah.am | http://twitter.com/abraham
This email is: [ ] shareable [x] ask first [ ] private.
Sent from Bloomington, IN, United States

Re: [twitter-dev] Keyword Searching

[Scott Wilcox]

That's what I was thinking, thanks Cameron :)

On 20 Dec 2009, at 18:36, Cameron Kaiser wrote:

>> I'm interesting in collecting all tweets containing a selection of words.
>> Whats the best way of fetching all tweets that contain one of these words
> 
> Sounds like a job for the Streaming API.
> 
> -- 
>  personal: http://www.cameronkaiser.com/ 
> --
>  Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com
> -- Po-Ching Lives! 
> 



smime.p7s
Description: S/MIME cryptographic signature

[twitter-dev] Server blacklisted? Not sure how to explain this

[chrisLiveFyre]

The twitter integration on our site stopped working a couple days ago,
it was unclear what caused this.  Some investigation revealed that the
getAccessToken() call was coming back with blank tokens.

1. Tried on dev server (different IP) with the same twitter app
credentials and confirmed broken
2. Tried on dev server with new twitter app credentials and it worked
3. Tried on live server with new twitter app credentials, still broken

Seems like the IP has been blocked somehow, no?  We're trying to get
in touch with Twitter engineers right now to solve this but any help
would be much appreciated.

Re: [twitter-dev] Keyword Searching

[Cameron Kaiser]

> I'm interesting in collecting all tweets containing a selection of words.
> Whats the best way of fetching all tweets that contain one of these words

Sounds like a job for the Streaming API.

-- 
 personal: http://www.cameronkaiser.com/ --
  Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com
-- Po-Ching Lives! 

[twitter-dev] Keyword Searching

[Scott Wilcox]

Hi folks,

I'm interesting in collecting all tweets containing a selection of words. Whats 
the best way of fetching all tweets that contain one of these words or will I 
need to search via each one in turn? I'm going to be building a visualisation 
of certain terms, that's why I'm asking. Nothing spammy or related, purely 
visual to the end user.

Thanks for taking the time to read.

Scott.

smime.p7s
Description: S/MIME cryptographic signature

Re: [twitter-dev] 168.143.162.36... Connection timed out

[shiplu]

Used all these ips.

128.121.146.100
128.121.146.228
128.121.243.228
168.143.161.20
168.143.162.116
168.143.162.36
168.143.162.52
168.143.162.68
168.143.171.84

Result is same.


-- 
Shiplu Mokaddim
My talks, http://talk.cmyweb.net
Follow me, http://twitter.com/shiplu
SUST Programmers, http://groups.google.com/group/p2psust
Innovation distinguishes bet ... ... (ask Steve Jobs the rest)

[twitter-dev] Re: The remote name could not be resolved: 'twitter.com' problem

[Emre KIYAK]

yes I try but couldn't solve this problem

On 20 Aralık, 10:00, Ken Dobruskin  wrote:
> You might want to try the Twitterizer API Google group 
> here:http://groups.google.com/group/twitterizer
>
> hth,
>
> Ken
>
>
>
>
>
> > Date: Sat, 19 Dec 2009 17:53:05 -0800
> > Subject: [twitter-dev] The remote name could not be resolved: 'twitter.com' 
> >        problem
> > From: mr.ki...@gmail.com
> > To: twitter-development-talk@googlegroups.com
>
> > Hi there
>
> > I started to use twitterizer API for my blog. I post my tweet from my
> > cms system. I get this error
>
> > The remote name could not be resolved: 'twitter.com'
>
> > In the .cs file my code goes here
>
> > Twitter t = new Twitter("emrekiyak", "*");
> >             t.Status.Update(textbox1.Text);
>
> > and web.config configuration is that :
>
> > 
>
> > How can i solve this problem.
>
> > Thank you all
>
> _
> Windows Live Hotmail: Your friends can get your Facebook updates, right from 
> Hotmail®.http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-act...-
>  Alıntıyı gizle -
>
> - Alıntıyı göster -

[twitter-dev] Re: Undeletable list?

[shinichi]

Additional report:

At calling API to delete a undeletable list, it always returns
response as success, but still it remains.
And it seems that a undeletable list rejects any editting like adding
members, changes to list name and description.

Failure to delete a list with no error is very inconvenient. In my
situation, it causes to multiply extra lists named like "blahblah-3",
"blahblah-4", ... Because it intends to create a list as same name as
deleted list.



On Dec 18, 10:27 pm, shinichi  wrote:
> I have been getting same trouble, too.
> I made the list via API call. Then I found that I couldn't delete it
> via API. So I tried to delete it via web UI, but failed.
> I have two undeletable list, which 
> arehttp://twitter.com/hosokaws22/mixifriendsgenerated
> andhttp://twitter.com/hosokaws22/mixifriendsautogenerated.
>
> Shinichi
>
> On 12月16日, 午前8:15, "LeeS - @semel"  wrote:
>
> > I seem to have created an undeletablelistin one of my accounts (list
> > id 4667928)
>
> > I can'tdeleteit via the API, and deleting thelistvia twitter.com
> > also fails.
>
> > Lee

[twitter-dev] Re: Tweet length plain text or urlencoded?

[mndasher]

On Dec 20, 12:22 am, Cameron Kaiser  wrote:
> > Tweets are limited to 140 characters. If I am sending the tweet from
> > an API which requires the characters to be urlencoded is there a limit
> > there? Or is it the un-encoded length that must be <= 140?
>
> The un-encoded length must be <= 140. It is still not clear to me if this
> is fixed for UTF-8 characters, though; Matt Sanford was going to post
> something about that and I never heard anything about it later.
>
> --
>  personal:http://www.cameronkaiser.com/--
>   Cameron Kaiser * Floodgap Systems *www.floodgap.com* ckai...@floodgap.com
> -- This message will self-destruct in five seconds. Good luck, Jim. -- M:I 
> 

Ok - I need to sort this out.. it seems if a posting is >140 it just
doesn't get posted, and the API does not complain, i.e. no error
reported.  Using PHP and cURL for the API.

Re: [twitter-dev] 168.143.162.36... Connection timed out

[Raffi Krikorian]

do you have access to a different IP address you can test from?  i've just
tested from a variety of networks (including a cellular one), and i'm able
to connect.

you could also try a different IP addresses for twitter.com run

dig twitter.com +short

each time i run it, i get a different IP address for twitter.com -- you
could also see if the other addresses are having issues for you.

On Sun, Dec 20, 2009 at 6:49 AM, shiplu  wrote:

> Telnet
>
> $ telnet 168.143.162.36 80
> Trying 168.143.162.36...
> telnet: Unable to connect to remote host: Connection timed out
>
>
> And traceroute
>
> traceroute --max-hops=64 168.143.162.36
> traceroute to 168.143.162.36 (168.143.162.36), 64 hops max, 40 byte packets
>  1  10.163.145.33 (10.163.145.33)  586.913 ms  603.874 ms  682.882 ms
>  2  10.163.145.34 (10.163.145.34)  682.872 ms  742.845 ms  783.829 ms
>  3  192.168.226.81 (192.168.226.81)  802.824 ms  825.815 ms  1042.790 ms
>  4  192.168.250.10 (192.168.250.10)  1083.787 ms  1144.770 ms  1263.762 ms
>  5  10.10.205.14 (10.10.205.14)  1303.748 ms  1304.740 ms  1485.743 ms
>  6  202.56.4.2 (202.56.4.2)  1485.733 ms  866.271 ms  923.607 ms
>  7  202.56.5.25 (202.56.5.25)  942.598 ms  980.567 ms  1003.552 ms
>  8  * * *
>  9  * * *
> 10  * * *
> 11  * * *
> 12  * * *
> 13  * * *
> 14  * * *
> 15  * * *
> 16  * * *
> 17  * * *
> 18  * * *
> 19  * * *
> 20  * * *
> 21  * * *
> 22  * * *
> 23  * * *
> 24  * * *
> 25  * * *
> 26  * * *
> 27  * * *
> 28  * * *
> 29  * * *
> 30  * * *
> 31  * * *
> 32  * * *
> 33  * * *
> 34  * * *
> 35  * * *
> 36  * * *
> 37  * * *
> 38  * * *
> 39  * * *
> 40  * * *
> 41  * * *
> 42  * * *
> 43  * * *
> 44  * * *
> 45  * * *
> 46  * * *
> 47  * * *
> 48  * * *
> 49  * * *
> 50  * * *
> 51  * * *
> 52  * * *
> 53  * * *
> 54  * * *
> 55  * * *
> 56  * * *
> 57  * * *
> 58  * * *
> 59  * * *
> 60  * * *
> 61  * * *
> 62  * * *
> 63  * * *
> 64  * * *
>
>
> --
> Shiplu Mokaddim
> My talks, http://talk.cmyweb.net
> Follow me, http://twitter.com/shiplu
> SUST Programmers, http://groups.google.com/group/p2psust
> Innovation distinguishes bet ... ... (ask Steve Jobs the rest)
>



-- 
Raffi Krikorian
Twitter Platform Team
http://twitter.com/raffi

Re: [twitter-dev] 168.143.162.36... Connection timed out

[shiplu]

Telnet

$ telnet 168.143.162.36 80
Trying 168.143.162.36...
telnet: Unable to connect to remote host: Connection timed out


And traceroute

traceroute --max-hops=64 168.143.162.36
traceroute to 168.143.162.36 (168.143.162.36), 64 hops max, 40 byte packets
 1  10.163.145.33 (10.163.145.33)  586.913 ms  603.874 ms  682.882 ms
 2  10.163.145.34 (10.163.145.34)  682.872 ms  742.845 ms  783.829 ms
 3  192.168.226.81 (192.168.226.81)  802.824 ms  825.815 ms  1042.790 ms
 4  192.168.250.10 (192.168.250.10)  1083.787 ms  1144.770 ms  1263.762 ms
 5  10.10.205.14 (10.10.205.14)  1303.748 ms  1304.740 ms  1485.743 ms
 6  202.56.4.2 (202.56.4.2)  1485.733 ms  866.271 ms  923.607 ms
 7  202.56.5.25 (202.56.5.25)  942.598 ms  980.567 ms  1003.552 ms
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
31  * * *
32  * * *
33  * * *
34  * * *
35  * * *
36  * * *
37  * * *
38  * * *
39  * * *
40  * * *
41  * * *
42  * * *
43  * * *
44  * * *
45  * * *
46  * * *
47  * * *
48  * * *
49  * * *
50  * * *
51  * * *
52  * * *
53  * * *
54  * * *
55  * * *
56  * * *
57  * * *
58  * * *
59  * * *
60  * * *
61  * * *
62  * * *
63  * * *
64  * * *


-- 
Shiplu Mokaddim
My talks, http://talk.cmyweb.net
Follow me, http://twitter.com/shiplu
SUST Programmers, http://groups.google.com/group/p2psust
Innovation distinguishes bet ... ... (ask Steve Jobs the rest)

Re: [twitter-dev] 168.143.162.36... Connection timed out

[Raffi Krikorian]

yes - for example, on OS X, i would run

[ra...@tw-mbp13-raffi twitter (api_language_code)]$ *telnet 168.143.162.36
80*
Trying 168.143.162.36...
Connected to 168.143.162.36.
Escape character is '^]'.
^]
telnet> quit
Connection closed.

showing i can establish a connection. and then also

[ra...@tw-mbp13-raffi twitter (api_language_code)]$ *traceroute
168.143.162.36*
traceroute to 168.143.162.36 (168.143.162.36), 64 hops max, 40 byte packets

to show what route packets are taking.

On Sun, Dec 20, 2009 at 6:30 AM, Scott Haneda  wrote:

> On Dec 20, 2009, at 5:53 AM, shiplu  wrote:
>
> Why is this?
>
> $ curl -iv http://twitter.com/shiplu
> * About to connect() to twitter.com port 80 (#0)
> *   Trying 168.143.162.36... Connection timed out
> * couldn't connect to host
> * Closing connection #0
> curl: (7) couldn't connect to host
>
> I am facing this for almost 3-4 days.
>
>
> Telnet to the ip with correct port, run traceroute or mtr. Report your
> results back here.
> --
> Scott
> (Sent from a mobile device)
>



-- 
Raffi Krikorian
Twitter Platform Team
http://twitter.com/raffi

Re: [twitter-dev] 168.143.162.36... Connection timed out

[Scott Haneda]

On Dec 20, 2009, at 5:53 AM, shiplu  wrote:


Why is this?

$ curl -iv http://twitter.com/shiplu
* About to connect() to twitter.com port 80 (#0)
*   Trying 168.143.162.36... Connection timed out
* couldn't connect to host
* Closing connection #0
curl: (7) couldn't connect to host

I am facing this for almost 3-4 days.


Telnet to the ip with correct port, run traceroute or mtr. Report your  
results back here.
--  
Scott

(Sent from a mobile device)

[twitter-dev] 168.143.162.36... Connection timed out

[shiplu]

Why is this?

$ curl -iv http://twitter.com/shiplu
* About to connect() to twitter.com port 80 (#0)
*   Trying 168.143.162.36... Connection timed out
* couldn't connect to host
* Closing connection #0
curl: (7) couldn't connect to host

I am facing this for almost 3-4 days.

-- 
Shiplu Mokaddim
My talks, http://talk.cmyweb.net
Follow me, http://twitter.com/shiplu
SUST Programmers, http://groups.google.com/group/p2psust
Innovation distinguishes bet ... ... (ask Steve Jobs the rest)

RE: [twitter-dev] The remote name could not be resolved: 'twitter.com' problem

[Ken Dobruskin]

You might want to try the Twitterizer API Google group here: 
http://groups.google.com/group/twitterizer

hth,

Ken

> Date: Sat, 19 Dec 2009 17:53:05 -0800
> Subject: [twitter-dev] The remote name could not be resolved: 'twitter.com'   
> problem
> From: mr.ki...@gmail.com
> To: twitter-development-talk@googlegroups.com
> 
> Hi there
> 
> I started to use twitterizer API for my blog. I post my tweet from my
> cms system. I get this error
> 
> 
> The remote name could not be resolved: 'twitter.com'
> 
> 
> In the .cs file my code goes here
> 
> 
> Twitter t = new Twitter("emrekiyak", "*");
> t.Status.Update(textbox1.Text);
> 
> 
> and web.config configuration is that :
> 
> 
> 
> 
> 
> How can i solve this problem.
> 
> 
> Thank you all
> 
> 
  
_
Windows Live Hotmail: Your friends can get your Facebook updates, right from 
Hotmail®.
http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_4:092009