MurphyA/hacker-news huggingface dataset:
by zmmmmm | 2026-03-03 00:32:20+00:00
I do think it's completely unacceptable if Meta makes the glasses unable to be used for routine functions without (a) other humans reviewing your private content and (b) AI training on your content. There needs to be total transparency to people when this is happening - these are absolutes.

But I'm a bit confused by the article because it describes things that seem really unlikely given how the glasses work. They shine a bright light whenever recording. Are people really going into bathrooms, having sex, sharing rooms with people undressed while this light is on? Or is this deliberate tampering, malfunctioning, or Meta capturing footage without activating the light (hard to believe even Meta would do this intentionally).
by rmzi-a | 2026-03-03 00:32:30+00:00
Through the last few weeks, I've distilled my nearly 20 years as a software engineer, technology leader, data scientist, hackathoner and craftsman into a minimal set of tools that I use to push swarms of agents to implement all sorts of projects.

It's Claude plugin that contains a set of skills and agents that emulate the different roles / skills I look for in a team of engineers and presents an opinionated approach to the SDLC. It's not a reinvention of the wheel -- this is simply my preferred way of interacting with code as a team, built out using Claude as a stand-in for the individuals that make up a successful engineering team.

There's a white paper on the process in the repo under /docs.

NOTE: this does _not_ cover requirements definition as a whole. There are definitely some useful tools here to help talk through a problem and break that problem down into smaller tasks, but the idea is that these tools are focused on the actual process of building software, not defining it.

Let me know what you think! Fork it, open a PR, throw an issue at me. It's definitely WIP, but this, along with a few other tools I've built around tmux / juicing up my terminal, has increased my productivity immensely. I hope it does for you too!
by cyberax | 2026-03-03 00:32:35+00:00
I've been using Pixel devices for a decade. I don't remember any issues with moving? I think the only bothersome thing was re-authentication in some apps after the move.

It typically took me maybe an hour to move devices? Including moving to a non-Google phone once when I broke my phone during a foreign trip and had to get a temporary replacement.

> I'm not familiar with this, at all. The app switching is actually my favorite feature about iPhone. So easy to flip between two apps. I don't use a case, so maybe that's related.

I can't get it to switch consistently. On Android it's dead easy and reliable with a nav bar. On iPhone it's often not registering a gesture if I swipe too fast or don't start swiping from the very bottom.
Show HN: DevReel – A virtual gym for practical software engineering challenges
by giota_dev | 2026-03-03 00:33:53+00:00
Hi HN, I'm a software engineer from Japan building DevReel.

While platforms like LeetCode are fantastic for building the essential foundations of algorithms and data structures, I wanted to create a space dedicated to the other side of our jobs: the messy, practical realities of everyday software engineering.

DevReel is a "virtual gym" where developers tackle real-world scenarios. Here, you'll be fixing state mutation bugs, resolving concurrency issues, or making architectural choices, and then receiving instant AI-driven code reviews on your approach and thought process.

We've published a free Demo featuring a "Phantom Transaction" bug challenge—a real-world edge case reported by one of our early testers.

Our Pro challenges are currently in preparation and will be coming soon, but the demo is fully open today. We've also made our roadmap completely public.

I'd love for you to try breaking the demo challenge and hear your brutal technical feedback!

- Demo & Waitlist: https://www.devreel.tech/en/demo
- Public Roadmap: https://github.com/users/GiotaDev/projects/2/views/1
by foundatron | 2026-03-03 00:34:09+00:00
Right now OctopusGarden logs every LLM call with token counts and cost, and the SQLite store records each run and iteration (spec hash, scores per scenario, generated code). So you get a full trace of what was generated, what it was tested against, and how it scored.

For approvals, the current model is that the spec is the approval. If the spec is right and scenarios pass at 95%+ satisfaction, the code ships. There's no PR review step by design (the "code is opaque weights" philosophy).

That said, you could totally layer approvals on top. Gate on spec changes, require sign-off before a run kicks off, or add a human checkpoint between "converged" and "deployed." The tool doesn't enforce a deployment pipeline, so that's up to your org's workflow.

