Rendered at 21:12:28 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
JofArnold 30 minutes ago [-]
Let's say you could follow and unfollow once a second and they knew it. Then you could replicate the dots and dashes by the length of time you toggled the status plus the gaps where you weren't toggling at all.
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.
savhascelik 28 minutes ago [-]
Although not directly by “following”,
as king_zee said, it seems it can be done using a few different components; thank you
king_zee 39 minutes ago [-]
You only have 1 variable in your control, the time in-between follows. (I say this because there is no notification for "unfollowing" someone)
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.
savhascelik 29 minutes ago [-]
It seems it can be done using a few different components, even if not directly by “following”, thank you
xg15 45 minutes ago [-]
Were you blocked?
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.
savhascelik 33 minutes ago [-]
No, actually, I was just wondering if messaging like that is even possible; I suppose I’ve been reading a lot lately about encryption and private messaging in public spaces.
bigyabai 2 hours ago [-]
With just follow/unfollowing, you can't truly encode Morse code. You would have to override a metadata field or agree on an external clock source to overcome the idempotent follow/unfollow action and encode language into the state machine.
savhascelik 1 hours ago [-]
I suppose the interval between the two actions would correspond to a letter in the Morse code here
bigyabai 1 hours ago [-]
That would require an additional lookup table that doesn't qualify as Morse code, as well as an external clock source.
savhascelik 1 hours ago [-]
I suppose I should have gone over how Morse code works again before asking this question. Thank you.
ada1981 2 hours ago [-]
Do you mean following and unfollowing in some sort of rapid succession?
savhascelik 2 hours ago [-]
Yes, I think that’s exactly what I’m talking about; the interval between the two actions would correspond to a letter in Morse code
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.
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.
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.