6 ms·

So not 100% open source. Thanks for the info

by paxcoder 10mo ago

ddlsmurf 10mo ago
Well the Pebble specific parts are. This is an unfortunate state of affairs from hardware manufacturers, they are very late to the open source game, if at all.
- paxcoder 10mo ago
  From the article: >Another important note - some binary blobs and other non-free software components are used today in PebbleOS and the Pebble mobile app (ex: the heart rate sensor on PT2 , Memfault library, and others). Optional non-free web services, like Wispr-flow API speech recognizer, are also used. These non-free software components are not required - you can compile and run Pebble watch software without them. This will always be the case. More non-free software components may appear in our software in the future. The core Pebble watch software stack (everything you need to use your Pebble watch) will always be open source. 100% should mean 100%
  - darkwater 10mo ago
    If they are not mandatory it's 100%. Otherwise according to your standard, Debian is not 100% free software either.
    - bayindirh 10mo ago
      Debian doesn't advertise itself as 100% open source, either. Main and Contrib has to obey DFSG guidelines, and there's an optional non-free repository which you can enable if you prefer. Firmware is a gnarly can of worms though, and while I prefer 100% free firmware myself, companies are not brave enough to open that part of their ecosystem, yet, if ever.
      - aallaall 10mo ago
        Companies typically move more and more functionality to closed firmware, so they can ”open source” a thin wrapper, like a driver, that is often completely useless, and often encumbered with cryptography restrictions, strict trademarks and software patents anyway.
        bayindirh 10mo ago
        This is not always true. NVIDIA does exactly what you said. Move everything to firmware and closed GL libraries, and open source a kernel module to facilitate communication. They even created different firmware versions to prevent open source drivers to use the whole card. AMD did the inverse: They re-implemented a fully open driver from scratch, opened up the specs, made every part which they can make (legally) accessible, accessible, open sourced ROCm and send in packages to major distributions' (main / open source) repositories. Their firmware is closed source, but it's obtainable and doesn't require signatures to enable the card. They even clashed with HDMI forums to make a libre implementation of v2.1, but the forum basically threatened them. Intel's graphics drivers are basically the same with AMD. Broadcom / Intel / Realtek NICs work without their respective firmware blobs, yet their offloading capabilities are disabled. Either way, the drivers are completely open source and in the kernel mainline. Same for most sound cards sans Creative Labs. I want to hit them with a foam cluebat so bad. Logitech's all stuff works with open drivers. They are the primary contributor to V4L standard, standardize their webcam interfaces and provide drivers or help. Do you have any examples in mind?
    - paxcoder 10mo ago
      [dead]
  - rnewme 10mo ago
    100% of their own software.
    - paxcoder 10mo ago
      [dead]
  - wafflemaker 10mo ago
    IMHO, it's much closer to 100% than an iWatch or a Garmin.
    - aallaall 10mo ago
      1% is closer to 100%, than 0% is, yes.
  - RobotToaster 10mo ago
    > More non-free software components may appear in our software in the future. That sounds ominous. I can understand not being able to remove non-free dependencies that were used previously, but that sounds like they intend to create new non-free components.
- bloppe 10mo ago
  Surprising because you'd think the hardware itself would be their primary moat.
  - ddlsmurf 10mo ago
    Hardware isn't that hard to copy paste really, to make it hard you need to use really expensive processes (extreme uv etc), but otherwise, mostly you can pretty much take a picture. (very grossly speaking here, but just saying, the software is definitely a critical part)