Worth noting: this is purely a hobby project at this point. It hasn't been used in any commercial setting. The guard rails and approval workflow stuff is where it would need the most work before anyone used it for real.
by aloha2436 | 2026-03-03 00:34:34+00:00
> I'm sorry but if your out is linux and windows because you're not happy how stuff doesn't "just work" in the Apple ecosystem boy are you in for a bad surprise.

I think you and GP agree more than you realise, their point seems to be that Apple was worth all the locked down walled garden stuff because at least it "just worked." Now it's a locked down walled garden which _also doesn't work._ Tahoe and iOS 26 are the worst of both worlds.
by hightrix | 2026-03-03 00:35:07+00:00
While I'd like to agree with you, and do in some cases, there are many cases where this just isn't a feasible approach. For example, a peer coworker has a pair of these. I just don't interact with her while she is wearing them. If my boss were to get a pair there is no way I can justify slapping them off his face.
by llingelo | 2026-03-03 00:35:21+00:00
A macOS app that transcribes meetings in real time and generates smart summaries — fully offline, no API keys, no data leaves the machine. Captures mic and system audio (Zoom, Teams, Meet) via
ScreenCaptureKit, runs Whisper Turbo for STT and Ministral 3B for summaries/chat, all on Apple Silicon. Open source, MIT.
by stackskipton | 2026-03-03 00:35:31+00:00
I think you missed entire point of operation.

If everywhere runs on UTC, they will still have different times when people are working/not working/sleeping so you still have to look something up and figure it out.

With time zones, you look up "What time is it?", realize it's 4:30AM and since most people around the world follow similar schedule, you quickly realize he's fast asleep.
by musictubes | 2026-03-03 00:35:32+00:00
No software? DaVinci Resolve? Affinity Designer? Final Cut, Procreate, AUM, Logic Pro etc etc etc. As the processors get more powerful more demanding software can be made for it. Running multiple physical modeling AUVs along with FX loops eat up clock cycles. Final Cut Camera on iPhones along with Final Cut on an iPad allow for full multi camera controls and recording from 4 different iPhones with ProRes and log shooting at the same time.

If Apple hadn't continually upgraded the processing power then none of those programs would work. It's up to Apple to make compelling hardware. Better hardware allows more advanced programs. iPads are amazing.
Show HN: ThinqWith – generate one-click AI prompts for your readers
by nirajswami | 2026-03-03 00:35:35+00:00
I wanted readers to actually engage with ideas in my posts, not just skim them. I know they're already using AI to go deeper — the friction is in the setup.

ThinqWith takes a blog post and generates prompt vectors readers can launch directly into Claude, ChatGPT, or Gemini (or ThinqBits) — no copy-pasting, no setup.
by dasil003 | 2026-03-03 00:35:55+00:00
The more experienced I get the more I see how these simplified techniques that might be useful to a journeyman engineer in the right context can fail horribly in the wrong context.

For this particular example, the first question I have is why are we upgrading the ORM? As a codebase grows and matures, the cost of ORM change increases, and so too must the justification for upgrading it increase. Any engineer worth their salt needs to know this justification and have it mind at all times so they can apply appropriate judgment as the discovered scope increases. Let's assume now the change is justified.

The next question critical question is how do you know if you've broken anything? Right in the intro the author talks about an "untested and poorly documented codebase", but then in the example uses basic compilation as a proxy for success. I'm sorry to be harsh, but this completely hand-waves away the hard part of the problem. To have any confidence in a change like this you need to have a sense of what could go wrong and guard against those things, some of which could be subtle data corruption that could be extremely costly and hard to unwind later. This may involve logging, side-by-side testing, canary deployments, additional monitoring, static analysis and/or any other number of techniques applied based on an understanding of what the upgrade actually means under-the-hood for the ORM in question combined with an analysis of what risks that entails to the system and business/process in question. Drawing a mindmap of your refactoring plan is barely more than IntelliJ (let alone Claude Code) can already do at the click of a button.
by haunter | 2026-03-03 00:36:10+00:00
>The sources they are working from is something I'd be curious to know where they came from

They basically merged the Region 2 (Japan) Dragon Box DVD release with the Region 1 (NTSC USA) one.

