Message from discussion
Introduce yourself!
X-BeenThere: twitter-development-talk@googlegroups.com
Received: by 10.213.50.10 with SMTP id x10ls1546550ebf.3.p; Sat, 20 Feb 2010
13:52:50 -0800 (PST)
Received: by 10.213.44.10 with SMTP id y10mr261017ebe.8.1266702769106;
Sat, 20 Feb 2010 13:52:49 -0800 (PST)
Received: by 10.213.44.10 with SMTP id y10mr261016ebe.8.1266702769028;
Sat, 20 Feb 2010 13:52:49 -0800 (PST)
Return-Path: <nrauhau...@gmail.com>
Received: from mail-ew0-f220.google.com (mail-ew0-f220.google.com [209.85.219.220])
by gmr-mx.google.com with ESMTP id 17si267041ewy.3.2010.02.20.13.52.47;
Sat, 20 Feb 2010 13:52:48 -0800 (PST)
Received-SPF: pass (google.com: domain of nrauhau...@gmail.com designates 209.85.219.220 as permitted sender) client-ip=209.85.219.220;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of nrauhau...@gmail.com designates 209.85.219.220 as permitted sender) smtp.mail=nrauhau...@gmail.com; dkim=pass (test mode) header...@gmail.com
Received: by ewy20 with SMTP id 20so435396ewy.0
for <twitter-development-talk@googlegroups.com>; Sat, 20 Feb 2010 13:52:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=gamma;
h=domainkey-signature:mime-version:received:in-reply-to:references
:date:message-id:subject:from:to:content-type;
bh=qDETOO2ixTt6ofebPotOx9Oaf+qivrPZqGDqEcla6vw=;
b=lymz/dqKegb//b8t3fErZNDqbeH8O5k5+MM/mRRG7NSRkeRccoJI48+aWuCw+lTW4T
ziK6VKKcKG64uvqChjFjNnXsV2PpvRX1dTkPUa9+HgMy+NIkPsoiu6WjzVYk7C69lx8Z
wh85uSh8QzliHqevvUPOnn5jEQ7/04WIiU4cs=
DomainKey-Signature: a=rsa-sha1; c=nofws;
d=gmail.com; s=gamma;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:content-type;
b=lx8SE3ua/d8iKgUR1rVq8+Kcb56a2eHP5YdKUAkw1h/vIbp+cCqtYup3D/a6a5ibDx
YnR98KCqfRH8bc2pmY+VLvSr9w+uPECifV59OJMzhyCDxngpNRgVtkCgPOmm/m7/U+64
jD+0tDHdID1OrRvYzNhDia7WRYA6R07/NIU6U=
MIME-Version: 1.0
Received: by 10.216.89.137 with SMTP id c9mr4287943wef.228.1266702767510; Sat,
20 Feb 2010 13:52:47 -0800 (PST)
In-Reply-To: <20100220204518.GB18...@questright.com>
References: <4337d5481002191220hcd82ad3ia540e8736e56f...@mail.gmail.com>
<20100220204518.GB18...@questright.com>
Date: Sat, 20 Feb 2010 15:52:47 -0600
Message-ID: <9515c62d1002201352l2b55a735u5c26ffba7585f...@mail.gmail.com>
Subject: Re: [twitter-dev] Introduce yourself!
From: neal rauhauser <nrauhau...@gmail.com>
To: twitter-development-talk@googlegroups.com
Content-Type: multipart/alternative; boundary=0016e6d9714f7e546204800f3875
--0016e6d9714f7e546204800f3875
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
I'm Neal Rauhauser, @StrandedWind. Iowa State software engineering back
when - dodged a punchcard programming class by one semester. Cisco Certifie=
d
Network & Design Professional for a decade, recently lapsed as the cert is
devalued at both resellers and in general due to their failure to protect
the brand. I pay the bills operating a rural triple play carrier.
I'm a founding member of the Blog Workers Industrial Union, which came
together at the end of Netroots Nation 2009. We've spawned Progressive PST,
a social media consulting operation for Progressive Democratic candidates &
causes. PeanutButterPAC is another offshoot that I'm only tangentially
involved with, and we're chipping away at a workflow management system that
is Twitter enabled.
We very purposefully don't have a web site for the tools we build. Some o=
f
the BWIU are quite activist and they draw attention to themselves - we don'=
t
want to bring that kind of heat down on our hosting. Any complex data is
prepared for the back end in Google Docs and access is triggered by command=
s
in direct messages to controlled Twitter accounts. The security model is
implemented using private lists. Results and logs return from the gmail
accounts associated with a particular set of Twitter IDs. Those operating
the systems have no idea where the backend servers are physically located.
Twitter tolerates us having two whitelisted IPs, only one of which is activ=
e
at any given moment. The systems are quite geographically diverse and we've
been doing a good bit of cross training.
We've got low frequency, high value automated message placement - think
public service announcements for political campaigns and such. There's a on=
e
to many direct message utility that permits the receivers to go
onduty/offduty with a single message, no matter how many tasks groups
they've joined. Applications accessible by API can be triggered remotely by
non-technical users and they receive reports via email. None of this stuff
is particularly complex - any elegant looking code we might have is due to
Net:Twitter and the help Marc Mims has provided.
I am the resident programmer but you wouldn't have to follow me very long
to learn that I'm wrestling with #Lyme. I'd really like to find some more
stuff like Marc's Net:Twtter module - things that are simple to use, things
based on perl, thing that behave if I want to put them in a chain of unix
tools running in the background.
Oh, and we've got a couple of million plus users organizations that would
like us to do certain things, and I could really use an Oauth app but
nothing off the shelf is going to fit my needs ...
On Sat, Feb 20, 2010 at 2:45 PM, Marc Mims <marc.m...@gmail.com> wrote:
> Marc Mims. @semifor. Author and maintainer of Net::Twitter [1], the Perl
> interface to the Twitter API. I'm a freelance software developer
> specializing in modern perl (Moose, Catalyst, DBIx::Class, and
> Net::Twitter, of course).
>
> I'm a Linux enthusiast and run Debian on my personal systems with
> xmonad, Vim, Firefox+Vimperator. =EE=80=80Give me text, and take the mous=
e with
> you. :)
>
> My first Twitter app was Twirc [2], a local IRC gateway for Twitter.
> It's the Twitter client I use.
>
> Chris Thompson wrote and maintained Net::Twitter through version 2.12. I
> wrote replacement, from scratch, and Chris handed off the project to me.
> So I authored Net::Twitter 3.0 and maintain it, currently.
>
> Net::Twitter and the community of users and applications they've built
> have been a joy to work with. I'm registered for Chirp and I'm doing a
> little fund raising from the Net::Twitter users to help cover the costs
> of attending [3].
>
> In my spare time, I'm working on packrati.us (@packratius) [4], a
> Twitter + Delicious mashup. It started as a simple learning project for
> OAuth and the Streaming API. I'm really pleased with the backend code,
> which is where most of the effort has gone. If I can shake loose some
> more time, I need to do plenty of front end work (a designer I am not)
> and add some features to make it useful to a wider audience.
>
> I'll 2nd @Abraham's feature request for a conversation method returning
> replies for a specified status. I'd also like to see some consistency
> in error handling. Getting "Not authorized" for user_timeline can mean
> (1) the account is protected and the authenticated user is not
> authorized, (2) the account is suspended, (3) the account has 0 tweets.
> Getting a 500 response with HTML content from the Search API is
> unhelpful; getting an error response in the requested format would be
> much saner. There are many other inconsistencies in error responses.
> Life would be easier if they were addressed.
>
> Looking forward to Chirp and meeting some other Twitter devs there.
>
> @semifor
>
> [1] http://search.cpan.org/dist/Net-Twitter
> [2] http://search.cpan.org/dist/POE-Component-Server-Twirc/
> [3]
> http://semifor.posterous.com/how-1000-became-0-and-how-it-can-be-fixed-fo=
r
> [4] http://packrati.us
>
--=20
mailto:N...@layer3arts.com //
GoogleTalk: nrauhau...@gmail.com
GV: 202-642-1717
--0016e6d9714f7e546204800f3875
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div>=C2=A0=C2=A0 =C2=A0I'm Neal Rauhauser, @StrandedWind. Iowa State s=
oftware engineering back when - dodged a punchcard programming class by one=
semester.=C2=A0Cisco Certified Network & Design Professional for a dec=
ade, recently lapsed as the cert is devalued at both resellers and in gener=
al due to their failure to protect the brand. I pay the bills operating a r=
ural triple play carrier.</div>
<div><div><br></div><div>=C2=A0=C2=A0 I'm a founding member of the Blog=
Workers Industrial Union, which came together at the end of Netroots Natio=
n 2009. We've spawned Progressive PST, a social media consulting operat=
ion for Progressive Democratic candidates & causes. PeanutButterPAC is =
another offshoot that I'm only tangentially involved with, and we'r=
e chipping away at a workflow management system that is Twitter enabled.</d=
iv>
<div><br></div><div>=C2=A0=C2=A0We very purposefully don't have a web s=
ite for the tools we build. Some of the BWIU are quite activist and they dr=
aw attention to themselves - we don't want to bring that kind of heat d=
own on our hosting. Any complex data is prepared for the back end in Google=
Docs and access is triggered by commands in direct messages to controlled =
Twitter accounts. The security model is implemented using private lists. Re=
sults and logs return from the gmail accounts associated with a particular =
set of Twitter IDs. Those operating the systems have no idea where the back=
end servers are physically located. Twitter tolerates us having two whiteli=
sted IPs, only one of which is active at any given moment. The systems are =
quite geographically diverse and we've been doing a good bit of cross t=
raining.</div>
<div><br></div><div>=C2=A0=C2=A0We've got low frequency, high value aut=
omated message placement - think public service announcements for political=
campaigns and such. There's a one to many direct message utility that =
permits the receivers to go onduty/offduty with a single message, no matter=
how many tasks groups they've joined. Applications accessible by API c=
an be triggered remotely by non-technical users and they receive reports vi=
a email. None of this stuff is particularly complex - any elegant looking c=
ode we might have is due to Net:Twitter and the help Marc Mims has provided=
.</div>
<div><br></div><div>=C2=A0=C2=A0=C2=A0</div><div>=C2=A0=C2=A0I am the resid=
ent programmer but you wouldn't have to follow me very long to learn th=
at I'm wrestling with #Lyme. I'd really like to find some more stuf=
f like Marc's Net:Twtter module - things that are simple to use, things=
based on perl, thing that behave if I want to put them in a chain of unix =
tools running in the background.</div>
<div><br></div><div>=C2=A0=C2=A0Oh, and we've got a couple of million p=
lus users organizations that would like us to do certain things, and I coul=
d really use an Oauth app but nothing off the shelf is going to fit my need=
s ...</div>
<div><br></div><div><br></div><div><br></div><div><br><br><div class=3D"gma=
il_quote">On Sat, Feb 20, 2010 at 2:45 PM, Marc Mims <span dir=3D"ltr"><=
<a href=3D"mailto:marc.m...@gmail.com">marc.m...@gmail.com</a>></span> w=
rote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">Marc Mims. @semifor. Author and maintainer =
of Net::Twitter [1], the Perl<br>
interface to the Twitter API. =C2=A0I'm a freelance software developer<=
br>
specializing in modern perl (Moose, Catalyst, DBIx::Class, and<br>
Net::Twitter, of course).<br>
<br>
I'm a Linux enthusiast and run Debian on my personal systems with<br>
xmonad, Vim, Firefox+Vimperator. =EE=80=80Give me text, and take the mouse =
with<br>
you. :)<br>
<br>
My first Twitter app was Twirc [2], a local IRC gateway for Twitter.<br>
It's the Twitter client I use.<br>
<br>
Chris Thompson wrote and maintained Net::Twitter through version 2.12. I<br=
>
wrote replacement, from scratch, and Chris handed off the project to me.<br=
>
So I authored Net::Twitter 3.0 and maintain it, currently.<br>
<br>
Net::Twitter and the community of users and applications they've built<=
br>
have been a joy to work with. =C2=A0I'm registered for Chirp and I'=
m doing a<br>
little fund raising from the Net::Twitter users to help cover the costs<br>
of attending [3].<br>
<br>
In my spare time, I'm working on <a href=3D"http://packrati.us" target=
=3D"_blank">packrati.us</a> (@packratius) [4], a<br>
Twitter + Delicious mashup. =C2=A0It started as a simple learning project f=
or<br>
OAuth and the Streaming API. =C2=A0I'm really pleased with the backend =
code,<br>
which is where most of the effort has gone. =C2=A0If I can shake loose some=
<br>
more time, I need to do plenty of front end work (a designer I am not)<br>
and add some features to make it useful to a wider audience.<br>
<br>
I'll 2nd @Abraham's feature request for a conversation method retur=
ning<br>
replies for a specified status. =C2=A0I'd also like to see some consist=
ency<br>
in error handling. Getting "Not authorized" for user_timeline can=
mean<br>
(1) the account is protected and the authenticated user is not<br>
authorized, (2) the account is suspended, (3) the account has 0 tweets.<br>
Getting a 500 response with HTML content from the Search API is<br>
unhelpful; getting an error response in the requested format would be<br>
much saner. =C2=A0There are many other inconsistencies in error responses.<=
br>
Life would be easier if they were addressed.<br>
<br>
Looking forward to Chirp and meeting some other Twitter devs there.<br>
<br>
@semifor<br>
<br>
[1] <a href=3D"http://search.cpan.org/dist/Net-Twitter" target=3D"_blank">h=
ttp://search.cpan.org/dist/Net-Twitter</a><br>
[2] <a href=3D"http://search.cpan.org/dist/POE-Component-Server-Twirc/" tar=
get=3D"_blank">http://search.cpan.org/dist/POE-Component-Server-Twirc/</a><=
br>
[3]<br>
<a href=3D"http://semifor.posterous.com/how-1000-became-0-and-how-it-can-be=
-fixed-for" target=3D"_blank">http://semifor.posterous.com/how-1000-became-=
0-and-how-it-can-be-fixed-for</a><br>
[4] <a href=3D"http://packrati.us" target=3D"_blank">http://packrati.us</a>=
<br>
</blockquote></div><br><br clear=3D"all"><br>-- <br>mailto:<a href=3D"mailt=
o:N...@layer3arts.com">N...@layer3arts.com</a> //<br>GoogleTalk: <a href=3D=
"mailto:nrauhau...@gmail.com">nrauhau...@gmail.com</a><br>GV: 202-642-1717<=
br>
</div></div>
--0016e6d9714f7e546204800f3875--