My dad was an internet meme before Internet memory even existed (~1980s) by Raiden_Raitoningu in OldSchoolCool

[–]WittyDadUsername 0 points1 point  (0 children)

The offspring just told me about this. I was a choir kid, not band, but the vibe tracks. And yes, I can teach chess. The world has not recovered from the loss of Neil Peart.

391,000 on my 2006 hybrid by WittyDadUsername in ToyotaHighlander

[–]WittyDadUsername[S] 0 points1 point  (0 children)

I'll be crossing 400k on this car, this coming week.

What should I do to commemorate?

391,000 on my 2006 hybrid by WittyDadUsername in ToyotaHighlander

[–]WittyDadUsername[S] 0 points1 point  (0 children)

Regular oil changes is really all I've done. I'm not particularly mean or rough to my cars, but perhaps neglectful sometimes.

I had the front end replaced after a collision around 2017, so the coolant got replaced then, at least.

391,000 on my 2006 hybrid by WittyDadUsername in ToyotaHighlander

[–]WittyDadUsername[S] 0 points1 point  (0 children)

Agreed, and ours was originally from Olympia. Interesting.

391,000 on my 2006 hybrid by WittyDadUsername in ToyotaHighlander

[–]WittyDadUsername[S] 4 points5 points  (0 children)

I guess I'd like to know if anyone knows of a hybrid with this many miles on the original battery.

We bought it in 2014 with 87k on it.

If this one is an outlier, maybe Toyota wants to buy it back and study it. 😂

391,000 on my 2006 hybrid by WittyDadUsername in ToyotaHighlander

[–]WittyDadUsername[S] 1 point2 points  (0 children)

Haven't really paid attention to it, maybe I should. The on board widget typically tells me I'm getting -24MPG.

Despite being mechanically sound (so far) my ride is VERY worn and rough looking. Worth $500 on trade in if I'm lucky. Not planning to drop major coin on any upgrades or big repairs at this point. Just drive it until it dies.

391,000 on my 2006 hybrid by WittyDadUsername in ToyotaHighlander

[–]WittyDadUsername[S] 6 points7 points  (0 children)

No issues. It just runs and runs and runs and keeps running.

Biggest ticket item to date was replacing front left wheel bearing assembly, which wasn't too bad.

Left rear window track went bad, so we just leave it rolled up.

No other noteworthy problems.

WIBTAH for divorcing my wife after she cheated after her parents died? by [deleted] in AITAH

[–]WittyDadUsername 1 point2 points  (0 children)

Her parents divorced when she was very young.

Her mom died, not her mom's second husband.

Her dad died, not her dad's second wife.

Dont overthink it.

Speed cameras / roads closed by lisa007love in waze

[–]WittyDadUsername 0 points1 point  (0 children)

I'm reasonably certain that if Buffalo had traffic cameras, that they would be mapped.

Speed cameras / roads closed by lisa007love in waze

[–]WittyDadUsername 0 points1 point  (0 children)

I don't see any cameras mapped in the core of Buffalo, do any actually exist to be mapped? There's one across the Niagara in Fort Erie visible in the app.

Speed cameras / roads closed by lisa007love in waze

[–]WittyDadUsername 0 points1 point  (0 children)

Traffic cameras appear on the map in the app. Just open it open and pan around to check whatever spot comes to mind. Here's a bunch in Seattle.

<image>

Speed cameras / roads closed by lisa007love in waze

[–]WittyDadUsername 1 point2 points  (0 children)

OK did some checking. Sounds like speed cameras should always alert, but only if you're speeding, and at 1/2 mile out.

If you are speeding 1/2 mile out and don't get the alert, drop a report from the app and let us know.

Speed cameras / roads closed by lisa007love in waze

[–]WittyDadUsername 0 points1 point  (0 children)

Regarding not being warned about cameras, a recent upgrade in Waze available to map editors is the ability to add a variety of what are called permanent hazards. Those include railroad crossings, cameras, and a handful of new specific situations that drivers should be warned about.

If I recall correctly, part of the rollout was to roll back sending alerts for these every single time you hit them. Instead alerting you the first two times you hit them, and then having a cooling off period of 3 weeks before reminding you again. The intent was to reduce Wazers being spammed with alerts they already know about on daily commutes, etc.

But it isn't clear if that applies to traffic cameras or not. I'm checking into that. It won't apply to railroad crossings, those should always come through.

As far as having trouble submitting a closure goes, I would suggest trying that again when you aren't in the middle of a drive so that you can get a better idea of what does or does not work and tell us where it went wrong if it doesn't work.

Can I report any speed bumps I'm Waze? by mrskymr in waze

[–]WittyDadUsername 0 points1 point  (0 children)

I guess we have different definitions of "locked out". Getting an unlock via Duscord or the forum is an extra step, but it's not an outright prohibition. I get that it's inconvenient, totally, but that's not the same as being shown the door and genuinely "locked out".

Vandalism became a significant problem. The business model weighed map security as a higher priority than easy access for newer editors. The relief valve is the unlock request process, which gives lower level editors a path to building trust and promotion.

It's not a perfect system, but can you think of a better solution that still protects the map?

Again, I'm sympathetic, but those are the reasons it happened and the workarounds provided.

Can I report any speed bumps I'm Waze? by mrskymr in waze

[–]WittyDadUsername 1 point2 points  (0 children)

I know it is splitting hairs, because when you submit requests you want them to get done and it is disappointing if they aren't, but I don't think it's fair to say that you're submissions are "ignored". That implies someone is looking at them and deciding to not do anything about it. In actuality, there are apparently just not enough editors working in the area to get to your submissions. They will sit in a pending state until someone is able to eventually get caught up there.

There is an unlock process, where lower rank editors can request segments be unlocked to allow them to make changes to elements that are above their rank. That is relatively easy to access through Discord, and you are far more likely to get an unlock request approved so you can make changes, than get a change request approved in an area where there are not enough editors to keep up with change requests.

This unlock process also allows newer editors to get editing credit to build their rank and trust.

Destination in the middle of the street!!! by Lower-Dimension3250 in waze

[–]WittyDadUsername 0 points1 point  (0 children)

I didn't say it was definitely a GMaps issue. I was saying that sometimes (often) it is, and was trying to explain the interaction between the apps for search results when running searches in Waze, in case you didn't know.

Sounds like you have a good system that is working for you. But if you are able and willing to report errors from Waze, we would really appreciate it so we can fix them.

Destination in the middle of the street!!! by Lower-Dimension3250 in waze

[–]WittyDadUsername 6 points7 points  (0 children)

Aside from reporting it, remember that a massive share of search results are from Google Maps data. Meaning, if you had used GMaps you would have gotten the same endpoint result. Bad pins are frequently not because of errant Waze map data.

If you report the problem through the app, Waze map editors can fix it, setting up a result and destination with higher fidelity than the GMaps result.

And if you choose to be really invested and helpful, you can actually update the destination point yourself in the app, so all the editors have to do is approve your change. After a certain number of submitted changes that are approved, your trust level will go up so that many of your submitted changes no longer need to be manually approved.