>This merge of the two Dragon Boxes aims to get more detail at the boundary ranges of
luma in order to obtain a higher dynamic range in a natural manner, without artificially
distorting the luma through sigmoid-like functions. This is made possible due to the brightness
difference between the North American NTSC and the Japanese NTSC-J standards and how
the DVD compression codec (MPEG-2) handles this difference. Basically, MPEG-2 gives more
3
bitrate to brighter areas. Darker areas get less bitrate and so the image details there are blurrier
and often destroyed. Fortunately for us, the North American NTSC standard has brighter blacks
compared to NTSC-J, which means that MPEG-2 was able to allocate more bitrate to the dark
areas on the R1 Dragon Box compared to the R2J, even though the latter has a higher overall
bitrate. In addition to better dark details, the R1 Dragon Box also has more dark details. This
is because DVDs have a limited luma range, and the brighter blacks on the R1 allowed more
dark details to pass through that limited range. These same extra details missed the cut on R2J
and were clipped away instead. So what does all this mean? It means that the R1 Dragon Box
has better preserved dark details while the R2J Dragon Box has better preserved mid-and-bright
details.

https://jysze.github.io/SoM-DBZ-Merge/mergeproject/R1R2.pdf

And then this merged release were used for the color correction
by reggz | 2026-03-03 00:37:33+00:00
If you're paying for model calls, retrieval, or other backend work on each request, charging earlier is a lot easier to justify because usage can literally cost you money while you're still figuring things out.

But I agree that it's feels like a mistake to charge before the value is obvious enough for someone to understand what they're paying for. Especially products with low marginal cost.
by larryste | 2026-03-03 00:38:11+00:00
# Show HN: web-search-tool – Search/scrape web with AI-friendly output

*Project:* https://github.com/larryste1/web-search-tool
*PyPI:* https://pypi.org/project/web-search-tool/

## The Problem

Building AI assistants needs: reliable search with fallback, clean content extraction, API flexibility, and structured JSON output. Existing solutions are single-backend (breaks when API fails), too complex, or output raw HTML.

## The Solution

`web-search-tool` searches/scrapes with clean, AI-friendly output:

```bash
pip install web-search-tool
web-search "Python async best practices" # Search with AI answer
web-search "React hooks tutorial" --scrape # Full article content
web-search "machine learning" --include-domain arxiv.org # Filter domain
web-search "API design" --json # JSON output
```

## Features

- *3 Backends with Auto-Fallback*: Tavily → Serper → DuckDuckGo
- *Content Scraping*: Extract main article text via BeautifulSoup
- *Domain Filtering*: Include/exclude specific domains
- *Search Depth*: Basic or advanced
- *AI-Friendly Output*: Structured results with optional AI answers
- *JSON Output*: Pipe to jq or parse in scripts

## How It Works

```
Query → Tavily (AI, needs key) → Serper (Google, needs key) → DuckDuckGo (free)
```

## Examples

```bash
# AI Research with Answer
$ web-search "What is Rust ownership?"

Search: What is Rust ownership?
Backend: Tavily
Answer: Rust ownership manages memory allocation. Each value has one owner...

# Scrape Full Articles
$ web-search "Python decorators" --scrape --num 3

# Domain-Specific
$ web-search "type hints" --include-domain realpython.com --include-domain docs.python.org

# Programmatic Use
from web_search_tool import search_web
result = search_web("Python best practices", scrape_urls=True)
```

## API Keys

| Backend | Key | Get Key |
|---------|-----|---------|
| Tavily | Optional | https://tavily.com/ |
| Serper | Optional | https://serper.dev/ |
| DuckDuckGo | None | Free |

```bash
export TAVILY_API_KEY=your-key-here
export SERPER_API_KEY=your-key-here
```

Without keys, falls back to DuckDuckGo automatically.

## Why I Built This

Building AI assistants, I hit: single point of failure, messy output, no fallback. This tool tries multiple backends, extracts clean text, returns structured JSON, works without API keys.

## Tech Stack

Requests, BeautifulSoup4, Tavily API, Serper API, DuckDuckGo HTML

## Try It

