It doesn't seem to be in their tracker. Mapillary had a similar problem, it turns out that the camera API was updated to provide the orientation sensor orientation and they were using the older API on a phone with a rotated sensor.
Yes, most all of these were produced with an early beta of the apps. Has since been fixed. There's still a known issue where images appear mirrored in OSV when using certain Android phones, https://github.com/openstreetview/android/issues/3
> ...regardless of whether M$ accepts the pull request or not
They've already said that they won't accept the pull request, so...
> well your fork will still have the feature...
...we're left with what will potentially be a sea of forks, with no clear "best fork". Some might say that this isn't a big deal, but it is a significant point of friction.
I'm sorry if this comes through as offensive, but I would very much like to see all your points and research about the subject of this matter condensed into a single concise blog post and submitted to HN (if you've not already done so) instead of reading it from sporadic replies throughout the comments section of the related article(s).
as joshschreuder said, you can make your own filter. ublock orign also has a interactive element selector which can be used to hide particular DOM elements. Useful for hiding annoying stuff that may not be included in one of the filters
