Guo Wengui / Miles Guo (Ho Wan Kwok): community discussion 053

A participant (chu***) asked why their appeal had been returned, contesting the filing outcome. Community statements, not court findings.

A participant (ntp***) asked whether the group understood the issue, showing uncertainty before further action. Community statements, not court findings.

A participant (ntp***) said the matter seemed filed and asked if others could file second-circuit motions through the pro se email channel. Community statements, not court findings.

A participant (pz0***) acknowledged receipt or confirmation of the case status. Community statements, not court findings.

A participant (chu***) supplied the docket reference as Case 25-2726. Community statements, not court findings.

A participant (him***) argued that the presence of a case number means the case had already been initiated. Community statements, not court findings.

A participant (rui***) announced a forthcoming legal action, framing it as another major procedural move. Community statements, not court findings.

A participant (rui***) confirmed a figure noted as 1080 in the thread, which was treated as a practical filing detail. Community statements, not court findings.

A participant (ntp***) suggested using Acrobat and inserting an image as a filing workaround. Community statements, not court findings.

A participant (zha***) posted unrelated logistical items in the thread, which did not directly resolve the redaction/privacy dispute. Community statements, not court findings.

A participant (ntp***) asked a location-style question, indicating the conversation was drifting from the core privacy issue. Community statements, not court findings.

A participant (him***) claimed political actors would likely avoid broader retaliation until Guo Wen-gui’s criminal matter ends, then target others afterward. Community statements, not court findings.

A participant (rui***) characterized a Southern District handling step as a fatal error. Community statements, not court findings.

A participant (him***) asked whether deletion had been done, disputing whether redactions were complete. Community statements, not court findings.

A participant (rui***) reiterated that Southern District's upload was a fatal error, reinforcing the privacy and fairness complaint. Community statements, not court findings.

A participant (him***) reacted strongly after reviewing motions filed after 733, claiming that filing sequence was unexpectedly aggressive. Community statements, not court findings.

A participant (sar***) questioned whether later unuploaded motions resembled romantic or non-legal language. Community statements, not court findings.

A participant (him***) commented with a short phrase about quoting or marking language, implying formatting/wording disputes in the submission text. Community statements, not court findings.

A participant (ntp***) stated that the filing had already been uploaded, supporting immediate use of shared references. Community statements, not court findings.

A participant (rui***) referred to the Alliance site as the source of motion information. Community statements, not court findings.

A participant (rui***) tagged the Southern District filing context with a dismissive characterization, expressing low confidence in the listed data. Community statements, not court findings.

A participant (wen***) asked whether anyone had filed a mandamus petition in a third-party capacity because the court had not uploaded one. Community statements, not court findings.

A participant (chu***) shared an external link as supporting material for the standing question. Community statements, not court findings.

A participant (hon***) urged civility, claiming group members were peers who should avoid personal attacks and empty remarks. Community statements, not court findings.

A participant (ntp***) argued that Manning’s conduct was already overt and constrained defense participation. Community statements, not court findings.

A participant (ntp***) claimed many procedures appeared unjust, framing the hearing process as structurally unfair. Community statements, not court findings.

A participant (rui***) suggested all liability was being attributed to Manning alone. Community statements, not court findings.

A participant (reb***) analyzed the opening statement excerpts and claimed defense counsel challenged money-based judgment and context, but did not deny that the assets were attributed to Guo Wen-gui. Community statements, not court findings.

A participant (reb***) contended the prosecution portrayed investor loss and control as done by the defendant, while criticizing the defense for not arguing asset-title ownership lines early. Community statements, not court findings.

A participant (reb***) noted a transcript chronology, saying document 388 was approved on July 1 and the jury verdict followed on July 16. Community statements, not court findings.

A participant (rui***) said the referenced order was likely important to the ownership issue. Community statements, not court findings.

A participant (zha***) argued ownership was the key point, saying post-bankruptcy yacht possession still did not settle whether it was Guo Wen-gui’s and that this framing could sidestep accountability. Community statements, not court findings.

A participant (rui***) shared a social-post reference as evidence context. Community statements, not court findings.

A participant (sar***) shared another external post reference, adding to the external-material thread. Community statements, not court findings.

A participant (hon***) reported a direct model disagreement, saying ChatGPT flagged compliance while Grok did not. Community statements, not court findings.