Last I checked, not with StreetComplete. But the OSM wiki has a table of Android apps https://wiki.openstreetmap.org/wiki/Android which column "Record tracks" can be sorted by, to see which apps have that feature.
How I've done similar before is to record a GPS trace with an OsmAnd plugin, upload it to OSM servers, import it as an overlay in the web-based editor on desktop, and used that and satellite imagery as reference to draw in the missing trail.
In a pinch you can also record a trace and edit directly on it in the field with the Android app Vespucci, but its UX is clunky and much less friendly to new contributors than the web-based iD editor.
I always doubt statistics based on self-reporting, when there are such strong incentives not to be caught supporting the opposition. If you say the wrong thing, you may get prison, or very accidentally trip and tragically fall out of a window.
Jimmy Wales has been poked at with the question of whether he should call himself a founder or specifically co-founder for a long time, by right-wingers who think Wikipedia is too woke, and want to irritate and discredit him as much as possible, and instead raise up his co-founder Larry Sanger. Sanger has right-wing views and a habit of accusing any article as biased that doesn't praise Trump and fundamentalist Christian values, and takes these as proof that Wikipedia has a left lean.
The interview Wales walked out of was for his book tour. I imagine it's the umpteenth interview that week with the same question asked for the same transparently bad-faith reasons, trying to bend the interview away from his book and into right-wing conspiracy theory land.
I would have expected at least some consideration of public perception, given the extremely negative opinions many people hold about LLMs being trained on stolen data. Whether it's an ethical issue or a brand hazard depends on your opinions about that, but it's definitely at least one of those currently.
I use unwrap a lot, and my most frequent target is unwrapping the result of Mutex::lock. Most applications have no reasonable way to recover from lock poisoning, so if I were forced to write a match for each such use site to handle the error case, the handler would have no choice but to just call panic anyway. Which is equivalent to unwrap, but much more verbose.
Perhaps it needs a scarier name, like "assume_ok".
Such people should perhaps consider a ceramic-bladed knife. They stay sharp basically forever because the blade is extremely hard, with the downside that it's not repairable with ordinary equipment if chipped. But if the owner would never maintain their metal knife anyway, then it's not _really_ a downside.
Why does this stupid idea have to be killed so many times? Being watched constantly means living in fear, but seeing it almost become legally mandated practice over and over again is itself a form of living in fear. I'm so tired.
Cars break too, but roads for cars are typically constructed such that you won't go off a cliff or under a heavier vehicle like a train even if it happens. I believe GP's point is that cyclists' safety in failure scenarios is often not similarly accounted for.
Would you feel similarly if you went to a casino and won at roulette, only for the casino to claim that there was sand in the bearings or something and refuse to pay out your winnings?
Fully dynamic connectivity on general graphs comes to mind. https://en.m.wikipedia.org/wiki/Dynamic_connectivity (Graphs, with operations to connect and disconnect nodes, and to check whether two nodes are connected by some path.)
State of the art there is poly-logarithmic time worst case.
More than 0$, so definitely more than they're willing to lose in a Mexican court case that costs money and reputation, especially given the local courts are unlikely to rule in their favour.
Instead of each node storing the next- and previous-pointers separately, store a single pointer which is the XOR of the two. Which is obviously an invalid pointer. But when iterating, XOR the previous node's pointer with the combined pointer to get the next node's pointer, and so on. You can iterate this way in both directions. Feels illegal. :)
Run a memtest. Graphics cards usually crash badly when given invalid data, which can happen sporadically if you have bad RAM.
If memtest shows a specific memory region as failing, swap out sticks to check which it is, and buy a new one. (Or if you're on a tight budget, you can disable that region with kernel boot options.)
If memtest gives errors in lots of places, might be a bad overclock. Loosen timings or give it more voltage.