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

It's a normal video, I don't know what you're talking about.

I wanted similar for my Oura ring, but all the MCP servers were unmaintained. Claude suggested a SQLite db with cron sync, built it, and it works pretty great. An MCP server would've been overkill, and slower probably too. Only downside so far is the Oura API doesn't expose some metrics I care about, like cumulative stress.

Currently experimenting with prompt-injecting my sleep score etc with a startup hook, so agents automatically give simpler responses when I'm not "all there." (Also using this data to make it suggest less complicated/demanding perfume samples to try on those days.) Curious if anyone else has cool use cases for feeding health data to the AI overlords.


Have they published any data how they even calculate the "cumulative stress" metrics ? I would guess it's fairly straight forward

Did you implement it, or did Claude implement it?


I'm pretty sure an AI wrote all or most of this article.


I mean, you theoretically still could have that, USB decks send MIDI signals (even though I found it a bit obtuse trying to get my FLX4 to control anything except VirtualDJ - I was trying to map it to grandMA lighting controls). The TUI here could be primarily a presentation layer. I think the main benefits would be a) more hackable than VirtualDJ and b) it looks cool.


Totally! I'd love to work that in somehow


I've been thinking about this story a lot lately. When giving away your agency gives strictly better results, should you? And if you shouldn't, do you really think you're strong enough to resist it?


Would you give away your agency to another human or human organization if they gave strictly better results? My guess is you value your own agency over your life more than that. It's your life to make mistakes and hopefully learn from (but that's up to you), not somebody else's to live for you.


I'm super excited about the Index. All the time, I feel like I go "oh, I need to buy this thing" or "I should message that person about this" but I'm in the middle of a task and then I forget. (Or I have to get out my phone or a notepad to write it down - the phone is distracting and the notepad needs to be synced manually later, which I won't do.) I think my main use case is probably going to be adding stuff to my grocery list while I'm cooking, but I'm also excited about the webhooks integrations - I can pipe my idle while-driving questions to an agent and read the report later, for example. Or maybe I'll connect it to home assistant - "It's cold, turn down the AC please" or "hey can you play some music" without having to break focus. If this all works alright, I'm thinking about figuring out audio-out, so I can ask "what's on my calendar for tomorrow" and get a verbal answer. (Or maybe, putting this+todo lists on e-ink displays in physical space.)

I think the reason this is so exciting to me is that it's a way to interact with technology that's a lot less "evil" feeling. I am at my best when I'm not looking at screens all day, and the index provides an off-ramp that can potentially move several common workflows off those screens. I think even on my technology-off days, using the ring would still be fine. It also looks cool, and speaking into a ring to make things happen is much more aesthetically pleasing to me than "ok google." I really think you can't discount the cool factor here.


they want to isolate gay and trans children from other gay and trans people. don't you know, there's social contagion afoot, but if we protect y^Wour children from this inherently sexual (and thus adult) content, we can prevent it. this is enough to make me oppose age verification wholesale. I don't care if there's fancy ZKPs, it's still going to be used to isolate and harm hundreds of thousands of vulnerable trans kids, who are already experiencing astronomically elevated suicide rates over the past few years. they don't need more of this.


In Denver, they'll be expanding once they have budget. Also as soon as Axon finishes developing their integrations with civilian cameras into their Fusus product. They've also got natural-language queries in the pipeline ("find red trucks near here"), and they already have integration with the hundreds of existing non-ALPR LEO cameras. It's not better.


It's different. The primary harms of flock come from their horizontal integration into a nationwide surveillance network, working with ICE etc. Axon (formerly Taser) has strong vertical integration, which is new and we haven't thought through as much yet. (This is the position of city councilmember Sarah Parady, who's been part of a working group to research+draft ordinances about surveillance technology, and whose speech at the meeting voting on the contract I really respected. I think it's available online.)

The Axon contract is smaller than the Flock one, 50 cameras instead of >100, but that's because it's all they could get budget for, and they want to expand. DPD owns the data and is theoretically not supposed to share it with federal agencies, but there are lots of legal ways to make them comply. They're setting a 21-day retention period for data that's not part of an ongoing investigation, but I think that's missing the point, and it's not codified into law. The Axon cameras can be switched into a mode where DPD can view live feeds. Most of the contract provisions that the mayor's office added because of significant public outcry I would call "token." They're not addressing the real issues, and it's still contributing heavily to the development of the surveillance state.

Overall, it's an improvement, in the sense that breaking your leg is better than breaking both your legs. But don't get me wrong, they're coming for the other one as soon as they can.


Hi, I'm in Denver. They're already doing this over on Colfax. It's a significant change vs the existing halo cameras, because they use the drones to follow people.


Consider applying for YC's Winter 2027 batch! Applications are open till November 2.

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

Search: