Disguised Toast recalls “extremely uncomfortable” encounter with Nina Lin amid controversy
Disguised Toast has spoken about an “extremely uncomfortable” encounter with Nina Lin after a resurfaced clip

Streamer Jeremy “Disguised Toast” Wang has addressed his own “extremely uncomfortable” encounter with fellow content creator Nina Lin, following renewed attention on her past behaviour.
In October 2025, Twitch streamer Nina Lin faced widespread criticism after a 2024 video resurfaced showing her and influencer Zoe Spencer physically restraining FaZe Silky’s assistant, Said, without his consent.
Despite others in the room reminding them that he had not consented, the two continued. Lin later acknowledged her actions were “wrong,” stating, “During the situation, I genuinely, 100% thought it was a joke.”
Both Lin and Spencer were issued 24-hour bans on Twitch after the clip circulated online. Said later described the incident as “unreal.”
Amid the controversy, another old video featuring Lin and Disguised Toast resurfaced, prompting Wang to share his experience publicly. The footage showed Wang lying on a massage table as Lin approached and began imitating a masseuse, touching him inappropriately.
“I was trying to get a massage from the physical therapist, when Nina, an IRL streamer I’ve never met, pushed aside the therapist and started grabbing at my ass while I was already lying on the table,” Wang explained. While the video does not depict any physical pushing, Lin’s other actions are visible.
“I felt pressured to go along with it,” he said. “I did not want to escalate the situation. I was extremely uncomfortable the whole time.” Wang also added that he “regrets not speaking up earlier.”
Lin has yet to respond to Wang’s comments. The incident has intensified ongoing discussions in the streaming community about boundaries, accountability, and how creators address inappropriate conduct both on and off camera.


















COMMENTS
Comments are moderated and generally will be posted if they are on-topic and not abusive.
For more information, please see our Comments FAQ