alhirzel

I wonder how this relates to the ongoing ambiguity with CMMC 2.0 rollout.

The snake and its tail make a discovery...

Does math exist without humans?

Best advice I ever received was to learn to take good advice.

Still not sure how to do that...

Reminds me a bit of the MIT study that relates to spacing in densely packed roadways [1]. Whenever I apply the rule (look into my rear view mirror and decide how late to slow down), I feel like a good little molecule in an ideal gas.

[1] https://www.csail.mit.edu/news/improving-traffic-tailgating-...

Wow - thanks for pointing this out! I will be looking into it.

I should have also mentioned that my appetite also includes not being locked into one vendor's software stack. For instance, there are nice offerings from Eprosima [1] and Twin Oaks [2] that do this, but they seem to be "outstanding in their field" and would be difficult to replace if a need to do so developed. In the case of Eprosima's offerings, they also make some architectural assumptions that are difficult to maintain for some applications (such as having a paired Linux device with each embedded device acting as a translator).

But yes - there absolutely are solutions already. I guess I was just lamenting that they weren't really functionally accessible for all applications.

[1] https://micro-xrce-dds.docs.eprosima.com/en/latest/

[2] https://www.twinoakscomputing.com/

Reminds me a lot of the Tactical Microgrid Standard (aka TMS aka MIL-STD-3071) [1], probably just because TMS uses DDS as well. I would really like to know if there is a protocol that functions like DDS but caters to real-time guarantees and prioritizes (at a "simple protocol" level) usability on embedded systems with no dynamic memory allocation. It would also need to be just-as-functional with non-real-time systems. One problem with DDS is that it is too heavy-handed to implement well on an embedded system.

[1] https://battery.army.mil/system-integrator-hub/tms/

Not wrong!

I would probably abbreviate that to v17g.

I was too busy waxing my armchair and didn't do any reading on the actual practices. Thank you for replying with this. It makes sense. I wonder if this level of purity will survive the test of time; since there are paid kernel developers, the situation could be very different from e.g. an entirely volunteer-maintained project.

I am assuming that many of these are found with automatic analysis tools that are very creative (i.e. LLMs) and there may be a high proportion of very "cornered" cases. I think there needs to be a triage method that would amount to the severity, likeliness, and detection dimensions used to rank risks in a systematic framework [1]. I think if this could be submitted (or estimated) along with such bug reports, it could go a long way toward sustainable intake patterns for this number of possible defects.

[1]: https://en.wikipedia.org/wiki/Failure_mode_and_effects_analy...

I think it depends on how good is "good enough". Personally, I think as long as tasks are not coding, there would be a ton of "good enough" value in having your own personal Google on a hardware device. I think the company that designs and licenses the architecture that packages the silicon for the largest market share will be the winner in commercializing this product. Wouldn't be surprised if this is part of Apple's roadmap to retaining existing customer loyalty.

Thank you for sharing this!

Didn't know about sunshine request - the website[1] - until I searched for this term!

[1]: https://www.sunshinerequest.com/

"I'll spare you the total sample prep details"...

I am so glad to hear this. Thank you for your work in support of land conservation!

I have been on the board of directors of a land trust, and this situation is a poster-child for why an existent concern must retain standing to litigate. A lot of what the Land Trust Alliance (LTA) does is ensure things like the legal nuts-and-bolts of conservation stays possible and durable, including conservation easements. CEs can be a lot of work, especially as the legal landscape changes. I think the dismissal of this lawsuit is not necessarily a risk to CEs, but could be widened into one in the future. This is the risk that LTA exists to mitigate.

The land trust you work with - are they accredited with LTA?

85ms

https://github.com/WeebLabs/DSPi/commit/ba8e481570e6a5ce3d35...

You could consider similar devices and what they have used. Another angle is to look at ULPMark results: https://www.eembc.org/ulpmark/

The S3 (and other Espressif chips) are pretty power-hungry. May want to keep looking for a smartwatch application.

I love the symbol name: "AnalyticsMetadata_I_VERIFIED_THIS_IS_NOT_CODE_OR_FILEPATHS`.

It's the butterfly effect. After the momentum exchange (the rocket slamming, stuff being ejected in the impact, etc), the entire system was left with different properties. From now on, the equation F=Gm1m2/r^2 will have a different m1, and you can sum the equation over all m2 (literally every other massive object in the universe).

So many new features! The little things like 45 degree crosshairs, dynamic animation of overlapping lines, indication when bumping up against a selection filter - truly great polish. Board variants, propagation delay profiles, groups - the future is here! I hope KiCad is the next Blender-grade success story in OSS. It is certainly poised to disrupt commercial options.

This is going to get crazy as soon as companies start to assert their control over open source code bases (rather than merely proprietary code bases) to attempt to overturn policies like this and normalize machine-generated contributions.

OSS contribution by these "emulated humans" is sure to lever into a very good economic position for compute providers and entities that are able to manage them (because they are inexpensive relative to humans, and are easier to close a continuous improvement loop on, including by training on PR interactions). I hope most experienced developers are skeptical of the sustainability of running wild with these "emulated humans" (evaporation of entry level jobs etc), but it is only a matter of time before the shareholder's whip cracks and human developers can no longer hold the line. It will result in forks of traditional projects that are not friendly to machine-generated contributions. These forks will diverge so rapidly from upstream that there will be no way to keep up. I think this is what happened with Reticulum. [1]

When assurance is needed that the resulting software is safe (e.g. defense/safety/nuclear/aero industries), the cost of consuming these code bases will be giant, and is largely an externalized cost of the reduction in labor costs, by way of the reduced probability of high quality software. Unfortunately, by this time, the aforementioned assertions of control will have cleared the path, and the standard will be reduced for all.

Hold the line, friends... Like one commenter on the GitHub issue said, helping to train these "emulated humans" literally moves carbon from the earth to the air. [2]

[1]: https://github.com/matplotlib/matplotlib/pull/31132#issuecom...

[2]: https://github.com/markqvist/Reticulum/discussions/790

Don't forget about ELI the ICE man!

The physics of magnetic torquing maybe could probably work in most if not all locations on Earth for a sufficiently small and power dense vertical top that spins sufficiently slow. Want the smallest possible local dot product of gravity vector and magnetic field for an ordinary top (without considering "sideways" tops), which may lead to better performance in some locations on Earth (could map this with e.g. IGRF). 3D field actuation would be beneficial to allow higher efficiency and longer periods of actuation around the window where the Earth's magnetic field is maximized in the spun plane, while minimizing imbalance: this actuation timing is probably the only strategy that would make practical sense for most of the magnetic power, because you will need to take a break once in a while for sensing. Another practically difficult part would be avoiding on-board soft iron noise in magnetic field, because higher spin speed would require the device and environment to damp out the device-induced magnetic field at a higher minimum rate to afford any budget for accurate sensing of the background field during the "off"-time. That is: sensing trades with spin speed because it takes non-zero time and requires a stable environment.

To implement this, I think you'd first want to test in a controlled environment with a larger magnetic field and then gradually turn down the applied field until it is Earth-like. I am honestly unsure whether you could practically get there, so earlier I used the words "maybe could", but humans are crazy so I appended the "probably".

This would be a fun YouTube video to watch.