grav
grav on Hacker News
Fix:
(() => {
const KILL = ['wheel', 'mousewheel', 'DOMMouseScroll', 'touchmove'];
const block = e => e.stopImmediatePropagation();
for (const t of KILL) {
window.addEventListener(t, block, { capture: true, passive: true });
document.addEventListener(t, block, { capture: true, passive: true });
}
document.documentElement.classList.remove('lenis','lenis-smooth','lenis-scrolling','lenis-stopped');
console.log('Scroll hijack disabled — native scrolling restored.');
})();
I fail to understand how two LLMs would be "consuming" a different amount of tokens given the same input? Does it refer to the number of output tokens? Or is it in the context of some "agentic loop" (eg Claude Code)?
> Interestingly, the malware checks for the presence of Claude Code CLI or Gemini CLI on the system to offload much of the fingerprintable code to a prompt.
Can anyone explain this? Why is it an advantage?
In the demo, is there any specific reason that the voice doesn't go "up" in pitch when asking questions? Even the (many) rethorical questions would in my view improve by having a bit of a pitch change before the question mark.
At [previous company], we initially required branches to be up to date with main.
Since it was a relatively big mono repo, it slowed down productivity quite a bit.
Eventually we tried dropping that requirement and instead relied on testing main before deploying to production. It sped us up again, and main never broke because of bad merges while I was there.
Claude 3.7 Sonnet seems to have a context window of 64.000 via the API:
max_tokens: 4242424242 > 64000, which is the maximum allowed number of output tokens for claude-3-7-sonnet-20250219
I got a max of 8192 with Claude 3.5 sonnet.
It is possible, since spending has an API. I’ve recently implemented it on Azure for a company, to ensure our storage costs didn’t run wild.
Couldn’t find an out-of-the-box solution, maybe, as you say because it’s not in their interest.
Couldn't get the code to run with Perl on Mac:
$ plenv exec perl midi.pl
Not enough arguments for main::pedal_notes at midi.pl line 107, near "$note)"
BEGIN not safe after errors--compilation aborted at midi.pl line 150.
I got something similar working in Supercollider though, which has a lot of tools for these sort of things, eg:
MIDIIn.addFuncTo(\noteOn, ~myNoteOnHandler);
> no motion data
How come there's no motion data?
Very impressive. Also interesting that the motion type prediction ("is this a moving train?") generalizes to underground trains in other cities.
I see they support the the largest cities in Sweden and Norway, wonder if there are any plans for Copenhagen, Denmark?
(swap! state update :co2-level (partial * 0.8))
TL;DR: created a wifi-network on another phone with same SSID and password as the one that the lost phone usually connects to, walked around waiting for the phone to connect, receive the "Find my phone" notification and send out a sound.
Cool :)
Nice idea. I'm really missing a way to contol the dynamics. Maybe just mapping 1-9 keys to a velocity scaling?
I also experienced performance problems with Arch Linux ARM through UTM. Parallels seems to perform much better for me.
One issue might be that only OpenGL 2.1 is supported:
https://github.com/utmapp/UTM/issues/4285
I've been using the trick with enforcing realization by serializing to strings a few times. Slow, but quite useful in many contexts. However, instead of using `(with-out-str (pr ...`, there's simply`pr-str`, which is easier to remember.
I'm typically using it like so:
(defn realize [v] (doto v pr-str))
(binding [*some* binding]
(realize (f some-nested-lazy-seq)))
Works for me. You probably need to unmute the phone.
I can highly recommend Arch AMD64 under Parallels on M1. GPU acceleration, clipboard integration, stuff generally works
iZotope RX 7, mentioned in a comment above, has something called de-reverb. I didn't try that particular feature, but I did try the music rebalance feature, and it's pretty impressive.
I was expecting a 500 server error.
I agree it's a good response, both marketing wise (the compensation in the form of cheaper upgrade) and technically (the improved health visibility).
Regarding your concerns:
1) The software update that improved the power management was released for iPhone 6 and later only according to the article.
2) They state "Early in 2018". I think this is a pretty conservative, yet realistic estimate, considering they don't want to risk the user experience.
How's the story with source code obfuscation in Swift-land? Wouldn't that be an option for you?
Agree that Elm is a good all-in-one solution for SPAs.
You should also give ClojureScript with the simple React-wrapper Reagent a spin. All the functional stuff is built into the language, like Elm, albeit without the types, which both has its pros and cons.