‹ BackHN Continuity

Thread

Avoiding the babbling-idiot failure in a time-triggered communication system

24 points · 6 comments · ronfriedhaber

Loading the complete thread in the background. This saved snapshot is available now. Refresh

  1. DonHopkins · · focus · HN ↗
    [delayed]
    1. bobson381 · · focus · HN ↗
      Thanks for posting this. Very GEB
      1. poslathian · · focus · HN ↗
        Seconded, great share
  2. ronfriedhaber · · focus · HN ↗
    Tangent, First stumbled upon this reading Enigma's work [1].

    [1] <a href="https:&#x2F;&#x2F;www.enigma.inc&#x2F;posts&#x2F;sts3215-servo-hacking" rel="nofollow">https:&#x2F;&#x2F;www.enigma.inc&#x2F;posts&#x2F;sts3215-servo-hacking

  3. captainbland · · focus · HN ↗
    We could all do with a bus guardian at times
  4. amingilani · · focus · HN ↗
    Like a time-out timer (TOT) on radios?

    &gt; When activated, the Time-out Timer starts counting the moment a user begins transmitting. If the transmission continues beyond a pre-set duration, the timer automatically cuts off the transmission. This mechanism compels users to be concise in their communication and relinquish the channel, allowing others the opportunity to transmit.

    — <a href="https:&#x2F;&#x2F;talkpod.com&#x2F;blogs&#x2F;two-way-radio-wiki&#x2F;what-is-time-out-timer" rel="nofollow">https:&#x2F;&#x2F;talkpod.com&#x2F;blogs&#x2F;two-way-radio-wiki&#x2F;what-is-time-ou...

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.