Best description of Klout I've seen to date: "utter vainglorious masturbatory nonsense"
Twitter to Client Developers: Drop Dead
61–70 of 187 posts
Re: Twitter to Client Developers: Drop Dead
#62This doesn't surprise me at all. When you develop on someone else's platform, you have to walk a fine line between not being successful at all and being too successful such that the platform provider co-opts your business (maybe you get lucky and get bought out). This is nothing new. Such moves as this were (IMHO) inevitable. They'll slowly chip away at anything they see as taking revenue from them. The part I disagr…
Interesting point about being acquired. Do you think perhaps restricting 3rd party clients is a way to make them more appealing to a potential buyer like Apple?
If they're appealing to Apple, I'd say it's because they already have such a big partnership with Apple in iOS integration. For whatever reasons the partnership was appealing, an acquisition would likewise be appealing.
Re: Twitter to Client Developers: Drop Dead
#63I wonder how Twitter's developers are feeling about these changes... Devs tend to be pro-openess, I imagine this to have a bitter taste for most of them.
Re: Twitter to Client Developers: Drop Dead
#64From here, I think we should move to a distributed model, like email and xmpp. It needs to be Open Source so anyone can run it and everyone owns their data. It needs to be compatible with current Twitter apps so all it requires is setting the API root. It needs to be distributed so anyone can follow anyone anywhere. There is no owner or root, there is no place to shut down. Proof of concept: https://nstatus.herokuapp…
How do you control spam?
I don't, it's just a proof of concept.
In the distributed implementation I would have a chain of trust from the people you follow, where if you report someone as a spammer, the server that represents people who follow you could look at your list and filter spammers based off this. You could also set the depth to traverse. There is a lot you could do with this.
I'm not saying my implementation is right, but someone needs to do it. Tweeting is a type of communication and needs to be distributed.
Re: Twitter to Client Developers: Drop Dead
#65People keep talking about Facebook and Myspace, but they lack(ed) full-on third-party clients, so what I'm wondering about is the LiveJournal comparison.
LiveJournal too had and has third-party clients. And though hardly popular in the English-speaking world these days, it's still going. But I don't think it has similar guidelines. So what's the comparison?
Re: Twitter to Client Developers: Drop Dead
#66Earlier quoted context omitted.
Sure, that's a difference, but a rather incremental difference IMHO. Not nearly as big a difference as federation and open source, which is what we really need to break out of the walled gardens.
How many successful open-source platforms are there? I can't think of any. Unlike Free software, platforms have a maintenance cost (servers), and that cost cannot be paid by donated man-hours. The only thing close that I can think of is BitTorrent due to the distrubuted infrastructure, but that's quite impractical to duplicate in this context (how can browsing the content contribute back to hosting and storage automa…
There are many. Email is a particularly notable example. Luckily, the technology sector wasn't run by "entrepreneurs" back when email was invented, or we would have wound up with walled gardens there too (Hotmail users can only email other Hotmail users and contacts can't be exported, etc).
Re: Twitter to Client Developers: Drop Dead
#67Earlier quoted context omitted.
app.net looks more attractive, until the same shit starts happening there in 5 years. The problem is walled garden social networks. It's a fundamentally bad idea for everyone involved, except the people who own it and can turn a profit. StatusNet/Identica is a much better solution to this problem than yet another walled garden. Free, open source, and federated. How many times does the same shit need to happen before…
The whole point with app.net is that this doesn't happens. They don't mind that you use the data any way because you're paying for the platform, not the client.
That's not "the whole point". You're missing the part where it's yet another proprietary walled garden designed to maximize profits. That's not really a great model for end users.
Re: Twitter to Client Developers: Drop Dead
#68In the “good” quadrants are bullshit terms like “Social CRM”, “Social analytics”, and “Social influence ranking” Would he rather they put one-paragraph labels on each quadrant? Sometimes phrases that sound like MBA buzzwords (and might be MBA buzzwords) are actually useful too.
Ok, so what is "Social CRM"?
Re: Twitter to Client Developers: Drop Dead
#69This doesn't surprise me at all. When you develop on someone else's platform, you have to walk a fine line between not being successful at all and being too successful such that the platform provider co-opts your business (maybe you get lucky and get bought out). This is nothing new. Such moves as this were (IMHO) inevitable. They'll slowly chip away at anything they see as taking revenue from them. The part I disagr…
Everyone cites Myspace. Either Twitter or Facebook does something controversial and we hear everyone citing Myspace. Myspace didn't lose it's user base due to amazing UX for end-user. They lost their user base due to combination of bad UX and "mobile" user base. Majority of Myspace users were teenagers and by the time they went to college they had hot new social network in form of Facebook, which was exclusively for…
It's also a huge difference in scale. MySpace ultimately stumbled on a comparatively small stage. IIRC at it's height they had maybe 80-100 million legitimate accounts. A mass migration of say 20 million users in a short period of time is something totally different than say 100 million users. FaceBook also had about 50% as many users by the time MySpace hit their numerical peak. So to apply that to Twitter I think some new service would have to grow about 100 million users and then steal about 100 million from Twitter.
Re: Twitter to Client Developers: Drop Dead
#70From here, I think we should move to a distributed model, like email and xmpp. It needs to be Open Source so anyone can run it and everyone owns their data. It needs to be compatible with current Twitter apps so all it requires is setting the API root. It needs to be distributed so anyone can follow anyone anywhere. There is no owner or root, there is no place to shut down. Proof of concept: https://nstatus.herokuapp…
What would its advantages be over status.net/identi.ca?