> In the case of damage, due to flooding for instance, Cárdenas explains that the Magpie would likely not be found liable. "The river doesn't commit intentional damage, therefore it cannot be sued," she said, pointing out that those who build in known flood zones are also aware of the risks.
Intent is not a condition for successfully suing someone but realistically this entire thing is mostly a joke anyway so might as well make up the entire thing as they go.
An excerpt:
> The Clamzorians are animists. They believe every rock and tree and river has its own spirit. And those spirits are legal people. This on its own is not unusual – even New Zealand gives rivers legal personhood. But in Clamzoria, if a flood destroys your home, you sue the river.
But that's ~$20/mo and a moderate annoyance, so for now mostly just fingers crossed that eventually everywhere that matters will allow me to switch fully to authentication apps and hardware keys.
A separate number for each account might help. Maybe.
For tracing suspended Futures, I've worked on a few approaches:
1. If you don't mind annotating your async functions, you can use the async-backtrace crate, which provides pretty-printing out-of-the-box: https://crates.io/crates/async-backtrace
2. If you are already using the `tracing` ecosystem, you can use the tracing-causality crate (it doesn't yet include pretty-printing, but it's not too hard to add that on): https://crates.io/crates/tracing-causality
3. If you are only supporting Linux (and maybe MacOS) and you aren't stripping away debuginfo from your binaries, you can build atop the deflect crate (https://jack.wrenn.fyi/blog/deflect/). If your `Future` purely consists of `async` blocks, Tyler Mandry's reflection based approach works well: https://github.com/tmandry/rust-dbg-ext/tree/async-backtrace...
For analyzing stack traces of active futures, I'm not aware of any good ways to reliably filter out irrelevant frames (e.g., frames from the runtime).
It's a painful problem to actually make it happen because cities are all about network effects (you live there because people you know are there, etc). I just think it would be very appealing to me to live in a city that is optimized for biking + walking instead of having to own a car.
If I were ever to get rich, this would be an area I'd throw funding at to figure out. Is anybody aware of any research in this area?
I'm optimistic that I can make strides closer to home. I have only ever lived in places that predated the advent of automobiles. At one time, they were very accessible via walking, biking, rail, and trolley. So, last fall, when I moved back to Providence, I made it my mission to get involved in local transit activism. It's been a great source of social and civic satisfaction, and I intend to repeat the exercise when I move again next Fall.
It feels like positive change is (slowly) happening.