- phhYou can make frequency inertia with solar (even without batteries if you accept running with a constant reserve so with reduced efficiency). Spain showed that there is a learning curve, that's for sure, but their issue was a "simple" oscillation problem that can be fixed by adjusting frequency-follow rate and grid-disconnect rules. It wasn't like a peak of energy consumption or loss of energy production that only a rotating mass could compensate.
- 80% is catastrophic though. In a classroom of 30 all honest pupils, 6 will get a 0 mark because the software says its AI?
- Is there a survey of SoTA of what can be achieved with CSI sensing you would recommend?
What is available on the low level? Are researchers using SDR, or there are common wifi chips that properly report CSI? Do most people feed in CSI of literally every packet, or is it sampled?
- I'm curious why they are using actual modems rather than just doing it with VoWifi that merely requires a SIM card reader (pretty much just an UART)
- Except I'm guessing they are not selling their equity, they are making debt backed by their equity?
- Well you can't really do -600C sand (or anything), so the benefits of sand VS water largely diminished. "just" freezing water already gives you around 300C equivalent of sand (if my napkin is correct).
Also the point of this plant is to exploit the counter-correlation of cheap electricity and cold. Usually there is a bigger correlation between cheap electricity and heat.
- Well in FP4
- I dream of getting mcp with interoperable micropayments before ads.
- > > Tail recursion IME is a bigger foot gun
> This is true for some languages, but not all.
Useless anecdote that tail-recursive can be a foot gun even in Scala.
I did a (screening) job interview at Datadog, they asked for "give the spare change back on that amount of money" exercise (simple variant), "in whichever language you want". I did my implementation in tail-recursive Scala (with the annotation). I ended up trying to explain that tail-recursivity doesn't explode in memory for the rest of the call (and failed)
- It depends on espeak-ng which is GPLv3
- You can technically run it on a 8086 assuming you can get access to a big enough storage.
More reasonably, you should be able to run the 20B at non-stupidly-slow speed with a 64bit CPU, 8GB RAM, 20GB SSD.
- Well if nVidia wasn't late, it would be runnable on nVidia project Digits.
- > - Gesture navigation steals user input when swiping on the left/right edges of the screen,
Well I've seen even 1B+ dl apps failing to handle that (on a Google Pixel), so at this point I'm putting the blame on Google. I've switched back to three button navigation. Though even some trivial OS gestures like screen unlock fail reliably on my Pixel 6a. (As in, I do the gesture, it fails to register the gesture, i try to make the gesture "with more conviction" through the whole screen and it still fails, and after few minutes it ends up okay somehow)
- Kyutai's unmute has great latency, but requires a fast small-ish, non-thinking, non-tooled LLM. What I'm currently working on is merging both worlds. Take the small LLM for instant response, which will basically just be able to repeat what you said, to show it understood. And have a big LLM do stuff in the background, and feeding back infos to the small LLM to explain intermediary steps.
- So, my brain defaulted to "people are smart, so it makes sense", so it understood it as "it's the toy you keep within reach". But if you look at Pollen Robotics product, you see they have a "Reachy", which can indeed move, and has arms to interact with its environment. So yeah, it's a weird name. It reaches your heart through the feeling it communicates to you with its antennas?
- Looking at the BOM (6 cheapest servos, one usb camera, a usb hub, a microctronller ,two mics, 30cm-high low-precision plastic) the price looks fairly realistic to me. I could imagine it at half the price on aliexpress. The manufacturing or sourcing doesn't seem complicated. So overall it looks like a very realistic endeavor.
The only negative point I see: Pollen Robotics doesn't seem used to do mass market/cheap products. But as I said, it seems to be a pretty simple production (I mean, they are probably running everywhere like crazy because nothing is ready and everything is broken, but they should be able to accomplish this)
- Could we rather get a link to the original blog post? https://huggingface.co/blog/reachy-mini
- As someone who had to tweak many times LMK and Android's way to compute which process/app has which priorities, and how is a service restarted, I want to scream very loudly. But I guess that works.
- > - Samsung has their own basebands but only uses them on their premium phones
Uh? There are Samsung Exynos devices not using a Samsung baseband? (Exynos spans a large size of the range, just not the sub-100$)
> Utterly unbelievable that no Western government has tackled that situation. The market for basebands is completely and utterly rotten:
There is a global problem that in a lot of areas there is a monopoly lock-in via standards. Those companies are growing their strategies to control the way standards are written, to make it more complicated and costly for 3rd parties to implement.
One example of making standards more complicated which adds more patents is DVB-T2 [1]. 95% of the usage of DVB-T2 compared to DVB-T1 is increasing modulation rate and improving FEC, but it also adds PLP (which I've seen maybe three demos of), which is covered by several patents, largely increasing complexity and patent cost.
FWIW, I love standards and I agree that the industry should largely participate in making standards. I agree that standards needs to have "SHALL", you can't make everything optional to allow for lower costs. And I won't pretend there is an easy solution to those problems.
Sadly, the only way I can see to improve this situation, is to increase government's public funding into standardization.
[1] FWIW, I know nothing of how DVB-T2 has been written and who did it, so it's just an example of complicated requirements increasing the number of patents and thus cost of implementation. It's possible that those requirements have been added in good faith.
- I agree with the article, and I love how the author is (mis-)using MCP. I just want to rephrase what the accident actually is.
The accident isn't that somehow we got a protocol to do things we couldn't do before. As other comments point out MCP (the specificaiton), isn't anything new or interesting.
No, the accident is that the AI Agent wave made interoperability hype, and vendor lock-in old-fashioned.
I don't know how long it'll last, but I sure appreciate it.