“If McDonald’s offered three free Big Macs for a DNA sample, there would be lines around the block.” - Bruce
I have no idea about the eye thing taking off. But I think your comment is very HN and a bit out-of-touch with regular people. What "you're seeing" is a bubble and not representative of the general population. The eye thing is a slow frog boil and it will be commonplace before you can blink.
Agent instruction files are code, though. And none of this is really workstation-specific, it is codebase-specific. Should each developer keep a nearly identical copy of CLAUDE.md? The instructions really aren't for a developer, they are for an LLM agent. In most cases (I'd imagine, anyway) the agentic instruction files must be in source control for them to even provide much value.
It's an LLM-webapp-builder, sure, but different from the rest! I have the LLM write python code when it needs to modify an HTML file for example (it'll use beautifulsoup; then I run the code: it parses the source into a data structure, modifies the data structure, and then outputs the resulting html).
It's also a marketplace where you can publish your llm-powered webapp, and earn $ on the token margins (I charge 2x token rates) when people use your site.
Related, I'm still upset at the lies told by landlords regarding phone number privacy in buzz-in intercoms. I've been told multiple times at multiple apartment buildings, "don't worry, while the system will call your phone when someone taps your entry code, your phone number won't be revealed". And then you sign the lease, get a delivery from Instacart in your new place, and find that your 'private' number is blasted out loud, heard a whole city block away, in a loud-ass DTMF tone sequence.
I'm interested in the idea that LLMs writing raw code and doing line-or-diff replacements will not be the future, but that having the LLMs modify the structure of the code may end up being the best.
Also, I think that building LLM-powered webapps should earn the dev per token call; so I've built a margin into token costs where the end user is charged 2x the provider's token costs, and then I get 20% of the remaining and the dev gets 80%.
There are like, billions of internet-connected barometers in the world that are not used in weather models. I don’t know if Acme has any of that in mind, but there is plenty of good reason for a weather app to collect data from phones. I know @counters may disagree with me, but I believe there are opportunities to improve short term forecast accuracy using data collected from phones.
Also, pretty much every day, all the apps and all the sites will tell me the incorrect current conditions at my location, much less the forecast. It’s 2026 damnit. Why doesn’t my phone know what the weather is outside right now?
I haven’t got the app yet, but I plan on it (gotta upgrade iOS first I think). Acme seems to have a lot of ideas I agree with, so, definitely following this.
One more thing. Weather apps have not been “solved”. Not even close. They all suck, there’s billions in untapped opportunity, and a stale existing market of bad solutions. People die all the time from severe weather. There is so much more work to be done in forecast accuracy and communication.
> I believe there are opportunities to improve short term forecast accuracy using data collected from phones.
Alright, fair point. That could be a reasonable use case.
But judging by their advertised "Community reports" feature, Acme doesn't seem to be doing this. And even if they did, this feature should be opt-in, and their privacy policy should only apply for those users.
> Also, pretty much every day, all the apps and all the sites will tell me the incorrect current conditions at my location, much less the forecast. It’s 2026 damnit. Why doesn’t my phone know what the weather is outside right now?
Have you tried looking out the window? What do you need hyper-local and minute-accurate forecasts for? If you need to know accurate current conditions get a thermometer and barometer. If you want it on your smartphone, then the app could show you live readings from your device, without sending the data anywhere.
Weather forecasts have always been an inexact science, and likely always will be. Our models have gotten better over time, and at this point I think that they're good enough. I only need to know the general temperature and likelihood of certain weather events a few days in advance, at most. If there's a chance of rain, I carry an umbrella just in case. If it's going to be cold, I pack a jacket.
Highly accurate weather prediction doesn't solve any practical problem for the average person. Hyping it up like it does only serves as marketing for companies that want to build a profitable business around it.
After thinking more about this, I don't think smartphones would even be good sources of ambient data that could improve forecasts.
Smartphones are personal computers. They spend most of their time in pockets and controlled indoor environments. This ambient data is of no use to anyone, which is why there's still a market for home weather stations, whose sensors are typically placed outside.
The barometer data is for sure noisy, and must be cleaned and quality controlled. But that is possible to do, has been for 10 years now (there are published papers and demo apps that can do it). For one, rate of change of atmospheric pressure is pretty much the same inside as out, your main challenge for the raw value to be correct is user elevation. That can be corrected in quality control as well.
Plenty of work has been done on this front, and it can be demonstrated that you can assimilate the smartphone pressures into weather models and get some good results. It is hard, of course, and I’m not sure personally how much better the forecasts get.
But it’s absolutely possible.
> Weather forecasts have always been an inexact science
Weather forecasting is anything but "an inexact science." It's extremely exact up to the limitations and assumptions you impose on your model due to resource constraints.
And yes - I assume that this is what you mean by "an inexact science." But still in 2026 I regularly meet people who think that weather forecasting is the same as astrology, completely ignorant of massive amount of physical scientific understanding that goes into it.
> Weather forecasting is anything but "an inexact science." It's extremely exact up to the limitations and assumptions you impose on your model due to resource constraints.
It's "extremely exact" but our models are not good enough. So... inexact?
The reality is that we don't have the technology to model the physical world with extreme accuracy. If we did, we would be able to predict the future, and not just weather events. The world's most powerful supercomputers can model atmospheric conditions pretty well, and they've certainly improved over time, but there are still a lot of variables unaccounted for.
This is why I think that ~90% accuracy for a few days in advance[1] is good enough for most people. A smartphone app won't miraculously make this better, no matter how pretty or "fun" it is.
> It's "extremely exact" but our models are not good enough. So... inexact?
That's not the common way that the phrase "inexact science" is used. All modeling involves approximations at some levels, but you wouldn't turn around and call it "inexact science."
> ... but there are still a lot of variables unaccounted for.
Such as... ?
This is the problem with throwing away colloquialisms like "inexact science." What, specifically, is a "variable" that is unaccounted for that would unlock improved forecast accuracy or to push thresholds closer to the predictability limits?
> This is why I think that ~90% accuracy for a few days in advance[1] is good enough for most people. A smartphone app won't miraculously make this better, no matter how pretty or "fun" it is.
I agree, which is why the other portions of your comment come off poorly.
reply