This is also why open source wearables can’t have the best PPG heart rate/SPO2 tracking.

There are only about 4 PPG analog front ends still in production that don’t require an NDA and the Max86141 is the only one worth anything it seems.

You can’t do analog front ends with any small FPGAs that I know of and it is simply to large to do it (well, at least) on a small wearable with discrete components.

This seems like the perfect scam for Lemmy for setting up a fresh IP for launching a cyber attack/scam with a real residential IP. Helping a community member while circumventing shitty corporations. (Not saying OP is, just that it would be a decent scam)

This requires either an insane amount of trust in a random person or gullibility. Plugging a random mailed device into your network, even behind a VLAN.

I definitely would never do this if I didn’t have absolute full and complete access to every part of the pi’s software, or preferably set it up myself (optionally in collaboration with the requester) and the requester only had read-only access to it.

Disruptive by design?

Is this 2015 VC backed slop or something?

True, actual steam flatpak is a mess. Opensuse Kappa/Aeon actually use it and it took an afternoon of debugging and 3, barely - documented fixes to get proton games to launch at all.

Eh, I am not pro AI, but these sorts of non- critical projects are maybe not a horrible use for them. Keep AI out of my kernel, core programs, basis functionality, camera, and personal/health information etc… But for a sorting/catagorization tool maybe not so bad. (Ignoring the environmental and ethical concerns of course)

I am already trying to understand all of it first myself. In the middle of a full-strip renovation; I don’t think I will have time to spend on it 😂

Please dear god let STM or Nordic someone hire some technical writers for Zephyr, not just Nordic documentation.

The data structures, macro basics, and core concepts are OK, but for example ADCs have literally 0 documentation at all, documentation about DMAs is barebones at absolute best, non-led PWMs is not good, etc…

Pretty much every single peripheral needs 5x-100x the documentation it currently has lol.

I think it is the other evidence that it is vibe coded

• Brand new account
• Dev only responds to non-technical or feel-good comments
• other commenters have pointed to AI teltale vibe coding syntax signs in many of the files
• Claude extra files in early commits and changing gitignores to do it.

Advertised Vibe coded projects absolutely are by default bad and here is why:

• Developers do not understand what they have built, so can’t debug it beyond “Claude, fix this”
• Vibe coded projects are easy-come, easy-go very often abandoned (73% of the vibe projects on flathub, and those are the people who thought far enough to decide putting it on flathub was worth it)
• developers can’t answer any questions on security when the app will be handling credentials, be hosted on a server, or attach to some sort of live service -> absolutely gaping security hole that you just have to cross you fingers that Claude didn’t do another “oops, you are completely right to push back,1500 common attack vectors were left open and you are now part of a CSAM botnet, do you want me to fix it?”

If someone wants to make small scripts, one-off test firmware for a home project, writing test cases, design reviews, boilerplates, etc… Are arguably good usecases.

Vibe coding an ongoing software service is almost always a hard no-go and statistically will be abandoned and unupdated, leading to even more security and usability issues.