Based on a post elsewhere from the EWG, I’d suggest that getting an update from them as to what the current situation actually is is probably the way forward. I’d suggest asking:
Are they managing the communications with Microsoft, or is it individual editor authors, or something else?
Do we/they know whether what JOSM users are seeing is a “quota” issue or a “brownout” one (both have been suggested)?
Do we/they know why the “no tiles displayed” issue only affects JOSM but not iD, P3, Vespucci (for me at least - based on my testing just now)**
It’s possible that they may not be able to give complete answers to all these, but a yes.no answer to “are they owning the problem” should be possible.
** For completeness, I’d agree with this previous post and do see “some issues” (odd messages etc.) but I personally do see Bing imagery everywhere but JOSM (in the UK, over the same UK BT-provided IP address).
We do have a coordinated communication with Microsoft. Two weeks ago we asked if ok for all OSM editors to uses the key used by iD, as that account has a a different limit, and should be good until 2028. They have not yet responded. I just pinged on the thread now to see if we can make that move.
I can jump in to help with that. I will check if the ID key is ok to be used for JOSM. Send me a message who did you try to contact so I can include them into conversation
Just to be clear on this: this is an extremely bad idea, not only does it amount to simply kicking the can, it actively makes things worse. Any issues (and as you are not supporting the migration to Microsofts new service, all the systematic issues with the service will remain) will effect all applications using that key.
So I guess we have no choice than to suck up and provide MS with our credit card details (and phone numbers).
I have a have a hard time believing Microsoft will stop supporting one of the biggest tools to edit OSM. I think it just needs to reach the right person at Microsoft to fix the issue or come up with a solution to migrate to the new Azure service.
Nobody has implied that Microsoft is stopping support, though now that you mention it, their permission to use the Bing imagery is specific to that service and should be updated.
The problem is more that
we have to migrate, aka work (offset by the hope that going forward we can delete a lot of custom code).
sharing keys is bad (Azure might support generating multiple keys with restricted scope, so this is potentially solvable).
setting up individual Azure accounts (the alternative to the EWG doing something) requires developers to expose personal data to Microsoft and assume the financial risk.
The thing that is clear since the demise of Maxars offering (see the bit above about keys) there is a very unhealthy dependency on one imagery source at least in some regions.
Simon
PS: I started with OSM just a bit before we had access to Bing and any reasonable global high quality imagery, it is completely possible to map without imagery, today even more so then back then.