Reeder Calls Out MobileRSS For Design Theft, Community Backlash Begins

Re:Reeder Calls Out MobileRSS For Design Theft, Community Ba... by Pent on Wednesday December 22, 2010 @09:18PM (#2033303)

Why did ReadItLater feel that they needed to get their hands dirty and intervene? Now I have to use Instapaper.. sigh

[ Parent | on HN ]

Re:Reeder Calls Out MobileRSS For Design Theft, Community Ba... by Kylekramer on Wednesday December 22, 2010 @09:53PM (#2033349)

Bad news: http://twitter.com/marcoarment/status/17674488195850240

It is an interesting question. I mean, Reeder was clearly cloned pretty heavily, but kneecaping interoperability in retaliation seems like a dangerous road to head down.

[ Parent | on HN ]

Re:Reeder Calls Out MobileRSS For Design Theft, Community Ba... by hallmark on Sunday December 26, 2010 @04:42PM (#2041222)

When you are using the resources of an API, you are entering a community. And when you abuse another respected member of the community, it responds.

These bookmarking services weren't cutting off a developer client to protect themselves, which I consider more dangerous. They were throwing their weight behind Reeder.

Checks and balances.

[ Parent | on HN ]

Re:Reeder Calls Out MobileRSS For Design Theft, Community Ba... by macrael on Wednesday December 22, 2010 @11:08PM (#2033485)

He laid out his reasons pretty clearly in his post about it: http://readitlaterlist.com/blog/2010/12/a-quick-word-on-the-...

[ Parent | on HN ]

Re:Reeder Calls Out MobileRSS For Design Theft, Community Ba... by trotsky on Wednesday December 22, 2010 @11:23PM (#2033509)

Update: After speaking with a number of other developers, including Silvio from Reeder, I’ve decided that the best thing to do is re-enable MobileRSS’s API key.

[ Parent | on HN ]