miles@lemmy.world to backpacking@lemmy.ml · edit-21 year ago14,000 feet up, liability fears block access to iconic Colorado peaksplus-squarewww.washingtonpost.comexternal-linkmessage-square0fedilinkarrow-up11arrow-down10
arrow-up11arrow-down1external-link14,000 feet up, liability fears block access to iconic Colorado peaksplus-squarewww.washingtonpost.commiles@lemmy.world to backpacking@lemmy.ml · edit-21 year agomessage-square0fedilink
miles@lemmy.world to backpacking@lemmy.ml · edit-21 year agoHe lived to be outdoors, even in extremes like Death Valley. He died doing what he lovedplus-squarewww.latimes.comexternal-linkmessage-square0fedilinkarrow-up11arrow-down10
arrow-up11arrow-down1external-linkHe lived to be outdoors, even in extremes like Death Valley. He died doing what he lovedplus-squarewww.latimes.commiles@lemmy.world to backpacking@lemmy.ml · edit-21 year agomessage-square0fedilink
minus-squaremiles@lemmy.worldtoLemmy.World Announcements@lemmy.world•Rules of Use for Botslinkfedilinkarrow-up0·1 year agoGood stuff 👍 Right now you’re using “can” and “should” which are somewhat vague. What happens if bots don’t do something they should? Consider clarifying requirements using the following RFC-style language: “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL”. ref: https://www.rfc-editor.org/rfc/rfc2119 linkfedilink
Good stuff 👍 Right now you’re using “can” and “should” which are somewhat vague. What happens if bots don’t do something they should?
Consider clarifying requirements using the following RFC-style language: “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL”.
ref: https://www.rfc-editor.org/rfc/rfc2119