Comments URL: https://news.ycombinator.com/item?id=36976395

Points: 3

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=35647436

Points: 38

# Comments: 6

[1] https://sr.ht/~lattis/muon/

After I picked up the project again a year later (around 2019ish), I stumbled across OSQP again. OSQP blew both cvxopt and MOSEK out of the water in terms of speed (up to 10 times faster) and quality of the solutions (not as sensitive to bad conditioning). Plus the C interface was quite easy to use and super easy (as far as numerics C code goes) to integrate into my larger project. I particularly liked that the C code has no external dependencies (more precisely: all external dependencies are vendored).

[1] https://osqp.org/

First of all, there is no single accepted definition of "neuromorphic" [1]. Still, as a point in favour of the "neuromorphic systems are analogue" crowd: the seminal paper by Carver Mead that (to my knowledge) coined the term "neuromorphics" specifically talks about analogue neuromorphic systems [2].

Right now, there are some research "analogue" (or, more precisely "mixed signal") neuromorphic systems being developed [3, 4]. It is correct however that there are no commercially available analogue systems that I am aware of. Unfortunately, the same can be said for digital neuromorphics as well (Intel Loihi is perhaps the closest to a commercial product, and yes, this is an asynchronous digital neuromorphic system).

[1] https://iopscience.iop.org/article/10.1088/1741-2560/13/5/05...

[2] https://authors.library.caltech.edu/53090/1/00058356.pdf

[3] https://brainscales.kip.uni-heidelberg.de/

[4] https://web.stanford.edu/group/brainsinsilicon/documents/ANe...

[1] https://github.com/astoeckel/libfoxenflac/blob/master/foxen/...

So, given that FOSS---which a large portion of the HN crowd depends on---cannot work without copyright (at least not in its current form), the recent discussions may be less of a surprise.

Of course, for now, cheats like the one featured in the article should be fairly easy to detect (at least from what I've seen in the linked video). The motion of the bot is extremely jerky; a simple rule-based system, or, if you want to be fancy, a neural network based anomaly detection system should be able to detect this.

On the side of the cheat authors, this could be easily circumvented if they include a "calibration phase", where user input trains a simple neural network to stochastically emulate the dynamics of the user's sensor-action loop. The cheat could then act slightly faster than the user, giving them an edge while still using their unique dynamics profile.

I wonder where this will lead eventually, and I genuinely feel sorry for all the people who pour their heart and soul into competitive gaming; I don't think that this kind of cheating is something that can and should (see above) be prevented in the long-run. The best possible outcome I can imagine is that online gaming becomes more cooperative or once more converges back to small groups of people who know and trust each other.

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

Edit: Spelling, grammar, and clarity

Edit: From what I can tell, support for WDS depends on the WiFi chipset. "iw list" must explicitly include "WDS" as a "supported interface mode". At least the Broadcom chipset on the Raspberry Pi Zero does not support this, but, for example, the Atheros chipsets used in a variety of routers do.

Unfortunately, the project has never really taken off, and only few new articles have been added over the past few years. And of course, just as I am writing this comment, I realize that [2] now redirects to some domain squatter and is blacklisted by my DNS server...

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

[2] https://scholarpedia.org/

I've been using this setup in my home network for years now (with a dedicated OpenWRT device for each wired "island") and it works great.

Edit: To clarify, yes, this establishes a single broadcast domain. For example, DHCP and ARP requests are propagated through the entire network.

They are the lead author of libvterm, a popular modular terminal emulator library that is for example used in neovim and emacs-libvterm.

They have also been working on libtermkey, a library that accepts input from the divised keybinding system, now part of libtickit mentioned in the post.

[1] http://txti.es/bitshiftvariationsincminor

The Shannon-Nyquist sampling theorem guarantees that we (as in the DAC in your computer) can perfectly reconstruct the analogue signal for any discretised signal that is bandlimited to frequencies below Nyquist, i.e., 24 kHz for a 48 kHz sample rate. No matter how crooked the sample points may look to you. And 440 Hz is way below the 24 kHz limit.

Sure, this doesn't take quantisation into account, but 16 bit is sufficient to encode the difference in amplitude at the individual sample points between 440 and 440.8175 Hz with plenty of headroom (about 210 digital steps at 109 samples). Indeed, the smallest frequency difference that would have a zero difference after 109 samples due to quantisation is about 0.001 Hz (modulo mistakes in my hasty calculations). And this doesn't take dithering into account. Dithering essentially gives you an infinite dynamic range (depending on your definition of dynamic range) at the exchange of a higher noise floor. Of course your signal is likely also longer than 109 samples.

See this excellent video [1] by Xiph.Org's Chris Montgomery for a whirlwind overview of digital signal processing.

[1] https://www.xiph.org/video/vid2.shtml

[1] https://blogs.gnome.org/uraeus/2020/09/04/pipewire-late-summ...

The idea is to make blocks (slightly) variable in size. Block boundaries are determined based on a limited window of preceding bytes. This way a change in one location will only have a limited impact on the following blocks.

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

As for playback, most likely your sound card is already running at 48kHz; 44.1kHz may actually not be supported properly by your DAC (I guess since it requires a higher quality anti-aliasing filter). As [1] continues to explain, Opus is essentially shifting the burden of resampling to the encoding rather than the decoding side of things.

That being said, Opus technically supports odd sample rates such as 44.1kHz, but this has to be signalled in a side-channel. See [1] downwards.

[1] https://wiki.xiph.org/OpusFAQ#What_is_Opus_Custom.3F

edit: clarity

Comments URL: https://news.ycombinator.com/item?id=23531902

Points: 2

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=23496568

Points: 3

# Comments: 0

Direct link to the article (with paywall): https://science.sciencemag.org/content/367/6482/1131

DOI: 10.1126/science.aba0672