Counter countermeasures

I'm pretty sure the answer to this question is, "no way, Jose," but I figured I'd ask anyway. When I took a break from SL 5 months ago, there was no way to prevent this; perhaps there has been an innovation since my hiatus.

Q: is there any convenient way to counter or even detect when a scripted object is llPushObject'ing or llApplyImpulse'ing you?

My particular vexation with this is when I'm editing a vehicle in the sandboxen and I'll:
1. hop into the vehicle
2. the vehicle enables physics to unpin itself and begin moving
3. orbited by someone's autopusher attachment

Frankly, it'd just be nice to know who is doing it; usually a quick IM to the owner fixes things right up.

It'd be great to have a scripted attachment that llOwnerSays, "hey, you just got orbited by XXXXXX XXXXXX." Apparently the abuse detector doesn't catch this kind of thing. By the time my client crashes and I relog and pick up the pieces, I'm worried that I won't be kind to the person (unwittingly) orbiting vehicle users around them.

Any suggestions or am I pipedreaming?

No, there's no way to detect a push apart from to look at your own position. If you've moved 10,000m in 0.1s, you've probably been pushed. Setting something on a timer to check for that sort of thing, if so move you back to your last known position, if not update your last known position, is the way to go to protect there. Using warppos, you can be back where you were in an instant.

I didn't think WarpPos worked above 768m. Above that, I thought you had to use llPushObject or llApplyImpulse.

Actually, yeah, I think you're right there, I was thinking of flatter pushes.

Ah good. I was imagining WarpPos/pusher loops where the warper tried to plunk me back next to the pusher. Nasty business, that.

Also, Ordinal, many kudos to you for your trolley build in Caledon.