- bayindirh 10mo ago
  Between the cross-licensing of hardware IP blocks and 3rd party software which never sees the light of the day, hardware manufacturers work like a secretive three letter agency to be able to control every part of their ecosystem. I tend to understand where this comes from. It's part business, part continuation of old customs and the way they did it and being able to control obsolescence to be able push new things to the market. However, if the periphery of the software you put out is closed source, even though this periphery is optional, it's not fair or ethical to say it's 100% open source. From my perspective, it can be said it's open core, and it's pretty fair, and acceptable in my case, but writing 100% Open Source* (*: 100% of the open part of the software stack, exceptions apply) is not fair game. It's misleading.
  - ddlsmurf 10mo ago
    Seems a bunch are angry about this, honestly, 100% of what they made/control is open source was a good enough bar for me. Specially if all closed components are optional. I value the flexibility of being able to use or not even closed stuff. It's unclear to me what the issue is, false advertisement ? This is as good as it gets for things like this, maybe the "100%" was indelicate, but I wouldn't go so far as misleading. I can also understand the hardware companies, history has shown that the vast majority of industry actors have a purely parasitical relation to open source, and have no qualms copying/stealing IP.
    - bayindirh 10mo ago
      Personally, I'm not angry. On the contrary, I'm pretty neutral about closed-source, optional add-ons. I started playing/working with computers pretty early, and the current state is an utopia when compared to olden times in terms of Free and Open Source software (OTOH, both Free Software and Open Source is under heavy attack because of many reasons I won't enter here). What bothers me is "100%" part of the open source claim. I personally like the Debian model a lot. It's DFSG compliant by default, and if non-free software is needed, it's attainable. Debian is "as Free as you want, as closed as you need". I see, new Pebble follows the same model, and it's perfectly fine, but branding it as 100% Open Source is not. I'll not discuss hardware companies. It's a can of worms that doesn't belong to that reply. Let's say while I understand some of their reservations, these reservation doesn't change that they're greedy and selfish (beyond acceptable limits).
gf000 10mo ago
Above a certain complexity, there is basically no 100% open-source hardware out there. Like none of the Pinephone, Librem, Framework laptops are "open-source" to the bone.
- squarefoot 10mo ago
  Given how easy is to put and keep hidden malware into devices, governments should demand openness in that field as well. By "putting malware" I don't mean script kiddies in their moms basement but malware/spyware planted by design, which is extremely easy to do if you're the manufacturer, extremely easy to demand/force if you're the government above that manufacturer, and extremely hard to detect if you're a different user in a different country under a government that didn't demand full openness. I know it's impossible as business rules go, but ideally it shouldn't be.
  - RobotToaster 10mo ago
    Every intel processor has a closed source IME, which is probably a NSA backdoor.
    - aallaall 10mo ago
      Isn’t minix open source?
      - RobotToaster 10mo ago
        Yes, the original is, but it's under a permissive license so Intel don't have to release the modified source code of their version.
  - graemep 10mo ago
    The thing is governments are the people doing it, and most governments want to be able to put backdoors in more badly than they want other governments to not put backdoors in.
- cncjchsue7 10mo ago
pjc50 10mo ago
Incidentally, this is one reason why there's not so much open source hardware out there: people get pedantic about it and apply gradually more unreasonable levels of requirement, rather than accepting partially or substantially open source solutions.
- 123pie123 10mo ago
  The reason why people get "pedantic" about this stuff, is due the ability in the future to get screwed over when the priority blob owner start to charge money or other pull other license crap
  - aallaall 10mo ago
    Enshittification. Open source is a valuable guarantee against that.
- user3939382 10mo ago
  Read Reflections on Trusting Trust to understand why having little bits of binary blobs sprinkled all over your compute arch is actually a major problem. Just because it’s a hard problem doesn’t mean we’re gonna pretend it’s fine.
  - 0xEF 10mo ago
    PDF link for those that are curious: https://www.cs.cmu.edu/~rdriley/487/papers/Thompson_1984_ReflectionsonTrustingTrust.pdf https://www.cs.cmu.edu/~rdriley/487/papers/Thompson_1984_Ref... The general sentiment is that you cannot trust code you did not write yourself and that we need to be able to trust the person who did, but you can form your own conclusions about how that fits into the modern tech landscape.
    - kchr 10mo ago
      One of the points made in that paper is that you can't even trust the compiler, even if you write the code yourself. I think this is one of the stronger points as it shows you it is unfeasible to require everybody to audit all source code before running it. Be pragmatic, know your threat model, decide who you trust and move on with more important things in your life. Full disclosure: am free software advocate.
Wowfunhappy 10mo ago
They said 100% of Pebble Watch software. The binary blobs are other people's software.
- aallaall 10mo ago
  Closed verilog I can accept. But in general firmware is also software, for example it has become quite popular in the recent years to execute firmware on an embedded riscv cpu. And move more and more functionality to that kind of firmware.

So not 100% open source. Thanks for the info

Well the Pebble specific parts are. This is an unfortunate state of affairs from hardware manufacturers, they are very late to the open source game, if at all.

paxcoder 10mo ago
From the article: >Another important note - some binary blobs and other non-free software components are used today in PebbleOS and the Pebble mobile app (ex: the heart rate sensor on PT2 , Memfault library, and others). Optional non-free web services, like Wispr-flow API speech recognizer, are also used. These non-free software components are not required - you can compile and run Pebble watch software without them. This will always be the case. More non-free software components may appear in our software in the future. The core Pebble watch software stack (everything you need to use your Pebble watch) will always be open source. 100% should mean 100%
- darkwater 10mo ago
  If they are not mandatory it's 100%. Otherwise according to your standard, Debian is not 100% free software either.
  - bayindirh 10mo ago
    Debian doesn't advertise itself as 100% open source, either. Main and Contrib has to obey DFSG guidelines, and there's an optional non-free repository which you can enable if you prefer. Firmware is a gnarly can of worms though, and while I prefer 100% free firmware myself, companies are not brave enough to open that part of their ecosystem, yet, if ever.
    - aallaall 10mo ago
      Companies typically move more and more functionality to closed firmware, so they can ”open source” a thin wrapper, like a driver, that is often completely useless, and often encumbered with cryptography restrictions, strict trademarks and software patents anyway.
      - bayindirh 10mo ago
        This is not always true. NVIDIA does exactly what you said. Move everything to firmware and closed GL libraries, and open source a kernel module to facilitate communication. They even created different firmware versions to prevent open source drivers to use the whole card. AMD did the inverse: They re-implemented a fully open driver from scratch, opened up the specs, made every part which they can make (legally) accessible, accessible, open sourced ROCm and send in packages to major distributions' (main / open source) repositories. Their firmware is closed source, but it's obtainable and doesn't require signatures to enable the card. They even clashed with HDMI forums to make a libre implementation of v2.1, but the forum basically threatened them. Intel's graphics drivers are basically the same with AMD. Broadcom / Intel / Realtek NICs work without their respective firmware blobs, yet their offloading capabilities are disabled. Either way, the drivers are completely open source and in the kernel mainline. Same for most sound cards sans Creative Labs. I want to hit them with a foam cluebat so bad. Logitech's all stuff works with open drivers. They are the primary contributor to V4L standard, standardize their webcam interfaces and provide drivers or help. Do you have any examples in mind?
  - paxcoder 10mo ago
    [dead]
- rnewme 10mo ago
  100% of their own software.
  - paxcoder 10mo ago
    [dead]
- wafflemaker 10mo ago
  IMHO, it's much closer to 100% than an iWatch or a Garmin.
  - aallaall 10mo ago
    1% is closer to 100%, than 0% is, yes.
- RobotToaster 10mo ago
  > More non-free software components may appear in our software in the future. That sounds ominous. I can understand not being able to remove non-free dependencies that were used previously, but that sounds like they intend to create new non-free components.
bloppe 10mo ago
Surprising because you'd think the hardware itself would be their primary moat.
- ddlsmurf 10mo ago
  Hardware isn't that hard to copy paste really, to make it hard you need to use really expensive processes (extreme uv etc), but otherwise, mostly you can pretty much take a picture. (very grossly speaking here, but just saying, the software is definitely a critical part)
bayindirh 10mo ago
Between the cross-licensing of hardware IP blocks and 3rd party software which never sees the light of the day, hardware manufacturers work like a secretive three letter agency to be able to control every part of their ecosystem. I tend to understand where this comes from. It's part business, part continuation of old customs and the way they did it and being able to control obsolescence to be able push new things to the market. However, if the periphery of the software you put out is closed source, even though this periphery is optional, it's not fair or ethical to say it's 100% open source. From my perspective, it can be said it's open core, and it's pretty fair, and acceptable in my case, but writing 100% Open Source* (*: 100% of the open part of the software stack, exceptions apply) is not fair game. It's misleading.
- ddlsmurf 10mo ago
  Seems a bunch are angry about this, honestly, 100% of what they made/control is open source was a good enough bar for me. Specially if all closed components are optional. I value the flexibility of being able to use or not even closed stuff. It's unclear to me what the issue is, false advertisement ? This is as good as it gets for things like this, maybe the "100%" was indelicate, but I wouldn't go so far as misleading. I can also understand the hardware companies, history has shown that the vast majority of industry actors have a purely parasitical relation to open source, and have no qualms copying/stealing IP.
  - bayindirh 10mo ago
    Personally, I'm not angry. On the contrary, I'm pretty neutral about closed-source, optional add-ons. I started playing/working with computers pretty early, and the current state is an utopia when compared to olden times in terms of Free and Open Source software (OTOH, both Free Software and Open Source is under heavy attack because of many reasons I won't enter here). What bothers me is "100%" part of the open source claim. I personally like the Debian model a lot. It's DFSG compliant by default, and if non-free software is needed, it's attainable. Debian is "as Free as you want, as closed as you need". I see, new Pebble follows the same model, and it's perfectly fine, but branding it as 100% Open Source is not. I'll not discuss hardware companies. It's a can of worms that doesn't belong to that reply. Let's say while I understand some of their reservations, these reservation doesn't change that they're greedy and selfish (beyond acceptable limits).

gf000 10mo ago

Above a certain complexity, there is basically no 100% open-source hardware out there. Like none of the Pinephone, Librem, Framework laptops are "open-source" to the bone.

squarefoot 10mo ago
Given how easy is to put and keep hidden malware into devices, governments should demand openness in that field as well. By "putting malware" I don't mean script kiddies in their moms basement but malware/spyware planted by design, which is extremely easy to do if you're the manufacturer, extremely easy to demand/force if you're the government above that manufacturer, and extremely hard to detect if you're a different user in a different country under a government that didn't demand full openness. I know it's impossible as business rules go, but ideally it shouldn't be.
- RobotToaster 10mo ago
  Every intel processor has a closed source IME, which is probably a NSA backdoor.
  - aallaall 10mo ago
    Isn’t minix open source?
    - RobotToaster 10mo ago
      Yes, the original is, but it's under a permissive license so Intel don't have to release the modified source code of their version.
- graemep 10mo ago
  The thing is governments are the people doing it, and most governments want to be able to put backdoors in more badly than they want other governments to not put backdoors in.
cncjchsue7 10mo ago

pjc50 10mo ago

Incidentally, this is one reason why there's not so much open source hardware out there: people get pedantic about it and apply gradually more unreasonable levels of requirement, rather than accepting partially or substantially open source solutions.

123pie123 10mo ago
The reason why people get "pedantic" about this stuff, is due the ability in the future to get screwed over when the priority blob owner start to charge money or other pull other license crap
- aallaall 10mo ago
  Enshittification. Open source is a valuable guarantee against that.
user3939382 10mo ago
Read Reflections on Trusting Trust to understand why having little bits of binary blobs sprinkled all over your compute arch is actually a major problem. Just because it’s a hard problem doesn’t mean we’re gonna pretend it’s fine.
- 0xEF 10mo ago
  PDF link for those that are curious: https://www.cs.cmu.edu/~rdriley/487/papers/Thompson_1984_ReflectionsonTrustingTrust.pdf https://www.cs.cmu.edu/~rdriley/487/papers/Thompson_1984_Ref... The general sentiment is that you cannot trust code you did not write yourself and that we need to be able to trust the person who did, but you can form your own conclusions about how that fits into the modern tech landscape.
  - kchr 10mo ago
    One of the points made in that paper is that you can't even trust the compiler, even if you write the code yourself. I think this is one of the stronger points as it shows you it is unfeasible to require everybody to audit all source code before running it. Be pragmatic, know your threat model, decide who you trust and move on with more important things in your life. Full disclosure: am free software advocate.

Wowfunhappy 10mo ago

They said 100% of Pebble Watch software. The binary blobs are other people's software.

aallaall 10mo ago
Closed verilog I can accept. But in general firmware is also software, for example it has become quite popular in the recent years to execute firmware on an embedded riscv cpu. And move more and more functionality to that kind of firmware.