-
Website
http://www.scobleizer.com/ -
Original page
http://scobleizer.com/2009/01/01/twitter-warning-your-data-is-being-sold/ -
Subscribe
All Comments -
Community
-
Top Commenters
-
danja
44 comments · 4 points
-
polizeros
52 comments · 1 points
-
AndyBeard
69 comments · 4 points
-
Zachary Adam Cohen
35 comments · 8 points
-
dbarefoot
40 comments · 3 points
-
-
Popular Threads
-
The best and worst thing Twitter did in 2009: RT
17 hours ago · 20 comments
-
World-brand-building mistakes France’s entrepreneurs make
1 week ago · 181 comments
-
2010: the year SEO isn’t important anymore
6 days ago · 66 comments
-
iPhone developers abandoning app model for HTML5?
6 days ago · 51 comments
-
A 2010 real-time app development platform from Kynetx
14 hours ago · 2 comments
-
The best and worst thing Twitter did in 2009: RT
I have to say, the speed and trust that some people give to these twitter add ons for a little ease is scary. It's only a day old! Geeze...
It's just rabid idiots that run around with their head chopped off that are quick to assume the worst of any website. Get your head out of your ass.
It was a great idea that was flawed because it missed a few main components (eg: Privacy Policy, Terms of Service, etc.) It does NOT mean that the person who created it was a spammer.
The individual that created is a young, talented individual. He didn't have the financial means to continue to support Twply but thought his idea was worth something, and decided to sell it to someone that had the financial capabilities to keep it active.
Get off your goddamn high-horses.
Twitter severely needs to implement some form of authentication, preferably OAuth, since the foundation of twitter is third-party usage. Whether twitter opts to implement OAuth or something as simple as what FriendFeed has done with the "user key" is not as important as them finally implementing such measures.
Aren't you on a first name basis with everyone? Can't you just call your boy Ev and ask him if there are any plans for a third-party authentication scheme for twitter?
Exactly how has your service been able to clearly demonstrate that it can "hand (sic) the high load?" I find it hard to believe Twply has a really good understanding about what a true high load is. Such a claim seems purely suspect.
Everyone can say what they want.
Welcome to the blogosphere, where people can and will say what they want. If you are interested in turning the drama in to good will then you might consider answering some of the many lingering questions:
1. Why does Twply have no privacy policy posted?
2. Why does Twply have no terms of service posted?
3. Why does Twply require Twitter passwords when you can merely convert user RSS feeds and email those. Finding @replies is as easy as using the Twitter API, which does not require a users password for most functionality.
4. Does Twply store Twitter user passwords unencrypted, encrypted or hashed?
Until you start answering questions with honest answers, expect the ill-will to continue. My $0.02 anyhow. :-)
BUEK!
Hei, hei, hei from Budapest :)
No password required and absolutely no spamming!!
All your deets are belong to them.
It is not yet released, and I have no plans to sell it once it is, but hypothetically, were I to sell it someday, it would most definitely include users names/passwords because that is what the site DOES (lets you access Twitter in a different way.)
For those of us that make Twitter apps to utilize it plus combination with our own creativity, there is no other way (I don't think) to do some of these things without requiring the id/pw. Apps like @mrtweet are able to look at public info and use an algorithm to give neat results. But if you are using an alternate client, such as Tweetdeck, Twitterific or my soon-to-launch Twitterface, there's no other way at this time to do it.
Given that, rather than throw the baby out with the bathwater, I think people should follow app creators on Twitter, look up reviews, and do as much due diligence as needed to feel comfortable before giving out your Twitter account info. I was already planning on privacy policy, etc. but I think some additional things are in order as well, based on this feedback, and I am going to be thinking about everyone's concerns here a lot.
I do not know the Twply creators, but I do have a lot of experience working with startups, and the simple fact is, many cool things can be created by people who don't have all the information they need about launching a product. Therefore you might not see privacy policies, etc. It does not indicate bad intentions necessarily for these things to be missing - it may have been out of a lack of experience in doing something like this. Not sure.
I've started on a very hacky way to not steal a user's Twitter credentials when making API calls. I've plans for more elegance but as it stands it will Just Work.
Jordan.
www.theriverjordan.net
Applications would then have to use OAuth and a different API endpoint to access the twitter API, but the rest could stay the same.
they must be held accountable!