hmm, reconstructing the timeline of events, the trigger may have been tweet 776497511594860544 after all and it was just misguided antispam
Conversation
Replying to
which would be stupid since the domain has long been grabbed but understandable - nobody ever cleans spam filters.
anyway good night