Twitter Tweets about Proxy as of February 24, 2009
michiganmoves: Anyone else having proxy errors on AR?
amfjb: new proxy code 60.22.156.41 port = 808
PaulFranz: @ianmayman Only problem I see is that it won't work with a web proxy.
JasonBarile: @A_Robson Just saw your tweet about TFS source control and WCF proxy generation. Anything I can help with?
NicoleKramer: Has anyone else noticed that you could really RT anything @kevinokeefe sends and appear smart and informed by proxy?
ArgosBikeTech: Pues no pude publicar con el viejo método de PoderPDA, tendre que usar flickr. (malditos sean los de sistemas y su proxy. Si, lo recordé).
extraspecial: does anyone recommend any Windows Twitter clients that don't use Adobe Air (doesn't play nice w/our authenticating proxy)?
danatnr: Safari is hanging a little on links. Proxy handling could be a little flaky.
tmgadops: 2009-02-24 18:05:02 - Proxy List - Could Not Open XML File 0.000s.
regimus_prime: @melloniel & @zandroid - it seems to have picked up a little now, but for a while there it was like it was running through a dial-up proxy.
VespaRos: go through a proxy service like daveproxy.co.uk then direct it to spotify.com and create an account
jherskowitz: @matsm Yeah, for Spotify: 1) get an invite, 2) register while in (or proxy) the UK , 3) have a valid zip code, 4) set client proxy.