Hack Club Wiki - Recent changes [en]

List of Incidents

172.18.0.3 — Tue, 08 Sep 2026 17:10:46 GMT

wikitable

← Older revision		Revision as of 17:10, 8 September 2026
Line 1:		Line 1:
	# List of Incidents		{\| class="wikitable"
			\|+ List of Incidents
			\|-
			! Name !! Description !! Date
			\|-
			\| 2024 Hack Club Confessions Controversy \|\| A period of significant internal conflict within the community centered on Confessions and its moderation \|\| November 2024 — Ongoing
			\|-
			\| Privacy concerns and data handling at Hack Club \|\| Ongoing community scrutiny and external criticism regarding its data privacy practices \|\| November 2024 — Ongoing
			\|-
			\| 2025 Zach Latdroid Incidents \|\| The 2025 Zach Latdroid Incidents refer to the circulation of two distinct satirical videos posted under or in reference to the sock puppet account name "Zach Latdroid" within the Hack Club community in October 2025. \|\| October 2025
			\|}

	\|Name\| Description\| Date		\|Name\| Description\| Date

	\|---\|---\|---\|		\|---\|---\|---\|

	\|~~2024 Hack Club Confessions Controversy~~\| A period of significant internal conflict within the community centered on Confessions and its moderation\| April 2024\|		\|\| A period of significant internal conflict within the community centered on Confessions and its moderation\| April 2024\|

	\|Privacy concerns and data handling at Hack Club\| Ongoing community scrutiny and external criticism regarding its data privacy practices\| November 2024 — Ongoing\|		\|Privacy concerns and data handling at Hack Club\| Ongoing community scrutiny and external criticism regarding its data privacy practices\| November 2024 — Ongoing\|

	\|2025 Zach Latdroid Incidents\| The 2025 Zach Latdroid Incidents refer to the circulation of two distinct satirical videos posted under or in reference to the sock puppet account name "Zach Latdroid" within the Hack Club community in October 2025.\| October 2025		\|2025 Zach Latdroid Incidents\| The 2025 Zach Latdroid Incidents refer to the circulation of two distinct satirical videos posted under or in reference to the sock puppet account name "Zach Latdroid" within the Hack Club community in October 2025.\| October 2025

List of Incidents

172.18.0.3 — Tue, 08 Sep 2026 17:08:24 GMT

import md

New page

# List of Incidents
|Name| Description| Date

|---|---|---|

|2024 Hack Club Confessions Controversy| A period of significant internal conflict within the community centered on Confessions and its moderation| April 2024|

|Privacy concerns and data handling at Hack Club| Ongoing community scrutiny and external criticism regarding its data privacy practices| November 2024 — Ongoing|

|2025 Zach Latdroid Incidents| The 2025 Zach Latdroid Incidents refer to the circulation of two distinct satirical videos posted under or in reference to the sock puppet account name "Zach Latdroid" within the Hack Club community in October 2025.| October 2025

List of Community Teams

172.18.0.3 — Tue, 08 Sep 2026 17:07:31 GMT

Created page with "# List of Community Teams A list of community teams is below. |Name|Description|Accepting Applicants|Channel| |---|---|---|---| |Gardeners|Welcomes new members to the slack|No|#gardeners| |Nest Admins|Manages Nest|No|#nest| |Special Activities Division|Runs events for the general Hack Club Community|No|#specialactivities-division [sic]| |Fire Department|Runs day-to-day moderation in the Hack Club Slack|No|#fire-dept |Confessions|Review Team|Manages operations over #conf..."

New page

# List of Community Teams
A list of community teams is below.

|Name|Description|Accepting Applicants|Channel|
|---|---|---|---|
|Gardeners|Welcomes new members to the slack|No|#gardeners|
|Nest Admins|Manages Nest|No|#nest|
|Special Activities Division|Runs events for the general Hack Club Community|No|#specialactivities-division [sic]|
|Fire Department|Runs day-to-day moderation in the Hack Club Slack|No|#fire-dept
|Confessions|Review Team|Manages operations over #confessions and #meta, moderates posts submitted through Prox2|No|#confessionsmeta|
|DNS Crime Squad/Friends|Reviews hackclub/dns pulls|???|#dns
|Newspaper Team|Manages the Hack Club Newspaper|???|#hack-clubnewspaper
|Fraud Squad|Handles matters related to primarily Hackatime fraud, but most other kinds of fraud too (not HCB fraud)|Invite only| @Fraud Department (bot)|

*Archived from https://web.archive.org/web/20251022192447mp_/https://hackclub.wiki/en/List_of_Community_Teams*

Main Page

172.18.0.3 — Tue, 08 Sep 2026 17:06:47 GMT

Pages (Adapted from hack.wiki)

