The Post Ninja

  • 0 Posts
  • 70 Comments
Joined 1 year ago
cake
Cake day: July 8th, 2023

help-circle

  • Lots of things contribute to this. Vehicle weight (extra stress on the tires), wheel alignment (toe-in/out causes scrubbing which causes more wear), unmaintained suspensions (worn out shocks, struts and bushings causing the above), burnouts (obviously, but, even in winter being the guy doing a burnout on summer tires while trying to get up an icy hill or across the intersection still counts), tire compound, road design, and driving style. If we had more cargo trains doing logi instead of long haul trucks we could probably cut down on a lot of pollution both in exhaust particles and tire particles.










  • Those cameras end up costing the city more than the accidents they don’t prevent. What happens is, there are less red light crossing collisions, and more rear-end collisions. Eventually, you have less red light runners to ticket, but that turns the red light camera into an expensive cost - at least $4000/mo for each camera. You have to make more than that at each stop light to justify the camera.

    The real solution is to make sure the yellow light is set with proper timing for that road. A yellow too short for the intersection increases red light running and potential for rear end collisions. But if you did that, then you won’t make anything on red light tickets, because no one would run the red light.

    So the real problem is trying to budget the city based on criminal activity - you are effectively requiring a certain minimum level of crime to balance the books.







  • DHCP, when set up properly, makes for less work. Reservations will have the DHCP server hand out the same IP to the same hardware (MAC address) when it asks. If you have a device that is from the dinosaur age that doesn’t play nice with DHCP, then make sure you give it an address that is outside the DHCP range on the same subnet. ex: Some home routers use 192.168.1.100 to 192.168.1.200 as the dhcp range. Setting anything from 192.168.1.1 (or 2 if the router is on 1) to 192.168.1.99 is fine, as is 192.168.1.201-192.168.1.254 (or 253 if the router is on 254). However, by setting static ips, you have to remember those ips specifically to interconnect devices on the lan, whereas reserving via dhcp allows you to use local dns resolution to connect to devices via their hostname instead. In additon, you run the risk of ip conflicts from forgetting which device has what ip in an increasingly complex system, and if you change internet providers or routers, you have a lot of extra work to do to fix the network settings to get those static ips to connect.

    Alternately, just use the link-local ipv6 address to interconnect on the lan. That doesn’t change on most devices, as it is based on the MAC address, and is always reachable on the lan.