The conversation

Business & incomeExperience excerpt · English

Summarizing the dispute, for anyone interested: Rebble's "one red line" is "there has to be a …

Summarizing the dispute, for anyone interested: Rebble's "one red line" is "there has to be a future for Rebble in there." They fear being replaced/made irrelevant after Core builds their own infrastructure using Rebble's work. They want guarantees that if they give Core access to the app store data, Core won't build a proprietary/walled garden that cuts Rebble out. There's also emphasis on "our work," "we built this," "we spent hundreds of thousands of dollars." They feel Eric isn't acknowledging where his infrastructure came from. Core Devices' thing is explicitly stating concern about relying on a third party (Rebble) for "critical services" his customers depend on. If "Rebble leadership changes their mind," they can't guarantee customer experience. They wants the app store archive to be "freely available" and "not controlled by one organization." They don't want to need "permission from Rebble" before building features (like free weather, voice-to-text) that might compete with Rebble's paid services. …

Original discussionPebble, Rebble, and a path forward248 source comments · at import
4

Community replies 0

No community replies yet. Add your perspective.

Replies from the source 4

Direct replies available in this import. Original-language excerpts.

PO

They sent an email a few minutes after I posted, saying that their fulfillment centre dropped the ball and they're escalating internally. I guess complaining on HN worked. Hope they can figure out the dispute with Rebble. Maybe they end up hosting apps on a package manager and create some binding contract?

Full original
MA

> They fear being replaced/made irrelevant after Core builds their own infrastructure using Rebble's work. They want guarantees that if they give Core access to the app store data, Core won't build a proprietary/walled garden that cuts Rebble out. It's understandable that Rebble fears someone doing this, since this is what Rebble did. Rebble took the original open-source Pebble work of thousands of independent developers, scraped it off the original store, and is re-offering it within their own walled garden and calling it "theirs". It's great Rebble kept things alive but they seem to be fearing a second one of themselves. > being at the mercy of a nonprofit's decisions when his company has customers and obligations. Both Rebble and Core Devices are for-profit companies, neither is a non-profit, so I'm not actually sure which you're referring to here.

Full original
GO

Core went bankrupt once doing exactly what they want to do now. I think the concern users will be left holding the bag, again, is reasonable.

Full original
TR

It is the HashiCorp fiasco all over again. HashiCorp thinks third-party is profiting from Terraform, they relicense, Terraform gets forked into OpenTofu. Here, Rebble says Core is profiting from their work (hey, look at your licenses). It would be a direct violation of their ToS though, since there is this clause: > 4. Services Usage Limits > > You agree not to reproduce, duplicate, copy, sell, resell or exploit any portion of the Service, use of the Service, access to the Service, or Content accessed through use of the Service, without Rebble’s express written permission. So I don't know what to think honestly, I don't see any bad actors here...

Full original
Continue on Hacker News

Respect different perspectives. Share concrete experiences.

Sign in to post, reply, repost, and quote.