We were tired of the noise on Twitter (noisy apps, lame content, erratic but otherwise valuable tweeters), so we decided to fix it. Proxlet is a Twitter API Proxy that runs scripts to modify the Twitter experience. Works with Twitter for iPhone, TweetDeck, and any other client that supports custom API URLs, including a 1-click install Chrome Extension for Twitter.com
What do you think? Right approach? (@aaronwhite & @ChrisRicca)
Nice job! A couple questions... Is there a way to manage mutes (so you can unmute something that's been muted forever, for example)? Also, if I do mutes, etc., on one computer's Proxlet will they also take effect on another computer I use the Proxlet extension on?
Proxlet manages all your settings at Proxlet.com, so if you use multiple Proxlet enabled clients, all your settings will be shared. In terms of unmuting, you can go to Proxlet.com and mute someone for "1 minute" and that will effectively un-mute them. We'll be adding a far more obvious method both on the website and in the extension soon.
I had this same frustration and same implementation idea -- proxy is awesome because any client can easily gain features by a checkbox pref "Use proxlet".
I never pursued it because I wasn't sure how I could sustain it -- I asked my heavy-twitter friends about it. They all agreed it sounded like a good idea, but none of them thought they'd be willing to pay for it.
Have you done any market research, or are you just doing it for fun for now?
Anyway, I'm happy to see it. Where's the paypal donate button?
We did it to scratch our own itch primarily. It also gave me an excuse to play w/ the Twitter API and lots of really interesting technology (full blog post on how Proxlet is architected soon). Not desperate to monetize it, it can handle many many thousands of users at a cost of $10/mo to us, but we do have some ideas.
Paypal donate?! Probably should add that for satisfied super-fans :)
Nice. The chrome extension is new? One of the things I wasn't crazy about before was having to configure my twitter clients to grab my feed via proxlet.
Yup, the Chrome Extension is new and what makes it exciting (again). The per-client install process was too difficult/error-prone, so when we saw we could "hook" Twitter.com, we jumped on it.
What do you think? Right approach? (@aaronwhite & @ChrisRicca)