From CBP's own website[1], emphasis is mine:

    An immigrant visa (IV) is issued to a foreign national wishing to live permanently in the United States.

    A nonimmigrant visa (NIV) is issued to a foreign national with permanent residence outside the United States but wishes to be in the United States on a temporary basis for tourism, medical treatment, *business,  temporary work, or study*, as examples. Note: There are more than 20 different categories of nonimmigrant visa classifications.

I'll move on to other parts soon, like the Bay Area.

The next thing I’d like to do is categorize some of the plants that are ideal for foundation planting (water management, vertical taproots) or curb islands (between sidewalks & streets).

Thanks again for the suggestion. It’ll take some refining but I also included nearby cities so it’s easier to get a sense of scale and proximity.

Level III/IV Maps are here: https://www.epa.gov/eco-research/level-iii-and-iv-ecoregions...

At the very least I'll make sure each region page links to this given it's the source that determines what species are shown.

The most fun I had with Indigene was when I decided to add French ecoregions so my parents could use the app too. Most of the work is in this PR where I used a recently published study’s plant host species data to offer ecosystem value/services metrics since the Tallamy data doesn’t cover that: https://github.com/olivierlacan/indigene/pull/53

That stuff reignitated the kind of deep data hunt fever I haven’t had since my COVID Tracking Project days when I was finding random ArcGIS dashboards and extracting data from their JSON calls to find some reliable case data.

I’m bummed I didn’t find your project before. I kept looking for something when I moved from Florida to Washington after converting my entire yard there. Having to learn a whole new ecoregion was rough and it made me think the barrier should be drastically lower for people who aren’t as motivated.

On the financial opportunity side, I hoped for a while that there may be a way to align our best interest as a species (and our ecosystem) with what our modern societies value but the last decade has made it clear to me that neither governments nor private enterprise are capable to remain as focused as they need to be. Plus leveraging worldwide public-funded science to make a living seems a bit odd if I can instead use my engineering expertise to not require unnecessary waste of resources (servers, more LLM tokens, etc.) as the ecosystem rapidly degrades.

So I take this feedback to heart and just like with the (sourced & generated) French localization I’m working my way through validating everything. This is another benefit of the project being entirely public, you can see precisely in the repo what I did and didn’t think to do in order to ensure accuracy.

When it comes to prose & style, I’ve set some clear accessibility goals in the agent config, and I’ve rewritten some things but it can be hard to fight the needless verbosity of LLMs at times.

I would deeply appreciate if you took the time to send a PR for any kind of improvement or addition). Thanks in advance.

So, mini show HN: https://indigene.app is a browser-only, offline & mobile-friendly, no account, no ads, open source tool to help you find native plants that would thrive exactly where you are. I've tried to make it as thoroughly sourced as possible but focus heavily on folks that have less experience with gardening and native plants in general.

I've been adding coverage to a handful of US and French ecoregions for now (what I know) and you can already do plant lookups by GPS, postal code, and ecoregion). The app will help you identify you spot, sun, soil, and specific ecosystem support goals (wildlife, birds, erosion or runoff control, growth) and offer a sortable list you can fine-tune with requirements (max height/width, no thorns, pet safe, spread, zero watering, etc.).

There's a lot more in there I've wanted for years like bloom windows, host species counts, dependent native wildlife, growth-over-time charts, propagation tips, and tons of sourced references that overlap with a lot of the resources Joey Santore and other native plant folks reference.

None of this replaces useful tools like iNaturalist whose excellent open API I use to show what native plants look like in Indigene, but hopefully it encourages folks who have the means and the time to start rebuilding local ecosystems we've neglected or actively destroyed.

PS: because I can't help it, the app has detailed release notes gendered from its changelog at https://indigene.app/release-notes/. It also takes privacy & safety very seriously: https://indigene.app/privacy

I've had to contend with Conventional Commits both in the OSS world and at work as it proliferated from what seemed to me like robotic adoption by folks who were even loosely associated with the Angular ecosystem (remember that?).

I've always had a stance with KAC that folks trying to automate changelog creation (prior to LLM rise, mind you) were focusing on the wrong thing. I still think there's a fundamental difference in focus between what you write in a git commit and what you present in a changelog.

I know there are fundamental philosophical differences for folks who were used to HISTORY vs. NEWS vs. CHANGELOG but with the growing adoption of KAC-like CHANGELOG.md files and Release Notes (often not synonymous) I think we're thankfully past the weird era were maintainers dumped raw git log ranges between two tags and called that a changelog. I'm sure some still do it. But that's what Conventional Commits tries to replicate.

What's really odd to me is that this assumes (broadly) that every single commit in a repository is relevant to the eventual version release changelog (or release notes). Even if you assume some CC types get filtered and deprioritized from generated changelogs by some tools, it's still a huge miss on what communicating about a release typically means: these change likely matter to you as a package dependent or direct user, while others were omitted for good reason.

I'm trying to articulate that much more clearly in KAC 2.0 because there's a fundamental paradigm shift when a robot can now analyze recent work (yours or theirs) and craft changelog entries that appropriately shift the audience perspective from "git message for me/us in the future to understand this change" to "changelog entry for you/them to know what this group of changes means".

[0]: https://keepachangelog.com

[1]: https://github.com/olivierlacan/keep-a-changelog/pull/600 if anyone's curious and wants to get involved

From working on RubyGems.org a long time ago I vaguely remember that the metadata extracted from the gemspec is version-specific. So if you add a new native_extension boolean you'd have to artificially reprocess those previously published gemspecs to change the metadata for all past versions.

Being able to mutate metadata for past versions is dangerous enough that I'd be surprised it's allowed or even possible. So that might not even be something Aaron considered here for that reason. That said, it seems reasonable to me to suggest this improvement going forward to make unpacking the gem unnecessary to know whether it'll affect installation order.

https://www.france24.com/en/france/20251228-bardot-leaves-co...

Many outlets — including this CNN piece which is making the passive voice work real hard to make her awfulness about other’s perception of it — are slinging hagiographies as if death absolves all.

It's shocking to me how good Roborock mop-vacuums are for example, Eufy vacuums are nice as well. They still run into unavoidable issues, but they're: much quieter even at their highest setting; show you how they map out the space; allow you to easily customize routes or focus on specific rooms; do a shockingly good job at self-emptying; and best of all you don't have to rescue them from the exact same sliding door track every single time you run them.

Reading memories from the people Noah impacted in his life feels like a good way to understand the kind of person he was.

It's an underused treasure, however simplistic the UI may be.

See: https://www.nhc.noaa.gov/refresh/graphics_ep4+shtml/204534.s...

You can find individual static maps (sadly very low resolution) here as well for Hurricane Hilary: https://www.nhc.noaa.gov/graphics_ep4.shtml?start#contents

This kind of return on ultra flexible accounts is basically unheard of in most of Europe in recent memory as far as I know (born & lived in Europe as recently as 2019). What you describe are called Certificate of Deposit (CDs) in the U.S. and you can get 5.50% for those in August 2023 [1].

[1]: https://www.nerdwallet.com/best/banking/cd-rates

John Carmack is a very intelligent person who can teach you a lot about many extremely complex engineering-related matters.

Applying his advice on health and work-life balance without a full understanding of the many variables that skew his perspective and his own daily life is probably a bad idea.

Expertise is not automatically domain-transferable. Anyone claiming otherwise is suffering from hubris, or star-struck.