Why do you think you should be the one to make that decision for someone else?
More and more people are finding these things hovering outside their windows in urban environments, and as they become easier and easier to fly, people are flying into flight paths, dangerously over people and roadways, and in locations that should be obvious to avoid.
Chicago enacted strict drone ordinances to combat this after an explosion of "nosy drone sightings", and this wasn't pearl clutching, it was downright creepy behavior by the operators.
More recently, the FAA had to issue a warning about drone operators flying into the flight paths of planes on approach to O'Hare. People take their drone out to the lake and think everything's fine, but a lot of the lake is directly in those flight paths.
Especially in city centers, a drone is participating in a large and complex airspace, and it's more about ensuring drones continue to operate safely in that environment and less about making that decision for someone else.
If you fly a plane, you're transmitting ADS-B, because that is what is required to fly a plane safely. The same requirement is looking more and more necessary for drones.
With the current MOC methods, it's really just a way for law enforcement to seek out stuff that's flying in the extremely immediate (like <1km) vicinity.
My issue with RemoteID is that it's ALSO transmitting the _current_ physical location of the pilot. The pilot of a potentially very expensive piece of gear. That seems like a great way to get robbed. The rest of RemoteID is fine.
Seems like a bad implementation of a necessary thing.
Why do you think that what you do in public air space is private?
