Dossier / Suddenly UI-TomPublic-interest record
Response and right of reply
They knew. One moderator said they laughed.
Reddit and Discord removed Tom after the dispute became public, and Tom agreed that he should have stepped down years earlier. In the ensuing discussion, moderators described their prior knowledge, their decision to retain the two-account arrangement, and their treatment of members who challenged it.
The outcome
Tom was removed from both moderator teams
On August 28, Reddit and Discord moderators announced that Tom would be removed. Their statements credit him with helping build the communities and say he disclosed his Ubiquiti employment to the moderator team after he was hired.
SuddenlyEngineer agreed with the decision: I should have stepped down years ago.
He also acknowledged that maintaining a personal account with moderation privileges had undermined community trust.
D-009DocumentedA Discord administrator announced Tom's removal after community objections, while crediting his work as a moderator and saying he had disclosed his Ubiquiti employment to the team. SuddenlyEngineer accepted the decision, wrote that he should have stepped down years earlier, and acknowledged that keeping moderation privileges on his personal account had undermined community trust.
Public statements
The removal and Tom’s acknowledgment
D-009DocumentedA Discord administrator announced Tom's removal after community objections, while crediting his work as a moderator and saying he had disclosed his Ubiquiti employment to the team. SuddenlyEngineer accepted the decision, wrote that he should have stepped down years earlier, and acknowledged that keeping moderation privileges on his personal account had undermined community trust.
M-002DocumentedAn r/Ubiquiti moderator announced Tom's removal after community objections, while crediting his earlier work and saying the team knew about his Ubiquiti employment. Suddenly_Engineer agreed with the decision, wrote that he should have stepped down years earlier, and acknowledged that retaining privileges on a personal account undermined community trust.
What the moderators said next · D-010
The team knew. Critics were told to grow up—or leave.
Jon, the server owner, says Tom disclosed his Ubiquiti employment to the moderator team immediately after he was hired. Nevyn adds more detail: Tom approached the team in May 2022 intending to step down, but another moderator suggested keeping the personal account as a moderator while adding a separate official account. Nevyn says the proposal received immediate support
because the team did not want to lose him.
The moderators’ own account changes the institutional history. The conflict did not escape notice: the team discussed Tom’s proposed departure and deliberately retained his personal moderator account alongside an employee-tagged identity. Knowledge remained inside the team while ordinary members continued to encounter the accounts without the same explanation.
When members raised the resulting loss of trust, Jon, the server owner, described the criticism as jealousy and told one participant to grow up
because everyone is lying in some way.
Spot, displayed under the t.c.o.a. moderator identity, said we all laughed our asses off while he was doing that,
told critics they could fucking leave,
and called the server a benevolent dictatorship.
A third administrator or moderator speaker questioned whether the lack of disclosure had affected anyone’s life.
“Meanwhile, we all laughed our asses off while he was doing that.” spot / t.c.o.a. · Discord moderator
Role attribution: the publisher identifies Jon as the server owner, t.c.o.a. (displayed as spot) as a moderator, and skeletorri (displayed as Reiko) as an administrator or moderator. The export preserves account titles and display names but does not render role badges. Nevyn is not identified by this publication as a former moderator or server owner.
D-010DocumentedThe Discord discussion following Tom's removal records the team's prior knowledge of his Ubiquiti employment and its decision to keep his personal moderator account beside a separate employee-tagged identity. When members question the lack of disclosure, moderator or administrator speakers ridicule the concern, insult participants, and tell critics to leave.
Exact excerpts from the supplied export
The discussion in their own words
“another mod … suggested he simply have an official account as well rather than transitioning to a non-mod role completely. This got immediate support”
Nevyn · 7:34 PM
“also no real reason for it to be public knowledge”
Reiko · identified by publisher as skeletorri · 7:49–7:50 PM
“jealousy comes in many forms”
Jon · 7:45 PM
“grow up. it’s the internet. everyone is lying in some way.”
Jon · 7:59 PM
“we all laughed our asses off while he was doing that. If you don’t like it, you can fucking leave.”
spot · t.c.o.a. · Discord moderator · 7:59 PM
“This isn’t freedom of speech. This is a benevolent dictatorship.”
spot · t.c.o.a. · Discord moderator · 8:06 PM
These excerpts isolate the statements most relevant to prior knowledge, public disclosure, and the treatment of critics. The linked export and chronological transcript preserve the surrounding questions, praise for Tom, criticism of the investigation, and competing views so the selections can be checked against the complete exchange.
Disclosure concern · 16 CFR § 255.5
Members asked whether the nondisclosure crossed a legal line
Several participants framed the dispute as a disclosure problem affecting the credibility of advice, product recommendations, and moderation decisions. Pcmike asked why the association had been hidden and said SuddenlyEngineer had told him, I don’t work for UI.
Icemanxbe asked how that conduct could be considered trustworthy. DukeChocula then attached a federal citation to the concern.
“Wait, doesn’t this violate the FTC’s Material Connection Disclosure Requirement? I’ve seen SuddenlyEngineer the Ubiquiti employee promote/encourage the sale of Ubiquiti products.” DukeChocula · 8:16 PM
Duke linked to 16 CFR § 255.5. The current federal text says a connection between an endorser and seller that could materially affect an endorsement’s credibility—and is not reasonably expected by the audience—must be disclosed clearly and conspicuously. Employment can be such a business connection.
Jon replied oh my god
and posted four eye-roll emojis two minutes later. No substantive answer to the legal or disclosure question appears in the export.
Reddit follow-up · R-007
Two readers linked the evidence. Moderators removed both comments.
The Reddit announcement produced a long argument about Tom’s contributions, the undisclosed employment relationship, moderator authority, and the federal disclosure concern. LifeChange0900 and prisonerofmemewar each linked this investigation in a different reply branch. The archive preserves both comments before removal and the matching branches afterward.
R-007-LC-BEFOREDocumentedBefore: LifeChange0900 posts the link and an account of the investigation’s findings.
R-007-LC-AFTERDocumentedAfter: LifeChange0900 remains in the same reply-tree position, but the link and text are replaced by Comment removed by moderator.
R-007-PM-BEFOREDocumentedBefore: prisonerofmemewar edits a separate comment to add the investigation link.
R-007-PM-AFTERDocumentedAfter: the same replies remain, while the parent is replaced by [deleted] and Comment removed by moderator.
Each match is supported by its reply structure. LifeChange0900 remains visibly named beneath scytob, followed by the same Capable-Magician2094, NeoTravel, scytob, and drumstikka replies. The prisonerofmemewar pair retains the same nutscrape_navigator, prisonerofmemewar, scytob, nutscrape_navigator, BBSig, and shinkamui sequence. Both later states say Comment removed by moderator.
The currently published subreddit rules require Ubiquiti-related content and prohibit AI/LLM-generated content. Both removed comments concerned Ubiquiti and responded directly to the moderator announcement. The captures provide no indication that either comment was AI-generated, and neither removal notice cites a rule. Any discretionary or unstated rationale remains undisclosed in the public record.
Original outreach record · ROR-001
The direct message failed, but public responses followed
Before publication, a Discord message requested comment, factual corrections, and context. Discord displayed: Your message could not be delivered.
The later announcements and discussion are substantive public responses to the controversy and are published beside the investigation. They do not establish that the failed direct message was ever received through Discord or that its recipient learned of the request through another channel.
Open the outreach record →
SHA-256 c5eee546…b7cb8dSubjectStatusLast updatedOutcome
The invitation remains open
Responses and corrections remain welcome.
Anyone named in the reporting may provide context, challenge an interpretation, submit a factual correction, or supply a complete primary record. Substantive responses will appear beside the claims they address so readers can compare the competing accounts.