• Stantana@lemmy.sambands.net
    link
    fedilink
    English
    arrow-up
    5
    ·
    1 year ago

    Crowdsourcing is nice but I’m not happy about the “don’t mark temporary hindrances” thing in OSM, some of them last for months and I can’t warn others. Sometimes I even forget the hindrance myself and feel real unsmart dumb.

    • paraphrand@lemmy.world
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 year ago

      That seems like a tricky one to moderate. I’m sure they are worried about things being set and forgotten and never repealed.

      • Stantana@lemmy.sambands.net
        link
        fedilink
        English
        arrow-up
        8
        ·
        1 year ago

        I understand why, but I also have examples of compromises;

        • Set a marker, it expires after a certain timeperiod. Users “validate” that the hindrance is still there, resetting the timer.
        • Set a marker, “Hindrance here at 2023-11-03”
          • “Expected end”
            • Today
            • This week
            • This month
            • Later (Marked hindrance disappear some time after “Expected end” if no users validate that it’s still there, with new “Expected end”.

        Just some thoughts.

          • Stantana@lemmy.sambands.net
            link
            fedilink
            English
            arrow-up
            5
            ·
            1 year ago

            users with good intent

            Oh right, it could easily be abused by traffic trolls. Didn’t cross my mind, sometimes my faith in other people are unreasonably high.

            Perhaps some sort of validation system, if two users report the same temporary hindrance? TBH I can’t be bothered to work out a fool-proof system for a hypothetical solution I doubt will ever be implemented hah.