Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Why the Quick Bar (“dickbar”) is still so offensive

marco.org

Post reply on HN
Print view View original

11–20 of 106 posts

Re: Why the Quick Bar (“dickbar”) is still so offensive

#11

Post by defen »

forkandwait wrote: post #3

Is the sms -> internet/ server -> sms pathway tied up in business patents by Twitter? I am sure I am (sort of) underestimating, but Twitter seems like a weekend project for a couple of decent hackers; if they piss enough people off is there any reason to stick with them except for (VERY non-trivial) first past the post market share?

Instead of doing that, a team of one computer literate person could fork StatusNet, and you could spend the rest of the weekend trying to convince Ashton Kutcher and Charlie Sheen to join your service, and buying hardware to support them.

Re: Why the Quick Bar (“dickbar”) is still so offensive

#12

Post by pavel_lishin »

forkandwait wrote: post #10

Let me rephrase from earlier -- is Twitter technology patented?

Why?

To reiterate, yes you could build a clone, but the odds of duplicating Twitter's success is almost nil at this point.

Or are you asking if they're legally capable of forbidding people from creating other clients?

Re: Why the Quick Bar (“dickbar”) is still so offensive

#13

Post by djcapelis »

forkandwait wrote: post #9
forkandwait wrote: post #3

Is the sms -> internet/ server -> sms pathway tied up in business patents by Twitter? I am sure I am (sort of) underestimating, but Twitter seems like a weekend project for a couple of decent hackers; if they piss enough people off is there any reason to stick with them except for (VERY non-trivial) first past the post market share?

Rather than downvoting my rather heavily caveatted remarks, perhaps you could answer the question: Is there a patent encumbrance that makes this more than a technical problem? EDIT: moved "heavily qualified" to something more idiomatic.

Since it's sometimes considered nice to explain a downvote, I wanted to mention I downvoted you for spending time telling us how qualified you were instead of just restating your question in a simpler way.

I don't know why your other post was downvoted, but probably because people think it's not an interesting question, could be determined by actually going to Google yourself and doing your own homework/search and most people don't feel like patents, if they exist, are the problem with twitter's dominance.

Re: Why the Quick Bar (“dickbar”) is still so offensive

#15

Post by jonursenbach »

pavel_lishin wrote: post #5
forkandwait wrote: post #3

Is the sms -> internet/ server -> sms pathway tied up in business patents by Twitter? I am sure I am (sort of) underestimating, but Twitter seems like a weekend project for a couple of decent hackers; if they piss enough people off is there any reason to stick with them except for (VERY non-trivial) first past the post market share?

Ooh, another "it's just a weekend project!" comment. Next step: convince everyone to use your weekend project, instead of Twitter. Allowing people to import all of their tweets and friends would be helpful, so be sure to implement that. Next next step: Handle all of Twitter's traffic. Consistently, and you not only have to do it better than they did in the beginning, but better than they do it now .

Also create mobile clients for everybody to use. And don't forget about an API.

Re: Why the Quick Bar (“dickbar”) is still so offensive

#16

Post by DanI-S »

I'd be interested to hear what 'normal', non-power users of Twitter think. The 'mouth-breathing buffoons' that Jeff Rock so denigrates (and evidently make up most of Twitter's users) may actually like this UI feature.

Viewing the world through nerd-tinted spectacles makes many things seem horrible that are perfectly OK to a regular person.

Re: Why the Quick Bar (“dickbar”) is still so offensive

#17

Post by generalk »

forkandwait wrote: post #9
forkandwait wrote: post #3

Is the sms -> internet/ server -> sms pathway tied up in business patents by Twitter? I am sure I am (sort of) underestimating, but Twitter seems like a weekend project for a couple of decent hackers; if they piss enough people off is there any reason to stick with them except for (VERY non-trivial) first past the post market share?

Rather than downvoting my rather heavily caveatted remarks, perhaps you could answer the question: Is there a patent encumbrance that makes this more than a technical problem? EDIT: moved "heavily qualified" to something more idiomatic.

No, there's probably not a patent encumbrance. IANAL.

But there's so much more that makes it more than just a technical problem. Ask your random 40-year-old working in a non-tech industry if they've heard of Twitter. Now ask them if they've heard of StatusNet or identi.ca.

In a nutshell, that is what makes it more than just a technical problem.

Re: Why the Quick Bar (“dickbar”) is still so offensive

#19

Post by forkandwait »

djcapelis wrote: post #13
forkandwait wrote: post #9

Earlier quoted context omitted.

Rather than downvoting my rather heavily caveatted remarks, perhaps you could answer the question: Is there a patent encumbrance that makes this more than a technical problem? EDIT: moved "heavily qualified" to something more idiomatic.

Since it's sometimes considered nice to explain a downvote, I wanted to mention I downvoted you for spending time telling us how qualified you were instead of just restating your question in a simpler way. I don't know why your other post was downvoted, but probably because people think it's not an interesting question, could be determined by actually going to Google yourself and doing your own homework/search and mo…

Well, you don't seem to understand what "qualified" means in the context written -- when I said that my response was qualified it meant that I put caveats around it ("I qualified my response"). Sorry if I was unclear.

Re: Why the Quick Bar (“dickbar”) is still so offensive

#20

Post by robc »

ALXfoo wrote: post #4

Not just that, with the new update every time you launch the iPhone app it asks you "Twitter would like to use your current location, allow, don't allow" No means no

That's interesting. The alert should only be presented to you twice - if you respond No to both cases, it should simply disable location services for the app.

Mind you, I did that manually - at least once I discovered it leaves them enabled the whole time the app's running, which means a significant battery hit on the GPS.

Post reply on HN