> The claim was that Rebble paid the developers of NimBLE, Codecoup, to assist with integration of NimBLE into RebbleOS
OK, that claim wasn't actually made in this post. I see in a blog post last month they say "We engaged the services of Codecoup – the maintainers of NimBLE – to help us find a handful of bugs in our implementation of Bluetooth on legacy watches". Core Devices isn't selling legacy watches though, and they've been working on Bluetooth since long before last month. So it's still not clear to me what Bluetooth work Rebble is claiming to have paid for that Core Devices is actually relying on.
Also, in that same post they say "we’ve made it work by agreeing that Core will pay us a reasonable amount to cover our costs and to support the maintenance of Rebble Web Services". So Core is actually supposed to be paying Rebble, they're not just using the store for free. No mention of that in this post...
OK, that claim wasn't actually made in this post. I see in a blog post last month they say "We engaged the services of Codecoup – the maintainers of NimBLE – to help us find a handful of bugs in our implementation of Bluetooth on legacy watches". Core Devices isn't selling legacy watches though, and they've been working on Bluetooth since long before last month. So it's still not clear to me what Bluetooth work Rebble is claiming to have paid for that Core Devices is actually relying on.
Also, in that same post they say "we’ve made it work by agreeing that Core will pay us a reasonable amount to cover our costs and to support the maintenance of Rebble Web Services". So Core is actually supposed to be paying Rebble, they're not just using the store for free. No mention of that in this post...