Hacker Newsnew | past | comments | ask | show | jobs | submit | alhirzel's commentslogin

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?


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

They are. Great comment, I could not agree more with your thoughts.


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



The 85ms is configurable per-output delay for time alignment. That same file in the docs claims a typical end-to-end latency of 10 to 15ms.


Ouch, thats pretty average, what a pity ..


That's the maximum delay when adding a delay for synchronising with other sources.

The end-to-end delay is about 10ms, according to this comment:

https://www.audiosciencereview.com/forum/index.php?threads/i...


Why? This is a device more for home audio/audiophile uses it seems? Why does latency matter there?


Audio systems get used for more than playing back music and film soundtracks.

People use audio system at home to play electronic instruments. People also play video games. People do all kinds of stuff.

Latency is an important factor in these things.

Even videoconferencing and podcasting: With a microphone pointed at your face and a set of headphones used for monitoring that microphone, latency matters.

(It matters more to some people than others -- some people can tolerate hearing themselves later and continue to speak just fine, while some others increasingly sound like they're having a stroke as monitoring latency goes up and eventually become unable to produce coherent strings of phonemes.)


Huh thanks for the info! I didn't know about any of this at all. Latency sounds like it could be an important consideration for some people.


Its an important consideration for everyone, since we all have our own tolerance levels for latency - think about it when you're on a Teams call and someone in your room starts speaking but you hear them a half second later on 'delay' ..

Latency is percievable by most people down to about 8-12ms .. lower than that and its harder to perceive, higher than that and you will get some people feeling like there are glitches in the audio ..

This is also important for musicians such as keyboard players, whose perception of their instrument is radically altered by that instruments latencies. Most modern synthesizers work very hard to get audio latency in their internal engines below 20ms ..


Hmm it seems like latency is an important factor for everyone, but especially serious musicians.


Would be nice to use it as a synthesis DSP if the latency were a bit better.


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


S3 was just for me to do an initial prototype. Longer term was going to try with the C3, though I'm open to suggestions :)


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


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.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: