Thanks for your answer and thoughts.
Regarding the traffic reports, I do find your arguments a little contradictory. You say that reporting good traffic would have no effect on the routing, but then reporting bad traffic doesn't either. So my question would be: why have one and not the other. If they are both useless, get rid of both.
My thought on this is that you can visually see what roads have good traffic and what roads don't. In the ideal world, Waze takes care of that and paints the roads accordingly. However, a lot of times I find that Waze only finds out a road is blocked when I'm stuck in it!
The good or bad reporting would only have a visual aid to drivers - that's all. If you have one, then why not have the other?
Regarding educating users, that would be great. I just find it shouldn't be the rule and will simply never reach a big enough audience. Ever seen Steve Jobs tell people they have to read the manual? No, he makes it so intuitive that people just know how to use it. Even my 3 year old daughter is comfortable using am iPad. Waze should be the same. If people are doing something wrong because they didn't read the manual, in my opinion, the programmers are wrong, not the user.
As for the speed camera, I totally agree to keep things simple and not too many options. But, as explained above, people are not using it right and, as it is, it brings less value to the users who end up not being warned about mobile radars.
Anyway, just my two cents...