```bash
pip install web-search-tool
web-search "Python tutorials" # No API key needed
```

*GitHub:* https://github.com/larryste1/web-search-tool

*Feedback:* What backends should I add? How do you handle web search in AI projects?

---
Built after too many API failures with single-backend tools.
by zackkrida | 2026-03-03 00:39:18+00:00
the identical rhythm and structure of these low-effort AI slop posts is so distracting that it makes me unable to evaluate their substance.

even the best high school plagiarists know that you're meant to rewrite the sentences you've stolen. why can't these slop authors be bothered to do that with all the time they're proportedly saving by using AI in the first place?
by Arch485 | 2026-03-03 00:39:19+00:00
I feel like days are a non-issue; they would just start at different times (UTC) in different territories. This wouldn't make things any more complicated than they already are (currently, if I want to talk to someone in Australia, I have to look up what time it is in Australia and infer the day of the week from that, if necessary. If everything is under UTC, I know what "time" it is, but I still have to look up what day it is).

Most of the issues time zones cause are not "day of the week" related anyways (at least in my experience), so I think having to figure out what day of the week it is somewhere else wouldn't be a common problem anyways.
by Nevermark | 2026-03-03 00:39:48+00:00
> People don't care about privacy as long as a faceless corporation is doing the spying.

This isn't true. Most everyone hates the fact they are being surveilled, but it is pervasive and people only can deal with so many complications in life.

Avoiding surveillance is not a decision or action, it is 1000 decisions and actions. Endless decisions and actions.
by losvedir | 2026-03-03 00:39:58+00:00
Agreed. I'm confused trying to map what the article is saying to what's happening at a technical level. For example, obviously it's not doing on-device inference, so it's unsurprising that it won't work without a network connection, but this is totally distinct from your recordings ending up getting labeled. It talks about being able to opt into that, which is one thing. But I guess I don't understand if you don't opt in, if the data still gets sent out for labeling.

I feel like this article is either a bombshell, or totally confused.
by dumpsterdiver | 2026-03-03 00:40:29+00:00
What’s the intent of pointing out the presumed provenance in writing, now that LLMs are ubiquitous?

Is it like one of those “Morning” nods, where two people cross paths and acknowledge that it is in fact morning? Or is there an unstated preference being communicated?

Is there any real concern behind LLMs writing a piece, or is the concern that the human didn’t actually guide it? In other words, is the spirit of such comments really about LLM writing, or is it about human diligence?

That begs another question: does LLM writing expose anything about the diligence of the human, outside of when it’s plainly incorrect? If an LLM generates a boringly correct report - what does that tell us about the human behind that LLM?
by aryzach | 2026-03-03 00:40:40+00:00
SF Sauna -- SF Bay Area

Electrical / Power Systems Engineer - Build a battery-integrated sauna heater

Paid contract role, $80 - 150/hr, 15–25 hr initial scope

This is a multi-kW DC system problem (battery pack, resistive heater, contactor, safety logic). The constraint is reaching sauna temps without relying on a 240V wall connection.

We currently generate ~$5k MRR renting saunas in the SF Bay (sfsaunarental.com). We've validated pain-point and demand.

If there’s mutual interest and the prototype goes well, this could extend into deeper collaboration or a more dedicated role.

To apply, email zach (at) sf-sauna (dot) com and include:

A short description of the EE project you're most proud of building from scratch
A link (GitHub, project photos, writeup, resume, etc)

Visit sf-sauna.com for more info about the problem space.
Google just killed my project
by othmanosx | 2026-03-03 00:41:05+00:00
For the past year, I’ve been building GM Pro — a Chrome extension that upgrades the chat experience inside Google Meet.

It started simple: reactions, replies, mentions, dark mode for chat. Then I added auto-join, auto-mute, transcription tools, lobby notifications, attendee shuffling. Basically all the things you wish Meet chat had by default.

People loved it. 5-star reviews. Steady installs. Real usage.

And then, after many years of lackluster chat, Google announced they’re integrating Meet chat directly with Google Chat — persistent conversations, reactions, file sharing, the works.

Which means… the exact surface area I built on top of is becoming a first-party feature.

