Rebble: Core Devices Stealing Our Work
- This post from the Rebble team outlines a critical juncture for the Pebble/Core watch community and asks for community input on how to proceed.They are facing a request...
- * Eric's Request: Core Devices wants full access to Rebble's data (apps, contributions, etc.).
- * Data Preservation: Rebble stepped up to preserve the Pebble ecosystem's data after Pebble went under, something Eric didn't do at the time.
Summary of the Rebble Post: A Fight for the Future of Pebble/Core Watch Development
This post from the Rebble team outlines a critical juncture for the Pebble/Core watch community and asks for community input on how to proceed.They are facing a request from Eric (of Core Devices) for an unrestricted license to their data – data that Rebble has painstakingly collected and maintained. here’s a breakdown of the key points:
The Core Issue: Data Control & Future of the Ecosystem
* Eric’s Request: Core Devices wants full access to Rebble’s data (apps, contributions, etc.).
* Rebble’s Concern: Granting this access woudl allow Eric to perhaps build a competing app store, effectively taking control of the community’s work and potentially leading to its demise.They fear a repeat of the Pebble shutdown scenario.
* Ancient Context: The post draws parallels to the fate of Pebble, North (smart glasses), and other companies where beloved products were acquired and then discontinued (“closed-source enshittification”).
* Long-Term Uncertainty: even if Core is stable now, they could be acquired by a larger company (like OpenAI) who might not prioritize the community or the long-term health of the ecosystem.
Why Rebble Feels Responsible
* Data Preservation: Rebble stepped up to preserve the Pebble ecosystem’s data after Pebble went under, something Eric didn’t do at the time.
* Community Ownership: They emphasize that Rebble and its data belong to the community – the developers and users who have contributed over the past decade.
* Unauthorized Use: They explicitly stated to Eric that scraping their data for commercial purposes was not allowed.
Two Proposed Paths Forward (and a request for community input):
- Aggressive Protection: Fight for control of the data and protect the community’s work through legal means. They have resources to do so, but prefer to focus on development.This will be a difficult and potentially costly path.
- Let Eric Proceed: Allow Eric to use the data as he sees fit. The post implies this would be a relinquishing of control and a risk to the community’s future.
Overall Tone: The post is urgent, protective, and deeply concerned about the future of the Pebble/Core watch ecosystem. They are clearly passionate about the community and want to ensure its longevity. They are framing this as a crucial decision that requires collective input.
In essence, Rebble is asking the community: Do we fight to maintain control of our collective work, or do we risk losing it to a potentially profit-driven entity?