Davide Barbato

I think I need a PoC for this, can't figure by myself, sorry.

I'd only say that "sleep time between beacons" and "skew/randomness" should not be enforced by our library but by the 3rd-party tool (in our case, the `screep` example program), since...

make sense if use it. We can add them as a future enhancement (I'd say: in the base class and with default value that should be overrided by each channel....

Yeah I recognize that we need something better, even if this situation happens only on Twitter (or in any other channel that has a kind of limitation on messages' length)....

Agree with you @DakotaNelson . I'd say: let's implement the mandatory/optional parameters and then let's decide inside `send|()` based on params. What do you think?

are we going to use the method explained in #7 ? I think i'd be a better idea to implement it, merge into master and then start working on modules...

Agree, and also I agree on your thoughts on the other issue. Let's move the discussion there :)

done here: 8359795

I think it would be a good idea to add the "delete" function, but leave the usage to the coder. I mean, it's not a thing the library should decide,...

So I'd say we can keep it simple by doing: `(data) -> [encoders] -> filetype -> channel` Where `[encoders]` includes encoding (b64), encryption, and compression (we can leverage the 'chaining'...