On one hand, this validates the idea. The direction was right. The need was real.

On the other hand, platform risk just punched me in the face.

When you build on top of a giant platform, you’re effectively prototyping features for them. If the feature works, they absorb it. If it doesn’t, you disappear quietly. Either way, they win.

Now I’m thinking through:

Do I pivot to power-user tools Google won’t prioritize?

Double down on automation and workflow features?

Move away from chat and toward meeting intelligence?

Or accept that consumer Chrome extensions sitting on core UI are inherently fragile?

Curious how other builders here think about platform dependency.

Have you ever had your product “Sherlocked” by the platform you’re building on? What did you do next?
by dylan604 | 2026-03-03 00:41:27+00:00
It's funny, I've been around the 16mm reels provided to Funimation for a long time. The first time they transferred to SD DigiBeta tapes I was an assistant editor at the post house doing the transfers. Those transfers were used to make the NTSC broadcast masters. Eventually, they started making DVDs. By that time, I was at a different company that was hired to program the DVDs before eventually working directly at Funi. While I was there, they decided to go back to the film prints for a new transfer, but some very questionable decisions were made during that transfer. When the box set was released, the fans hated it. They went back to those prints a third time for a new transfer with a more sane approach. The colorist found reference film for the stock the prints were on, and had the closest color the creator had seen. After some years later, I was working directly with that colorist. We talked a bit about that film. He was flabbergasted about the fans. Someone on the internet looked him up and reached out to him with less than favorable things to say. That's when he learned about anime fans. While I was at Funi, we had arguments with fans that didn't believe we had the film to do these transfers. They were adamant that we took the original DigiBeta tapes, yet not questioning the origin of those tapes. Posting replies with people holding the film reels did nothing to dissuade them. Funi went so far to include an extras on the Blu-ray release of the process of the film transfers, the frame-by-frame restoration process, and other steps. Fans were still online saying they could do better. I wish them luck.
by tempestn | 2026-03-03 00:41:47+00:00
In the winter I can see arguments both ways (though I'm personally in the evening light is better camp). But in the summer, it already gets light earlier than almost anyone would want to be awake. An extra hour of sunlight at 4am is little benefit to anyone, and likely just makes it harder to sleep. Light evenings in the summer are wonderful though. I think part of the health argument against DST is that those light evenings make it harder to get to sleep at night, which is fair, but I still wouldn't want to give them up!
by nicktikhonov | 2026-03-03 00:41:56+00:00
I'd say it was a collaboration. I had to hand-hold Claude quite a bit in the early stages, especially with architecture, and find the right services to get the outcome I wanted. But if you care most about where the code came from - it was probably 85-90% LLM, and that's fantastic given that the result is as performant as anything you'll be able to find out of the box.
by pndy | 2026-03-03 00:42:03+00:00
In two banks I was in in last 20 years before and after Payment Services Directive implementation, I was a secondary user to the account. I could do almost anything on the account which saved my mother lots of stress. It's enough for her to check balance and outgoing transactions and rest lies in my hands. Wouldn't that help you as well?

In Poland we have a rather well-functioning digital services platform. Tho, two weeks ago news outlets raised a small tantrum that our digital identity wallet application may be non-compliant with the upcoming EU standards. But as for now, once you log into the application (there are few ways - ID card with chip, 3rd party login by bank and so on), the session is kept for a year.
After that's done you can log on desktops by QR code or pass data from app to app.

mObywatel app tries to include all the essentials: from digital ID copy (identity confirm, validation for you and someone else) your DNI-equivalent protection (won't allow to process your personal information in some cases). There's healthcare services handling (prescriptions, but we also have a dedicated app), inbox/outbox for official matters, payments and taxes, section for car and vehicles (penalty points, accident reporting), environment (reporting accidents, air quality, flood alerts) and travel (rail tickets wallet, tips and warning for traveling destinations - atm it shows that Spain is on 4th level terrorist threat). Tbh, it's way better than used to be few years ago with complex login flow that could break midway.

It's all convenient stuff but older generations are already digitally marginalized and we may indeed head into the future where we won't be able to do anything without a smartphone, in both real and digital life.