Yikes. Street lighting is one of the most important safety improvements, especially for people walking, as most pedestrian deaths due to drivers occur at night.
https://safety.fhwa.dot.gov/provencountermeasures/lighting.c...
Of course, if we weren't so dependent on cars to do literally everything this wouldn't be the case, and we could safely get rid of a lot of street lighting.
Can’t even change the name servers, since that’s not configurable with cloudflare.
And I can’t move the domain out of cloudflare so I can change nameservers for 60 days because I just registered the domain…
Support very unhelpful, situation sucks.
You can do unique things like offer a trial period without syncing (database wholly in browser), which allows for ridiculously quick onboarding. And then when the user signs up for a paid plan, you just hook up CouchDB and the data syncs right on over.
The sync mechanism works so damn well. It's really cool how easy it is to implement a Google Docs-like sync mechanism with conflict resolution baked in.
I'd like to see an invite-based signup option like Mastodon, but other than that, it's a nice roadmap!
Edit: Created an idea post: https://ideas.joinpeertube.org/posts/139/invite-links-to-cre...
I don't think so. Obviously, the signal heads would have to be placed in a certain way that the MUTCD also prohibits in order to ensure near-side signals are easy and prominent when stopped at the stop bar (for example, minimum signal head distance from ground).
On the contrary, I actually think the MUTCD enforced far side signals create dangerous situations where certain signage, like "no turn on red" is less visible, especially on arterials where most traffic deaths and severe injury occur, because the signage is literally 140 ft away on the opposite side of the intersection on the far-side signal head monopole.
140 ft is very far for any signage placed at this distance when the driver is stopped at the stop bar, especially if you're not specifically looking/familiar with the area.
I was actually hit by someone driving a month ago on a multi use path because a driver turned right on red, despite not not being allowed. I believe that signal head placement led to this, because the no turn on red signage is very hard to see here (again, 140 ft away).
This is in contrast with the Netherlands, for example, which their overhead, near-side signal heads are only 20-30 ft away from the driver, very prominent and easy to see out of the windshield, and any signage next to the signal would be extremely prominent, despite the intersection size being similar (140 ft). NL obviously doesn't allow turns on red in the first place, but that's a whole other discussion...
Sorry I don't have photo examples on this computer atm. But this is something I've been discussing with local city engineers. It's a recurring problem, and they're aware of it, but any solution has to work around the MUTCD.
I do agree with you that signals are incredibly inefficient and ideally we would be getting rid of them wherever possible-
> “Traffic signals are the most mindless and wasteful thing Americans routinely install to manage traffic. Removing nearly all of them within cities would improve our transportation systems and overall quality of life.”
https://gettingaroundsac.blog/2022/03/16/too-many-traffic-si...
My largest personal pet peeves with the MTUCD is the requirement for far side signal heads. Far side signal heads cause crosswalk encroachment. If signals were near side only like in EU, crosswalk encroachment would be impossible because you lose sight of the signal head.
https://streets.mn/2021/04/30/thinking-outside-the-pedestria...
If you check out my second link in my first comment from NACTO, near the bottom there is a table of various cities and their specific issues with the MUTCD. Mine (Madison, WI) is here: https://www.regulations.gov/comment/FHWA-2020-0001-0258
It could even be argued that the MUTCD is awful for driving in an urban area. MUTCD designs streets similarly to rural highways, and this can create conditions where people speed when they need to be driving slowly, because the design of the street doesn't reflect the speed the sign says you need to be driving.
The MUTCD needs a different approach to urban streets. One that creates an environment where making a mistake doesn't lead to death. One where the design of the street reflects the posted speed limit. It will make the experience better for everyone.
https://americawalks.org/how-the-mutcd-creates-unsafe-condit...
https://nacto.org/program/modernizing-federal-standards/
https://www.bloomberg.com/news/articles/2021-05-05/it-s-time...
Earlier today, a number of people I know have been spammed via GitHub issues and discussions, using @-mentions. Push notifications and emails sent. Very annoying because the report process for spamming on GitHub is not that quick.
Flying my paramotor is one of the things I love to do in my free time, and this project (weather report for paramotor pilots) is the result of that!
Also open source https://github.com/aeharding/ppg.report
For example, in SFSafariViewController there is no “add to home screen” button in the share menu, but in actual safari there is. Despite them both being web view experiences controlled entirely by Apple.
(And you can’t detect SFSafariViewController vs Safari as a web app, so good luck onboarding users for your PWA.)
For example, in SFSafariViewController there is no “add to home screen” button, but in actual safari there is. Despite them both being web view experiences controlled entirely by Apple.
(And you can’t detect SFSafariViewController vs Safari as a web app, so good luck onboarding users for your PWA.)