Worth noting however that they are starting to introduce rate limits lately so you might struggle to run multiple concurrent sessions, though this is very inconsistent for me. Some days I can run 3-4 sessions concurrently all day, other times I get rate limited if I run one non-stop..

The simplicity of extending pi is in itself addictive, but even in its raw form it does the job well.

Before finding pi I had written a lot of custom stuff on top of all the provider specific CLI tools (codex, Claude, cursor-agent, Gemini) - but now I don’t have to anymore (except if I want to use my anthropic sub, which I will now cancel for that exact reason)

I've been building https://photoweather.app because I never end up having time to look at weather forecasts, which means I also don't go out with my camera enough since outdoor photography is quite a weather dependent activity.. so I'm trying to turn this around by having the app tell me when and where I could be photographing instead.

It's a bit of a challenge for sure, weather forecasts are not always the most reliable, not to mention learning enough about weather to forecast photographic opportunities.. but it's also been really enjoyable to finally build something real and something that I myself actually use all the time.

A year and a half or something later.. I recently started a project of my own trying to bring all "weather dependent" photo opportunities together in one place, if you wouldn't mind I would be happy to experiment with bringing Sunsethue data to https://photoweather.app - your prediction model is certainly a lot more sophisticated than mine and it would be very cool to offer that

And a closed beta (Google requirement) test for Play Store that could very much use more testers, DM me if interested (having more testers would really help out)

You define rules like: `aurora_quality > 60 AND cloud_cover < 20% AND moon_below_horizon` `fog_prob > 70% AND within 30min of sunrise AND wind < 5 mph`

When a rule matches, you get an email and/or an iCal event. The iCal feed is the part I am maybe most proud of: subscribe once and upcoming "shoot windows" show up in your calendar.

One example that made me sure this wasn't just a toy: last October it alerted "clear skies + no moon + strong aurora" and I drove to a nearby high spot in Helsinki. Ended up catching aurora and Comet C/2025 A6 (Lemmon) in one frame: https://reddit.com/r/Finland/comments/1obc5nz/

Not my best photo ever, but probably the most unique and memorable, and I'll continue to remember my real-life "photoweather actually works" moment through it.

A few things that differentiates this from your average weather app:

Spatial sampling A single forecast coordinate often isn't representative of what you'll actually see. So for many scores I sample 24 points around the location (8 directions × 3 distances). Rainbow probability is a good example – it checks for rain in the antisolar direction and clear sky toward the sun.

Derived scores Photography-specific scores like fog probability use actual meteorology: dewpoint spread, vapor pressure deficit, with guard clauses (wind >6m/s disperses fog, so score drops to zero).

Data / stack Open-Meteo as the primary model; GFS for multi-point sampling and cross-checks; GEFS for ensemble clouds; GFS Wave for sea conditions; NOAA OVATION + SWPC/Kp for aurora; CAMS aerosols. FastAPI + Postgres + Celery/Redis + React/TypeScript.

Free tier is usable but tuned for low running cost; paid unlocks mainly more locations and rules, more specialized weather data and faster refreshes.

Landing page: https://photoweather.app | Demo dashboard: https://app.photoweather.app/demo/live-demo

Would love to hear feedback, especially things like:

Would you actually use this? Does the UI/UX make sense (I feel a bit blinded by building+being a user at the same time)? Is there anything that would make it more useful/usable for you?

Comments URL: https://news.ycombinator.com/item?id=46453725

Points: 4

# Comments: 2