← Older revision		Revision as of 17:06, 8 September 2026
Line 5:		Line 5:
	[https://news.hackclub.com Feed from news.hackclub.com]		[https://news.hackclub.com Feed from news.hackclub.com]

	== Pages (Adapted from ~~hack~~.wiki) ==		== Pages (Adapted from hackclub.wiki) ==
	Pages from the original wiki.js wiki.		Pages from the original wiki.js wiki.
	* [[List of YSWS]] (see also the new [[YSWS]])		* [[List of YSWS]] (see also the new [[YSWS]])

2024 Hack Club Confessions Controversy

172.18.0.3 — Tue, 08 Sep 2026 17:06:26 GMT

← Older revision		Revision as of 17:06, 8 September 2026
(One intermediate revision by the same user not shown)
Line 1:		Line 1:
	~~# 2024 Hack Club Confessions Controversy~~		The ''2024 Hack Club Confessions controversy'', sometimes referred to as ''Coup du CRT'', was a period of significant internal conflict within the community centered on Confessions and its moderation. The event, which occurred in April 2024, involved a disputed change in moderation policy, the removal of volunteer moderators, and the banning of a prominent community member.
	The 2024 Hack Club Confessions controversy, sometimes referred to as Coup du CRT, was a period of significant internal conflict within the community centered on Confessions and its moderation. The event, which occurred in April 2024, involved a disputed change in moderation policy, the removal of volunteer moderators, and the banning of a prominent community member.

	## Incident		== Incident ==
	The situation began with a surge of confessions that were critical Hack Club HQ team, alongside counter-confessions defending it. This led to a chaotic atmosphere that, according to subsequent statements from the community team, negatively affected the mental well-being of several community members and volunteers, with some considering leaving the community altogether. In response, on April 13, a member of the community team instructed the Confessions Review Team (CRT) in a private channel to begin censoring all anti-HQ confessions. This instruction was soon revealed publicly by a CRT member, who also announced their intention to resign.		The situation began with a surge of confessions that were critical Hack Club HQ team, alongside counter-confessions defending it. This led to a chaotic atmosphere that, according to subsequent statements from the community team, negatively affected the mental well-being of several community members and volunteers, with some considering leaving the community altogether. In response, on April 13, a member of the community team instructed the Confessions Review Team (CRT) in a private channel to begin censoring all anti-HQ confessions. This instruction was soon revealed publicly by a CRT member, who also announced their intention to resign.

	A vote was subsequently held within the CRT on a new policy to formally disallow confessions criticizing HQ. The vote saw low participation, with three members in favor and one against. Shortly after, the community team announced the policy change publicly in the #confessions channel, stating it had been approved by a "majority" of the CRT. This claim was immediately contested by other CRT members, who argued the process was undemocratic due to the short voting window and the low number of affirmative votes, which did not constitute a majority of the entire team.		A vote was subsequently held within the CRT on a new policy to formally disallow confessions criticizing HQ. The vote saw low participation, with three members in favor and one against. Shortly after, the community team announced the policy change publicly in the #confessions channel, stating it had been approved by a "majority" of the CRT. This claim was immediately contested by other CRT members, who argued the process was undemocratic due to the short voting window and the low number of affirmative votes, which did not constitute a majority of the entire team.

	## Reception		== Reception ==
	The dispute escalated when two CRT members who had protested the new policy were removed from the team by the community team for insubordination, specifically for continuing to approve critical messages after the announcement. This action triggered a community outcry, including the creation of polls demanding the moderators' reinstatement and the deployment of spam bots by a user demanding more transparency. In the ensuing turmoil, the primary community member who had leaked the initial policy change was banned from the Slack workspace for up to one year. Later, it was extended to an indefinite ban.		The dispute escalated when two CRT members who had protested the new policy were removed from the team by the community team for insubordination, specifically for continuing to approve critical messages after the announcement. This action triggered a community outcry, including the creation of polls demanding the moderators' reinstatement and the deployment of spam bots by a user demanding more transparency. In the ensuing turmoil, the primary community member who had leaked the initial policy change was banned from the Slack workspace for up to one year. Later, it was extended to an indefinite ban.

	Later, the other member of CRT was reinstated back onto CRT.		Later, the other member of CRT was reinstated back onto CRT.

2024 Hack Club Confessions Controversy

172.18.0.3 — Tue, 08 Sep 2026 17:04:06 GMT

markdown

New page

# 2024 Hack Club Confessions Controversy
The *2024 Hack Club Confessions controversy*, sometimes referred to as *Coup du CRT*, was a period of significant internal conflict within the community centered on Confessions and its moderation. The event, which occurred in April 2024, involved a disputed change in moderation policy, the removal of volunteer moderators, and the banning of a prominent community member.

## Incident
The situation began with a surge of confessions that were critical Hack Club HQ team, alongside counter-confessions defending it. This led to a chaotic atmosphere that, according to subsequent statements from the community team, negatively affected the mental well-being of several community members and volunteers, with some considering leaving the community altogether. In response, on April 13, a member of the community team instructed the Confessions Review Team (CRT) in a private channel to begin censoring all anti-HQ confessions. This instruction was soon revealed publicly by a CRT member, who also announced their intention to resign.

A vote was subsequently held within the CRT on a new policy to formally disallow confessions criticizing HQ. The vote saw low participation, with three members in favor and one against. Shortly after, the community team announced the policy change publicly in the #confessions channel, stating it had been approved by a "majority" of the CRT. This claim was immediately contested by other CRT members, who argued the process was undemocratic due to the short voting window and the low number of affirmative votes, which did not constitute a majority of the entire team.

## Reception
The dispute escalated when two CRT members who had protested the new policy were removed from the team by the community team for insubordination, specifically for continuing to approve critical messages after the announcement. This action triggered a community outcry, including the creation of polls demanding the moderators' reinstatement and the deployment of spam bots by a user demanding more transparency. In the ensuing turmoil, the primary community member who had leaked the initial policy change was banned from the Slack workspace for up to one year. Later, it was extended to an indefinite ban.

Later, the other member of CRT was reinstated back onto CRT.

Privacy concerns and data handling at Hack Club

172.18.0.3 — Tue, 08 Sep 2026 17:01:26 GMT

wikitextified

← Older revision		Revision as of 17:01, 8 September 2026
Line 1:		Line 1:
	~~# Privacy concerns and data handling at Hack Club~~
	Hack Club has faced ongoing community scrutiny and external criticism regarding its data privacy practices, compliance with regulations, and the security of its systems. These concerns center on the collection and retention of personal data, particularly from minors, the security of its digital infrastructure, and its adherence to data protection laws like the General Data Protection Regulation (GDPR).		Hack Club has faced ongoing community scrutiny and external criticism regarding its data privacy practices, compliance with regulations, and the security of its systems. These concerns center on the collection and retention of personal data, particularly from minors, the security of its digital infrastructure, and its adherence to data protection laws like the General Data Protection Regulation (GDPR).

	## Debates on Data Practices		== Debates on Data Practices ==
	Internal discussions within the Hack Club Slack have highlighted privacy concerns. Community members have repeatedly questioned GDPR compliance, citing the lack of a formal privacy policy for an extended period and the indefinite retention of government-issued identification documents used for YSWS verification. In response, staff members acknowledged the complexity of GDPR for an organization of Hack Club's structure and the challenges of verifying the identities of international high schoolers at scale. They stated that a privacy policy was being developed and that IDs were set to be automatically deleted after 90 days, though this was debated as a balance between privacy and the "legitimate interest" of preventing fraud.		Internal discussions within the Hack Club Slack have highlighted privacy concerns. Community members have repeatedly questioned GDPR compliance, citing the lack of a formal privacy policy for an extended period and the indefinite retention of government-issued identification documents used for YSWS verification. In response, staff members acknowledged the complexity of GDPR for an organization of Hack Club's structure and the challenges of verifying the identities of international high schoolers at scale. They stated that a privacy policy was being developed and that IDs were set to be automatically deleted after 90 days, though this was debated as a balance between privacy and the "legitimate interest" of preventing fraud.

	Further concerns were raised about marketing practices, with users noting that signing up for programs like HCB automatically enrolled them in organizational newsletters, a practice that critics argued should be opt-in rather than opt-out under regulations like PECR and CAN-SPAM. Staff acknowledged the issue and pointed to functional unsubscribe links in marketing emails.		Further concerns were raised about marketing practices, with users noting that signing up for programs like HCB automatically enrolled them in organizational newsletters, a practice that critics argued should be opt-in rather than opt-out under regulations like PECR and CAN-SPAM. Staff acknowledged the issue and pointed to functional unsubscribe links in marketing emails.

	## Security Incidents		== Security Incidents ==
	The internal debates were compounded by a series of public incidents documented in external blog posts. In July 2025, a former member of Hack Club disclosed multiple unprotected API endpoints across Hack Club programs. One endpoint in the Neighbourhood program allegedly exposed participants' full legal names using only their Slack ID, without any authentication. Internal communications provided by the researcher suggested this lack of protection was an intentional design decision by a developer, despite being warned by another team member that it constituted a GDPR breach.		The internal debates were compounded by a series of public incidents documented in external blog posts. In July 2025, a former member of Hack Club disclosed multiple unprotected API endpoints across Hack Club programs. One endpoint in the Neighbourhood program allegedly exposed participants' full legal names using only their Slack ID, without any authentication. Internal communications provided by the researcher suggested this lack of protection was an intentional design decision by a developer, despite being warned by another team member that it constituted a GDPR breach.

Line 14:		Line 13:
	A third area of concern involved "Orpheus Engine," an internal analytics pipeline. According to a technical analysis, this system was used to profile grant applicants by scraping their activity across various social platforms and using third-party APIs to infer demographic data like gender. Critics argued this constituted extensive profiling without opt-in or transparency.		A third area of concern involved "Orpheus Engine," an internal analytics pipeline. According to a technical analysis, this system was used to profile grant applicants by scraping their activity across various social platforms and using third-party APIs to infer demographic data like gender. Critics argued this constituted extensive profiling without opt-in or transparency.

	## Governance and Response		== Governance and Response ==
	The response to these disclosures became a point of contention. The researcher reported that initial contact with Hack Club staff, some of whom were teenage interns, yielded legally inaccurate responses, including the claim that GDPR did not apply to the US-based organization and that advice had been sourced from ChatGPT. Leadership was criticized for being dismissive of formal breach notifications. Furthermore, the dedicated GDPR contact email (gdpr@hackclub.com) was taken offline shortly after the issues were raised publicly, with operations staff later explaining it was a temporary solution managed by a part-time contributor.		The response to these disclosures became a point of contention. The researcher reported that initial contact with Hack Club staff, some of whom were teenage interns, yielded legally inaccurate responses, including the claim that GDPR did not apply to the US-based organization and that advice had been sourced from ChatGPT. Leadership was criticized for being dismissive of formal breach notifications. Furthermore, the dedicated GDPR contact email (gdpr@hackclub.com) was taken offline shortly after the issues were raised publicly, with operations staff later explaining it was a temporary solution managed by a part-time contributor.

	Hack Club's leadership acknowledged the need for improved policies. The COO stated in a Slack message that the organization was in the process of assembling its policies for publication. In internal discussions, staff expressed a philosophy that the need for formal policy documents was a sign of underlying issues but agreed that clarity for users was necessary.		Hack Club's leadership acknowledged the need for improved policies. The COO stated in a Slack message that the organization was in the process of assembling its policies for publication. In internal discussions, staff expressed a philosophy that the need for formal policy documents was a sign of underlying issues but agreed that clarity for users was necessary.

Privacy concerns and data handling at Hack Club

172.18.0.3 — Tue, 08 Sep 2026 17:00:37 GMT

markdown

New page

# Privacy concerns and data handling at Hack Club
Hack Club has faced ongoing community scrutiny and external criticism regarding its data privacy practices, compliance with regulations, and the security of its systems. These concerns center on the collection and retention of personal data, particularly from minors, the security of its digital infrastructure, and its adherence to data protection laws like the General Data Protection Regulation (GDPR).

## Debates on Data Practices
Internal discussions within the Hack Club Slack have highlighted privacy concerns. Community members have repeatedly questioned GDPR compliance, citing the lack of a formal privacy policy for an extended period and the indefinite retention of government-issued identification documents used for YSWS verification. In response, staff members acknowledged the complexity of GDPR for an organization of Hack Club's structure and the challenges of verifying the identities of international high schoolers at scale. They stated that a privacy policy was being developed and that IDs were set to be automatically deleted after 90 days, though this was debated as a balance between privacy and the "legitimate interest" of preventing fraud.

Further concerns were raised about marketing practices, with users noting that signing up for programs like HCB automatically enrolled them in organizational newsletters, a practice that critics argued should be opt-in rather than opt-out under regulations like PECR and CAN-SPAM. Staff acknowledged the issue and pointed to functional unsubscribe links in marketing emails.

## Security Incidents
The internal debates were compounded by a series of public incidents documented in external blog posts. In July 2025, a former member of Hack Club disclosed multiple unprotected API endpoints across Hack Club programs. One endpoint in the Neighbourhood program allegedly exposed participants' full legal names using only their Slack ID, without any authentication. Internal communications provided by the researcher suggested this lack of protection was an intentional design decision by a developer, despite being warned by another team member that it constituted a GDPR breach.

Subsequently, in September 2025, a separate incident occurred where a developer committed a log file containing three minors' full names, email addresses, home addresses, dates of birth, and phone numbers to a public repository. The response from Hack Club was described as attempting to overwrite the data and later making the repository private, but the data reportedly persisted in forks and web archives. The former member characterized this as a pattern of "gross, willful negligence" rather than an isolated error.

A third area of concern involved "Orpheus Engine," an internal analytics pipeline. According to a technical analysis, this system was used to profile grant applicants by scraping their activity across various social platforms and using third-party APIs to infer demographic data like gender. Critics argued this constituted extensive profiling without opt-in or transparency.

## Governance and Response
The response to these disclosures became a point of contention. The researcher reported that initial contact with Hack Club staff, some of whom were teenage interns, yielded legally inaccurate responses, including the claim that GDPR did not apply to the US-based organization and that advice had been sourced from ChatGPT. Leadership was criticized for being dismissive of formal breach notifications. Furthermore, the dedicated GDPR contact email (gdpr@hackclub.com) was taken offline shortly after the issues were raised publicly, with operations staff later explaining it was a temporary solution managed by a part-time contributor.

Hack Club's leadership acknowledged the need for improved policies. The COO stated in a Slack message that the organization was in the process of assembling its policies for publication. In internal discussions, staff expressed a philosophy that the need for formal policy documents was a sign of underlying issues but agreed that clarity for users was necessary.

Nest

Marcus Taisa — Tue, 08 Sep 2026 11:57:19 GMT

← Older revision		Revision as of 11:57, 8 September 2026
(One intermediate revision by the same user not shown)
Line 1:		Line 1:
	https://github.com/hackclub/nest/blob/9e8e55549c47beed2a91d8e21cdf23062a605d44/brand/logo.png		<nowiki><img src="https://github.com/hackclub/nest/blob/9e8e55549c47beed2a91d8e21cdf23062a605d44/brand/logo.png" /></nowiki>
	Nest is a free Linux-based web hosting service provided by Hack Club, primarily aimed at teenagers and students for hosting web applications, projects, and other software. The service is modeled after the concept of a Tilde, which allows students to share computing resources in a communal environment. Nest provides users with shell access, Git repositories, and other development tools without the need for paid hosting.		Nest is a free Linux-based web hosting service provided by Hack Club, primarily aimed at teenagers and students for hosting web applications, projects, and other software. The service is modeled after the concept of a Tilde, which allows students to share computing resources in a communal environment. Nest provides users with shell access, Git repositories, and other development tools without the need for paid hosting.

2025 Zach Latdroid Incident

Marcus Taisa — Tue, 08 Sep 2026 09:25:13 GMT

fixed link

← Older revision		Revision as of 09:25, 8 September 2026
(One intermediate revision by the same user not shown)
Line 1:		Line 1:
	~~# 2025 Zach Latdroid Incident~~
	The 2025 Zach Latdroid incident refers to the circulation of a video posted by a sock puppet account named "Zach Latdroid" on the Hack Club Slack workspace on 11 October 2025.		The 2025 Zach Latdroid incident refers to the circulation of a video posted by a sock puppet account named "Zach Latdroid" on the Hack Club Slack workspace on 11 October 2025.

	## Background		== Background ==
	On 11 October 2025, a user account named "Zach Latdroid" posted a video to the Hack Club Slack workspace. The video was a critical montage of the organization's culture and operations. The name is a portmanteau of Hack Club founder Zach Latta and the word "droid."		On 11 October 2025, a user account named "Zach Latdroid" posted a video to the Hack Club Slack workspace. The video was a critical montage of the organization's culture and operations. The name is a portmanteau of Hack Club founder Zach Latta and the word "droid."

	## Content of the Video		== Content of the Video ==
	The video was an edited montage using various clips and images to convey its critique. Its content included:		The video was an edited montage using various clips and images to convey its critique. Its content included:

	- Opening Segment: The video began with a clip from a Y2K-era presentation by Microsoft CEO Steve Ballmer. The clip was edited to feature the Hack Club flag on Ballmer's person, with logos for the Musk Foundation and GitHub Education superimposed. Ballmer's exclamation, "I love this company!" was presented as a commentary on Hack Club's perceived corporate culture.		* Opening Segment: The video began with a clip from a Y2K-era presentation by Microsoft CEO Steve Ballmer. The clip was edited to feature the Hack Club flag on Ballmer's person, with logos for the Musk Foundation and GitHub Education superimposed. Ballmer's exclamation, "I love this company!" was presented as a commentary on Hack Club's perceived corporate culture.
	- Audience Scene: A segment showed an audience raising their hands in a uniform manner, accompanied by the sound of a Slack notification. A later, censored version of the video replaced this scene with a error message for an inappropriate username, which was interpreted by some viewers as comparing Hack Club's administration to a dictatorship.		* Audience Scene: A segment showed an audience raising their hands in a uniform manner, accompanied by the sound of a Slack notification. A later, censored version of the video replaced this scene with a error message for an inappropriate username, which was interpreted by some viewers as comparing Hack Club's administration to a dictatorship.
	- Internal Mockery: The video included a screenshot of an interaction in a Slack channel, purportedly showing a member of the "Fraud Department" and another user [~~exchanging the onomatopoeia "meow."](~~https://web.archive.org/web/20251014092407mp_/https://en.wikipedia.org/wiki/Furry_fandom)		* Internal Mockery: The video included a screenshot of an interaction in a Slack channel, purportedly showing a member of the "Fraud Department" and another user [https://web.archive.org/web/20251014092407mp_/https://en.wikipedia.org/wiki/Furry_fandom exchanging the onomatopoeia "meow."]
	- Puppetmaster Imagery: An edited image depicted a figure labeled as the CEO with a partially robotic face (so-called "Zach Latdroid"), with strings attached to the profile pictures of users with cat avatars. This was seen as an implication that the leadership exerts control over a segment of the community.		* Puppetmaster Imagery: An edited image depicted a figure labeled as the CEO with a partially robotic face (so-called "Zach Latdroid"), with strings attached to the profile pictures of users with cat avatars. This was seen as an implication that the leadership exerts control over a segment of the community.
	- Critique of Operations: The montage featured a selection of posts from Confessions and referenced the 2023 pay rate of $12.50 per hour for certain HCB roles. It also included footage of someone rapidly editing event planning documents for various Hack Club programs (e.g., Power Hour, Arcade, Summer of Making), altering only minor details, to suggest a repetitive event model.		* Critique of Operations: The montage featured a selection of posts from Confessions and referenced the 2023 pay rate of $12.50 per hour for certain HCB roles. It also included footage of someone rapidly editing event planning documents for various Hack Club programs (e.g., Power Hour, Arcade, Summer of Making), altering only minor details, to suggest a repetitive event model.
	- AI and Corporate Allegiance: A segment used symbolic imagery, including a pyramid structure and corporate logos (GitHub, Microsoft, Slack), to critique the organization's relationship with Github, Microsoft and use of artificial intelligence.		* AI and Corporate Allegiance: A segment used symbolic imagery, including a pyramid structure and corporate logos (GitHub, Microsoft, Slack), to critique the organization's relationship with Github, Microsoft and use of artificial intelligence.
	- Named Shout-outs: The video concluded by displaying the usernames of four individuals within the Hack Club community.		* Named Shout-outs: The video concluded by displaying the usernames of four individuals within the Hack Club community.

	## Aftermath and Response		== Aftermath and Response ==
	The video received mixed reactions from Hack Clubbers. Some users referred to it as the “neo-nazi edit” due to its imagery and controversial symbols. The sock puppet account was subsequently banned by the Fire Department and its username was changed to "(redacted)".		The video received mixed reactions from Hack Clubbers. Some users referred to it as the “neo-nazi edit” due to its imagery and controversial symbols. The sock puppet account was subsequently banned by the Fire Department and its username was changed to "(redacted)".

	The purported video creator later posted a statement via Prox2, clarifying that the video was intended as a parody comparing Hack Club to a dictatorship in the opening segment and that certain elements were placeholders or references to internet memes.		The purported video creator later posted a statement via Prox2, clarifying that the video was intended as a parody comparing Hack Club to a dictatorship in the opening segment and that certain elements were placeholders or references to internet memes.

2025 Zach Latdroid Incident

Marcus Taisa — Tue, 08 Sep 2026 09:13:37 GMT

import md

New page

# 2025 Zach Latdroid Incident
The 2025 Zach Latdroid incident refers to the circulation of a video posted by a sock puppet account named "Zach Latdroid" on the Hack Club Slack workspace on 11 October 2025.

## Background
On 11 October 2025, a user account named "Zach Latdroid" posted a video to the Hack Club Slack workspace. The video was a critical montage of the organization's culture and operations. The name is a portmanteau of Hack Club founder Zach Latta and the word "droid."

## Content of the Video
The video was an edited montage using various clips and images to convey its critique. Its content included:

- Opening Segment: The video began with a clip from a Y2K-era presentation by Microsoft CEO Steve Ballmer. The clip was edited to feature the Hack Club flag on Ballmer's person, with logos for the Musk Foundation and GitHub Education superimposed. Ballmer's exclamation, "I love this company!" was presented as a commentary on Hack Club's perceived corporate culture.
- Audience Scene: A segment showed an audience raising their hands in a uniform manner, accompanied by the sound of a Slack notification. A later, censored version of the video replaced this scene with a error message for an inappropriate username, which was interpreted by some viewers as comparing Hack Club's administration to a dictatorship.
- Internal Mockery: The video included a screenshot of an interaction in a Slack channel, purportedly showing a member of the "Fraud Department" and another user [exchanging the onomatopoeia "meow."](https://web.archive.org/web/20251014092407mp_/https://en.wikipedia.org/wiki/Furry_fandom)
- Puppetmaster Imagery: An edited image depicted a figure labeled as the CEO with a partially robotic face (so-called "Zach Latdroid"), with strings attached to the profile pictures of users with cat avatars. This was seen as an implication that the leadership exerts control over a segment of the community.
- Critique of Operations: The montage featured a selection of posts from Confessions and referenced the 2023 pay rate of $12.50 per hour for certain HCB roles. It also included footage of someone rapidly editing event planning documents for various Hack Club programs (e.g., Power Hour, Arcade, Summer of Making), altering only minor details, to suggest a repetitive event model.
- AI and Corporate Allegiance: A segment used symbolic imagery, including a pyramid structure and corporate logos (GitHub, Microsoft, Slack), to critique the organization's relationship with Github, Microsoft and use of artificial intelligence.
- Named Shout-outs: The video concluded by displaying the usernames of four individuals within the Hack Club community.

## Aftermath and Response
The video received mixed reactions from Hack Clubbers. Some users referred to it as the “neo-nazi edit” due to its imagery and controversial symbols. The sock puppet account was subsequently banned by the Fire Department and its username was changed to "(redacted)".

The purported video creator later posted a statement via Prox2, clarifying that the video was intended as a parody comparing Hack Club to a dictatorship in the opening segment and that certain elements were placeholders or references to internet memes.

Nest

Marcus Taisa — Tue, 08 Sep 2026 09:04:04 GMT

img

← Older revision		Revision as of 09:04, 8 September 2026
(One intermediate revision by the same user not shown)
Line 1:		Line 1:
	~~# Nest~~		https://github.com/hackclub/nest/blob/9e8e55549c47beed2a91d8e21cdf23062a605d44/brand/logo.png
	Nest is a free Linux-based web hosting service provided by Hack Club, primarily aimed at teenagers and students for hosting web applications, projects, and other software. The service is modeled after the concept of a Tilde, which allows students to share computing resources in a communal environment. Nest provides users with shell access, Git repositories, and other development tools without the need for paid hosting.		Nest is a free Linux-based web hosting service provided by Hack Club, primarily aimed at teenagers and students for hosting web applications, projects, and other software. The service is modeled after the concept of a Tilde, which allows students to share computing resources in a communal environment. Nest provides users with shell access, Git repositories, and other development tools without the need for paid hosting.

	## Overview		== Overview ==
	Nest is operated and maintained by Hack Club volunteers, with infrastructure hosted on a dedicated Hetzner server located in Helsinki, Finland. It enforces user resource limits to prevent abuse and ensure equitable access for all users.		Nest is operated and maintained by Hack Club volunteers, with infrastructure hosted on a dedicated Hetzner server located in Helsinki, Finland. It enforces user resource limits to prevent abuse and ensure equitable access for all users.

	## Infrastructure		== Infrastructure ==
	~~###~~ Hardware		=== Hardware ===
	The primary server is a Hetzner AX162-R dedicated server with the following specifications:		The primary server is a Hetzner AX162-R dedicated server with the following specifications:

	AMD EPYC Genoa 9454P processor		* AMD EPYC Genoa 9454P processor
	256 GB DDR5 RAM		* 256 GB DDR5 RAM
	2 × 1.92 TB NVMe SSDs		* 2 × 1.92 TB NVMe SSDs
	Gigabit internet connection		* Gigabit internet connection
	~~###~~ Data Management		== Data Management ==
	Nest provides transparency regarding user data, including storage locations and access procedures. Data is stored primarily in users' home directories and associated databases across the Nest intranet. Nest tends to operate with the GDPR privacy framework.		Nest provides transparency regarding user data, including storage locations and access procedures. Data is stored primarily in users' home directories and associated databases across the Nest intranet. Nest tends to operate with the GDPR privacy framework.

Nest

Marcus Taisa — Tue, 08 Sep 2026 08:58:18 GMT

Created page with "# Nest Nest is a free Linux-based web hosting service provided by Hack Club, primarily aimed at teenagers and students for hosting web applications, projects, and other software. The service is modeled after the concept of a Tilde, which allows students to share computing resources in a communal environment. Nest provides users with shell access, Git repositories, and other development tools without the need for paid hosting. ## Overview Nest is operated and maintained..."

New page

# Nest
Nest is a free Linux-based web hosting service provided by Hack Club, primarily aimed at teenagers and students for hosting web applications, projects, and other software. The service is modeled after the concept of a Tilde, which allows students to share computing resources in a communal environment. Nest provides users with shell access, Git repositories, and other development tools without the need for paid hosting.

## Overview
Nest is operated and maintained by Hack Club volunteers, with infrastructure hosted on a dedicated Hetzner server located in Helsinki, Finland. It enforces user resource limits to prevent abuse and ensure equitable access for all users.

## Infrastructure
### Hardware
The primary server is a Hetzner AX162-R dedicated server with the following specifications:

AMD EPYC Genoa 9454P processor
256 GB DDR5 RAM
2 × 1.92 TB NVMe SSDs
Gigabit internet connection
### Data Management
Nest provides transparency regarding user data, including storage locations and access procedures. Data is stored primarily in users' home directories and associated databases across the Nest intranet. Nest tends to operate with the GDPR privacy framework.

Confessions

Marcus Taisa — Tue, 08 Sep 2026 08:57:08 GMT

reformatted into wikitext

← Older revision		Revision as of 08:57, 8 September 2026
Line 1:		Line 1:
	~~# Confessions~~		Confessions, sometimes stylized as <code>#confessions</code>, is an anonymous messaging channel within the Hack Club Slack. It uses an open-source bot named Prox2 to allow community members to submit messages for review and subsequent anonymous posting by the bot. The channel is governed by an informal moderation policy enforced by a volunteer Confessions Review Team (CRT).
	Confessions, sometimes stylized as `#confessions`, is an anonymous messaging channel within the Hack Club Slack. It uses an open-source bot named Prox2 to allow community members to submit messages for review and subsequent anonymous posting by the bot. The channel is governed by an informal moderation policy enforced by a volunteer Confessions Review Team (CRT).

	## Purpose		== Purpose ==
	The primary function of Confessions is to provide a platform to discuss sensitive topics, share personal struggles, offer feedback about operations in, and engage in serious discussions while maintaining pseudo-anonymity.		The primary function of Confessions is to provide a platform to discuss sensitive topics, share personal struggles, offer feedback about operations in, and engage in serious discussions while maintaining pseudo-anonymity.

	## Policy		== Policy ==
	All submissions to Confessions are reviewed by the Confessions Review Team (CRT).		All submissions to Confessions are reviewed by the Confessions Review Team (CRT).

	## Confessions Review Team		== Confessions Review Team ==
	The Confessions Review Team (CRT) is a group of community members responsible for enforcing the moderation policy. CRT members are via an application and round system. The team is independent of the Hack Club staff, though it is acknowledged that Hack Club Staff retains the ultimate authority to discontinue the Confessions.		The Confessions Review Team (CRT) is a group of community members responsible for enforcing the moderation policy. CRT members are via an application and round system. The team is independent of the Hack Club staff, though it is acknowledged that Hack Club Staff retains the ultimate authority to discontinue the Confessions.

	The CRT reviews submissions in a private channel. The bot Prox2 hashes the submitter's Slack ID to verify the submitter without revealing their identity, and the CRT does not have access to the original, unhashed identifiers.		The CRT reviews submissions in a private channel. The bot Prox2 hashes the submitter's Slack ID to verify the submitter without revealing their identity, and the CRT does not have access to the original, unhashed identifiers.

	## Reception		== Reception ==
	Confessions channel has been a significant part of the Hack Club community culture. It has been credited with providing mental health support and a channel for community feedback without fear of retribution. However, it has also been a source of community conflict, with instances of racist messages, verbal abuse, and targeted attacks being posted through Confessions, although they were stopped before they were made public by CRT.		Confessions channel has been a significant part of the Hack Club community culture. It has been credited with providing mental health support and a channel for community feedback without fear of retribution. However, it has also been a source of community conflict, with instances of racist messages, verbal abuse, and targeted attacks being posted through Confessions, although they were stopped before they were made public by CRT.


			As archived from [https://web.archive.org/web/20251031063018/https://hackclub.wiki/en/Confessions Confessions on hackclub.wiki]

Confessions

Marcus Taisa — Tue, 08 Sep 2026 08:51:26 GMT

Created page with "# Confessions Confessions, sometimes stylized as `#confessions`, is an anonymous messaging channel within the Hack Club Slack. It uses an open-source bot named Prox2 to allow community members to submit messages for review and subsequent anonymous posting by the bot. The channel is governed by an informal moderation policy enforced by a volunteer Confessions Review Team (CRT). ## Purpose The primary function of Confessions is to provide a platform to discuss sensitive t..."

New page

# Confessions
Confessions, sometimes stylized as `#confessions`, is an anonymous messaging channel within the Hack Club Slack. It uses an open-source bot named Prox2 to allow community members to submit messages for review and subsequent anonymous posting by the bot. The channel is governed by an informal moderation policy enforced by a volunteer Confessions Review Team (CRT).

## Purpose
The primary function of Confessions is to provide a platform to discuss sensitive topics, share personal struggles, offer feedback about operations in, and engage in serious discussions while maintaining pseudo-anonymity.

## Policy
All submissions to Confessions are reviewed by the Confessions Review Team (CRT).

## Confessions Review Team
The Confessions Review Team (CRT) is a group of community members responsible for enforcing the moderation policy. CRT members are via an application and round system. The team is independent of the Hack Club staff, though it is acknowledged that Hack Club Staff retains the ultimate authority to discontinue the Confessions.

The CRT reviews submissions in a private channel. The bot Prox2 hashes the submitter's Slack ID to verify the submitter without revealing their identity, and the CRT does not have access to the original, unhashed identifiers.

## Reception
Confessions channel has been a significant part of the Hack Club community culture. It has been credited with providing mental health support and a channel for community feedback without fear of retribution. However, it has also been a source of community conflict, with instances of racist messages, verbal abuse, and targeted attacks being posted through Confessions, although they were stopped before they were made public by CRT.

Main Page

Marcus Taisa — Tue, 08 Sep 2026 08:50:46 GMT

Pages (Adapted from hack.wiki)

← Older revision		Revision as of 08:50, 8 September 2026
(2 intermediate revisions by the same user not shown)
Line 3:		Line 3:
	=== News ===		=== News ===
	<rss max=4 highlight="community wiki foundation">https://news.hackclub.com/feed.xml</rss>		<rss max=4 highlight="community wiki foundation">https://news.hackclub.com/feed.xml</rss>
	[https://~~News~~.hackclub.com]		[https://news.hackclub.com Feed from news.hackclub.com]

	== Pages ==		== Pages (Adapted from hack.wiki) ==
	* [[YSWS]] & [[List of ~~YSWS~~]]		Pages from the original wiki.js wiki.
			* [[List of YSWS]] (see also the new [[YSWS]])
			* [[List of Hackathons]]
			* [[List of Community Teams]]
			* [[List of Incidents]]
			* [[Confessions]]
			* [[2024 Hack Club Confessions Controversy]]
			* [[Nest]]
			* [[Privacy concerns and data handling at Hack Club]]
			* [[2025 Zach Latdroid Incident]]

	== Getting started (Mediawiki) ==		=== Getting started (Mediawiki Tutorials) ===
	Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User's Guide] for information on using the wiki software.		Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User's Guide] for information on using the wiki software.
	* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]		* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]

List of Hackathons

Marcus Taisa — Tue, 08 Sep 2026 06:22:37 GMT

← Older revision		Revision as of 06:22, 8 September 2026
(2 intermediate revisions by the same user not shown)
Line 1:		Line 1:
	~~# List of Hackathons~~		''<big>See also [https://hackathons.hackclub.com hackathons.hackclub.com]</big>''
	See also [~~hackathons.hackclub.com](~~https://hackathons.hackclub.com)

	~~A list of teenage~~ hackathons ~~endorsed by some way by Hack Club. Some of these are part of YSWS programs, while others are unaffiliated or run by Hack clubbers~~.

	~~\|Name\|Description\|Date\|Attendance\|~~
	~~\|---\|---\|---\|---\|~~
	~~\|Undercity\|TBA\|2025-07-11 to 2025-07-14\|\|~~
	~~\|Shipwrecked\|4-day hackathon on Cathleen Stone Island\|2025-08-08 to 2025-08-11\|128\|~~
	~~\|Daydream\|12-hour or 24-hour Hackathon in various cities\|2025-09-27 to 2025-09-28[^1][^2]\|100+ cities; varied\|~~

	Archived from [https://web.archive.org/web/20251102014713mp_/https://hackclub.~~wiki/en/List_of_Hackathons~~]~~(https:~~//web.archive.org/web/20251102014713mp_/https://hackclub.wiki/en/List_of_Hackathons)

	~~[^1]: Daydream Philippines was delayed to 2025-10-05 due to Typhoon Ragasa (Typhoon Nando)~~
	~~[^2]: Daydream Delhi was delayed to 2025-10-05 due to overlap with~~
	*IITD'~~s RendezvousFest and Navaratri~~

			A curated list of teenage hackathons endorsed in some way by Hack Club. Some of these are part of YSWS programs, while others are unaffiliated or run by Hack clubbers.

	{\| class="wikitable sortable"		{\| class="wikitable sortable"
	\|+ ~~Caption text~~		\|+ List of Hackathons (Archived)
	\|-		\|-
	! Name !! Description !! Date !! Attendance		! Name !! Description !! Date !! Attendance
	\|-		\|-
	\| Undercity \|\| TBA \|\| ~~Example~~ \|\| -		\| Undercity \|\| TBA \|\| 2025-07-11 to 2025-07-14 \|\| -
	\|-		\|-
	\| Shipwrecked \|\| Cathleen Stone Island \|\| ~~Example~~ \|\| 128		\| Shipwrecked \|\| Cathleen Stone Island \|\| 2025-08-08 to 2025-08-11 \|\| 128
	\|-		\|-
	\| Daydream \|\| 12-hour or 24-hour Hackathon in various cities \|\| ~~Example~~ \|\| 100+ cities; varied		\| Daydream \|\| 12-hour or 24-hour Hackathon in various cities \|\| 2025-09-27 to 2025-09-28 <ref>Daydream Philippines was delayed to 2025-10-05 due to Typhoon Ragasa (Typhoon Nando)</ref><ref>Daydream Delhi was delayed to 2025-10-05 due to overlap with IITD's RendezvousFest and Navaratri</ref>\|\| 100+ cities; varied
	\|-		\|-
	\| Example \|\| Example \|\| Example \|\| Example		\| Example \|\| Example \|\| Example \|\| Example
	\|}		\|}


			== Bibliography ==
			# ''Archived from [https://web.archive.org/web/20251102014713mp_/https://hackclub.wiki/en/List_of_Hackathons List of Hackathons, Archived on the Internet Archive]''

			<references />

List of Hackathons

Marcus Taisa — Tue, 08 Sep 2026 06:09:56 GMT

Made page. Pasted markdownified versions of the original wiki.

New page

# List of Hackathons
*See also [hackathons.hackclub.com](https://hackathons.hackclub.com)*

A list of teenage hackathons endorsed by some way by Hack Club. Some of these are part of YSWS programs, while others are unaffiliated or run by Hack clubbers.

|Name|Description|Date|Attendance|
|---|---|---|---|
|Undercity|TBA|2025-07-11 to 2025-07-14||
|Shipwrecked|4-day hackathon on Cathleen Stone Island|2025-08-08 to 2025-08-11|128|
|Daydream|12-hour or 24-hour Hackathon in various cities|2025-09-27 to 2025-09-28[^1][^2]|100+ cities; varied|

*Archived from [https://web.archive.org/web/20251102014713mp_/https://hackclub.wiki/en/List_of_Hackathons](https://web.archive.org/web/20251102014713mp_/https://hackclub.wiki/en/List_of_Hackathons)*

[^1]: Daydream Philippines was delayed to 2025-10-05 due to Typhoon Ragasa (Typhoon Nando)
[^2]: Daydream Delhi was delayed to 2025-10-05 due to overlap with
*IITD's RendezvousFest and Navaratri

{| class="wikitable sortable"
|+ Caption text
|-
! Name !! Description !! Date !! Attendance
|-
| Undercity || TBA || Example || -
|-
| Shipwrecked || Cathleen Stone Island || Example || 128
|-
| Daydream || 12-hour or 24-hour Hackathon in various cities || Example || 100+ cities; varied
|-
| Example || Example || Example || Example
|}

List of YSWS

Marcus Taisa — Tue, 08 Sep 2026 05:59:10 GMT

← Older revision		Revision as of 05:59, 8 September 2026
Line 1:		Line 1:
			''See also: [[List of Hackathons]]''

	A [[YSWS]] ("you ship, we ship") is a program where a participant first builds and "ships" a project, and in return, they receive a reward, often hardware, from the organizer.		A [[YSWS]] ("you ship, we ship") is a program where a participant first builds and "ships" a project, and in return, they receive a reward, often hardware, from the organizer.

User:Marcus Taisa

Marcus Taisa — Tue, 08 Sep 2026 05:56:07 GMT

User account Marcus Taisa was created

Main Page

156.146.51.133 — Tue, 08 Sep 2026 05:03:18 GMT

← Older revision		Revision as of 05:03, 8 September 2026
(2 intermediate revisions by the same user not shown)
Line 1:		Line 1:
	<strong>Welcome to the (unofficial) Hack Club Wiki!</strong>		<strong>Welcome to the (unofficial) Hack Club Wiki!</strong>

			=== News ===
	<rss max=4 highlight="community wiki foundation">https://news.hackclub.com/feed.xml</rss>		<rss max=4 highlight="community wiki foundation">https://news.hackclub.com/feed.xml</rss>
			[https://News.hackclub.com]
	~~Consult the~~ [https://~~www~~.~~mediawiki~~.~~org/wiki/Special:MyLanguage/Help:Contents User's Guide~~] ~~for information on using the wiki software.~~

	== Pages ==		== Pages ==
	* [[YSWS]] & [[List of YSWS]]		* [[YSWS]] & [[List of YSWS]]

	== Getting started ==		== Getting started (Mediawiki) ==
			Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User's Guide] for information on using the wiki software.
	* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]		* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]
	* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]		* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]

Main Page

37.19.200.19 — Mon, 07 Sep 2026 10:25:35 GMT

added links

← Older revision		Revision as of 10:25, 7 September 2026
Line 4:		Line 4:

	Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User's Guide] for information on using the wiki software.		Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User's Guide] for information on using the wiki software.

			== Pages ==
			* [[YSWS]] & [[List of YSWS]]

	== Getting started ==		== Getting started ==

List of YSWS

37.19.200.19 — Mon, 07 Sep 2026 07:40:20 GMT

added proper wikitext

List of YSWS

37.19.200.19 — Mon, 07 Sep 2026 07:39:37 GMT

made page

New page

A [[YSWS]] ("you ship, we ship") is a program where a participant first builds and "ships" a project, and in return, they receive a reward, often hardware, from the organizer.

- Blueprint: Design a hardware project, up to $400 to build it! (ends 2025-12-01)
- Shiba Arcade: Make a game with Godot, earn SSS, and get invited to build an arcade in Tokyo (flight stipends available!) (ends 2025-10-20)
- Siege: Code every week, get prizes. Make it to the end, get a framework! (ends 2025-11-30)
- Emerge: create an emergent behaviour, place pixels on the group canvas, get the canvas shipped to you! (ends 2025-11-01)
- Reactive: Ship a website built with React, get $15 to buy a domain. (ends 2025-10-16)
- Fanpage: Ship a project that celebrates a fandom, and we ship you something related to it! (ends 2025-10-17)
- Hackberry: Built a machine learning project in python, get a personalized raspberry pi kit! (ends 2025-10-13)
- Waveform: Make your own waveform visualizer, get a grant to buy music (ends 2025-09-26)
- birthday-cards: You ship a birthday themed project we ship a birthday card! (ends 2026-08-12)
- Miniverge: Spend 2 hours on a bot, get stickers and a chance for a Blåhaj or Minecraft! (ends 2025-09-28)
- Penumbra: Make shaders, and we'll ship you GPUs and posters! (ends 2025-10-08)
- Playphone: Work together to built a godot game, get a custom hackclub badge (ends 2025-12-01)
- Clutter: You ship something to organize your digital life. We ship you a grant to buy something to organize your physical life. (ends 2025-09-17)
- Fusering: Design a keyring, get your keyring and a carabiner to hang it from! (ends 2025-09-30)
- iFrame: Draw or edit images using any programming language and we will hang your custom image on HQ wall and send a copy to you
- BakeBuild: Design a cookie cutter, get it shipped!
- HackCraft: Create a Minecraft mod, get Stickers, Minecraft or a server and terraria!
- Summer of Making: Build stuff. Get stuff. Repeat. (ends 2025-09-30)
- Sprig: Build a JS game and play it on your own console.
- Boba Drops: Build a website and get boba!

''Originally archived from https://web.archive.org/web/20251011134836mp_/https://hackclub.wiki/en/List_of_You_Ship_We_Ships''

YSWS

37.19.200.19 — Mon, 07 Sep 2026 07:38:18 GMT

added list of ysws link

← Older revision		Revision as of 07:38, 7 September 2026
(2 intermediate revisions by the same user not shown)
Line 1:		Line 1:
	~~# YSWS~~
	Hack Club YSWS programs, short for "You Ship, We Ship", are a part of the main divisions of programs run by Hack Club. Participants develop their own projects, and in return, receive support to incentivize them to work on their next project.		Hack Club YSWS programs, short for "You Ship, We Ship", are a part of the main divisions of programs run by Hack Club. Participants develop their own projects, and in return, receive support to incentivize them to work on their next project.
	The organisation of YSWSes are governed by HQ, and rewards around the principles of Hacker Value.		The organisation of YSWSes are governed by HQ, and rewards around the principles of Hacker Value.

	~~## Philosophy~~		Refer to [[List of YSWS]] for a dynamic list of all YSWS programs.
	>Good hackers / engineers are never quite an employee. They can be managed, but rarely directed. They follow their own curiosity their own way, always honestly, often infuriatingly, along with their sense of ~~taste~~ for ~~which problems are interesting and which aren't~~.
	~~>-Deven~~

	## References		== Philosophy ==
	1. [~~The Plan For Hack Club World Dominance notes.deven.dev](~~https://notes.deven.dev/posts/the-plan-for-hack-club-world-dominance)		<blockquote>
			Good hackers / engineers are never quite an employee. They can be managed, but rarely directed. They follow their own curiosity their own way, always honestly, often infuriatingly, along with their sense of taste for which problems are interesting and which aren't.
			-Deven
			</blockquote>

			== References ==
			1. [https://notes.deven.dev/posts/the-plan-for-hack-club-world-dominance Plan For Hack Club World Dominance notes.deven.dev]

Main Page

37.19.200.19 — Mon, 07 Sep 2026 05:56:11 GMT

← Older revision		Revision as of 05:56, 7 September 2026
Line 1:		Line 1:
	<strong>~~MediaWiki has been installed.~~ Welcome to the Hack Club Wiki!</strong>		<strong>Welcome to the (unofficial) Hack Club Wiki!</strong>

	<rss max=4 highlight="community wiki foundation">https://news.hackclub.com/feed.xml</rss>		<rss max=4 highlight="community wiki foundation">https://news.hackclub.com/feed.xml</rss>

YSWS

37.19.200.19 — Mon, 07 Sep 2026 05:46:47 GMT

Created page with "# YSWS Hack Club YSWS programs, short for "You Ship, We Ship", are a part of the main divisions of programs run by Hack Club. Participants develop their own projects, and in return, receive support to incentivize them to work on their next project. The organisation of YSWSes are governed by HQ, and rewards around the principles of Hacker Value. ## Philosophy >Good hackers / engineers are never quite an employee. They can be managed, but rarely directed. They follow thei..."

New page

# YSWS
Hack Club YSWS programs, short for "You Ship, We Ship", are a part of the main divisions of programs run by Hack Club. Participants develop their own projects, and in return, receive support to incentivize them to work on their next project.
The organisation of YSWSes are governed by HQ, and rewards around the principles of Hacker Value.

## Philosophy
>Good hackers / engineers are never quite an employee. They can be managed, but rarely directed. They follow their own curiosity their own way, always honestly, often infuriatingly, along with their sense of taste for which problems are interesting and which aren't.
>-Deven

## References
1. [The Plan For Hack Club World Dominance notes.deven.dev](https://notes.deven.dev/posts/the-plan-for-hack-club-world-dominance)

← Older revision		Revision as of 07:40, 7 September 2026
Line 1:		Line 1:
	A [[YSWS]] ("you ship, we ship") is a program where a participant first builds and "ships" a project, and in return, they receive a reward, often hardware, from the organizer.		A [[YSWS]] ("you ship, we ship") is a program where a participant first builds and "ships" a project, and in return, they receive a reward, often hardware, from the organizer.

	- Blueprint: Design a hardware project, up to $400 to build it! (ends 2025-12-01)		* Blueprint: Design a hardware project, up to $400 to build it! (ends 2025-12-01)
	- Shiba Arcade: Make a game with Godot, earn SSS, and get invited to build an arcade in Tokyo (flight stipends available!) (ends 2025-10-20)		* Shiba Arcade: Make a game with Godot, earn SSS, and get invited to build an arcade in Tokyo (flight stipends available!) (ends 2025-10-20)
	- Siege: Code every week, get prizes. Make it to the end, get a framework! (ends 2025-11-30)		* Siege: Code every week, get prizes. Make it to the end, get a framework! (ends 2025-11-30)
	- Emerge: create an emergent behaviour, place pixels on the group canvas, get the canvas shipped to you! (ends 2025-11-01)		* Emerge: create an emergent behaviour, place pixels on the group canvas, get the canvas shipped to you! (ends 2025-11-01)
	- Reactive: Ship a website built with React, get $15 to buy a domain. (ends 2025-10-16)		* Reactive: Ship a website built with React, get $15 to buy a domain. (ends 2025-10-16)
	- Fanpage: Ship a project that celebrates a fandom, and we ship you something related to it! (ends 2025-10-17)		* Fanpage: Ship a project that celebrates a fandom, and we ship you something related to it! (ends 2025-10-17)
	- Hackberry: Built a machine learning project in python, get a personalized raspberry pi kit! (ends 2025-10-13)		* Hackberry: Built a machine learning project in python, get a personalized raspberry pi kit! (ends 2025-10-13)
	- Waveform: Make your own waveform visualizer, get a grant to buy music (ends 2025-09-26)		* Waveform: Make your own waveform visualizer, get a grant to buy music (ends 2025-09-26)
	- birthday-cards: You ship a birthday themed project we ship a birthday card! (ends 2026-08-12)		* birthday-cards: You ship a birthday themed project we ship a birthday card! (ends 2026-08-12)
	- Miniverge: Spend 2 hours on a bot, get stickers and a chance for a Blåhaj or Minecraft! (ends 2025-09-28)		* Miniverge: Spend 2 hours on a bot, get stickers and a chance for a Blåhaj or Minecraft! (ends 2025-09-28)
	- Penumbra: Make shaders, and we'll ship you GPUs and posters! (ends 2025-10-08)		* Penumbra: Make shaders, and we'll ship you GPUs and posters! (ends 2025-10-08)
	- Playphone: Work together to built a godot game, get a custom hackclub badge (ends 2025-12-01)		* Playphone: Work together to built a godot game, get a custom hackclub badge (ends 2025-12-01)
	- Clutter: You ship something to organize your digital life. We ship you a grant to buy something to organize your physical life. (ends 2025-09-17)		* Clutter: You ship something to organize your digital life. We ship you a grant to buy something to organize your physical life. (ends 2025-09-17)
	- Fusering: Design a keyring, get your keyring and a carabiner to hang it from! (ends 2025-09-30)		* Fusering: Design a keyring, get your keyring and a carabiner to hang it from! (ends 2025-09-30)
	- iFrame: Draw or edit images using any programming language and we will hang your custom image on HQ wall and send a copy to you		* iFrame: Draw or edit images using any programming language and we will hang your custom image on HQ wall and send a copy to you
	- BakeBuild: Design a cookie cutter, get it shipped!		* BakeBuild: Design a cookie cutter, get it shipped!
	- HackCraft: Create a Minecraft mod, get Stickers, Minecraft or a server and terraria!		* HackCraft: Create a Minecraft mod, get Stickers, Minecraft or a server and terraria!
	- Summer of Making: Build stuff. Get stuff. Repeat. (ends 2025-09-30)		* Summer of Making: Build stuff. Get stuff. Repeat. (ends 2025-09-30)
	- Sprig: Build a JS game and play it on your own console.		* Sprig: Build a JS game and play it on your own console.
	- Boba Drops: Build a website and get boba!		* Boba Drops: Build a website and get boba!

	''Originally archived from https://web.archive.org/web/20251011134836mp_/https://hackclub.wiki/en/List_of_You_Ship_We_Ships''		''Originally archived from https://web.archive.org/web/20251011134836mp_/https://hackclub.wiki/en/List_of_You_Ship_We_Ships''