Researched by Robert Quattlebaum darco@deepdarc.com.
Last updated 2020-02-03.
use futures::prelude::*; | |
use pin_utils::unsafe_pinned; | |
use std::ops::Deref; | |
use std::pin::Pin; | |
use std::sync::Arc; | |
/// A container for a single object with lifetime that is bound to that of an `Arc`. | |
/// This is useful for passing around boxed futures that have a lifetime that is limited | |
/// to that of the object that created it. | |
/// |
/// Demonstration of compile-time key-value type safety. | |
/// | |
/// This program demonstrates how you use Rust generics to encode type | |
/// information into the keys for a key-value store. This allows for | |
/// type-safe access to data in the store, preventing things like writing | |
/// strings to keys that should only contain integers. Attempting to | |
/// do so results in a compile-time error. | |
/// | |
/// The example code is at the top of this file, the implementation details | |
/// are below the example. |
/// Demonstration of a way to do polymorphic property lookup of standardized | |
/// collections of properties via simple traits and getter methods. This | |
/// approach could be extended to do things like fetch a list of the supported | |
/// keys, or expose aritrary traits via a property interface. | |
/// This is the trait that will be our general-purpose property interface. It | |
/// is intended to be used as a trait object. | |
/// | |
/// This trait is implemented automatically by the `impl_super_trait!` macro, |
/* ATTiny LED Twinkler | |
* | |
* This is come code I wrote a while back to "twinkle" | |
* four GPIO outputs that would drive LEDs. It was designed | |
* to be run on an eight-pin ATTiny13 chip. It works | |
* quite well, even considering how inefficient it is. | |
* | |
* - Robert Quattlebaum, 2012 | |
*/ |
You can locally pull data from your Rainforest Eagle-200 using cURL.
Rainforest has published a local API document which explains the details of the protocol. But this particular document is about quickly getting to the point and giving you some cURL commands you can use to immediately start pulling out data.
First, I'll assume that you have the following environment variables set:
I hereby claim:
- I am darconeous on github.
- I am darconeous (https://keybase.io/darconeous) on keybase.
- I have a public key whose fingerprint is 23D1 FEC8 37D0 5C91 5BA3 8A5D 95B0 6A0F 3F86 5814
To claim this, I am signing this object:
Original "dumb" smoke detector interconnect sounds the siren on all interconnected smoke detectors when a 9-to-12 volt (referenced to neutral/white) direct-current signal is continuously present on the signal wire (red). This still how pretty much all interconnected smoke alarms indicate a fire condition.
However, modern interconnected detectors are capable of detecting carbon monoxide and other conditions. When these conditions are signaled, they must be identified as something other than a smoke alarm by the other detectors. Ideally, any dumb smoke detectors
Overall goal is to remove the requirement that hosts keep track of a packet counter across resets. This is a common source of implementation difficulty. When not implemented correctly, it can severely compromise the security of the network.
In the symmetric version of this scheme, there is a single secret