Editing software could be generally aware of high and low density locales and advise accordingly. And it could subdivide a large request into smaller ones. But the JOSM developers prefer to offer a closer-to-the-API experience.

[0] https://wiki.openstreetmap.org/wiki/API_v0.6#Retrieving_map_...

I'm an OSM mapper & enjoy linking mapped benches to their profiles on OpenBenches. It gets hairy, though, when a single bench features multiple memorial plaques. Wonder if you'd consider revising your data model to permit multiple inscriptions per bench?

https://xkcd.com/548/

Notification of incoming texts was the only problem. I jailbroke the thing and started trying to schedule network requests, thinking I'd add some kind of new message counter on the home screen. This proved hard. But it occurred to me that the best place for the counter would be right next to the Kindle's device name, at the top of the screen. And the device name could be updated from her Amazon account.

So I automated a web browser on the home server to log into Amazon and update the device name to "My Kindle (x)" where x was the number of unread Google Voice texts. The Kindle would update the name on the home screen in less than a minute. This worked for years!

(Eventually that Kindle was stolen. I wanted to update its name to something foul but the device disappeared from her account too quickly.)

Disassembling my first junk phone and playing with the rotary relay was even more fun.

But the best was learning to dial numbers by manually pulsing the switch on the handset cradle. Timing was tricky but luckily there was some leeway. (And it helped that phone numbers were shorter then.)

The opposite process also happens, though... not just a 3- and 4-story residential buildings demolished for large residential towers (plenty of that in NYC) but single-family brownstones carved up into smaller dwelling units.

The map caption "Conversions Have Erased Some Gains in NYC's Housing Stock" would make a less deceptive headline. The map shows data from a defined timespan ("between 2010 and 2021") and shows that there's not a single community district that hasn't added housing units. The headline, meanwhile, refers to a vague "70-plus years" timeframe. That's long enough that you could probably find hundreds of buildings that have bounced between single- and multi-family several times.

And in fact the underlying research characterizes any building that was ever recorded as multifamily and currently isn't as a "loss." I fear it risks romanticizing the 20th century's cramped tenements.

(And again, just to be clear, I find conversion of viable multifamily buildings into mansions generally repugnant.)

Talent agencies will negotiate training rights fees in bulk for popular content creators, who will get a small trickle of income from LLM providers, paid by a fee line-itemed into the API cost. Indie creators' training rights will be violated willy-nilly, as they are now. Large for-profit LLMs suspected or proven as training rights violators will be shamed and/or sued. Indie LLMs will go under the radar.

And I agree with the author that the design of Bing Map Builder looks problematic. The biggest problem being that it's segregating its contributors from the general OSM population in the name of "privacy."

And also bring a waterproof paper map because it's lighter, easier to read, more resilient, and more fun.

My assumption is that these kiosks log all wifi and bluetooth traffic from nearby persons and vehicles, and USB device IDs of anything plugged in for charging. And of course the new ones will be logging 5G signals as well. Maybe there's not yet a centralized effort to coordinate these logs with the camera feeds to map people's physical appearance to their electronic footprints, but I can't imagine it isn't somewhere on the roadmap.

(Maybe better described as feral apples? Old orchards with trees unpruned for decades.)