Admin of lemmy.blahaj.zone

I can also be found on the microblog fediverse at @ada@blahaj.zone or on matrix at @ada:chat.blahaj.zone

  • 10 Posts
  • 315 Comments
Joined 2 years ago
cake
Cake day: January 2nd, 2023

help-circle




  • Ada@lemmy.blahaj.zonetoFuck Cars@lemmy.worldInsanity
    link
    fedilink
    English
    arrow-up
    8
    ·
    3 days ago

    Our biggest cities normally have bus and train. About half of them have some sort of light rail/tram equivalent too. The coverage isn’t completely comprehensive, so it’s possible to find suburbs that don’t have great coverage, but by and large, it’s pretty good. Footpaths and bicycle paths are common too. The cycling infrastructure is often gappy, so you on commutes etc, you can find yourself navigating spaces without dedicated cycling infrastructure, but generally, you can get a good portion of a cycle commute on dedicated bike spaces. The only roads without a pedestrian corridor of some sort are generally major highways

    In our smaller and medium cities, the trains are normally inter city, not local, so they’re not so much use as public transport, but there are generally buses, though with less coverage. Good pedestrian infrastructure even in smaller cities though. It’s harder to survive in smaller cities without a car, but possible.

    Once you get out of smaller cities and in to towns and villages though, it gets harder again.
















  • So, in its current form, lemmy sends federation packets in serial form. It can send them to multiple instances in parallel, but the feed between any two given instances is serial.

    And serial means that the second packet doesn’t get sent until the first packet has been processed. Add in geographic latency, which is relevant at multiple steps of resolving any given AP packet, which adds to the per packet processing time, and now, lemmy.world is producing packets faster than it’s possible for a geographically remote instance to process them, no matter what hardware they’re running on.

    The problem would be resolved with parallel sending, but that’s not currently a thing that lemmy allows for, and apparently, is not trivial to implement either.