The following is the text of an email that I sent, via an intermediary, Jay, early this morning. Enjoy!
So I asked for Jay Postones of @tesseractband to state PUBLICLY the allegations against me (which led to my a) ban from his #Twitch channel, b) ban from the TesseracT Discord, and c) temporary (allegedly - we'll see, I guess) band from @Rockwithdan's personal Discord server) 1/x
The following is the text of an email that I sent, via an intermediary, Jay, early this morning. Enjoy!
I posted a 100% truthful thread, here:
https://t.co/ZnBI9t7eWg
and be in NO doubt that, until ANY allegations against me are posted THERE, in full view of the public" 5/x
12 minutes 24 seconds in...https://t.co/ERpcWIwsJh
— Catherine Taylor (@cathesaurus) February 11, 2021
Jay knows how I make a living. Which means he ALSO knows that I can devote 24x7x365 attention to this ridiculous situation because my suicidal distraught of yesterday has morphed" 6/x
Please feel free to forward this email to Jay." 7/x
https://t.co/JJEAhCUt7r
You May Also Like
BREAKING: @CommonsCMS @DamianCollins just released previously sealed #Six4Three @Facebook documents:
Some random interesting tidbits:
1) Zuck approves shutting down platform API access for Twitter's when Vine is released #competition
2) Facebook engineered ways to access user's call history w/o alerting users:
Team considered access to call history considered 'high PR risk' but 'growth team will charge ahead'. @Facebook created upgrade path to access data w/o subjecting users to Android permissions dialogue.
3) The above also confirms @kashhill and other's suspicion that call history was used to improve PYMK (People You May Know) suggestions and newsfeed rankings.
4) Docs also shed more light into @dseetharaman's story on @Facebook monitoring users' @Onavo VPN activity to determine what competitors to mimic or acquire in 2013.
https://t.co/PwiRIL3v9x
Some random interesting tidbits:
1) Zuck approves shutting down platform API access for Twitter's when Vine is released #competition

2) Facebook engineered ways to access user's call history w/o alerting users:
Team considered access to call history considered 'high PR risk' but 'growth team will charge ahead'. @Facebook created upgrade path to access data w/o subjecting users to Android permissions dialogue.

3) The above also confirms @kashhill and other's suspicion that call history was used to improve PYMK (People You May Know) suggestions and newsfeed rankings.
4) Docs also shed more light into @dseetharaman's story on @Facebook monitoring users' @Onavo VPN activity to determine what competitors to mimic or acquire in 2013.
https://t.co/PwiRIL3v9x
