Kyℓe Hensel

That's because of #3239 – you'll never see [that warning](https://github.com/openstreetmap/iD/pull/8727) again :) There are a number of other performance improvements that we could do for saving history, but because of...

I'm going to reopen this one so that we have 1 place to discuss future optimisations. Currently there are various comments spread across 5 different https://github.com/openstreetmap/iD/labels/wontfix issues.

Ready to merge :)

> Now for the upload, you might have multiple create/modify/delete blocks in random order, including repeating blocks for the same action. How would this work with your proposed format? If...

got it, I wonder if we actually need to support this behaviour in the new JSON upload endpoint. Since this is brand new, we have a (somewhat rare) opportunity to...

for completeness, another option that hasn't been mentioned yet is: ```jsonc { "osmChange": [ { "type": "create", "elements": [a, b, c] }, { "type": "delete", "elements": [d, e] }, {...

If we decide to get rid of the `create`/`update`/`delete` blocks, then there are two options (broadly speaking): 1. allow attributes to be specified some some elements only. Requires a nested...

should we transfer this issue to [openstreetmap-website](https://github.com/openstreetmap/openstreetmap-website)? iD doesn't define the CSP itself, it seems like [the nonce is defined over there](https://github.com/openstreetmap/openstreetmap-website/blame/737ae2c6fef3b2525bd1c4a2ca843cec14149383/config/initializers/content_security_policy.rb#L43) if I'm reading the code right

I think it would be worth checking with @thomersch first if the osmcal API can handle an additional 18,000 API requests per day[^1] everytime someone uploads a changeset with iD...

can you provide a bit more info please, perhaps using [one of the issue templates](https://github.com/openstreetmap/iD/issues/new/choose)? iD already uses icons from NSI everywhere except in the map-renderer itself.