As an ethical AI user, I begin each session by asking the chatbot to give a stolen data acknowledgement. It is an important first step toward justice.

As the current maintainer of Rebble's developer documentation at https://developer.rebble.io, I've got some thoughts on Eric's recent blogpost, specifically around accusation #3 in the "Their accusations" section. I'll break this section down from my perspective.

Nothing of the sort was agreed uponIt's unfortunate that this is how I find out that Eric's word doesn't actually mean much when it's given to me. Either that, or he's already forgotten about the conversation he and I had in July, where we agreed that we would merge our developer documentation efforts into the same site. As I reported to the Rebble team after that call: "docs site will end up in our fork ultimately, we're agreed that docs should not be split". I'm disappointed that Eric never communicated this change of heart to me directly, but, well, here we are now, I guess.See the full written agreement that Core Devices has with Rebble towards the bottom. Rebble agreed that Core would host the developer site.Verbatim, from the screenshot in your own post: "Core will host developer.rePebble.com that is built from an open source repo". I'd love to be pointed to the part of this sentence that says we wouldn't continue to operate our own developer documentation, because I'm certainly not seeing it. What I have seen, however, is a previous draft of the agreement that would have had us redirect developer.rebble.io to developer.repebble.com. Given the change, it seems fair to assume that condition was consciously removed. So, implicitly, by the version of the agreement you've posted, we can continue to maintain and own our own documentation - and I intend to keep doing so, thanks.I have been maintaining and updating the developer site personally - all open sourceSo have I. And so have other people from the community.Having two sources of truth would be confusing for the communityAnd here's the real kicker. Here's the line that left me seeing nothing but red.

Eric, you know full fucking well that this is the argument that I have been making this entire time. As soon as I saw the rePebble documentation pop up, I was worried that having two copies of the docs (and two different pebble-tools, but that ship has long since sailed) would fracture the developer ecosystem. The whole reason we got on that call was to try to align on this! I made it quite clear during that call that what I wanted to avoid was confusing new developers by having two sites with the mostly-same-but-slightly-different content. And now here you are, twisting my own fucking words against me in an attempt to act like the agreement that we came to together, never even happened in the first place. You'll have to forgive me for finding this behaviour nothing short of abhorrent, deceptive, and outright disrespectful to not only my work, but the work of everyone who's contributed to our copy of the documentation.

If it wasn't painfully clear at this point - yeah, I'm not happy. I'm pretty mad. I feel betrayed, played for a fool, strung along like an idiot. Maybe that's my fault for trusting Eric's word. In any case, I don't think I'll be making that mistake again anytime soon.

#pebble #rebble #coredevices

https://rebble.io/2025/11/17/core-devices-keeps-stealing-our-work.html Well this is the least pleasant thing I have ever clicked publish on. God I wish it didn't have to go this way.

I think my favorite use of emoji responses on Slack/Discord/etc is when someone just latches onto a particular word in a message and attaches its emoji, with no semantic content intended. E.g. someone'll say "Sorry, the bus is running late" and someone else will just slap a 🚌 on there to confirm that they did indeed notice and recognize the word "bus"

i would like the people who are like "who needs content warnings just opt out using filters" to know that i am now on my 7th spelling of "us politics" for my filters