.. ..-. / -.-- --- ..- / -.-. .- -. / .-. . .- -.. / - .... .. ... --..-- / - --- ..- -.-. .... / --. .-. .- ... ...
You need to represent 2 variables : the dot/dash to represent symbols, and the dit, the time in-between symbols.
If you want to do this you need some sort of 2nd action, a comment or a twitter like, that way we could represent the dot/dash with either action, and then space them out to time the silence.
Or you can use "Morse tap code" where two close knocks represent a dot, and if the gap between them is slightly longer it's a dash. That takes two knocks for one dot/dash but it works and is (was?) used in practice.
More seriously, the events end up in a list, so a recipient would more likely "decode" them by comparing timestamps instead of "live" watching the actual sequence.
But I suppose if you timed your follows/unfollows really carefully, you could get certain patterns in the timestamps to appear which could be used to distinguish "long" and "short" pulses.
Eg in the first ten seconds 10 toggles, in the next 10 seconds a 5 second gap then 5 toggles. That would be dash, quiet, dot.