PolyCraft/index
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

top 10 lies - lets ban the facts

Browse Source
This commit is contained in:
lovebird 2026-03-31 12:51:48 +02:00
parent aa4d122def
commit e1aeb6245a
1 changed files with 20 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
ref/top-10-lies.md
View File

@ -23,6 +23,8 @@ This article organizes those concerns into recurring claim-versus-reality themes
### 1) “Sustainable Impact at Scale”
* **The claim:** Traditional recycling is "not working," but local micro-recycling is scaling globally with "1,000+ workspaces" to save the planet.
* **What users report:** Traditional recycling works—just not with "Precious Plastic toys." Critics allege the "1,000+" claims are manipulated metrics. Reports from within the trade suggest that **over 1,300+ workspaces** have been "censored or rejected" from the map for not being "obedient," leaving behind a cluttered map of mostly inactive "ghost" profiles. Genuine engagement is virtually non-existent, often reaching only a few dozen likes despite "150k followers."
* **Why it matters:** Manipulated success metrics hide a high rejection/attrition rate and mislead the public about the actual scale of the network.
@ -129,6 +131,24 @@ Beyond technical failures, a recurring theme in reports is the toxic environment
***
## Case Study: Weaponizing the Platform Against Critics
A primary example of the "Institutional Violence" mentioned above is the public smear campaign launched by the core team against long-term contributors who raise technical or financial questions.
### The "OSR-Plastic.org" Blacklisting
The core team published a coordinated "Warning" article targeting a 8-year veteran of the community (operating as *PlasticHub*, *Polymech*, etc.). This post serves as a textbook example of how the platform is used to "poison the well" against engineering-led critique:
* **The Narrative:** The critic is labeled a "Troll," "Data Thief," and "Harasser" to justify a complete ban from all platforms.
* **The Admission of Censorship:** The team admits to manually tracking IPs and VPNs to ban over 50 accounts associated with this single individual—confirming the "Aggressive Censorship" reported by other builders.
* **The Financial Motivation:** The smear campaign was explicitly launched during a "Version 5" fundraising window, stating that the critic was "targeting large donors"—indicating that protecting the flow of donations is prioritized over resolving technical disputes or fixing designs.
* **The Outcome:** By labeling a professional machine builder as "illegal" and "violent," the organization effectively "jails" his 8+ years of expertise, preventing newcomers from hearing well-documented critiques (and designs).
### Analysis of the Smear
This behavior demonstrates a shift from "Open Source Community" to "Protected Brand." In healthy engineering circles, technical claims (e.g., "machines are inefficient") are refuted with data and testing. In this ecosystem, they are refuted with character assassination, blacklisting, and a "Report This User" guide for followers.
***
## Systemic Issues Reported by Builders
* **Documentation Rot:** Guides heavily diverge from current designs; repositories lack revision history.