<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>Slacker News</title><description>Official news from the Hack Club Slack.</description><link>https://news.hackclub.com/</link><item><title>AI time tracking</title><link>https://news.hackclub.com/news/ai-time-tracking/</link><guid isPermaLink="true">https://news.hackclub.com/news/ai-time-tracking/</guid><description>The hardest problem to solve is AI time tracking. How can we figure out how many hours of productive struggle someone spends toward a project when building it with AI? To that end, I&apos;m excited to announce the biggest bounty in Hack Club&apos;s history: $10,000 USD to build an open source AI time tracking tool.</description><pubDate>Wed, 18 Nov 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;Yesterday I wrote about a vision for an AI native Hack Club.&lt;/p&gt;&lt;p&gt;The hardest problem to solve is AI time tracking. How can we figure out how many hours of productive struggle someone spends toward a project when building it with AI?&lt;/p&gt;&lt;p&gt;So, to that end, I&apos;m excited to announce the biggest bounty in Hack Club&apos;s history: $10,000 USD to build an open source AI time tracking tool.&lt;/p&gt;&lt;p&gt;Here are the requirements:&lt;/p&gt;&lt;p&gt;1. It must be open source under the AGPLv3 license.&lt;/p&gt;&lt;p&gt;2. It must accurately track the hours of productive struggle that teenagers spend building awesome projects with AI, like this Counter Strike 2 browser port by Rowan, age 17.&lt;/p&gt;&lt;p&gt;3. It must be meaningful and motivating to use in it and of itself, and not just an anti-fraud tool. Many teenagers are interested in self-improvement. This should be an amazing tool they want to install and use to self-improve, regardless of any You Ship, We Ship incentives. One of the things I love about Hackatime is that it helps me track and feel motivated to work on personal projects I never submit to Hack Club programs.&lt;/p&gt;&lt;p&gt;4. It must track time passively. The best thing about Hackatime is that you don&apos;t need to think about time tracking. When you are in an intense flow state for hours working on your project, Hackatime counts that time. When you jump into your project for 5 minutes before school, Hackatime counts that time. When you are multitasking and jump between 5 different projects in an afternoon, Hackatime accurately counts that time for each project. This solution must work passively too.&lt;/p&gt;&lt;p&gt;5. It must have a centralized server with accounts, public-by-default user profiles, projects, git integration, and a stats dashboard that updates in real-time as time is logged.&lt;/p&gt;&lt;p&gt;6. It must be privacy friendly in its approach and be something most privacy conscious users are comfortable installing and using.&lt;/p&gt;&lt;p&gt;7. It must work with all AI models and all harnesses (or at least support the most popular ones starting out and have a plugin approach where integrations can be built for every use case in the future).&lt;/p&gt;&lt;p&gt;8. It must support all 3 popular operating systems (Windows, Mac, Linux) and work on low spec computers. The average Hack Clubber is on a 10 year old Windows laptop!&lt;/p&gt;&lt;p&gt;9. It must be trustworthy. When we ran Hack Club High Seas, the first event with Hackatime, most hours submitted were valid. In Hack Club Stardance, which ran this past summer, 123,400 Hackatime hours were submitted and so far we&apos;ve only been able to approve 27,600 (which means we hand-reviewed and validated them as hours of productive struggle). Most of this isn&apos;t fraud. Many were hours where we felt the person wasn&apos;t pushing themselves, so we had to deflate to only the hours we felt could be justified as productive struggle. Another big contributor was people using AI without proper self-declaration. But the point holds: for the most part, an hour submitted via this new system should equal 1 hour of actual productive struggle toward a shipped project.&lt;/p&gt;&lt;p&gt;10. Submitted hours must be auditable by an external party (ex. program authors, reviewers, and Fraud Squad) to validate there is no time exaggeration, fraud, and that each hour is an actual hour of productive struggle. There can be different privacy guarantees for logged hours vs. submitted hours. For example, if it uses a timelapsing approach, perhaps the timelapses for all logged hours stay locally on your computer and only submitted hours are uploaded to the server.&lt;/p&gt;&lt;p&gt;11. The hosting cost cannot exceed $500 USD/month for 15,488 monthly active users logging 109,759 hours per month (these are Hackatime&apos;s stats for the last 30 days). Hackatime&apos;s hosting bill for its overpowered server is currently $213 USD/month. I just SSHed into its server and for the past hour it has averaged 10% of CPU use on a machine with 32 cores, 65 out of 192 GB of RAM, 1 out of 4 TB of storage, 1 MB/s of network activity, and 60 MB/s of disk read - so it still has plenty of headroom. The effective monthly hosting cost for Hackatime based on its resource usage is $55/month.&lt;/p&gt;&lt;p&gt;Criteria for acceptance: The first time tracking system that meets the above requirements and is used to track 1,000 weighted projects in the Hack Club Unified Projects DB wins this bounty. This can be a completely new piece of software, an improved version of Hackatime or Lapse, or an approach we haven&apos;t even thought of yet. This doesn&apos;t need to be built on top of Hackatime.&lt;/p&gt;&lt;p&gt;This bounty is open to current Hack Clubbers, alumni, teen contractors, and staff. It can be won by an individual or a group, but if it&apos;s won by a group there must be a group leader who submits on behalf of the group and is responsible for communicating the final split. If you are an existing contractor in Hack Club, you cannot log work hours toward this bounty - you must do this outside the scope of your existing contract unless otherwise approved by me and me alone. If you are Hack Club staff and pursue this completely outside of your normal workday, you are eligible for the full $10,000. If you pursue it during your workday, you will receive $5,000 instead of $10,000 because you will already be getting compensated for your time.&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>A vision for an AI native Hack Club</title><link>https://news.hackclub.com/news/vision-for-an-ai-native-hack-club/</link><guid isPermaLink="true">https://news.hackclub.com/news/vision-for-an-ai-native-hack-club/</guid><description>We need to have a better approach to AI than how we handle it today. If some of the coolest projects made by Hack Clubbers don’t count in most Hack Club programs, we need to improve our approach. But how do we do that without rewarding slop?</description><pubDate>Tue, 17 Nov 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;AI is changing what it means to be a programmer. Soon it will change what it means to be a hardware engineer too.&lt;/p&gt;&lt;p&gt;A year ago, the projects in Hack Club that most relied on AI were slop. Today, many of the coolest projects built by Hack Clubbers are 100% written by AI - like cs2go.3kh0.net, a Counter-Strike 2 port to the browser by Rowan, age 17.&lt;/p&gt;&lt;p&gt;These cool projects take actual skill to build. You can’t one-shot them. Most people who use AI aren’t yet capable of building them. And learning how to use AI effectively to build stuff like this is actually a lot like learning to code. It’s a distinct skill, you get better at it through practice, and it applies across building many different types of projects.&lt;/p&gt;&lt;p&gt;Many of you probably heard about some of the Millennium Prize Problems being solved with AI. I’ve been enjoying reading Terrance Tao’s blog. He’s a famous mathematician and talks about how he uses AI. Interestingly, the way he uses AI is very similar to the way I see the most effective builders I know using it - and it’s different from how most people use AI. He and other mathematicians are practicing the same meta-skill that the best AI builders like Rowan in Hack Club have developed.&lt;/p&gt;&lt;p&gt;It’s clear that if Hack Club wants to help people become technically skilled, form lifelong friendships, and build personal agency, we need to have a better approach to AI than how we handle it today. If some of the coolest projects made by Hack Clubbers don’t count in most Hack Club programs, we need to improve our approach.&lt;/p&gt;&lt;p&gt;But how do we do that without rewarding slop?&lt;/p&gt;&lt;p&gt;Here’s my pitch for an AI native Hack Club:&lt;/p&gt;&lt;p&gt;1. We must solve AI time tracking. Hours of productive struggle toward shipped projects is still the right metric because one-shotting takes 2 minutes of productive struggle while intense reverse engineering takes dozens of hours, but Hackatime doesn’t currently count how much time you are actively solving problems when building with AI. It just counts how active your AI agent is. We must either improve Hackatime to count this time accurately, or develop a new tool that can answer the question: “how many hours of productive struggle did I spend building this project?“. Importantly, not all hours of screen time or time prompting is productive struggle - if you are in dark flow or doing the same thing over and over again, that shouldn’t count.&lt;/p&gt;&lt;p&gt;2. We must do way more in-person events. How can we create a world where events like Hack Club Haven happen 5 times per year? Last weekend, 6,017 teenagers checked into an in-person Haven event on Hack Club Attend, 2,161 games were made by 4,843 teens for the theme “Bounce Back”, and 2,864 people gave feedback with an average NPS of 71 (scored from -100 to 100). That is absolutely incredible and probably the largest and highest quality high school game jam of all time! And there are 13 more Havens happening next weekend! We need to be doing stuff like this all the time. Hats off to the Haven team.&lt;/p&gt;&lt;p&gt;3. We must change the definition for what counts as a shipped project in Hack Club to include: “The project must do what it says it does”. The biggest problem with most AI slop projects is that they don’t actually work. Previously, whether a technical project was deployed was a pretty good proxy for whether it did what it said it did. Most people who put in the effort to ship their project also tested it to make sure it actually worked. AI has made it way easier to ship projects, so this is no longer a good enough proxy and we must start checking this ourselves.&lt;/p&gt;&lt;p&gt;4. We must introduce external feedback to You Ship, We Ships. My belief is that if you want to become great at building projects, the trifecta is as follows: 1) you must ship lots of projects, 2) you must spend many hours of productive struggle on those projects, 3) you must get and incorporate feedback from the outside world into your projects. Today we measure #1 and #2, but don’t yet measure #3 even though all the best projects in Hack Club include it.&lt;/p&gt;&lt;p&gt;We need to change this. The more hours of productive struggle you spend, the more you need feedback feeding back into your projects. That can look like getting actual users, posting your work on Reddit and getting people to engage with it, or just having instrumentation in place to see that your project actually works (ex. if you say your app has a login function, there needs to be analytics showing that people have actually logged in and used it - even if it’s a small number of people).&lt;/p&gt;&lt;p&gt;What if we built a free service like Hackatime that was kind of like Posthog? Hack Clubbers could incorporate it into their apps and through that, they - and we - could see their projects getting external feedback through usage.&lt;/p&gt;&lt;p&gt;5. We must continue running incredible, life-changing, high-agency adventures like Hack Club Fallout in China, Hack Club Undercity in San Francisco, The Hacker Zephyr in a train across the USA, and Hack Club Infill in Denver. So many Hack Clubbers have formed their closest friendships and had formative experiences like traveling alone for the first time through these events.&lt;/p&gt;&lt;p&gt;Join upcoming ones like Hack Club Phantom in Philadelphia, Hack Club Taiyaki in Japan, Hack Club Fallen in China, and Hack Club Crossroads in a train across Europe!&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>How to Pitch a YSWS, the Right Way</title><link>https://news.hackclub.com/essays/how-to-pitch-a-ysws/</link><guid isPermaLink="true">https://news.hackclub.com/essays/how-to-pitch-a-ysws/</guid><description>Hack Clubbers suggest YSWS ideas every day, and most never get a sponsor. That doesn&apos;t mean the idea was bad. The answer lies in the pitch.</description><pubDate>Thu, 05 Nov 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;Editor&apos;s note: adapted from a Slack canvas by @ren&lt;/p&gt;&lt;p&gt;Hack Clubbers suggest YSWS ideas every day, but most end up missing the bar for sponsorship. This means the idea can&apos;t be successful, right? Wrong. The answer lies in the pitch.&lt;/p&gt;&lt;p&gt;Over the last few months working at HQ, I&apos;ve noticed that we have practically unlimited, amazing ideas for programs, but loads of them never make it into existence. They disappear into the void forever because it seems like no one wants to give them a shot!&lt;/p&gt;&lt;p&gt;The truth is that a good pitch can exponentially increase your chances of sponsorship. Since your pitch gives HQ the first glimpse of how your program will run and at its chances of success, it&apos;s important to get it right the first time. So, here&apos;s how to pitch a YSWS for the highest chance of getting sponsored: the right way.&lt;/p&gt;&lt;p&gt;You have an awesome YSWS idea, but you need a sponsor[^sponsor]! What do you do? (And what don&apos;t you do?)&lt;/p&gt;&lt;p&gt;First, I recommend making a good YSWS draft. That could be a one-page Google Doc (recommended!), alongside a website, artwork, or anything else that proves you can execute your idea. Gap years[^gappies] take on a lot of risk when they sponsor something, so we&apos;re only likely to sponsor things we think will succeed!&lt;/p&gt;&lt;p&gt;Open with your hook. That&apos;s a one-sentence description of your YSWS. For example:&lt;/p&gt;&lt;p&gt;Say whether your YSWS is general or themed.&lt;/p&gt;&lt;p&gt;If it&apos;s themed, make sure your participants still make technical projects[^technical]: coding or electronics! Non-technical projects can&apos;t be shipped to Unified[^unified], so non-technical YSWSs are unlikely to get sponsored. No ships in Unified means no weighted projects[^wp], and no weighted projects means no funding.&lt;/p&gt;&lt;p&gt;Include an example project!&lt;/p&gt;&lt;p&gt;The best way to prove you can support your participants is to do your own program. Incoming gap years are told: &quot;You are the CEO of your own program, so you are responsible for all areas of your program.&quot; That applies to your events too! Your sponsor will help you, but you need to put yourself in your participants&apos; shoes and get a feel for your own program. An example project also helps gappies understand what your program is about.&lt;/p&gt;&lt;p&gt;Know your target audience.&lt;/p&gt;&lt;p&gt;Have a budget.&lt;/p&gt;&lt;p&gt;Do a little research into the weighted projects system. It&apos;s how your program will fund itself, so you should really have an idea of how it works. Try to budget around $5 per hour of coding, in line with what gappies are told to aim for. If you&apos;re pitching an in-person event, think about how you&apos;ll fund that too. Venues, transport, food and lodging all cost money. Where is it coming from?&lt;/p&gt;&lt;p&gt;Be realistic. Can you execute this with your current skill set? If not, do you have a realistic plan for how you&apos;ll make it happen? Show us!&lt;/p&gt;&lt;p&gt;Be open to changing and iterating on your idea!&lt;/p&gt;&lt;p&gt;A gap year asking for changes is not a no. It means we&apos;d be open to sponsoring your program with a few tweaks. Changes are usually requested for a reason, often an incompatibility with the Unified DB, the budget, or participant safety.&lt;/p&gt;&lt;p&gt;Second: don&apos;t just spam everyone at HQ with your pitch. That&apos;s a sure-fire way to not get a sponsor, and to annoy literally everyone in the office. We talk to each other about these things. Once a pitch has reached a few of us, it&apos;s reached most of us.&lt;/p&gt;&lt;p&gt;Do your research! Like everyone else, we gappies have our own interests, and those shape what we&apos;re willing to sponsor. Sending a software-focused gappie a pitch for a hardware hackathon probably won&apos;t get you sponsored, and it wastes both your time and theirs. Target your pitches for a higher success rate . You can get an idea of someone&apos;s niche by checking out the programs they&apos;ve run before .&lt;/p&gt;&lt;p&gt;Please don&apos;t DM every single gap year. There&apos;s a reason most of the gappie lists floating around Slack say not to do this. We talk to each other, and spamming basically guarantees you don&apos;t get sponsored . When we decide what to sponsor, we&apos;re also deciding who we want to work with! A good first impression makes your pitch way more likely to get sponsored.&lt;/p&gt;&lt;p&gt;A surprising number of people forget that we all work in the same office five days a week.&lt;/p&gt;&lt;p&gt;So what are you waiting for? Go make that YSWS idea real!&lt;/p&gt;&lt;p&gt;[^sponsor]: Sponsor: the gap year who provides the funding and Hack Club infrastructure to run your program, in exchange for the weighted projects it generates.&lt;/p&gt;&lt;p&gt;[^gappies]: Gap years / gappies: in-person staff at Hack Club HQ in Vermont, working full-time for a year on the YSWS team.&lt;/p&gt;&lt;p&gt;[^technical]: Technical project: a project that can be &quot;shipped&quot; to the Unified DB and receive funding based on the time spent making it.&lt;/p&gt;&lt;p&gt;[^unified]: Unified / Unified DB / the DB: the big Airtable database where every project shipped to Hack Club ends up.&lt;/p&gt;&lt;p&gt;[^wp]: Weighted projects (WPs): the metric gap years are measured on, also used to allocate funding to programs. 1 WP = 10 hours of coding = $85, with $50 of that used for prize fulfillment.&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>How to Get Prometheus Powers</title><link>https://news.hackclub.com/news/how-to-become-a-promethean/</link><guid isPermaLink="true">https://news.hackclub.com/news/how-to-become-a-promethean/</guid><description>When someone asks me for Prometheus powers, I look for three things: you’re asking about a channel that is a public utility, you haven’t done anything shady or immature, and you have a vision for making the channel great.</description><pubDate>Thu, 22 Oct 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;I’m getting more and more requests to use Prometheus. This is great! Demand is the mark of a good product.&lt;/p&gt;&lt;p&gt;Managing all these requests is getting to be a lot. But rather than just posting a public policy and leaving it at that, let me explain why that’s the policy, and how it could change.&lt;/p&gt;&lt;p&gt;(I also give them out at the request of HQ employees to manage channels for their programs)&lt;/p&gt;&lt;p&gt;I want the Slack to have great channels where people love spending time. Prometheus a tool. My vision is bigger than the tool and I want yours to be too. I want to see that you have a plan for an awesome channel, and then you can have Prometheus to make it happen.&lt;/p&gt;&lt;p&gt;Public personal channels, I’m less sure about. The current problem is oversight: the powers could be abused, and I need to oversee the channels personally. There are far too many personal channels to apply it to all of them, and I don’t want to take on the job of picking and choosing which channels get it. That will create ugly conflicts, and leave me too little time for other projects.&lt;/p&gt;&lt;p&gt;What makes sense in a community of 1500 won’t always make sense in a community of 3000, or 6000. We can’t stop the Slack from changing, but we can shape the change. I’m thinking a lot about what the Slack should look like as it grows.&lt;/p&gt;&lt;p&gt;I would be open to using Prometheus more widely if I saw good solutions to these problems. This piece is my invitation to you, to think about them and share your ideas.&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>Not All Hours Can be Trusted Equally</title><link>https://news.hackclub.com/opinion/nonlinear-ysws-rewards-fraud/</link><guid isPermaLink="true">https://news.hackclub.com/opinion/nonlinear-ysws-rewards-fraud/</guid><description>Hack Club has a truly interesting structure for You Ship, We Ship projects. We have so many YSWS of all shapes and sizes, all with their quirks, benefits, and themes.</description><pubDate>Mon, 19 Oct 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;@kman here :)&lt;/p&gt;&lt;p&gt;Hack Club has a truly interesting structure for You Ship, We Ship projects. We have so many YSWS of all shapes and sizes, all with their quirks, benefits, and themes.&lt;/p&gt;&lt;p&gt;This format is extremely unique, but allows us to do some really cool things! It allows us to test ideas, improve upon each other, and most of all, employ different techniques to achieve the same goal: ship cool stuff to teenagers making cool projects.&lt;/p&gt;&lt;p&gt;Nearly every YSWS does it differently: #macando used tiers, #stardance uses peer-reviewing, #pixl uses a ladder that allows you to get better rates as you ship more, #wonders (upcoming) completely ignores hours and payouts and just ships you something cool for the work you do. And I think we can take advantage of this structure to solve (some) of our fraud problems.&lt;/p&gt;&lt;p&gt;On one hand, it&apos;s unfair on participants from these other countries that are honestly putting the work in, if we lower regional rates. Because, as Zach mentioned, electronics and flights cost the same no matter where you get them from. In fact, after doing a bit of research on about 10 items in the Stardance shop, most cost about the same if not more to purchase in India.&lt;/p&gt;&lt;p&gt;On the other hand, it&apos;s true that where you are plays a factor. Buying a 3D printer in India is objectively harder (from a monetary perspective, not fulfillment) than buying a 3D printer in the US. Therefore, the argument can be made that Hack Club should reflect that to some extent.&lt;/p&gt;&lt;p&gt;One downside to this whole system is that it might encourage even more inflation of hours. However, I think this is already incentivized a lot, and I trust in Fraud Squad to be able to detect this pretty easily.&lt;/p&gt;&lt;p&gt;I understand beginners might be disappointed by this model. That’s why I suggest having more beginner-friendly YSWSs and opportunities for us to “waive” the reduced rates and give a better rate instead, maybe by holding huddles where if you ship a project by the end, you get a better rate, or having extremely specific guides they can follow.&lt;/p&gt;&lt;p&gt;I’m also not very sure how hardware works… (I’ve never shipped hardware) so I’ll leave that up to you.&lt;/p&gt;&lt;p&gt;Thanks to @Elliot-entity for helping me develop these ideas.&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>CRT is back with a new bot</title><link>https://news.hackclub.com/news/crt-is-back/</link><guid isPermaLink="true">https://news.hackclub.com/news/crt-is-back/</guid><description>Prox2 vanished from Hack Club on September 1st. Since then, #confessions has been full of normal humans and there has been a lack of anonymous posts in #meta too! The community has been asking for answers for weeks, and we finally have one.</description><pubDate>Wed, 30 Sep 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;Prox2 vanished from Hack Club on September 1st. Since then, #confessions has been full of normal humans and there has been a lack of anonymous posts in #meta too! The community has been asking for answers for weeks, and we finally have one.&lt;/p&gt;&lt;p&gt;CRT as it was is no more. @Jeremy and I have been working to rework how the CRT works at a fundamental level. You may have many questions, so here are a few I can answer now:&lt;/p&gt;&lt;p&gt;Why?&lt;/p&gt;&lt;p&gt;And then comes Z! Jokes aside, CRT has been a great thing that has served us for quite some time, but it badly needed some rganizational and technical improvements. The old CRT was fragmented, and it was hard to get things done. For example, CRT ran applications for new members on July 21st, but nothing has happened with them since. This new CRT has a bit more structure and should keep things moving along.&lt;/p&gt;&lt;p&gt;How secure is this thing?&lt;/p&gt;&lt;p&gt;The bot has two modes to send confessions. One that is tied to a hashed and salted version of your Slack ID and one that is tied to a generated key. To quote the README:&lt;/p&gt;&lt;p&gt;“the submission form lets you choose a salted account hash or a generated private reply key. neither mode stores your raw Slack user ID. the private key mode needs both the key and the original account for replies, reactions, and withdrawal. you gotta save the key when it is shown, if it is lost, then its gg. salted account hashes recognize your account automatically, but in theory, someone with database access can try to crack them against known Slack user IDs. however, the owl bot running in hack club is hosted by trusted members of the community and less people have access to the owl database than the original prox2 database!&lt;/p&gt;&lt;p&gt;How do I use the new bot?&lt;/p&gt;&lt;p&gt;You can use the bot by running /owl or DMing the bot directly: redirects to Owl&apos;s profile&lt;/p&gt;&lt;p&gt;But this new team is led by people who work closely with HQ! How are you going to make sure that the CRT is independent?&lt;/p&gt;&lt;p&gt;Good point! In the interest of full disclosure, Jeremy and I (Rowan) are both part of HQ. We both get paid by HQ for the work we do for it. However, we are not going to let that affect how the CRT operates. The CRT is a community team and it will be run by the community. We both have a history of not letting our other positions affect how we act in the community. Personally, I have been doing work for HQ for quite some time and yet I still call them out. I will continue to do so as part of the CRT. Jeremy has a similar history and I trust him to do the same.&lt;/p&gt;&lt;p&gt;A new bot? Where is the source code?&lt;/p&gt;&lt;p&gt;Glad you asked! You can find it at hackclub-community/owl. Anyone is welcome to submit pull requests and I will try to review them regularly.&lt;/p&gt;&lt;p&gt;Where is the bot hosted?&lt;/p&gt;&lt;p&gt;The bot is hosted on a server from Njalla, a trusted privacy-focused hosting provider. Only I (Rowan) and Jeremy have access to the server. The bot will never be hosted on infrastructure that is owned, paid for, or controlled by HQ.&lt;/p&gt;&lt;p&gt;For comparison, the old Prox2 database (aka where all the confessions were stored) was hosted on a DigitalOcean droplet that was paid for by HQ as part of the long gone hack-as-a-service project. HQ had full access to the server at all times. Owl will be more independent than Prox2 ever claimed to be.&lt;/p&gt;&lt;p&gt;What about the old confessions?&lt;/p&gt;&lt;p&gt;Ani and I have copies of the old database in case they are needed. However, we do not intend to restore old confessions. Any confessions made via Prox2 cannot be replied to. If you submitted a confession to Prox2 during the downtime, it is lost.&lt;/p&gt;&lt;p&gt;How can I join the new CRT?&lt;/p&gt;&lt;p&gt;We are not looking to bring on new people right now. We will mostly be pulling in the existing CRT members who would like to join. However, applications are still open, and we will keep them in case we decide to bring on new people. Do not treat this as a promise that the same application will be used in the future; we may change this.&lt;/p&gt;&lt;p&gt;Conclusion&lt;/p&gt;&lt;p&gt;Sorry the wait took so long. Confessions is such a great part of the community and it&apos;s awesome to bring it back. We will be tweaking the bot and the team over time, so if you have any feedback, please let us know in #confessions-meta. Enjoy&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>Your Slack Profile Now Shows When You Last Shipped a Project</title><link>https://news.hackclub.com/news/last-shipped-at/</link><guid isPermaLink="true">https://news.hackclub.com/news/last-shipped-at/</guid><description>The desert of theory goes on forever, and you can wander it forever imagining things that wouldn&apos;t really work, believing they would. Only by doing will you finally know. And actually shipping a project teaches another lesson that theorizing can&apos;t: you (yes, you!) can change things. If you don&apos;t like your choices, you can color outside the lines and make new choices, even if an adult never gave you permission.</description><pubDate>Tue, 29 Sep 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;The desert of theory goes on forever, and you can wander it forever imagining things that wouldn&apos;t really work, believing they would. Only by doing will you finally know. And actually shipping a project teaches another lesson that theorizing can&apos;t: you (yes, you!) can change things. If you don&apos;t like your choices, you can color outside the lines and make new choices, even if an adult never gave you permission.&lt;/p&gt;&lt;p&gt;That&apos;s why we&apos;re here. We want you to make friends. But we want you to make friends by bonding over shipping projects. We want you to learn. But we want you to learn by shipping projects. We want to change your life. But we want to change your life by shipping projects.&lt;/p&gt;&lt;p&gt;So, did you ship yet? If not, why not? If yes, how long ago? Are you working on shipping something else? If not, why not? What are you doing to keep growing? What if you’re wandering the desert of theory?&lt;/p&gt;&lt;p&gt;Your Slack profile now has an API-controlled field &quot;Last shipped a project&quot;. Special thanks to @nora for pushing aside the soldering irons and ethernet switches on her desk long enough to make this happen. The Slack API documentation is...uhh...well, I would never criticize it for having too much information.&lt;/p&gt;&lt;p&gt;This is a device to help you hold yourself accountable. Do you feel subtly pressured to ship a project now? That&apos;s the idea! You don&apos;t have to, but...maybe you want to? To get that number down? Good, good. If you&apos;re new, this encourages you to break the Ship Barrier, because there&apos;s nothing like your first ship. It will probably be junk, but it will also change you by showing that you (yes, you!) can actually be a hacker instead of just wishing you were one. If you are not new, this is to stop you getting complacent. Once you do the thing, it&apos;s easy to say &quot;I am a person who has done the thing.&quot; But we always have more to learn.&lt;/p&gt;&lt;p&gt;This is also a device to keep the community focused where it should be. When a community discusses or debates, normally the most outspoken, the most persistent, or the most eloquent voices get the most influence. But none of these correlates with who is most correct. Shipping projects shouldn’t be the only thing that gets people listening to you, but it should be one of them, and now it is.&lt;/p&gt;&lt;p&gt;At time of writing, the sync up is still running, so not everybody has one yet. Getting a project into the DB updates your field automatically. Since things take a while to hit the DB, the field won’t be perfectly accurate. But stuff need not be perfect to be good. Manual overrides are possible, but we are not promising them. There are perhaps 5 people in all of Hack Club whom I would give a manual override for their work with me. If you are assuming you&apos;ll get a manual override, let that assumption go. Ship to a YSWS! Is the YSWS model not working for you? Do you have great projects, but our current programs can&apos;t accommodate you? Tell us! We want to hear about that. 40 gap years will fight over you.&lt;/p&gt;&lt;p&gt;What are you shipping next?&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>Hack Club can&apos;t ban Message Loggers. It shouldn’t try to</title><link>https://news.hackclub.com/opinion/hack-club-shouldnt-ban-loggers/</link><guid isPermaLink="true">https://news.hackclub.com/opinion/hack-club-shouldnt-ban-loggers/</guid><description>Disclosure/COI notice: I maintain Slick, the biggest Slack client mod that offers message logging. I have quite a stake in this argument, and you should hear that from me first.</description><pubDate>Tue, 29 Sep 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;Disclosure/COI notice: I maintain Slick, the biggest Slack client mod that offers message logging. I have quite a stake in this argument, and you should hear that from me first.&lt;/p&gt;&lt;p&gt;When you hit &quot;Delete&quot; on a message, you expect it to go away and never haunt you again.&lt;/p&gt;&lt;p&gt;Here is what actually happens when you delete a message: Slack&apos;s server sends every client a nice request of &quot;pretty please remove that message. :3&quot; Your normal Slack client would comply. A message logger keeps the message and marks it as deleted instead.&lt;/p&gt;&lt;p&gt;The idea is new to Slack but not new in general. On Discord, the MessageLogger plugin is one of the headline features of Vencord, a popular client mod. Vencord&apos;s own README admits that client mods break Discord&apos;s ToS, then notes that Discord seems indifferent and that no bans over it are known. It is a rule on paper that never gets enforced. Keep that in mind.&lt;/p&gt;&lt;p&gt;.png)&lt;/p&gt;&lt;p&gt;What goes on the Internet stays on the Internet.&lt;/p&gt;&lt;p&gt;Loggers make some people uneasy, and that is expected. But that unease comes from an assumption that deleting something from the Internet means that it is gone for good. I think we have all heard of the phrase “The Internet never forgets.” Yeah, people don’t say that for no reason.&lt;/p&gt;&lt;p&gt;If we focus only on Slack, a deleted message can already survive in plenty of places. Someone screenshotted it. It popped up as a notification and sits in someone&apos;s notification history. It got emailed to someone with email notifications on. A bot in the channel stored it. None of this requires a fancy mod, and all of it can happen by accident.&lt;/p&gt;&lt;p&gt;A logger saves what Slack already sent to your client. It does not break into Slack or use any trick to get data it wasn&apos;t given. When the FD asked the community for its takes on message logging in a \#fire-dept thread, it said it had no plans to log messages itself, but made it clear that any Hack Clubber could already log yours.&lt;/p&gt;&lt;p&gt;Loggers make the gap between what is deleted and what is truly gone visible. In my opinion, it&apos;s healthier for all of us to know that what we send is never really gone.&lt;/p&gt;&lt;p&gt;A ban would only punish honest people&lt;/p&gt;&lt;p&gt;But the million dollar question is: could a ban even work? A logger runs on the user&apos;s own machine. Nothing it does is visible to Slack, to the FD, or to anyone else in the channel. The only way the FD learns someone runs one is if they say so. A &quot;no message loggers&quot; rule punishes the people who tell you the truth. Anyone who uses a logger but keeps quiet is untouchable. You end up rewarding secrecy over honesty.&lt;/p&gt;&lt;p&gt;This is where Discord comes back into play. Discord bans client mods on paper, but in practice, they do nothing about it. Instead, people on Discord know that since message loggers are common, they should think twice before sending something they don&apos;t want to stick around. We don&apos;t have to look at Discord to see how this plays out, either. Slick&apos;s logger has been public since July and is used openly across the Slack, and nothing has blown up.&lt;/p&gt;&lt;p&gt;Counterclaim&lt;/p&gt;&lt;p&gt;Imma be honest, I could not come up with a cooler title than this&lt;/p&gt;&lt;p&gt;The strongest objection comes from people who delete their messages. We are all teenagers, and we have all sent things we probably shouldn&apos;t have. People sometimes need a legit way to take something back. Teenagers should be able to leave their mistakes behind, and I fully agree.&lt;/p&gt;&lt;p&gt;But you may ask how I can agree when I make the tool that supposedly defeats this? I see the harm not as the message existing somewhere, but as someone using it against the person. When someone shares a deleted log around, that can be Shrouded and punished.&lt;/p&gt;&lt;p&gt;Others may say they didn&apos;t consent to their messages being stored, and I get that. But once a message is sent, where it ends up was never fully in the sender&apos;s hands. A logger does make this automatic, where a screenshot takes someone choosing to save it, and I understand why that feels different. But the protection a ban promises, that nobody kept a copy, never existed in the first place. The same idea applies to people concerned that if people have loggers on, they can&apos;t freely speak their mind. I would rather people be told what they shouldn&apos;t post than trust that no one will screenshot their spicy take.&lt;/p&gt;&lt;p&gt;The last objection is the one the FD will raise: what happens to stuff the FD deletes? I won&apos;t pretend loggers are innocent here because they do make cleanup less complete. But cleanup was never complete in the first place! Everyone online when a message was posted already saw it, and anyone could have screenshotted it. The point of removing a message is to stop it from spreading, and a logger doesn&apos;t change that: the message is still gone from the channel for everyone else. What matters is what people do with it next. Loggers also cut the other way. Several FD members use Slick or their own loggers, so people who send something awful and delete it quickly can no longer count on getting off scot-free.&lt;/p&gt;&lt;p&gt;What to do about it instead&lt;/p&gt;&lt;p&gt;Hack Club is an amazing place for computer nerds, and as computer nerds, we have always made computers do unexpected things. But message loggers are not unexpected, and honestly, it is surprising how long it took for them to become common among the masses. A rule banning message loggers would be unenforceable, punish honest people, and fail to protect anyone the rule claims to protect. Instead, we should punish people who misuse deleted messages, not the people honest enough to say they keep them.&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>Community Logs is being overhauled</title><link>https://news.hackclub.com/news/community-logs-overhaul/</link><guid isPermaLink="true">https://news.hackclub.com/news/community-logs-overhaul/</guid><description>The Fire Department is discontinuing individual public logs in #community-logs, and replacing them with monthly Transparency Reports. Here is the reasoning behind that change.</description><pubDate>Fri, 25 Sep 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;“Disclaimer: This editorial was written collaboratively by members of the Conduct Working Group. Generative artificial intelligence was used to unify the writing style across original contributions, and the resulting text has been reviewed, edited as needed, and proof-checked by the team. The author takes full responsibility for the content of this publication.&lt;/p&gt;&lt;p&gt;From today, the Fire Department will be discontinuing individual public logs in #community-logs. In their place, we’ll be publishing monthly Transparency Reports to give you a clear picture of how the Fire Department operates. We realise this is quite a contentious change; however, after months of deliberation, we believe this change is the best way to balance privacy and safety, with transparency.&lt;/p&gt;&lt;p&gt;The #community-logs channel was one of the Fire Department’s attempts at being more open with the decisions we take. The intention behind publicly logging major infractions was to minimise confusion about why you are not able to communicate with a Hack Clubber anymore, and to encourage productive discussion whilst minimising speculation in other channels.&lt;/p&gt;&lt;p&gt;The reality is, #community-logs has steered away from that direction. Each log became fuel for gossip about individuals whom we took action on, which often led to toxicity hurting the person in question or the community in general. We’ve dealt with cases with Hack Clubbers going out of their way to dox/find personal information about people who’ve appeared in #community-logs, and in some cases, Hack Clubbers making alt accounts posing as someone who we’ve banned to cause trouble. These public logs have created flamewars where people who never would’ve involved themselves or who had only a passing interest felt obligated to become a part of the conversation.&lt;/p&gt;&lt;p&gt;From the perspective of someone appearing in #community-logs, it can feel like a permanent stain on your reputation. When a LYLA record is publicly logged, it remains there forever. We believe that people can change over time and learn from their mistakes, but they shouldn’t have that looming over their head for the rest of their time in Hack Club.&lt;/p&gt;&lt;p&gt;These Transparency Reports will take on the form of formal publications, released on a monthly basis through a medium that is yet to be determined as of now.&lt;/p&gt;&lt;p&gt;They’ll contain information like:&lt;/p&gt;&lt;p&gt;Transparency Reports won’t contain any information on specific cases. They won’t contain usernames, evidence, decision-making, or anything along these lines. The aim is to preserve the privacy of those involved whilst being as transparent as we feasibly can.&lt;/p&gt;&lt;p&gt;We’d actually argue that, in some ways, this approach is more transparent – and we’d encourage you to think about it for a second: what do you actually gain from knowing Slack User 24367 was banned for fraud?&lt;/p&gt;&lt;p&gt;Transparency Reports allow us to give you an insight into how the Fire Department takes actions without jeopardising the privacy of other Hack Clubbers. You get to see how we’re resolving reports, how long they’re taking us to resolve, and how these translate into actions taken. This is all information that you wouldn’t have normally been able to see with the old #community-logs.&lt;/p&gt;&lt;p&gt;Accountability is a term thrown around a lot here on Slack. The general idea is that “with community-logs, we can ensure that the Fire Department is making fair decisions.” While we’re all in favour of being held accountable for our mistakes, there’s really not much you can do without the full context.&lt;/p&gt;&lt;p&gt;We’ve seen it before: #meta posts from or on behalf of people who’ve been banned for one reason or another, but with only one side of the story shown and many crucial details left out. This isn’t accountability at all. If you don’t have the full context of a case, a simple log with a brief reason doesn’t give you enough information to tell if the Fire Department has made the right decision.&lt;/p&gt;&lt;p&gt;Transparency Reports give you a picture of how we operate, the volume of our work, and the patterns in our decision-making, without putting Hack Clubbers on display.&lt;/p&gt;&lt;p&gt;There’s a pretty big difference between someone making the decision to tell people about what’s happened to them and us forcefully broadcasting that for all to see. If a Hack Clubber truly wants people to know that they were banned or shushed, they’ll make their own choice to get the word out.&lt;/p&gt;&lt;p&gt;At the end of the day, the Fire Department’s goal isn’t retribution; it’s rehabilitation. Hack Clubbers who want to show change will recognise their mistakes and make change, and this is a private, developmental matter between them and us that the community doesn’t need to know about. If they want to make that public, it’s their choice, but it’s incredibly important that we make it their choice.&lt;/p&gt;&lt;p&gt;A couple of years ago, the Fire Department created the #community-logs channel for the purpose of logging major conduct infractions, including shushes and temporary or permanent bans. The Slack was a vastly different community then, where conduct actions were usually unheard of and bans were big news – @radioblahaj “Bans are always the last resort.&quot;&lt;/p&gt;&lt;p&gt;Since then, Hack Club has grown significantly. The Slack now has an estimated 200,000 members, the Fire Department deals with hundreds of conduct reports a week, and #community-logs has become something very different from what it was originally intended to be.&lt;/p&gt;&lt;p&gt;We made #community-logs read-only a while back, which helped reduce some of the heated conversations; however, that did not solve the underlying problem.&lt;/p&gt;&lt;p&gt;“Transparency” is a word that gets thrown around a lot. There is a high expectation for the Fire Department to be open and held accountable. We try to act on that feedback, and this change is part of that.&lt;/p&gt;&lt;p&gt;However, it’s important to establish what transparency means in this context, and what Hack Clubbers often expect from the Fire Department is “full transparency”. That would involve giving the community access to each Shroud report (and who submitted it), all the details and evidence in that case and any other reports or logs involving that person, so that Hack Clubbers can decide on their own accord whether the Fire Department’s action was appropriate. Obviously, we can’t do that, so what is the next level of transparency we can offer?&lt;/p&gt;&lt;p&gt;What we can do is be open about how we operate and the decisions we make, without exposing private details, to provide that assurance and accountability, and still give the community the opportunity to give feedback on the actions we take – that is what Transparency Reports are designed to do.&lt;/p&gt;&lt;p&gt;Transparency does not mean you are entitled to knowing every single piece of information or being able to stick your nose where it does not belong. Every piece of private information revealed in the name of transparency necessarily compromises some individual’s privacy, and unfortunately there is no perfect solution here, but we’re always open to feedback on how we can do better.&lt;/p&gt;&lt;p&gt;This is a big change, and we know it won’t land without questions, nor will it be perfect, and that’s okay. We’ve tried to be as open as we can about our reasoning here, and Transparency Reports are our commitment to keeping that openness every month. If you’ve read this far and found yourself thinking you could do more for the community, maybe you should – we’re currently opening applications for new firefighters and you can apply right now: https://forms.hackclub.com/fd-apps-sep-26! More info in this thread.&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>The Fallout documentary lands, in 2 parts</title><link>https://news.hackclub.com/news/fallout-documentary/</link><guid isPermaLink="true">https://news.hackclub.com/news/fallout-documentary/</guid><description>Hack Club has published a two-part documentary about Fallout, the hardware hackathon that ended with more than two hundred teenagers building electronics in Shenzhen. Both episodes are below.</description><pubDate>Tue, 15 Sep 2026 09:00:00 GMT</pubDate><content:encoded>&lt;p&gt;Fallout gave students an opportunity to design something that they could make real. In return, 200 of them were invited to a free week-long hardware hackathon in the electronics capitol of the world.&lt;/p&gt;&lt;p&gt;Hack Club has now published a two-part documentary about how that went. Anyone interested in how a program like this happens, or how they too could be given the resources could to learn and build awesome projects should give it a watch.&lt;/p&gt;&lt;p&gt;Part one covers the run-up and the arrival:&lt;/p&gt;&lt;p&gt;Part two picks up inside the hackathon itself:&lt;/p&gt;&lt;p&gt;Don&apos;t know where to start but imagine yourself being here? Beginners are welcome in every Hack Club event and guides are always provided to help you learn hardware and other skills.&lt;/p&gt;&lt;p&gt;By any means, if the idea of going on adventures and making things with other hackers excites you, keep an eye on the programs page to know when the next hardware YSWS drops.&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>How Common Is Plagiarism?</title><link>https://news.hackclub.com/news/plagiarism-study/</link><guid isPermaLink="true">https://news.hackclub.com/news/plagiarism-study/</guid><description>How much of the maker’s work in software projects in the unified database shows evidence of reuse from existing code?</description><pubDate>Tue, 15 Sep 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;How much of the maker’s work in software projects in the unified database shows evidence of reuse from existing code?&lt;/p&gt;&lt;p&gt;Similarity analysis is one way of answering this question. Similarity alone cannot establish code reuse, but substantial and distinctive similarity can be evidence of reuse, especially when examined in context. This approach is used by various plagiarism detection systems such as Turnitin, which identifies similarities for educators to review (source).&lt;/p&gt;&lt;p&gt;In my experience, people frequently use code from three sources: tutorials, answers and repositories. Repositories are easy to search (e.g. GitHub&apos;s code search, Sourcegraph, grep.app...), whereas tutorials and answers... not so much (requiring scraping or figuring out how to compare code snippets against whole projects). But code from popular public resources frequently makes its way to public repositories, which means these can act as a proxy corpus. This study targeted software projects and checked for similarities between project code and public repositories.&lt;/p&gt;&lt;p&gt;For candidate selection, the project was checked out at a pre-approval date and 30 lines were randomly picked, with ineligible lines being rerolled. The following conditions were checked to determine eligibility:&lt;/p&gt;&lt;p&gt;These lines were used as search queries in GitHub&apos;s code search API. The resulting repositories were scored using the number of hits, while taking the number of query results and the repository&apos;s position in the result ranking into account to promote rarer lines. Both candidates before and after the project were considered and categorized accordingly. Candidates predating the project could show that the matching code existed publicly before project submission, whereas candidates after the project could be useful since repositories were also being treated as a proxy corpus: code from tutorials, answers or other sources could appear in a public repository afterwards. Up to 10 pre-project and up to 3 post-project results were selected as candidates.&lt;/p&gt;&lt;p&gt;After the candidate selection and comparison design were finalized, the data was filtered:&lt;/p&gt;&lt;p&gt;After these two stages, there were still more than 2000 projects left. Since processing was very time-consuming, 200 projects were picked at random.&lt;/p&gt;&lt;p&gt;There were three main code similarity analysis tools: MOSS, Dolos and JPlag. Of these, only JPlag supported project comparisons. However, JPlag only supported specific languages (such as Java, C, C++, C\#, Go, Kotlin, Python, R, Rust, Scala, Swift, JavaScript, TypeScript, LLVM IR, and Scheme), and adding support for new languages was a costly process, to say the least. Language distribution in the dataset was analyzed, and it was found that JavaScript was the most prevalent language, by several measures: &quot;language appears in repository&quot;, &quot;more than 50% of code belongs to language&quot; and &quot;most code in repository is language&quot;. However, after looking into it, I found out that this was because of the many JavaScript variants, such as JSX (not supported by JPlag). In the end, I focused on one language only for simplicity. I chose Python, the second most prevalent language, as it did not have the same variant problem as JavaScript. Analyses were run with a minimum match length of 24 tokens. Dependencies and Python virtual environments were filtered out. After analysis, due to JPlag’s frequent false positives, GPT 5.6 Luna classified matches according to the following categories:&lt;/p&gt;&lt;p&gt;200 projects were selected, of which 180 were successfully analyzed. The remaining 20 could not be analyzed, for example, because they were too large or did not have Python as the dominant language at the time of approval.&lt;/p&gt;&lt;p&gt;Generated or vendored code was excluded from all coverage/project statistics, as it is not part of the maker’s work. Reuse was defined as code which appears to have been derived from an external resource, rather than written independently. In practice, this refers to matches classified as external usage.&lt;/p&gt;&lt;p&gt;Across all analyzed projects, 3.03% of tokens were covered by matches with code in repositories predating the project. Considering only reuse matches, the coverage was 2.64%.&lt;/p&gt;&lt;p&gt;Percentage of code in each project which matched repositories from before the submission date&lt;/p&gt;&lt;p&gt;AI classification results for matches&lt;/p&gt;&lt;p&gt;Some example projects include:&lt;/p&gt;&lt;p&gt;“Project is plagiarized from another source (tutorial with no modifications, stolen code, copy of a previous project with little/no modifications, etc.) YSWS Project Submission Guidelines&lt;/p&gt;&lt;p&gt;Before drawing any conclusions, I think it&apos;s important to look at the current rules on plagiarism and tutorial use, which I wholeheartedly agree with. Putting plagiarism aside, beginner coders need educational resources to be able to get started. However, mindlessly copying tutorials without understanding them doesn&apos;t help them get started and shouldn&apos;t be rewarded. There&apos;s also a fairness aspect: if person A, who follows a tutorial 1:1, receives the same credit as person B, who plans and designs their own project, there&apos;s far less incentive to make truly creative projects, which is what Hack Club is all about.&lt;/p&gt;&lt;p&gt;Having said that, the good news is that most analyzed projects showed no detected overlap with pre-existing work. The less good news is that a small number showed substantial overlap with existing work, including cases that appear to be incompatible with the guidelines described above. The results of this study suggest three things:&lt;/p&gt;&lt;p&gt;I carried out an extension study after the initial investigation, to see whether plagiarism could be detected at scale. I figured it was the least boring option among &quot;more languages&quot;, &quot;sensitivity tests&quot; and &quot;more samples.&quot;&lt;/p&gt;&lt;p&gt;Here is a brief summary of the results:&lt;/p&gt;&lt;p&gt;The study was designed almost entirely by the author. AI analyzed the data per the author’s design. This writeup is human-made.&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>Temporary Regional Restrictions for Hack Club Haven</title><link>https://news.hackclub.com/news/haven-regional-restrictions/</link><guid isPermaLink="true">https://news.hackclub.com/news/haven-regional-restrictions/</guid><description>Haven is the latest iteration of Hack Club’s flagship satellite hackathons. For this cycle, we have made the difficult decision to not fund satellite events in certain countries. This post explains what we found in the Campfire and Daydream data that led to that decision, and how we measured it.</description><pubDate>Tue, 08 Sep 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;Deven Jadhav is YSWS Chief of Staff&lt;/p&gt;&lt;p&gt;Haven is the latest iteration of Hack Club&apos;s flagship satellite hackathons. For this cycle, we have made the difficult decision to not fund satellite events in certain countries. This post explains what we found in the Campfire and Daydream data that led to that decision, and how we measured it.&lt;/p&gt;&lt;p&gt;As of today, 175 people in the countries listed above have signed up to organize a Haven event. Funnily enough, many of them are organizers of Campfire events that are currently under fraud investigation.&lt;/p&gt;&lt;p&gt;We looked at four sources.&lt;/p&gt;&lt;p&gt;The Campfire Airtable is where regional managers tracked each event: signups, check-ins, scan-ins on the day, and how much money was granted from HQ. Here are some important terms:&lt;/p&gt;&lt;p&gt;HCB is Hack Club&apos;s fiscal sponsorship platform that all the events used to raise and manage their funds. Every Campfire satellite had its own HCB org and every transaction on those orgs is public.&lt;/p&gt;&lt;p&gt;The Unified YSWS DB is where shipped projects go after review. Campfire satellite projects are recorded there with the shipper&apos;s geocoded country.&lt;/p&gt;&lt;p&gt;After Campfire ended, we discovered about $14,000 worth of fraudulent transactions, and a fraud team was assembled to document the fraud and track down the parties involved. The fraud team&apos;s investigation report covers twelve African events. It includes IP address overlap between organizer accounts, phone and address checks, and venue verification calls.&lt;/p&gt;&lt;p&gt;We compared the banned regions to all other satellite regions combined. The banned regions had 42 events (out of a total of 216 events worldwide).&lt;/p&gt;&lt;p&gt;Campfire satellites were funded by automated grants (triggered by this script). Each country had a rate per signup, between $2.51 and $4.06 across this region, and the grant was disbursed to the event&apos;s HCB org as signups came in.&lt;/p&gt;&lt;p&gt;The banned countries produced 38% of all satellite signups, received 25% of the money, and accounted for 15% of the people who showed up.&lt;/p&gt;&lt;p&gt;These regions accounted for 90% of the total amount of fraud globally ($12.6k / $14k). For context, that is enough money for us to be able to support another 15–20 hackathons in other regions that serve real teenagers and help them build cool projects.&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>Mnemosyne - Better Slack Analytics for Everyone</title><link>https://news.hackclub.com/news/mnemosyne-analytics-and-moderation/</link><guid isPermaLink="true">https://news.hackclub.com/news/mnemosyne-analytics-and-moderation/</guid><description>Where is everyone? What are the most active Slack channels? Which channels have the most unique posters? Where do potential new users go, and where do they get stuck? How many people are active on the Slack? How many people just lurk? And how do you explain the pen?</description><pubDate>Tue, 08 Sep 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;Where is everyone? What are the most active Slack channels? Which channels have the most unique posters? Where do potential new users go, and where do they get stuck? How many people are active on the Slack? How many people just lurk? And how do you explain the pen?&lt;/p&gt;&lt;p&gt;For some of these questions, we have flawed data. For others, we have no data. We’re forced to rely on our own impressions, but the Slack is fragmented, so those impressions are radically different depending on where you spend your time.&lt;/p&gt;&lt;p&gt;Mnemosyne is how we get answers. Since we switched to the enterprise plan last year, we’ve gained a lot of new powers. But we haven’t really used them to their full ability, until now. Mnemosyne uses an org owner token to power two projects: Nemo, an analytics dashboard for the Slack; and Fire Engine, a case management system for the Fire Department.&lt;/p&gt;&lt;p&gt;We’ve tried to design this in a way that doesn’t threaten your privacy. We’re open to questions. The data that Nemo collects, and who can see it, are open for discussion. This is our first attempt, and we accept it might need changes.&lt;/p&gt;&lt;p&gt;In that spirit, note that these analytics will probably change. As we start to use Nemo, we’ll think things like “I wish I could see each channel’s most active time of day!” and end up adding them. It’s open source, so you can always see these changes.&lt;/p&gt;&lt;p&gt;The first attempt was called Con Man (Conduct Manager). May he rest in peace. The second attempt is called UCAT (Unified Conduct Airtable). At some point we’ll probably move it to a postgress DB, necessitating yet another name change (Miss Conduct?). UCAT also holds records from the Fraud Squad, and will soon hold records from HCB and Attend, the events platform. This will make it possible to see someone’s whole conduct history in one place.&lt;/p&gt;&lt;p&gt;Access is restricted. The Fire Department and senior adult staff at HQ will have full access. Fraud Squad and HCB can only see fraud cases. Other staff, like gap years, do not have access to the system at all. When they need information (for example because they are considering hiring somebody) they can request it on a case-by-case basis.&lt;/p&gt;&lt;p&gt;Since we already have a new airtable base and an org token for Nemo, we’re going to try bundling case management into a web interface to see if this is easier than the FD’s current, Slack-based system. This is still in testing.&lt;/p&gt;&lt;p&gt;Go visit nemo.hackclub.com and tell us what you learn about the Slack!&lt;/p&gt;&lt;p&gt;@mat and @rowan - Security testing&lt;/p&gt;&lt;p&gt;@sahil, @lynn, @izie - UX testing of Fire Engine&lt;/p&gt;&lt;p&gt;@msw - The idea for the proxy architecture&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>Ingestion Engine Features Slack Messages on SN</title><link>https://news.hackclub.com/changelogs/ingestion-engine-features-slack-messages/</link><guid isPermaLink="true">https://news.hackclub.com/changelogs/ingestion-engine-features-slack-messages/</guid><description>Hack Clubbers spend a lot of time on Slack (honorable mentions), and understandably a lot of news and discussion starts there! In an effort to make Slacker News more embedded in the community and Slack,</description><pubDate>Sun, 06 Sep 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;Hack Clubbers spend a lot of time on Slack (honorable mentions), and understandably a lot of news and discussion starts there! In an effort to make Slacker News more embedded in the community and Slack,&lt;/p&gt;&lt;p&gt;1. Streamlining submissions using Slack&lt;/p&gt;&lt;p&gt;Existing channels like #ysws, #hc-opportunities, and many others already do many of the things which traditional newspapers do, providing various combinations of reporting and community updates.&lt;/p&gt;&lt;p&gt;Right now, cool, newsworthy happenings are hidden by fragmentation. Slacker News is our bet to centralize information, and automatic submissions make that far easier.&lt;/p&gt;&lt;p&gt;Over the last couple of months, we&apos;ve been developing and experimenting with Indigest, the Slack bot currently making this possible in trusted channels, and News Wire, a bot allowing community members to submit stories for review! These new tools are part of an attempt to continue making Slacker News represent an up-to-date picture of the community and are the source for the new columns shown on the site&apos;s homepage.&lt;/p&gt;&lt;p&gt;In the same vein, Slacker News strives to be a place which shows what Hack Clubbers are doing — and it now exhibits projects shipped by community members. Alongside the ongoing Ship of the Week contest in #ship, SN now features ads for projects made by Hack Clubbers in exchange for their positive contributions and service to the community.&lt;/p&gt;&lt;p&gt;To be clear, this automatic featuring is reserved only for trusted channels like #ysws and #hc-opportunities. For others (including #community-announcements and #ship), manual channel admin review is necessary to feature messages on the site.&lt;/p&gt;&lt;p&gt;And in the case of community member-posted messages, author should be requested before publishing either publicly or behind the authwall.&lt;/p&gt;&lt;p&gt;2. Trying out #news as a front door&lt;/p&gt;&lt;p&gt;Another recent change made to News in Hack Club is the creation of a new channel, #news[^1], which exists to surface news content to the entire community. As of a couple weeks ago, it&apos;s now a default workspace channel, which means new members will automatically be added to it.&lt;/p&gt;&lt;p&gt;#news doesn&apos;t have @channel or @here pings, but we think it can be a new front door to introduce newcomers to what&apos;s happening in the community. We&apos;ll keep watching #news as it improves and grows, but we hope a global feed will be effective in simplifying the distribution of information to where Hack Clubbers already are.&lt;/p&gt;&lt;p&gt;[^1]: Formerly #news-wire, and formerly formerly #news&lt;/p&gt;</content:encoded></item><item><title>Slacker News Gets a Members-Only Area</title><link>https://news.hackclub.com/changelogs/slacker-news-gets-members-only-area/</link><guid isPermaLink="true">https://news.hackclub.com/changelogs/slacker-news-gets-members-only-area/</guid><description>“&quot;Slacker News began with a dream: fewer flamewars. The Slack is not a good place for hard conversations, especially public ones. You deserve better than to have your idea buried in a thread with 1000+ replies. And you deserve a fair hearing. Slacker News is the way. Few responses written carefully, instead of many responses quickly.&quot;</description><pubDate>Mon, 31 Aug 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;“&quot;Slacker News began with a dream: fewer flamewars. The Slack is not a good place for hard conversations, especially public ones. You deserve better than to have your idea buried in a thread with 1000+ replies. And you deserve a fair hearing. Slacker News is the way. Few responses written carefully, instead of many responses quickly.&quot;&lt;/p&gt;&lt;p&gt;As of last week, some articles on Slacker News are hidden unless a user is logged in. This article serves to explain the background behind this change and the reasons behind it.&lt;/p&gt;&lt;p&gt;Why are we doing this?&lt;/p&gt;&lt;p&gt;The story of this feature suggestion goes back pretty far, and as far as I know started with a PR @sahil submitted to Slacker News when it was still a static jekyll blog. At the time we opted against creating the impression of security for a project which contained raw article markdown in the codebase.&lt;/p&gt;&lt;p&gt;Nevertheless, the motivation behind adding authentication remained relevant until @ani proposed an authgate for the site in #meta. Opinions were variable on how this could be implemented (and whether publishing opinions on SN was even the right path), but a consensus was reached that an authgate would be beneficial to the site&apos;s purpose for community opinion and criticism.&lt;/p&gt;&lt;p&gt;Even back then, I was already working on protecting articles, but my chosen method, a self-hosted Payload CMS instance, was complex and had several major flaws (namely performance, stability, and maintainability). While a more seamlessness submission process is still a priority today, we&apos;ve always known that the comfort and freedom of expression offered to article-submitters was worth it.&lt;/p&gt;&lt;p&gt;But today we&apos;re happy to finally announce this second objective as achieved, and that this progress did not require shipping an ineffective protection, close-sourcing the project, or undermining its ability to serve as a place where Hack Clubbers share what they&apos;re doing, thinking, and making with each other (and the world[^1]!).&lt;/p&gt;&lt;p&gt;From now on, any published opinion or essay on SN can be designated by its author as intended to be protected, a decision which will place it behind a Hack Club Auth-wall and restrict access to site visitors and RSS feed subscribers with valid authentication verification.&lt;/p&gt;&lt;p&gt;In order to showcase the new auth-gating features of the site, the Ship Ads column also temporarily requires authentication to view.&lt;/p&gt;&lt;p&gt;Now go write something&lt;/p&gt;&lt;p&gt;So, that&apos;s all we have for this changelog, meaning this is your chance! We encourage you to find a community topic you&apos;ve seen debated and write your thoughts, submit a response to a relevant #meta thread, or write an essay about the tech industry in general. Slacker News is Hack Club&apos;s microphone, but it could be yours too![^2]&lt;/p&gt;&lt;p&gt;Now that I&apos;m writing this it almost sounds like a you-ship-we-ship [insert vague &quot;hmm&quot; here]: SN provides a thoughtful, curious space to share (and change!) your opinions and all we ask from you is to respect the truth, our submission guidelines, and the Hack Club code of conduct.&lt;/p&gt;&lt;p&gt;[^1]: This wasn&apos;t as prominent in @ani&apos;s meta thread as the site&apos;s potential appeal to adults was, but we also hope Slacker News&apos; audience can include future or prospective Hack Clubbers for whom getting a glimpse of how the community converses and (co)operates could be positive!&lt;/p&gt;&lt;p&gt;[^2]: I&apos;m blatantly plagiarizing paraphrasing Evan here, but go read Responses and Followups for yourself!&lt;/p&gt;</content:encoded></item><item><title>Vercel opens up a direct line with Hack Clubbers</title><link>https://news.hackclub.com/news/vercel-x-hack-club/</link><guid isPermaLink="true">https://news.hackclub.com/news/vercel-x-hack-club/</guid><description>Vercel has been a long time partner with Hack Club, and now they’re opening up a direct line with Hack Clubbers!</description><pubDate>Wed, 26 Aug 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;Vercel has been a long time partner with Hack Club, and now they’re opening up a direct line with Hack Clubbers! If you are part of the Hack Club Slack, you can now reach out to Vercel directly in the #mitochondria-is-the-powerhouse-of-the-vercell channel.&lt;/p&gt;&lt;p&gt;To make sure you understand these little house keeping rules, Prometheus will ask you to confirm that you understand the purpose of the channel by writing out a short message in the channel that goes along the lines of &quot;I understand the purpose of this channel&quot; once you join. This is just to make sure that everyone is on the same page and that the channel stays high quality!&lt;/p&gt;&lt;p&gt;If all this sounds like fun, please join the Hack Club Slack and head over to the #mitochondria-is-the-powerhouse-of-the-vercell channel to say hi to the Vercel team!&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>How to Be Nice Without Being a Chump or a Pushover</title><link>https://news.hackclub.com/essays/be-nice-without-being-a-chump-or-pushover/</link><guid isPermaLink="true">https://news.hackclub.com/essays/be-nice-without-being-a-chump-or-pushover/</guid><description>As a kid, I wasn’t nice. I wasn’t mean either. But the people telling me to be nice were adults, and most adults were chumps.</description><pubDate>Mon, 03 Aug 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;As a kid, I wasn’t nice. I wasn’t mean either. But the people telling me to be nice were adults, and most adults were chumps.&lt;/p&gt;&lt;p&gt;They meant well. But they were clueless. They were excited for stuff I hated. They wanted me to read Shakespeare, solve math problems, and play sports. In the sports, people threw stuff at my face. This is fun, the adults explained patiently. They were also useless in a conflict: other kids would do something bad to me, I&apos;d ask adults for help, and the adults--unable to figure out who was telling the truth--would give me a &quot;both sides&quot; homily. A few adults were better than this, and I am grateful for them. But overall I learned by observation that being nice meant being a chump.&lt;/p&gt;&lt;p&gt;When I became an adult, I met another nice archetype: the pushover. Pushovers have all kinds of stories for why they let other people treat them like garbage: I don’t want to cause trouble, it’s really no big deal, I need these people because no one else wants me. Many stories, many roads, one destination: they get used remorselessly, again and again, by the worst people they meet.&lt;/p&gt;&lt;p&gt;Because they are obvious, chumps and pushovers were the face of kindness, at least for me. Small wonder I didn’t want to be like them.&lt;/p&gt;&lt;p&gt;Thing is, there are other, better ways to be kind. But they are easy to miss, and therefore hard to learn. But slowly, I started to notice people being kind without making a fool of themselves.&lt;/p&gt;&lt;p&gt;I see a lot of kindness at Hack Club. I also see a lack of kindness, which I don&apos;t chalk up to meanness. When I see Hack Clubbers lacking kindness, I assume you are making the same calculation I did at your age: being nice requires being an idiot, so I&apos;m not gonna be mean, but I&apos;m not gonna be nice either.&lt;/p&gt;&lt;p&gt;There is a better way, and I want to share it with you. So I went around and I asked some of the nicest people at Hack Club: “How do you be kind to people?”&lt;/p&gt;&lt;p&gt;Felix&lt;/p&gt;&lt;p&gt;I wanted to interview Felix because he is a master of de-escalation. Many a time, people have been pissed at each other in a thread, and Felix steps in to say something that everyone finds satisfying, or at least gets people to treat each other well. He made three points:&lt;/p&gt;&lt;p&gt;First, In conflict, use &quot;I statements&quot;. E.g. instead of &quot;it is annoying that we&apos;ve...&quot;, say &quot;I feel kind of annoyed that we&apos;ve...&quot;. The idea is that whereas one places blame (“you&apos;re being annoying”), the other focuses on my experiences.&lt;/p&gt;&lt;p&gt;Second, separate understanding their feelings, understanding their argument, and agreeing with their opinion. I acknowledge that I understand their argument or how they feel, by saying things like &quot;yea that&apos;s fair&quot;. It doesn&apos;t mean I agree, just that I get their viewpoint and can see why they think that.&lt;/p&gt;&lt;p&gt;Third, there&apos;s a distinction to make between nice and kind. 1 Being nice is performative and often not a reflection of who someone is. It&apos;s about &quot;keeping the peace&quot;, like when people say &quot;Just be nice okay?&quot; Being kind is genuine and also leaves room to be upset. I&apos;m not being nice when I say &quot;I feel kind of annoyed...&quot; but I am being kind.&lt;/p&gt;&lt;p&gt;Rebeka&lt;/p&gt;&lt;p&gt;Most Hack Clubbers don’t know Rebeka, because she works more with HQ staff. I will always be grateful to her for how much she helped me when I first moved to Vermont; she even found me a place to live.&lt;/p&gt;&lt;p&gt;Rebeka is also quietly badass. Before Hack Club, she worked with homeless people. Some of them had serious problems that also made it hard for others to be around them. Rebeka had to learn how to stand up for herself respectfully, even when people were screaming at her and cursing her out. 2 She said:&lt;/p&gt;&lt;p&gt;I like to ask people a question or two to learn more about who they are, based on what they’ve already hinted they are interested in. When I pick these questions, I watch myself to make sure I’m not being competitive. I like hiking, but I wouldn’t ask “Have you climbed a 4000 footer?”&lt;/p&gt;&lt;p&gt;I also try to emulate all the people who made me feel comfortable and good. When I was younger, I even copied the language and body language of people whom I admired. If it’s an in-person interaction, I try to smile!&lt;/p&gt;&lt;p&gt;Meghana&lt;/p&gt;&lt;p&gt;Give other people the benefit of the doubt, that they don’t know they are being rude or annoying. Assume that just like me, they want to build cool things.&lt;/p&gt;&lt;p&gt;Lou&lt;/p&gt;&lt;p&gt;If you appreciate something about someone, even if it’s tiny, tell them.&lt;/p&gt;&lt;p&gt;If you are having a text conversation and all your responses are all very short, every once in a while send a full sentence with a thank you or a smile or something.&lt;/p&gt;&lt;p&gt;Put a space before an exclamation mark !&lt;/p&gt;&lt;p&gt;Wally&lt;/p&gt;&lt;p&gt;Most conversations I have are with Hack Clubbers I&apos;ve seen before but don&apos;t know that well. In those cases, I try to constantly evaluate the conversation as it&apos;s going to hopefully have a &quot;successful&quot; one. If it&apos;s turning into an argument or becoming uncomfortable, I&apos;d rather end it while it&apos;s still successful-ish than let it turn into an FD case.&lt;/p&gt;&lt;p&gt;Zach&lt;/p&gt;&lt;p&gt;Being nice makes everything better. I’ve spent a lot of time in spaces where I was younger than other people, and there were huge power differences. Power, both explicit and implicit, asserts itself everywhere. I want a social contract where everyone gets to decide who they want to be. That’s not the default though. It only happens if you make it happen. I remember how specific people treated me when I was living alone in SF at the age of 15. Some were very nice. Some were exploitative. I remember all of them. Hack Clubbers will go on to have outsize influence in the world. When you are an adult, are you going to be like the person who, when they saw me sleeping on a couch at 16 years old, spontaneously invited me to join a Thiel fellows orientation week even though I wasn’t one yet? Or are you going to be like the executive who tried to get me drunk as a 15-year-old?&lt;/p&gt;&lt;p&gt;Being nice is really hard. But I think it’s not about telling people what they want to hear, but treating them how you’d want to be treated.&lt;/p&gt;&lt;p&gt;Me&lt;/p&gt;&lt;p&gt;Once I started noticing people who are good at being kind, I consciously adopted their ways. And I started learning from my experiences: how others made me feel, times when I helped people, and times when I hurt them. And as a debate coach, I started noticing common patterns that led to pointless, stupid debates. I slowly built a set of habits to be kind and have productive disagreements. Some of them have already been said. Here is what remains:&lt;/p&gt;&lt;p&gt;Asking a lot of questions about people’s opinions, especially if I think I disagree with someone.&lt;/p&gt;&lt;p&gt;Focusing on what people are doing, without making assumptions about why they are doing it.&lt;/p&gt;&lt;p&gt;Explaining my reasoning and giving people the chance to challenge me.&lt;/p&gt;&lt;p&gt;Keeping criticism and concerns in DMs to avoid public embarrassment.&lt;/p&gt;&lt;p&gt;When someone doesn’t know something obvious, remembering that I don’t know stuff that is obvious to other people.&lt;/p&gt;&lt;p&gt;Giving people a chance to express their feelings without interruption. Much frustration comes from not being or not feeling heard.&lt;/p&gt;&lt;p&gt;Giving people openings to say things that they might be thinking, but are afraid to say.&lt;/p&gt;&lt;p&gt;Asking people “What can I do to help?” or “Is there anything I can do to make things easier for you?”&lt;/p&gt;&lt;p&gt;The result is not perfect. But I don’t feel like a pushover or a chump, and I feel proud of the hard work I put into learning these habits. And though I wasn’t expecting it when I undertook to learn them, kindness has actually had a huge personal payoff. Kind people can sense each other, and gravitate together. All of my friends are really kind, and as a result I’ve had life-affirming experiences of love and trust, safety and acceptance, and near zero drama. It really is a better way to live.&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>Journals aren&apos;t Timesheets</title><link>https://news.hackclub.com/opinion/journals-but-not-for-hours/</link><guid isPermaLink="true">https://news.hackclub.com/opinion/journals-but-not-for-hours/</guid><description>How do you measure effort? Many hardware programs answer that question with journals. Today, I want to question the assumption that journals are the right way to measure effort on hardware projects.</description><pubDate>Fri, 31 Jul 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;How do you measure effort? Many hardware programs answer that question with journals. Today, I want to question the assumption that journals are the right way to measure effort on hardware projects.&lt;/p&gt;&lt;p&gt;To be clear, I do not think journals should disappear. In fact, I think they are one of the best parts of Hack Club hardware.&lt;/p&gt;&lt;p&gt;I enjoy writing and reading journals. Journals document progress, encourage reflection, teach other people, and create a public record of what someone built. They allow people outside of Hack Club to follow along with a project and understand the work that went into it.&lt;/p&gt;&lt;p&gt;However, while journals are excellent for documenting work, I do not believe they are a reliable way to measure effort. My argument is not that journaling should go away, but that journals should not be used as a quantitative system for counting hours.&lt;/p&gt;&lt;p&gt;Scalability Is The Real Problem&lt;/p&gt;&lt;p&gt;To have any meaningful understanding of how long something should take, you need experience. The response is usually that we need better reviewers, and I agree. However, this does not solve the underlying problem. It assumes that a large supply of highly experienced reviewers exists and can simply be recruited.&lt;/p&gt;&lt;p&gt;In reality, experienced hardware reviewers can be scarce. Most highly experienced builders are busy building. Even Blueprint, which had some of the strongest reviewers in Hack Club, struggled with review throughput. If accurate reviewing requires a relatively small pool of highly experienced people, I do not think that scales as hardware and Hack Club continues to grow, with 100k new people with Stardance, and 2.5 times more gap years this year.&lt;/p&gt;&lt;p&gt;This becomes even more concerning as hardware grows. Maintaining consistency across dozens of programs would require significant auditing and coordination. The system becomes increasingly dependent on everyone making similar judgment calls, despite those judgments being inherently subjective.&lt;/p&gt;&lt;p&gt;Manipulation and Consistency&lt;/p&gt;&lt;p&gt;Construct&apos;s initial journal inflation, where some organizers specifically inflated time under the pretense that “people often don’t know how long something took” is a proven case study showing that journals are really easy to manipulate. This remained under-the-radar for months, and was only stopped due to their other actions. Even if we can trust certain people to harshly deflate and keep things roughly accurate, that consistency never remains. Organizers can be very light on deflation, and in most cases I do not see how that would ever be caught.&lt;/p&gt;&lt;p&gt;Accuracy and Verification&lt;/p&gt;&lt;p&gt;Solely journal-based systems are fundamentally subjective. The use of solely journaling for deflation is prone to manipulation and bias, and can simply be inaccurate. They should not be used for a quantitative measurement of effort.&lt;/p&gt;&lt;p&gt;Journals are realistically guesses as far as deflation goes. A reviewer can never truly know how long work took. Even if reviewers have experience and a good understanding of hardware, they are still estimating.&lt;/p&gt;&lt;p&gt;As Seb, Hack Club&apos;s Quality and Integrity Manager, put it: &quot;I honestly think it&apos;s just guessed, sometimes people are just deflating a project that didn&apos;t need to get deflated just to avoid getting flagged and some other times I don&apos;t even think they are checking the project properly.&quot;&lt;/p&gt;&lt;p&gt;When I review projects, it always feels messy. First I look at their other projects to understand their technical depth. Then I compare it to my own experience, my understanding of the average hardware person, how detailed their logs are, and my general knowledge of the topic. Then I estimate how long it took and compare that to their journaled time and justification. Even if this process makes reviews more accurate, it doesn’t prove accuracy.&lt;/p&gt;&lt;p&gt;One thing that consistently concerns me is that many arguments for journal accuracy ultimately rely on intuition. A common response is that experienced reviewers know how long things normally take. That doesn’t prove it’s accurate; it just shows that having experienced reviewers is better than not having experienced reviewers. Similarly, people often point to Blueprint and say journaling works there. My question is always the same: what data can be used to support that it works while avoiding circular reasoning?&lt;/p&gt;&lt;p&gt;I’ve heard arguments like &quot;the expected time for a Hackpad is 8 to 10 hours and that’s what gets reported.&quot; But isn’t the expected time itself based on self-reported time? Additionally, Hackpads are recurring projects that are much easier to analyze than almost every other project.&lt;/p&gt;&lt;p&gt;The issue is that journals are difficult to verify. If someone adds 15 minutes to a journal, then 15 minutes to the next one, then 15 minutes to the next one, how does that become obvious? Even something like five extra minutes per journal can add up significantly over the course of a project. It also makes fraud easier to commit. Seb went further, confirming that with journaling &quot;it&apos;s very possible to fabricate a project out of thin air.&quot; Additionally, &quot;stupid&quot; things can take large amounts of time; the same task can vary dramatically depending on the person’s experience level. Among beginners, something that takes one beginner 30 minutes might take another beginner 3 hours; hard things don’t challenge different people the same way.&lt;/p&gt;&lt;p&gt;Aarav J, a Forge organizer, captured the core problem clearly: &quot;Right now the review process is so much so 100% guessing as neither party can accurately verify how many hours they really spent on the project. [...] Adding 10 or 15 minutes here and there to a journal will compound and eventually give massive gains.&quot; His experience with timelapsing as an alternative is instructive: &quot;In my opinion it makes life SO much easier for reviewers as we don’t have to guess – we can start validating their time based on real metrics that we receive from their lapse.&quot;&lt;/p&gt;&lt;p&gt;Where I Think Hardware Should Go&lt;/p&gt;&lt;p&gt;To be clear, I do not think journals should disappear. In fact, I think they are one of the best parts of Hack Club hardware.&lt;/p&gt;&lt;p&gt;However, I think journals should become documentation rather than be used for counting hours. They are excellent at documenting progress, teaching others, and showing work publicly. What they are not excellent at is proving how many hours somebody spent on a project. For example, Fallout uses a hybrid of journal-based documentation and timelapsing. Breadboard uses a mix of journal-based documentation and on-platform time tracking.&lt;/p&gt;&lt;p&gt;These systems have worked tremendously well; hours have become very easily recordable, verifiable, and real, with users having tracked 69,754 hours through Fallout.&lt;/p&gt;&lt;p&gt;When hardware was smaller and more experimental, journaling was a sufficient solution for coordinating effort at that scale.&lt;/p&gt;&lt;p&gt;That context has changed: hardware is now much larger and operating under conditions where informal judgment and self-reported quantitative tracking no longer remain consistent or scalable.&lt;/p&gt;&lt;p&gt;As a result, Hack Club hardware should move away from relying on journal-based quantitative measurement and continue actively replacing it with systems that are more verifiable and robust. Journals should remain, but their role as a mechanism for measuring effort is no longer justified by the demands of the current system.&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>Fraud Squad Applications Are Open</title><link>https://news.hackclub.com/news/fraud-squad-applications-open/</link><guid isPermaLink="true">https://news.hackclub.com/news/fraud-squad-applications-open/</guid><description>We&apos;re hiring. Read the form before you apply.</description><pubDate>Sat, 18 Jul 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;Fraud Squad applications are open. The form is here: forms.hackclub.com/fraud.&lt;/p&gt;&lt;p&gt;Read the intro on the form, it tells you what the job actually is, and I&apos;d rather you decide it&apos;s not for you before filling anything out than three weeks in into the role. If it still sounds like your kind of thing, I&apos;d love to have you on the team.&lt;/p&gt;&lt;p&gt;Submissions close next Wednesday, July 22nd at 15:00 Eastern Time. If you have any questions, feel free to reach out to me (Rowan) on Slack.&lt;/p&gt;&lt;p&gt;\- @Rowan :)&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>If You Want to Sound Good, Don&apos;t Use AI</title><link>https://news.hackclub.com/opinion/dont-use-ai/</link><guid isPermaLink="true">https://news.hackclub.com/opinion/dont-use-ai/</guid><description>People send me high-stakes messages about getting unbanned. Wanting to sound Serious and Professional, they turn to AI to rephrase and polish their message.</description><pubDate>Sat, 11 Jul 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;People send me high-stakes messages about getting unbanned. Wanting to sound Serious and Professional, they turn to AI to rephrase and polish their message.&lt;/p&gt;&lt;p&gt;Don&apos;t. If you use AI, I will take you less seriously, not more.&lt;/p&gt;&lt;p&gt;Sorry. It&apos;s not some kind of ideological holy war, I&apos;m just being practical. I can&apos;t tell the difference between &quot;Claude, here&apos;s my apology, make it classy&quot;, and &quot;Claude, write my apology, and make it sincere.&quot;&lt;/p&gt;&lt;p&gt;I want to hear from you. I promise I don&apos;t care about your splling, you&apos;re grammar, or your mastery of the em dash--really. I just want to know that what you&apos;re saying is real. Imagine if Hack Club HQ used AI to write our communications with you.&lt;/p&gt;&lt;p&gt;I&apos;m not alone. I know lots of people at HQ who feel this way, probably the majority, possibly everyone. Whether it&apos;s a ban appeal or a job application, let us talk to the real you.&lt;/p&gt;&lt;p&gt;Postscript: there is an ongoing debate about the use of AI to anonymize #meta posts. This piece is not about that.&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>New Bounty System to Fix Overdue Fulfillment</title><link>https://news.hackclub.com/news/fulfillment-bounties/</link><guid isPermaLink="true">https://news.hackclub.com/news/fulfillment-bounties/</guid><description>Teenagers deserve more trust than they get. People don’t let you do things because they’re afraid you’ll screw it up. Hack Club is proof that you are being underestimated. We trust teenagers with the kind of freedom, responsibility, and resources that most people only give to adults. We ask you to do something bigger and more ambitious than anything you’ve ever done. In return, you create a totally unique, life-changing community. So thanks!</description><pubDate>Fri, 10 Jul 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;Teenagers deserve more trust than they get. People don’t let you do things because they’re afraid you’ll screw it up. Hack Club is proof that you are being underestimated. We trust teenagers with the kind of freedom, responsibility, and resources that most people only give to adults. We ask you to do something bigger and more ambitious than anything you’ve ever done. In return, you create a totally unique, life-changing community. So thanks!&lt;/p&gt;&lt;p&gt;When people do something bigger and more ambitious than they’ve ever done though, mistakes will happen. That’s no reason not to do it. But that means we should be ready for mistakes when they come.&lt;/p&gt;&lt;p&gt;Many YSWS programs that stumble or faceplant do so on the rock of fulfillment. Promises get made, and then organizers struggle to keep them. But we don’t want you to pay the price for that. We want you to have certainty that our promises will be kept and your hard work will be rewarded.&lt;/p&gt;&lt;p&gt;So we’re creating a Fulfillment Bounty Program. Here’s the simple version: if you were promised a certain product by a certain date, and it’s more than 14 days overdue, fill out a form and HQ will send you what you were promised, along with a little something extra. Requests cannot be more than 180 days overdue, because at that point it may become logistically or metaphysically impossible to fulfill your order.&lt;/p&gt;&lt;p&gt;Check it out!&lt;/p&gt;&lt;p&gt;Dev is the YSWS Chief of Staff. His other writings can be found here.&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>Behind the Scenes at the Fire Department</title><link>https://news.hackclub.com/essays/behind-the-scenes-at-fd/</link><guid isPermaLink="true">https://news.hackclub.com/essays/behind-the-scenes-at-fd/</guid><description>Have you ever wondered what the Fire Department is up to? Most of our work is kind of behind the scenes and the community doesn&apos;t really get to know what happens. So I&apos;m here to give you a sneak peek at what we&apos;ve been doing over the past 3 months and better explain what that looks like.</description><pubDate>Thu, 02 Jul 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;Have you ever wondered what the Fire Department is up to? Most of our work is kind of behind the scenes and the community doesn&apos;t really get to know what happens. So I&apos;m here to give you a sneak peek at what we&apos;ve been doing over the past 3 months and better explain what that looks like.&lt;/p&gt;&lt;p&gt;In the span of the past 3 months:&lt;/p&gt;&lt;p&gt;Out of 330 cases the split of infractions looks like this:&lt;/p&gt;&lt;p&gt;And when it comes to the actions we took, the split looks like this:&lt;/p&gt;&lt;p&gt;You might be wondering how we got 1000 Shroud reports but only 330 ended up becoming resolved conduct cases in LYLA. Some reports are duplicates submitted by different people, some others don&apos;t have enough context or information for us to work off of and some are about stuff that doesn&apos;t break the Code of Conduct. Every report we get is looked at even if the outcome ends up being no action taken by us. In some rare cases we don&apos;t log actions we take. This is specific to informal DM reminders and age-related cases like those involving adults.&lt;/p&gt;&lt;p&gt;When we get a report, we usually need to get context and evidence (if it isn&apos;t already given), look at previous history and sometimes discuss amongst ourselves before a decision is made, especially if a case is complex. Some reports can be reviewed in a few minutes, while others can take much longer which again is dependent on the complexity.&lt;/p&gt;&lt;p&gt;One of the biggest changes we&apos;ve seen over the past three months has been an increase in the volume of reports we get due all the new people joining from Stardance. We had about 800 Shroud reports between January and April while LYLA cases filed remained just about the same. As more people join the community, it becomes more active so the number of reports is bound to increase. We got a new batch of firefighters that came in and they have been doing a phenomenal job at making sure these reports are handled well. Over the past week alone we have had a median case closure time of about an hour which is incredible from our previous 3 hour case closure time before the new batch joined.&lt;/p&gt;&lt;p&gt;Bans and shushes are the moderation actions that everyone usually sees (cough… #community-logs), but as you can tell around half of all conduct cases over the past three months were resolved with warnings while bans and shushes make up a much smaller portion. Because warnings happen in private it is easy to assume moderation is mostly about banning or shushing people. In reality a lot of our time is spent helping people who break the Code of Conduct understand what they did wrong and giving them the chance to be better.&lt;/p&gt;&lt;p&gt;While putting these numbers together we realised what we do is pretty much invisible. So we talked about this in the Fire Dept and we think it&apos;s important for the community to have a better understanding of what we are doing. So over the coming weeks, we&apos;ll be adding moderation statistics like the ones here to #community-logs. For now we won&apos;t be removing individual logs, but we hope this new format helps answer your questions about what we do while being as transparent as we can and giving everyone a better idea of how we work to keep Hack Club a welcoming and enjoyable space for everyone!&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>Hacker Value</title><link>https://news.hackclub.com/essays/hacker-value/</link><guid isPermaLink="true">https://news.hackclub.com/essays/hacker-value/</guid><description>&quot;wait, what do you mean you are not filling the shop with grants?&quot;</description><pubDate>Tue, 30 Jun 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;&quot;wait, what do you mean you are not filling the shop with grants?&quot;&lt;/p&gt;&lt;p&gt;Editor&apos;s note: this article is reproduced with the author&apos;s permission. The original can be found here.&lt;/p&gt;&lt;p&gt;When I first joined Hack Club, it was because of Shipwrecked, an all-expenses-paid hackathon on an island near Boston. I was completely blown away by it and honestly thought it was a scam the moment it landed in my inbox.&lt;/p&gt;&lt;p&gt;I spent around 60 hours across four projects, which are unfortunately collecting dust on my GitHub account nowadays. I really haven’t had the time to come back to them and properly polish them, mostly because I’ve been busy with school and other responsibilities I deal with on a day-to-day basis.&lt;/p&gt;&lt;p&gt;And I’m actually pretty proud of them! Some even reached around 14 stars on GitHub, which is honestly surprising considering they were built over the span of about a month. I know that if I ever come back to polish them properly, they could blow up in popularity.&lt;/p&gt;&lt;p&gt;Sadly, my visa was rejected at the U.S. embassy in my country after the interview, so I couldn’t go to Shipwrecked. To this day, I’m still not fully sure why it was rejected, but I’m pretty sure it was related to the fact that, back then, we didn’t have a system like https://visas.hackclub.com where the consulate could verify the invitation letter I brought that day.&lt;/p&gt;&lt;p&gt;I spent all the hours I earned on visa reimbursements exclusively, since there really weren’t any items in the shop at the time, and I didn’t know programs gave out MacBooks, 3D printers, and other stuff. So I just left it at that and was honestly happy to have had the experience of flying to another city and visiting the U.S. embassy, which was genuinely beautiful, even if I got rejected in the end at that same place.&lt;/p&gt;&lt;p&gt;I may not have left with a MacBook or a 3D printer, which I would have absolutely loved to have, but I did leave with the experience of going to one of the coolest places I had wanted to visit for a long time, seeing how everything worked there, and experiencing the views of the city. At the same time, I left with four really cool projects that I’m genuinely proud of.&lt;/p&gt;&lt;p&gt;Hacker value comes from something that will genuinely help you build projects as an incentive to keep going. It’s something you’ll see, get your hands on, and most likely use to build your next project, or at least build it with the help of it.&lt;/p&gt;&lt;p&gt;Sometimes YSWS organizers know certain things are part of a hacker’s identity. That’s why we add items like blahajs to the shop, because we know people are going to connect with them and genuinely appreciate having them as a reminder of the journey they have went through. The same goes for stickers and similar things, like fursuits.&lt;/p&gt;&lt;p&gt;That’s why you’re most likely never going to see something like an iPhone 17 Pro Max 4TB orange edition in a program shop, because let’s be real here, you definitely do not need that to make projects, nor is it going to help you much at all considering Xcode exists. We don’t want to normalize expensive status-item rewards because it changes the expectations around programs.&lt;/p&gt;&lt;p&gt;Grants are the last resort when fulfilling an item in a shop. There are risks that come with offering grants, especially how they can make people feel like they’re working for a wage instead of being motivated to build projects for fun.&lt;/p&gt;&lt;p&gt;That’s why when a grant-based reward is added, like a Steam grant, it’s penalized by lowering the $/hr ratio of the item as a way to make the people who really want that prize work for it.&lt;/p&gt;&lt;p&gt;There are people who tell me they have a mouse that’s five times cheaper than the MX Master 3S we have in our program shops, and I should just give them a grant. But is that cheaper mouse actually going to last? Are you even going to remember it in three months and think, “Damn, I made a bunch of cool projects and grinded so hard to get this mouse, and it’s still rocking”? Probably not.&lt;/p&gt;&lt;p&gt;Adding vague grant items like a “$5/hr mouse grant” is honestly something really sad to me. I understand it for things like laptop grants, because that laptop is going to become your best friend while building and shipping projects. But vague grant items tend to push people into doing the bare minimum work possible just to get something finished and claim the reward, instead of actually caring about the projects they’re making.&lt;/p&gt;&lt;p&gt;I know I probably repeated myself a lot throughout this post. I’m really not the best at writing my thoughts, and this is one of the first times I’ve actually decided to make a blog post.&lt;/p&gt;&lt;p&gt;You might still think that, at the end of the day, you’re still working for a reward and aiming for an item in the shop... and that’s valid! I actually agree with you.&lt;/p&gt;&lt;p&gt;My point here is that I want you to aim higher and set a higher bar for what you build to earn the prize you want. I want you to be creative, make cool projects, go crazy with them, blow them up, and maybe even become popular because of them.&lt;/p&gt;&lt;p&gt;I could easily not care about you, the teenager making projects. I could throw a bunch of grants into the shop and lock them to merchants and call it a day. But I do care about you, and I want you to improve and learn something new every day. That’s why I put so much effort into what I do.&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>On Answering the Right Question</title><link>https://news.hackclub.com/opinion/answering-the-right-question/</link><guid isPermaLink="true">https://news.hackclub.com/opinion/answering-the-right-question/</guid><description>Hi! I&apos;m Raygen, your local hardware hack clubber and statistics nerd. I spent 2 years leading my FRC team&apos;s scouting team in the past, where I was responsible for one of, if not the most comprehensive scouting system in FIRST capable of telling you literally everything a robot did in a game with very high accuracy. I love data.</description><pubDate>Wed, 24 Jun 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;Hi! I&apos;m Raygen, your local hardware hack clubber and statistics nerd. I spent 2 years leading my FRC team&apos;s scouting team in the past, where I was responsible for one of, if not the most comprehensive scouting system in FIRST capable of telling you literally everything a robot did in a game with very high accuracy. I love data.&lt;/p&gt;&lt;p&gt;That&apos;s, frankly, an insane amount of data. It led my team to do a lot of thinking, notably: what could we derive from that data? One of my biggest takeaways from that (and the couple statistics classes I&apos;ve been in) has been to ask an important question: What are you trying to measure?&lt;/p&gt;&lt;p&gt;This sounds similar to Villarante&apos;s article, and it somewhat is. The thing is, Villarante never answered the question of &quot;What are you trying to measure?&quot; Villarante discussed the question &quot;How are you measuring your data?&quot;&lt;/p&gt;&lt;p&gt;These are separate questions. To summarize Villarante&apos;s article, he proposes that the study measured the gap between what genderize.io thinks your identity is from your name and the delta between what you state you are. I agree with the issues Villarante has identified about this methodology, but I also have done enough studies that I understand why this is the methodology used. From exclusively the data that is in Unified, this is a half-decent methodology and I can&apos;t think of a better one. It&apos;s not ideal and it does misrepresent things a tad, but as long as it&apos;s the only methodological flaw, it&apos;s fine enough.&lt;/p&gt;&lt;p&gt;Villarante goes on to say that it would be better to measure trends over time. I agree with this some, but I still believe the mark is being missed.&lt;/p&gt;&lt;p&gt;Let&apos;s pretend, for a moment, that no studies have been taken. How do we make one? Well, the answer is a series of questions. We first ask a question: &quot;What do we want to know?&quot; The answer to this question is &quot;The quantity of an identity in Hack Club&quot;.&lt;/p&gt;&lt;p&gt;This is good. We now know what the conclusion we want is. We then determine that figuring out the representation of an identity means figuring out the amount of hours they&apos;ve shipped to Unified. There&apos;s also some thoughts about how to count transgender individuals after this, but it&apos;s not what I want to point out.&lt;/p&gt;&lt;p&gt;Here&apos;s a color-coded flowchart showcasing how the study is come up with and how it functions.&lt;/p&gt;&lt;p&gt;There&apos;s something not right here, though. There&apos;s an extra blue box that is fundamentally changing the study and the answer given: trying to fix a failure mode. This was intentional. To quote the original article from zrl &amp;amp; eps:&lt;/p&gt;&lt;p&gt;“After determining gender identity (more on that in a moment) we found each identity&apos;s percentage of hours shipped rather than percentage of people who are in the DB. This avoids the failure mode where groups superficially appear to be equal, when in reality one group is participating 10x more than another group.&lt;/p&gt;&lt;p&gt;The best way to explain what&apos;s going on is an example.&lt;/p&gt;&lt;p&gt;Assume that Unified has a total of 10 Hack Clubber projects in it. 9 of these are from cis girls and 1 of them is from a cis guy. Each cis girl spent 1 hour on their project, while the cis guy spent 100 hours. I&apos;m excluding transgender individuals from this for the sake of easier math. Here&apos;s this represented as a table:&lt;/p&gt;&lt;p&gt;If we do the math, 90% of the populace in my Unified Mini table is made up of cis girls. There is 109 total hours contributed by all identities. Let&apos;s also account for the failure mode proposed by zrl &amp;amp; eps, by finding the percentage that each identity has contributed to Unified Mini. For cis girls, this is ~8.2%. For cis guys, this is ~91.7%. Congratulations, 91.7% of Unified Mini is cis guys!&lt;/p&gt;&lt;p&gt;Wait, what just happened? What&apos;s going on here? We&apos;ve just changed the question we&apos;re answering.&lt;/p&gt;&lt;p&gt;This has not given us the representation of each identity in Unified Mini, it&apos;s given us the contribution of each identity. It answers the question &quot;How much does each identity contribute to Unified?&quot; but it does not answer the question of &quot;What is the percentage of an identity in Hack Club?&quot;. This is still useful data, but very separate questions with separate answers. This is a stacked bar chart showcasing the difference:&lt;/p&gt;&lt;p&gt;I apologize to all dark mode users, and I blame Google Sheets.&lt;/p&gt;&lt;p&gt;Here&apos;s my preferred study. It boils down to focusing on the representation of the populace, then deriving data from that.&lt;/p&gt;&lt;p&gt;There&apos;s a lot more data available here. This version of the study is able to provide:&lt;/p&gt;&lt;p&gt;A note: I&apos;ve suggested deduplicating names. Unified might have my name in it 5 times, so we need to only count my name once or else we might not have the right data. In an ideal world this would also be able to account for a transgender individual changing their name, but I believe we shouldn&apos;t try to track the changes in people&apos;s identity for privacy.&lt;/p&gt;&lt;p&gt;Evan is right when he says that if you want truth, you have to forget perfection. You just need to ensure that your truth is even the right one. You can&apos;t measure the weather with a scale, and you can&apos;t measure an identity by how many hours it&apos;s worked.&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>If You Want Truth, Forget Perfection</title><link>https://news.hackclub.com/opinion/perfect-measurements/</link><guid isPermaLink="true">https://news.hackclub.com/opinion/perfect-measurements/</guid><description>&quot;Measuring the Wrong Thing&quot; is the sort of piece I&apos;d like to publish more often. It&apos;s smart, careful, and clearly motivated by truth. I also think it&apos;s wrong.</description><pubDate>Wed, 24 Jun 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;&quot;Measuring the Wrong Thing&quot; is the sort of piece I&apos;d like to publish more often. It&apos;s smart, careful, and clearly motivated by truth. I also think it&apos;s wrong.&lt;/p&gt;&lt;p&gt;I.&lt;/p&gt;&lt;p&gt;If this comparison feels unfair, take a look at this:&lt;/p&gt;&lt;p&gt;This is a high-end scale. The box is there because otherwise, air currents will mess up your measurements. And thermometers have problems of their own; the fluid&apos;s expansion is nonlinear as a function of temperature. But if your recipe calls for 200g of beans, and your kitchen scale does not have a glass box to prevent the measurement from being affected by air currents, do you declare the scale useless? Or do you use it anyway because it is accurate enough for what you&apos;re doing?&lt;/p&gt;&lt;p&gt;I appreciate people pointing out our methodological flaws. Because our audience is Hack Clubbers, we included an entire section on methodological flaws. It makes me happy that Hack Club is the kind of place where we can do that. So it&apos;s not like we thought the numbers were perfect. We knew they were flawed, were up front about the flaws, and published anyway because the results are still useful. We are not measuring the wrong thing. We are measuring the right thing, imperfectly.&lt;/p&gt;&lt;p&gt;II.&lt;/p&gt;&lt;p&gt;The question is, &quot;Are the methodological flaws big enough to invalidate the result?&quot; The answer is no.&lt;/p&gt;&lt;p&gt;Think about correlated versus uncorrelated errors. If errors point in a random direction, meaning they are uncorrelated with each other, then the errors cancel out. If I roll a die and tell you it landed on a 1, you do not know whether it was a 4-, 6-, 20-, or 100-sided die. But if I roll 100 identical dice and tell you that the average roll was 3.7, you can infer that they were 6-sided dice. 1 Our 12-month Unified DB sample was large, like rolling hundreds of dice, so uncorrelated errors are not an issue. Statistical noise can be beaten with scale. This is why polling a few thousand people can give you accurate information about public opinion in a country of 330 million people.&lt;/p&gt;&lt;p&gt;If the errors are correlated, that&apos;s a different story. Errors that distort your data in one direction can absolutely cook your results. And as Villarante points out, we have a source of correlated error: trans people who change their names AND gender identities together between projects get counted as cis people in the database. In which direction does this error point? It points towards us undercounting trans people. As we pointed out in our original article, there were also at least two other sources of correlated error, both of which pointed in the direction of undercounting trans people.&lt;/p&gt;&lt;p&gt;So what do you do with this? Throw out the result? No, not at all.&lt;/p&gt;&lt;p&gt;Consider the context. Hack Club has had many debates about gender representation. One question (or disagreement) I&apos;ve seen many times is whether transgender and nonbinary people are underrepresented at Hack Club. This context matters, because it means that our directionally-biased result is actually quite useful.&lt;/p&gt;&lt;p&gt;Villarante is correct that looking at trends over time would be revealing, and less subject to error. But that doesn&apos;t exhaust what our data can show us. Suppose you have a thermometer that you know always reads too cold. You want to know whether to wear shorts today. You check the thermometer, and it says the temperature is 80 degrees. Should you wear shorts? Yes, you should. The thermometer is directionally biased, so the temperature outside is 80 degrees or higher. This study suggests (but doesn&apos;t prove) a lower bound on the representation of trans people at Hack Club: equal representation. This is good news!&lt;/p&gt;&lt;p&gt;Think in terms of evidence, not proof. Villarante learned to critique studies from a stats class. I took a stats class, but I learned much more about it from Slate Star Codex, which introduced me to Bayes&apos; Theorem. Formally stated, it looks like this, where A is the claim and B is the evidence:&lt;/p&gt;&lt;p&gt;$$ P(A \mid B) = \dfrac{P(B \mid A) \, P(A)}{P(B)} $$&lt;/p&gt;&lt;p&gt;I love treating beliefs as probabilities, not yes-or-no binaries. It makes life so much easier. I can&apos;t tell you how many times I saw people deadlocked over whether some piece of evidence &quot;proves&quot; a certain conclusion true or false. It&apos;s so liberating to just say, &quot;I now think this is less likely than I did before.&quot; Proof is a luxury. Life almost never gives us proof of anything, but it gives us plenty of evidence. Thinking accordingly feels like a cheat code.&lt;/p&gt;&lt;p&gt;Start with the base rate assumption that Hack Club resembles the population as a whole, and trans people are neither over- nor underrepresented. Now add the evidence of a study finding that they are slightly overrepresented 2 . You should update your probability in the direction of trans people being overrepresented at Hack Club, and away from trans people being underrepresented, because a study that undercounted trans people still did not find them underrepresented.&lt;/p&gt;&lt;p&gt;&quot;This changes everything&quot; or &quot;this changes nothing&quot; is a false dichotomy. Learning happens in between.&lt;/p&gt;&lt;p&gt;III.&lt;/p&gt;&lt;p&gt;Several people said, &apos;just do a survey! If you want to know, put away Genderize and just ask&apos;. I want to note that our methodology for counting nonbinary Hack Clubbers did exactly what our critics wanted--we asked--and found that nonbinary people are overrepresented. I haven&apos;t seen anyone challenge that finding. All of the controversy around the article is about counting trans people in particular, but the controversy about gender at Hack Club extends into whether nonbinary people are underrepresented. It seems they are not, which is good. I know many wonderful nonbinary Hack Clubbers and I&apos;d be sorry to learn we were missing out on more. My informal impression is that the representation of nonbinary, rather than trans teens, is actually the most contentious question in this area. This finding alone made the study worth doing.&lt;/p&gt;&lt;p&gt;But also, I want you to notice that a direct survey about trans Hack Clubbers would have its own significant sources of error. It would suffer from response bias, because trans Hack Clubbers might not be sure they are trans, or might not feel comfortable sharing. This would undercount trans people. It would also suffer from sampling bias based on which set of people we asked.&lt;/p&gt;&lt;p&gt;Does this mean surveys are useless? No! Our method had limitations, as would a survey. But I&apos;m not saying dismiss both. I&apos;m saying take both seriously. If a large survey of Hack Clubbers found trans underrepresentation, I&apos;d treat it as important evidence. You should treat this study as important evidence too.&lt;/p&gt;&lt;p&gt;IV.&lt;/p&gt;&lt;p&gt;You can&apos;t escape. If you have an opinion about the level of trans representation at Hack Club, it must be based on something. It can be based off of our flawed study, or it can be based off of a flawed survey, or it can be based off of your flawed personal impressions (spoiler: the last one is the worst option). But you have to base it on something, or else you have to have no opinion at all. We did this study for the ones who do have an opinion--and also for ourselves--so that we can have better data, because this question is causing conflict, and many conflicts are healed when people can agree on facts.&lt;/p&gt;&lt;p&gt;I did not have an opinion before conducting this research, just a hunch. On the basis of this research, and after reading all the critiques, I am updating my beliefs. I think it is unlikely that trans and nonbinary people are underrepresented at Hack Club. Not impossible, but unlikely. I remain open to evidence to the contrary, and the evidence doesn&apos;t need to be perfect.&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>Hack Club AMA with Astronauts Aboard the ISS</title><link>https://news.hackclub.com/news/ama-with-astronauts-on-iss/</link><guid isPermaLink="true">https://news.hackclub.com/news/ama-with-astronauts-on-iss/</guid><description>Hack Club’s programs reach people all over the world, but nobody in space. We are officially fixing this oversight. On September 1, our AMA series will cross the Kármán line to reach the crew of the International Space Station.</description><pubDate>Tue, 23 Jun 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;Hack Club’s programs reach people all over the world, but nobody in space. We are officially fixing this oversight. On September 1, our AMA series will cross the Kármán line to reach the crew of the International Space Station.&lt;/p&gt;&lt;p&gt;What would you ask an astronaut? NASA gives this advice:&lt;/p&gt;&lt;p&gt;Want to ask a question? Join the Stardance Challenge, our program where you make cool STEM projects and get free STEM prizes. The shop is selling 12 questions for the AMA, along with everything from macbooks to hot chocolate, and once-in-a-lifetime experiences like these! Your questions and the astronauts’ answers will be presented on the Learn with NASA youtube channel. Our usual format for terrestrial guests will have to change; questions will be pre-recorded and must be submitted to NASA for screening no later than August 1.&lt;/p&gt;&lt;p&gt;The ISS orbits the Earth at 76.6 kilometers per second. It is arguably the most expensive object ever created. It is also a reminder that when we let go of fear and conflict, we can build things together that change the world.&lt;/p&gt;&lt;p&gt;Start thinking of questions.&lt;/p&gt;</content:encoded><media:content url="https://www.nasa.gov/wp-content/uploads/2023/02/International-Space-Station-in-2021.jpg" medium="image"/><media:thumbnail url="https://www.nasa.gov/wp-content/uploads/2023/02/International-Space-Station-in-2021.jpg"/><media:title type="plain">The International Space Station</media:title></item><item><title>Gender Identity at Hack Club</title><link>https://news.hackclub.com/news/gender-identity-at-hackclub/</link><guid isPermaLink="true">https://news.hackclub.com/news/gender-identity-at-hackclub/</guid><description>How many Hack Clubbers are boys? How many are girls? How many are nonbinary? And how many are transgender? We set out to answer this question. Here are the results.</description><pubDate>Mon, 22 Jun 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;How many Hack Clubbers are boys? How many are girls? How many are nonbinary? And how many are transgender? We set out to answer this question. Here are the results.&lt;/p&gt;&lt;p&gt;We looked at the Unified DB. When you ship a project, after it passes reviews and quality controls, this is where we record it. The DB is quite important at HQ. It&apos;s our main measure of whether we&apos;re succeeding at our mission to get you making things. Each YSWS program&apos;s funding is based on how many hours it adds to the DB.&lt;/p&gt;&lt;p&gt;At what point are you a Hack Clubber? When you make an HCA account? When you send a Slack message? When you join a YSWS? When you ship a project?&lt;/p&gt;&lt;p&gt;There is no clear minimum threshold. But there is a clear maximum threshold: when your name appears next to a project in the DB, there is no more debating whether the system has reached you.&lt;/p&gt;&lt;p&gt;After determining gender identity (more on that in a moment) we found each identity&apos;s percentage of hours shipped rather than percentage of people who are in the DB. This avoids the failure mode where groups superficially appear to be equal, when in reality one group is participating 10x more than another group.&lt;/p&gt;&lt;p&gt;We looked at two sets of data:&lt;/p&gt;&lt;p&gt;For Stasis, we chose to look at projects shipped rather than attendees in order to exclude the effect of subsidies and other measures to increase girls&apos; participation. This figure is our pre-intervention baseline.&lt;/p&gt;&lt;p&gt;Teens self-report their gender identity for events and when they ship a project. It&apos;s usually a free-response field, so they can potentially put anything. Self-identified male, female, and nonbinary teenagers were found by classifying and counting these answers. We excluded people who did not report a gender identity.&lt;/p&gt;&lt;p&gt;We do not collect data directly on whether Hack Clubbers are transgender. To find them, we ran the names through genderize.io to code them as male, female, or gender neutral. Teens with male-coded names who self-identified as female were coded as transgender. However, we did not classify teens as transgender if they had a male-coded name and self-identified as female or if they have a female-coded name and self-identified as female, but a male-coded name on their auth.hackclub.com identity verification (we did not use any auth.hackclub.com data for this). This is because Genderize frequently misclassifies South Asian male names as female, so applying our method to female-coded names would likely overcount trans Hack Clubbers.&lt;/p&gt;&lt;p&gt;For all of these operations, we used AI to classify and count self-reported identity. Finally, we applied manual spot checks. After pulling out trans and nonbinary shippers, we looked at the top 15 cis male shippers and the top 15 cis female shippers, and re-coded the ones that we personally know to be transgender or nonbinary. We kept doing this until the top 15 in both groups had no one that–as far as we know–is transgender. We looked at the top 15 shippers whom AI could not classify, and re-coded the ones we could (for example, one French boy listed his gender identity as &quot;il&quot;).&lt;/p&gt;&lt;p&gt;This left us with 5 categories:&lt;/p&gt;&lt;p&gt;All Unified DB projects, 12 months, % of hours attributable to each group&lt;/p&gt;&lt;p&gt;Stasis Unified DB projects from in-person Stasis attendees, % of hours attributable to each group&lt;/p&gt;&lt;p&gt;Reference: minority gender identity among US adults age 18-29&lt;/p&gt;&lt;p&gt;Source: Pew Research Center&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>Measuring the Wrong Thing</title><link>https://news.hackclub.com/opinion/measuring-the-wrong-thing/</link><guid isPermaLink="true">https://news.hackclub.com/opinion/measuring-the-wrong-thing/</guid><description>Hello, I am back for another article, this time directly replying to another Slacker News article about a gender study done by Evan and Zach. Many years ago, I took a statistics class, so we learned about the importance of conducting good studies to answer real questions. Let&apos;s dig into this together.</description><pubDate>Mon, 22 Jun 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;Editor&apos;s note: this piece was submitted pseudonymously&lt;/p&gt;&lt;p&gt;Hello, I am back for another article, this time directly replying to another Slacker News article about a gender study done by Evan and Zach. Many years ago, I took a statistics class, so we learned about the importance of conducting good studies to answer real questions. Let&apos;s dig into this together.&lt;/p&gt;&lt;p&gt;Say Ivan and Jack want to count the left-handed people in a crowd, but they aren&apos;t allowed to just ask directly. So they use a shortcut. Almost everyone wears their watch on the hand they don&apos;t write with, which means right-handers wear it on the left wrist and left-handers wear it on the right. So they figure: count the watches on right wrists, and you&apos;ve counted the lefties.&lt;/p&gt;&lt;p&gt;Except, it&apos;s not that simple. Plenty of right-handed people wear their watch on the right anyway, out of habit or just style, and some lefties wear theirs on the left like everyone else. So Ivan and Jack catch a few real lefties, wrongly tag a bunch of righties, and miss every left-handed person who wears their watch the ordinary way. To check their work, they compare the list against the handful of left-handed friends they have and nudge it until it looks about right. Then they announce: 4% of the crowd is left-handed.&lt;/p&gt;&lt;p&gt;But they actually never measured handedness. They measured unusual watch placement, which overlaps with being left-handed a little and is otherwise a completely different thing. &quot;4%&quot; describes where people wear their watches, not which hand they write with.&lt;/p&gt;&lt;p&gt;I want to briefly dig into the issues with measuring here, but not dwell on it since some people have already pointed out the issues (especially that one meta thread, bravo to the author of that, sorry that the replies tanked in terms of reasoning)&lt;/p&gt;&lt;p&gt;The study never measured gender identity. It measured the gap between what genderize.io thinks your name is and what you said you are, and called that gap &quot;transgender.&quot; Those are not the same thing. A cis girl named Alex can already break this. A transfem who already ships under her real name would count as a female self-ID, but is filed away as cis. The further along you are, the more invisible you become, which means the one bucket that would actually be interesting is built to miss the people. The meta author said this better than I can, and added the part I&apos;d have missed: if someone ships under one name and later under another, the database sees two strangers instead of one person, so their hours get split across genders and the headcount quietly inflates. Stack that on top of decimal-point percentages the method cannot support (72.1, really?) and a comparison to a US national figure that counts people, not shipped hours, and you have a table that feels more precise than it really is.&lt;/p&gt;&lt;p&gt;But let&apos;s not dogpile on clear methodology issues and zoom out and ask, &quot;What does this actually teach us?&quot;&lt;/p&gt;&lt;p&gt;Research should be done to either a) prove an existing point or b) uncover new information. This failed at both.&lt;/p&gt;&lt;p&gt;When you spend any time doing basic surface-level research, you can find some easy ball knowledge.&lt;/p&gt;&lt;p&gt;Let&apos;s use the fact &quot;Hack Club is mostly boys&quot; as an example. We don&apos;t need an API to tell us this; we just know it is a fact. The study claims that 72.1% of hours come from cis boys, which sounds like validation, but proving a point means putting it on firmer ground than it stood on before, and this study does not. The 72 to 18 split withstands the study&apos;s flaws because the gap is too big to rig, and no amount of genderizing errors can turn this landslide into a tie. We can only trust this number because of how large the gap is, not because the method is any good. You also can&apos;t call the method good for the numbers you liked and bad for the ones you didn&apos;t. If it was unreliable enough to wreck the trans count, it was never reliable enough to &quot;prove&quot; the boys count. The study didn&apos;t prove anything new with better proof, it just restated something everyone knew with a fat asterisk on it.&lt;/p&gt;&lt;p&gt;Now for b) uncover new information. The new information would be the smaller numbers, how many trans kids, how many nonbinary kids, the precise figure for girls. That&apos;s the part we genuinely didn&apos;t know walking in, and it&apos;s exactly the part the method can&apos;t answer. A transfem shipping under her real name reads as cis. One person shipping under two names reads as two people in two buckets. The numbers most likely to be new are the numbers most thoroughly mangled, and a number you can&apos;t trust isn&apos;t data, it&apos;s a guess dressed up as a neat table.&lt;/p&gt;&lt;p&gt;There was a version of (b) that would have worked, but the study completely missed the mark. Here is the thing about a flawed measurement: it can still tell you something real, as long as you take it the same flawed way more than once. If the method always undercounts trans kids by roughly the same amount, that error mostly cancels out when you compare two points in time. You don&apos;t need the number to be right; you just need the mistake to be consistent.&lt;/p&gt;&lt;p&gt;That is what makes a trajectory worth more than a snapshot. &quot;Girls are 18% of hours&quot; tells you almost nothing on its own. &quot;Girls went from 15% to 18% in a year, measured the same way both times&quot; tells you the work to bring more girls in is actually working, and that is genuinely new information, even with a strange method. The study even set this up: it called the Stasis figure a &quot;pre-intervention baseline&quot; but then never followed up with a post-intervention measurement.&lt;/p&gt;&lt;p&gt;This study failing at both objectives is a net negative, because people will treat it as a success. Someone commented we&apos;re only a couple points off the national rate, so we&apos;re probably fine. But this is a study that taught us nothing, being used to answer a question we should have kept digging for. The reassurance is fake because the method that produced it can&apos;t see the people it&apos;s supposed to be about. &quot;4%, close to Pew, moving on&quot; is the worst outcome if you actually care whether trans and nonbinary kids can show up here and stay.&lt;/p&gt;&lt;p&gt;Doing good studies is not too hard if you just ask one question that this study never asks: what decision is this number supposed to inform? If you can&apos;t find a good answer, this is not &quot;research&quot;; it&apos;s just a random number.&lt;/p&gt;&lt;p&gt;The meta author put it best, so I&apos;ll borrow it here: the database can see where you started and where you ended up. It just can&apos;t see that it&apos;s the same journey. Neither can a single snapshot of a community. We never needed a study to learn that Hack Club is mostly boys. We needed one to learn if that&apos;s changing, and for whom. That study still hasn&apos;t been run.&lt;/p&gt;&lt;p&gt;Thank you all for reading my posts, it is nice to see them being used and discussed in the Slack.&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>On Slop</title><link>https://news.hackclub.com/opinion/on-slop/</link><guid isPermaLink="true">https://news.hackclub.com/opinion/on-slop/</guid><description>I&apos;ve reviewed software for a few programs recently, and it&apos;s never really been harder to do so. Programs are hit with, frankly, an absurd amount of submissions. I used to look at reviewers with disdain - come on, it takes like a few minutes for a review, and so how hard could it possibly be for them just to review my project waiting for a month? Just take a look at any support channel. There are literally hundreds of tickets looking for reviews in #horizons-help and #macondo-help. There are people who wait weeks or even a month in some circumstances, even as reviewers are actively reviewing.</description><pubDate>Mon, 15 Jun 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;I&apos;ve reviewed software for a few programs recently, and it&apos;s never really been harder to do so. Programs are hit with, frankly, an absurd amount of submissions. I used to look at reviewers with disdain - come on, it takes like a few minutes for a review, and so how hard could it possibly be for them just to review my project waiting for a month? Just take a look at any support channel. There are literally hundreds of tickets looking for reviews in #horizons-help and #macondo-help. There are people who wait weeks or even a month in some circumstances, even as reviewers are actively reviewing.&lt;/p&gt;&lt;p&gt;Standing on the other side, it&apos;s not great. It&apos;s pretty demoralizing to watch the onslaught of slop pouring in, beginner projects, broken ones, occasionally fraud. And of course, most people aren&apos;t trying to make low-quality, broken, sloppy submissions. They often just want to get a given X reward, or visit Y event. Queues fill with hundreds in the backlog, a slog to clear at scale.&lt;/p&gt;&lt;p&gt;Slop is a term we often toss around like candy. And yet, despite that, there exists no good definition of it. We can definitively classify some projects as slop - for example, Tic-Tac-Toe game #53 is probably something sloppy. These projects oftentimes serve no purpose or have no value. And with the growth of AI, the line between beginner projects, made with care but a lack of experience, and vibeslop (also often beginners) begins to blur to an extreme.&lt;/p&gt;&lt;p&gt;Before AI, the quality of a project, just the sheer weight of what it was, used to carry a useful signal about how much time was spent. You indeed couldn&apos;t build a functioning chat app all that easily (at least, not with a little bit of prompting to your LLM of choice). Just the fact that it existed was enough to justify the effort backing it - and of course, the commits to show progress. Now we deal with an onslaught of slop, where truly beginner projects are of a lower complexity than AI generated projects. This is no longer a useful signal in any shape or form. The time no longer indicates much as either - the number of times I&apos;ve seen typed-out AI-generated code, all to inflate hours, is staggering. It&apos;s impossible to know if someone was &quot;really&quot; spending that much time thinking, making, developing, or whatnot. Save for a few incredibly high-quality or innovative projects, this is the vast majority of projects being reviewed right now. And as we have sloppy projects with AI, we have sloppy projects without. If you haven&apos;t yet, you should read Deven&apos;s Shitty Projects page in the introduction to the YSWS handbook. Everybody has a shitty first project, and most Hack Clubbers are new folks. We want to reward the time they spent building. In reality, the true distinction between sloppy and shitty ends up being the effort and process, which we can capture with a variety of signals, but is a nuance to be communicated.&lt;/p&gt;&lt;p&gt;In the face of all of this, I have a question. What exactly are we optimizing for? What do we care about? The Weighted Project model incentivizes programs to get teens spending more hours... doing what exactly? Learning? Building? Shipping? Because all of these hours are certainly not worth the same amount. There are people who build incredible things with AI, projects that I use on a daily basis that have more AI-written code than human-written code, and there are people who use AI as a means to an end, to get some predefined rewards, without going through the process of learning and understanding what they built (or just make HTML/CSS vibeslop en masse). The WP model is supposed to alleviate this issue by exerting itself as a program-level pressure, rather than at an individual level. It becomes no surprise, then, that when programs move this down to an individual level by directly providing them some $ worth of grants per hour they spend, that this transactional nature leads to more slop - which is a topic to talk more in depth about another time.&lt;/p&gt;&lt;p&gt;On the other side, the WP model also has the side effect of reviewslop. Internal justifications are supposed to prevent a reviewer from submitting approvals without checking projects, and at that they do a pretty good job (over the previous system of doing nothing). But justifications are plenty, and audits are few, and I&apos;ve seen less than stellar justifications enter Unified, across multiple YSWS programs. It&apos;s also a very conflicting goal. When the bottleneck is review, and when the queue fills up with literally dozens of projects a day, sheer throughput becomes the primary goal, and quality goes second. Oftentimes I see people complaining that they got deducted just because of commits - and yeah, it&apos;s true we may rely too much on commits. Commit count is an easy cop-out for reviewers to trivially claim they&apos;ve checked the &quot;project quality&quot; without actually checking the project itself. I mean, hey, it&apos;s a really easy signal, and it&apos;s easy to quantify with the brilliant approved = min(hours, commits) . Every step of the review process pushes reviewers towards being lazier, and review quality is entirely dependent on who leads the review team, and what expectations they set by example. None of these are bad metrics in and of themselves, but at scale collapse into very simple metrics (commit count) without checking what actually happened in those commits, if they&apos;re consistent, if they reflect work, to give the benefit of the doubt. And this, oftentimes, is the core issue of why &quot;hire more reviewers&quot; isn&apos;t the right solution.&lt;/p&gt;&lt;p&gt;Sometimes, people wonder why approval criteria are so strict, and why deflations exist for low commit counts. When reviewers look at projects, there is often barely anything to go by. Reviewers receive your Hackatime hour time total and your repository. There is nothing available for reviewers to see otherwise. I personally use a tool of my own to view when people spent time coding, but otherwise the actual information of your Hackatime heartbeats (filepaths, languages worked, etc.) is strictly restricted to fraud review (understandably). Fraud review itself is also generally more time-intensive.&lt;/p&gt;&lt;p&gt;So what can we do? Journaling certainly is not a one-size-fits-all solution, for a variety of reasons (perhaps to be elaborated upon in a new article?), and scale is a problem that certainly is not going to reduce in magnitude. And as much as I wish there were a simpler solution, the truth is nuanced. YSWSes should have clear review guidelines, and more automated/highly expedited systems to prevent obviously-not-approvable projects from reaching reviewers in the first place - things like incorrect demo links, nonexistent or AI-generated READMEs, etc, and make it clearer to submissions the actual requirements. I don&apos;t mean a doc to link to that technically explains things, I mean concrete, hard facts that tell people what to do and what not to do. The value gained from making things vague, or not telling people directly, offloads extra work onto reviewers to figure out what it means themselves (for example, arbitrary difficulty tier systems). Rewards, if possible, should not be tied to hours themselves, but at least incentivize good quality (for example, the Macondo starfruit). AI usage policy should be defined if possible, and no, limiting it to 30% is a lazy cop-out (which, tangentially, has always somewhat bothered me - 30% of what? time? code? effort?) and serves as a way to hide behind numbers. I&apos;ve seen multiple different policies on this matter, and what I&apos;m personally a fan of is the (perhaps arbitrary) slop rejection - direct and evident vibeslop. We should have a large, public collection of past reviews, to demonstrate by example to reviewers what standards we have.&lt;/p&gt;&lt;p&gt;None of these solutions are perfect, or solve anything on their own, of course. But I hope that with as many small steps in the right direction as we can, we are able to handle these growing pains.&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>Scraping Use Policy for the Slack</title><link>https://news.hackclub.com/news/scraping-use-policy/</link><guid isPermaLink="true">https://news.hackclub.com/news/scraping-use-policy/</guid><description>The Fire Department regularly gets questions from people who want to scrape messages on the Slack, but don&apos;t know what&apos;s allowed.</description><pubDate>Sun, 14 Jun 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;The Fire Department regularly gets questions from people who want to scrape messages on the Slack, but don&apos;t know what&apos;s allowed.&lt;/p&gt;&lt;p&gt;After months of discussion with the community, we have a draft Scraping policy. It&apos;s not perfect, but it&apos;s a starting point, open to discussion and improvement. This policy takes effect on Monday, June 15.&lt;/p&gt;&lt;p&gt;&quot;Scraping&quot; means collecting and storing message content for later retrieval, analysis, indexing, training or reuse. Processing live message events without storing message contents is not considered scraping.&lt;/p&gt;&lt;p&gt;If a user withdraws consent for messages that were collected through explicit consent, reasonable efforts should be made to remove those messages from future datasets, indexes and storage.&lt;/p&gt;&lt;p&gt;Any use of scraped messages remains subject to the Code of Conduct.&lt;/p&gt;&lt;p&gt;Projects that scrape messages should clearly disclose what data is being collected and how it is being used.&lt;/p&gt;&lt;p&gt;Thank you for all the questions you&apos;ve asked that have helped us think about this. Can&apos;t wait to hear from you and know what you think and what you&apos;d like to see!&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>Self-Attention, From First Principles</title><link>https://news.hackclub.com/essays/attention-from-scratch/</link><guid isPermaLink="true">https://news.hackclub.com/essays/attention-from-scratch/</guid><description>Editor&apos;s note: this article is reproduced with the author&apos;s permission. The original can be found here.</description><pubDate>Thu, 11 Jun 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;Editor&apos;s note: this article is reproduced with the author&apos;s permission. The original can be found here.&lt;/p&gt;&lt;p&gt;Attention was introduced in Google&apos;s 2017 paper, Attention Is All You Need, and I&apos;ll go over how it works here — assuming you know some linear algebra but don&apos;t know how this specifically works.&lt;/p&gt;&lt;p&gt;For each token processed, we look at every previous token (including itself) in the sequence and calculate how relevant each one is to our current token — then pull info from them based on their attention weights, letting us build associations between individual tokens. A very basic example would be that when we process the token &quot;bank&quot; in &quot;the river bank&quot;, it&apos;s meaningless by itself, but the attention mechanism lets the trained model strongly associate it with the token &quot;river&quot;.&lt;/p&gt;&lt;p&gt;The transformer doesn&apos;t actually &apos;know&apos; what those &quot;river&quot; or &quot;bank&quot; tokens mean because this is all just maths. Before attention, the input token embeddings are put through three learned linear projections:&lt;/p&gt;&lt;p&gt;$$ \mathbf{Q} = \mathbf{X} \mathbf{W}Q \qquad \mathbf{K} = \mathbf{X} \mathbf{W}K \qquad \mathbf{V} = \mathbf{X} \mathbf{W}_V $$&lt;/p&gt;&lt;p&gt;The weight matrices , , and are what the model learns in pre-training, and we use them to create three vectors , , and for each token. is the token&apos;s query of what it&apos;s looking for, is the token&apos;s key of what it contains, and is the token&apos;s value of what it contributes to the output. These vectors are what actually lets statistical associations form — so knowing that, we can look at the attention formula itself:&lt;/p&gt;&lt;p&gt;$$ \text{Attention}(\mathbf{Q}, \mathbf{K}, \mathbf{V}) = \text{softmax}\left(\frac{\mathbf{Q}\mathbf{K}^\top}{\sqrt{d_k}}\right)\mathbf{V} $$&lt;/p&gt;&lt;p&gt;In the equation, we get an attention score by dotting with the transposed key , then divide the score by (where is the shared dimension of each and vector), run it through &amp;amp;nbsp; to produce an attention weight , and multiply by to get our output. The dot product works as a relevance score because the dot product of two vectors actually has a geometric identity, where is the angle between vectors and :&lt;/p&gt;&lt;p&gt;$$ \mathbf{q} \cdot \mathbf{k} = |\mathbf{q}||\mathbf{k}|\cos\theta $$&lt;/p&gt;&lt;p&gt;Here, we&apos;re using directional alignment to denote how closely related two vectors are. So when is small, approaches with a large dot product, meaning the vectors are pointing in similar directions (related). But when , then , meaning the vectors are perpendicular (unrelated). Basically the dot product measures how closely aligned two vectors are; a closer alignment means a larger dot product — and a larger dot product is a higher relevance score. In practice, here&apos;s what this looks like for a pair of -dimensional vectors and :&lt;/p&gt;&lt;p&gt;$$ \mathbf{v}1 = \begin{pmatrix} 3 \\ 4 \end{pmatrix} \qquad \mathbf{v}2 = \begin{pmatrix} 4 \\ 3 \end{pmatrix} \\ $$&lt;/p&gt;&lt;p&gt;We first compute magnitude:&lt;/p&gt;&lt;p&gt;$$ |\mathbf{v}1| = |\mathbf{v}2| = \sqrt{3^2 + 4^2} = 5 $$&lt;/p&gt;&lt;p&gt;They both have the same magnitude of , which means the only difference is their direction. We then compute the dot product:&lt;/p&gt;&lt;p&gt;$$ \begin{align} \mathbf{v}1 \cdot \mathbf{v}2 &amp;amp;= (3 \times 4) + (4 \times 3) \\ &amp;amp;= 12 + 12 \\ &amp;amp;= 24 \end{align} $$&lt;/p&gt;&lt;p&gt;A dot product of is large which means high relevance, and we can see this by calculating the angle between the two vectors:&lt;/p&gt;&lt;p&gt;$$ \begin{align} \theta &amp;amp;= \cos^{-1}\left(\frac{\mathbf{v}1 \cdot \mathbf{v}2}{|\mathbf{v}1||\mathbf{v}2|}\right) \\ &amp;amp;= \cos^{-1}\left(\frac{24}{5 \times 5}\right) \\ &amp;amp;\approx 16.3^{\circ} \end{align} $$&lt;/p&gt;&lt;p&gt;With this, we know that the vectors have close directional alignment, which is why they are relevant to each other. On a graph their relationship looks like this:&lt;/p&gt;&lt;p&gt;x y 3 4 4 3 v 1 · v 2 = 24 v 1 v 2 16.3° } /&amp;gt;&lt;/p&gt;&lt;p&gt;But now here&apos;s what the process looks like for two unrelated vectors and which also have an equal magnitude of :&lt;/p&gt;&lt;p&gt;$$ \mathbf{v}3 = \begin{pmatrix} 3 \\ 4 \end{pmatrix} \qquad \mathbf{v}4 = \begin{pmatrix} 4 \\ -3 \end{pmatrix} \\ $$&lt;/p&gt;&lt;p&gt;$$ \begin{align} \mathbf{v}3 \cdot \mathbf{v}4 &amp;amp;= (3 \times 4) + (4 \times -3) \\ &amp;amp;= 12 + (-12) \\ &amp;amp;= 0 \end{align} $$&lt;/p&gt;&lt;p&gt;$$ \begin{align} \theta &amp;amp;= \cos^{-1}\left(\frac{\mathbf{v}3 \cdot \mathbf{v}4}{|\mathbf{v}3||\mathbf{v}4|}\right) \\ &amp;amp;= \cos^{-1}\left(\frac{0}{5 \times 5}\right) \\ &amp;amp;= 90^{\circ} \end{align} $$&lt;/p&gt;&lt;p&gt;With a dot product of and an angle of , our vectors are orthogonal — meaning they&apos;re perpendicular and unrelated to each other:&lt;/p&gt;&lt;p&gt;x y 3 4 4 −3 v 3 v 4 90° } /&amp;gt;&lt;/p&gt;&lt;p&gt;Now, the actual reason that directional alignment means relevance is because projects each token&apos;s embedding into a -dimensional space where the direction of the vector means the query of &quot;what I&apos;m looking for&quot;. Meanwhile projects into the same space where the direction means the key of &quot;what I contain&quot;. So you see that the model trained these weight matrices to make tokens that should correlate end up pointing in similar directions in that shared space — where, for example, in our example sentence points roughly where also points to. Through training, the model already learns these alignments between tokens, but we use the dot product during inference to actually measure those alignments.&lt;/p&gt;&lt;p&gt;Moving on, &amp;amp;nbsp; is an important function because it emphasizes differences between raw attention scores through exponentiation, normalizes to , and leaves us with a probability distribution of attention weights:&lt;/p&gt;&lt;p&gt;$$ \text{softmax}(zi) = \frac{e^{zi}}{\sum{j=1}^{n} e^{zj}} $$&lt;/p&gt;&lt;p&gt;Another very important thing is dividing the score by to normalize before &amp;amp;nbsp; because the raw attention score is the dot product . After initialization, the components of each query vector and key vector are roughly independent with and . And since the components are independent, then &amp;amp;nbsp; , which just equals , so the score&apos;s typical magnitude is . This means that by around , the score grows so large that it saturates &amp;amp;nbsp; and kills the probability gradient, leaving us with only one dominant value while everything else is negligible.&lt;/p&gt;&lt;p&gt;Back to our example then — what actually happens is query is dotted with keys , , and to produce three attention scores. These are run through &amp;amp;nbsp; to produce a distribution of positive attention weights that sum to , where &quot;river&quot; is the largest value — so it&apos;s the heaviest weight. Then, our output is a weighted sum of all values, where the &apos;s are the &amp;amp;nbsp; weights:&lt;/p&gt;&lt;p&gt;$$ \mathbf{o}{\text{bank}} = w\text{the} \cdot \mathbf{v}{\text{the}} + w\text{river} \cdot \mathbf{v}{\text{river}} + w\text{bank} \cdot \mathbf{v}_{\text{bank}} $$&lt;/p&gt;&lt;p&gt;Token &quot;river&quot; dominates here because its weight is much larger which dilutes the other weights, and the output we generate is a point in embedding space that&apos;s been dragged closer to by the weight distribution. That&apos;s why there&apos;s no discrete selection here like &apos;choosing&apos; a token; attention is a dynamic mechanism, and whichever vector has dominant weight just pulls the output closer to itself.&lt;/p&gt;&lt;p&gt;For example, using -dimensional vectors to keep things simple, this is what the process looks like where we have token values:&lt;/p&gt;&lt;p&gt;$$ \mathbf{v}{\text{the}} = \begin{pmatrix} 0 \\ 1 \end{pmatrix} \qquad \mathbf{v}{\text{river}} = \begin{pmatrix} 4 \\ 3 \end{pmatrix} \qquad \mathbf{v}_{\text{bank}} = \begin{pmatrix} 1 \\ 1 \end{pmatrix} $$&lt;/p&gt;&lt;p&gt;And we have &amp;amp;nbsp; attention weights:&lt;/p&gt;&lt;p&gt;$$ w{\text{the}} = 0.05 \qquad w{\text{river}} = 0.90 \qquad w_{\text{bank}} = 0.05 $$&lt;/p&gt;&lt;p&gt;We multiply all of this stuff and sum it up:&lt;/p&gt;&lt;p&gt;$$ \begin{align} \mathbf{o}_{\text{bank}} &amp;amp;= 0.05\begin{pmatrix} 0 \\ 1 \end{pmatrix} + 0.90\begin{pmatrix} 4 \\ 3 \end{pmatrix} + 0.05\begin{pmatrix} 1 \\ 1 \end{pmatrix} \\ &amp;amp;= \begin{pmatrix} 0 \\ 0.05 \end{pmatrix} + \begin{pmatrix} 3.6 \\ 2.7 \end{pmatrix} + \begin{pmatrix} 0.05 \\ 0.05 \end{pmatrix} \\ &amp;amp;= \begin{pmatrix} 3.65 \\ 2.8 \end{pmatrix} \end{align} $$&lt;/p&gt;&lt;p&gt;So you see how aligns closely with but it&apos;s not exactly equal, because it&apos;s a weighted sum of all values including and . It&apos;s easier to see on a graph how our output is dragged towards the heaviest weighted value — but keep in mind that while this is -dimensional, real value vectors exist in much higher -dimensional spaces:&lt;/p&gt;&lt;p&gt;x y 0 1 3.65 4 1 2.8 3 v the v river v bank o bank } /&amp;gt;&lt;/p&gt;&lt;p&gt;And with that, we&apos;ve gone all the way from &quot;the river bank&quot; — where &quot;river&quot; and &quot;bank&quot; have nothing to do with each other by themselves — to proving exactly how &quot;bank&quot; is related to &quot;river&quot; with the maths behind self-attention. Now this is just one part of LLMs overall, but it&apos;s the one system that I&apos;d say is actually worth taking your time to understand.&lt;/p&gt;&lt;p&gt;github.com/williamalexakis/self-attention.c&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>Be Nicer than You Have to</title><link>https://news.hackclub.com/essays/be-nicer-than-you-have-to/</link><guid isPermaLink="true">https://news.hackclub.com/essays/be-nicer-than-you-have-to/</guid><description>A community where people are only as nice as they need to be is a crappy place. There are many reasons why.</description><pubDate>Wed, 10 Jun 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;A community where people are only as nice as they need to be is a crappy place. There are many reasons why.&lt;/p&gt;&lt;p&gt;One: people feel the required level of kindness depends on how they are treated. But this is a matter of perspective. Here&apos;s a story about parents getting into a brawl over seating at a kindergarten graduation. No doubt each of them thought that they were fully justified every step of the way. There’s a famous study where two people are told to take turns poking each other, each time exactly as hard as the other person just poked them. Consistently, the two participants poked each other slightly harder each time, and by the end were jabbing each other. People disagree on what crosses the line. Things escalate.&lt;/p&gt;&lt;p&gt;Two: other people will copy your example. I recently saw two cases on the Slack where people were being mean to a community member “for their own good”. One, a long-time Hack Clubber who is very nice but whose opinions are sometimes poorly-received. The other, a new Hack Clubber who seems to overestimate their own skills. In both cases, people have been contemptuous towards them. In both cases, I’ve heard this defended as making them git gud: we have to disrespect these guys, you see, so that they shape up to win our respect.&lt;/p&gt;&lt;p&gt;It doesn’t work like that. You don’t get to choose the lesson. What they see is that you are being mean to them. What lesson do they take from that? It could be any of the following:&lt;/p&gt;&lt;p&gt;You don&apos;t choose the lesson.&lt;/p&gt;&lt;p&gt;Three: silly mistakes are part of learning. Learning to code, learning to build, learning to have opinions about the world, learning social skills. What kind of space is Hack Club? If it is a space where you aren’t allowed to make mistakes–silly, embarrassing ones that are annoying for others–then it is a place you can’t join unless you’re already good.&lt;/p&gt;&lt;p&gt;I sometimes see an incumbency bias at Hack Club. We have a cool thing going, why let new people come in and get in the way? But this is like how people who own houses want property values to stay high, so they fight anything that could conceivably lower property values, then get surprised when their children have to keep living with them into their 30s because there is no affordable housing 1 . I want this to be a good neighborhood too, but it has to be one that newcomers can afford.&lt;/p&gt;&lt;p&gt;My point is that what’s best for the people currently in Hack Club is not necessarily what’s best for Hack Club. You have to leave behind something sustainable, for the next generation of Hack Clubbers. As teenagers you understand better than most adults what it’s like when people loot your future for their own short-term gains. If Hack Club is unkind to newcomers, then it will be a fun party for a while, and eventually become a ghost town, or a jerk magnet. Both dynamics are attractor states: once we’re in them, it will be very hard to get out.&lt;/p&gt;&lt;p&gt;When asked about this, Zach said &quot;If Hack Club becomes a negative place, all the best makers in Hack Club will leave and form their own private community. I saw this with a lot of online communities I ran as a teen. Super technical people start a community. Intermediate technical people join because they want to be like the super technical people. Beginner technical people join because they want to be like the intermediate technical people. Intermediate and beginner technical people see that the super technical people are respected because they get lots of attention, and realize that the easiest way to get attention is to be outrageous. The community becomes dominated by people being outrageous and by intermediate people becoming territorial. The super technical people leave and form their own private group. Now you have a community with no substance, and most people leave.&quot; Zach called this &quot;the natural trend for online communities&quot;, which is bleak. It means we can&apos;t just be adequate. We have to be slightly utopian, and unreasonably insistent on being nice and helping each other.&lt;/p&gt;&lt;p&gt;So be nice! Be nice to people who you don’t think deserve it. Be nice when most people would agree you are justified in being mean. Whether you are HQ staff or a community member, we will respect it more if you say “I need help dealing with this person” than if you blow up at them and then say later that you were provoked. You don’t have to lie down and take disrespect. You can stand up for yourself, but don’t confuse that with attacking someone else.&lt;/p&gt;&lt;p&gt;Hack Club is whatever we make it. We can make it special, and better than other online communities. But only if we are nicer than we have to be.&lt;/p&gt;&lt;p&gt;1. In fairness to homeowners, we kind of screwed them by tying their financial fate to their property values, but that is a conversation for another time. ↩&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>Strings Attached</title><link>https://news.hackclub.com/opinion/strings-attached/</link><guid isPermaLink="true">https://news.hackclub.com/opinion/strings-attached/</guid><description>I like analogies, so I think I will do another one. Consider the following situation: You want to throw a party, but you&apos;re broke. Your friend offers to fund the whole thing, food, venue, even a big speaker! But only if you hold it at his house, on his schedule, and only invite people he approves of. You could say no, hold no party, and stand on principle. Or you could say yes, throw a great party for the people who can make it, and use the experience to negotiate better terms next time. Neither choice is abhorrently wrong, but only one of them actually results in a party.</description><pubDate>Sat, 06 Jun 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;Editor&apos;s note: this piece was submitted pseudonymously&lt;/p&gt;&lt;p&gt;I like analogies, so I think I will do another one. Consider the following situation: You want to throw a party, but you&apos;re broke. Your friend offers to fund the whole thing, food, venue, even a big speaker! But only if you hold it at his house, on his schedule, and only invite people he approves of. You could say no, hold no party, and stand on principle. Or you could say yes, throw a great party for the people who can make it, and use the experience to negotiate better terms next time. Neither choice is abhorrently wrong, but only one of them actually results in a party.&lt;/p&gt;&lt;p&gt;I&apos;ve seen the #meta threads, and it seems like season two of &quot;region locked hackathons&quot; is airing. Nobody likes being told &quot;nuh uh, not for you,&quot; especially when what&apos;s being offered is pretty cool. But I think the conversation keeps missing the mark.&lt;/p&gt;&lt;p&gt;Where the money comes from matters more than you think. Hack Club has historically been pretty clean in this regard. Our donors were private individuals and companies, and they generally gave with no strings attached. That&apos;s extremely rare, and we were really lucky for this (this is what Christina does btw). Near the end of 2025, we entered our first major government-adjacent partnership with AMD. AMD&apos;s sponsorship loosely traces back to President Trump&apos;s &quot;America&apos;s AI Action Plan,&quot; a policy framework explicitly designed to channel government resources into private-sector AI infrastructure to give the U.S. an edge over Chinese AI. Lisa Su, AMD&apos;s CEO, subsequently joined the President&apos;s Council of Advisors on Science and Technology a few months later. We can tell that AMD is not just your average wafer company right now, but an arm of U.S. AI policy.&lt;/p&gt;&lt;p&gt;When you take money from a government initiative, you take the restrictions that come with it. There is no way the U.S. government will fund a hackathon for teenagers in Denmark unless Trump gets Greenland in return (which a hackathon is unlikely to do).&lt;/p&gt;&lt;p&gt;This is the same reason the official NASA logo could not be placed next to a Hack Club logo with an X between them on the Stardance posters. Every piece of material must be cleared with NASA&apos;s Office of Communications. The design would have been rejected for incorrectly displaying the Hack Club logo with the NASA logo, since it would imply that NASA directly endorses Hack Club. NASA is a government agency, and everything it touches is subject to scrutiny that would make #meta look like compliments. We have seen the consequences when Hack Club is not explicit about how relationships work, and Laura Loomer (far-right political activist for the uninitiated) tore Hack Club apart on Twitter, and Elon Musk took notice. These organizations have to be strict because they have their own reputations to protect.&lt;/p&gt;&lt;p&gt;As I looked more into region locks, I realized that they are not a new thing either.&lt;/p&gt;&lt;p&gt;Think about how fulfillment works. Hack Club ships prizes all over the world all the time, but not everywhere, and not always the same prizes. Some items can&apos;t clear customs. Some countries have import restrictions. Some vendors won&apos;t fulfill outside certain regions. We already made our point that we are a US-based nonprofit, and we can largely guarantee first-class support in the US and Canada, since the infrastructure is there and it&apos;s so close. The Eurozone is a close second in terms of reliability, but anything outside of that is no man&apos;s land. We would have to divert money and time that would go into events and prizes into boxes going halfway across the world, breaking import and electronics laws, and held ransom by governments with import taxes.&lt;/p&gt;&lt;p&gt;If we are causing a commotion about the U.S. government funding hackathons only for people in the U.S., where are the protests against the U.S.-based Framework not serving India, the third-largest country of professional developers?&lt;/p&gt;&lt;p&gt;I want to bring up the easy counterargument in every thread like this: that Hack Club could have just rejected AMD, or ace-attorney&apos;d away the geo-lock, or funded the non-U.S. component separately. Perhaps! I can&apos;t rule out every possibility or read into futures that never happened. But the realistic outcome was not &quot;same event, open to everyone.&quot; The realistic outcome was no event. And no event helps exactly zero people. There&apos;s a version of idealism that protects your principles at the cost of outcomes. Turning down a partnership because it doesn&apos;t serve everyone everywhere equally sounds noble and virtuous until you realize the people it would have helped are now just... not helped. The goal of Hack Club is not to help every single teenager in every single country, but to give as many teenagers as possible access to cool things. Sometimes you can do that globally. Sometimes you can only do it regionally. Both are better than flat-out nothing.&lt;/p&gt;&lt;p&gt;You might be asking: &quot;well okay, you complained that offering the same thing to literally everyone is hard and you want to please people with money without giving me a real solution, the hell am I supposed to do with just that!?&quot; and you would be right! Here comes the fun part: if you want more international opportunities, someone has to go find them. Someone said it in the thread, and they were right, lobby organizations in your country, find donors who care about your region, and build the thing you want to see. Midnight happened because people decided they wanted to go to Austria and made it happen. Beest happened because Euan had a budget and a vision. Macondo happened because Nathan wanted a real event in South America. These events exist because of humans, not because a world leader launched an AI initiative.&lt;/p&gt;&lt;p&gt;If you are a non-U.S. Hack Clubber who is frustrated with these region-locked events, that frustration is valid and worth channeling at something. Just make sure you&apos;re pointing it at the right thing. The target is not HQ, but the reality that the largest pools of capital for teen tech programs with Hack Club are concentrated in the United States, and are influenced by United States policy, and flow through United States institutions. Changing that will likely take years, if not decades, to fully catch up with the states, but it is not impossible. Like I said in my hiring article, talk is cheap. Great ideas like #hib never saw the light of day because we accepted the status quo of &quot;old politician says we can&apos;t do it, therefore we can&apos;t do it.&quot; When have real hackers actually knelt before governments to accept the way things are? Hackers make the system work in their favor, and if you are a real hacker, you will help lead the efforts in your local area.&lt;/p&gt;&lt;p&gt;Not every door will be open to you 24/7. This is true at Hack Club and everywhere. Some items we can&apos;t ship to you. Some hackathons we cannot open to you. Some AMAs will not be during the day in your timezone. We will always try our best to give you the most opportunities as humanly possible, but that also means you may not be able to do every single one.&lt;/p&gt;&lt;p&gt;Until next time,&lt;/p&gt;&lt;p&gt;Villarante&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>Getting Ready for Stardance</title><link>https://news.hackclub.com/news/getting-ready-for-stardance/</link><guid isPermaLink="true">https://news.hackclub.com/news/getting-ready-for-stardance/</guid><description>It is often said that in Chinese, the word for “crisis” also means “opportunity”. This is nonsense. Crisis is 危机, which means “moment of danger”, and opportunity is 机会, which means “moment of potential”. They have 机 in common, but that would be like one Chinese person telling another, “Hey, did you know that in English, the word for ‘hand soap’ also means ‘hand gun’?”</description><pubDate>Sat, 30 May 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;It is often said that in Chinese, the word for “crisis” also means “opportunity”. This is nonsense. Crisis is 危机, which means “moment of danger”, and opportunity is 机会, which means “moment of potential”. They have 机 in common, but that would be like one Chinese person telling another, “Hey, did you know that in English, the word for ‘hand soap’ also means ‘hand gun’?”&lt;/p&gt;&lt;p&gt;Stardance will roughly double the number of Hack Clubbers. This isn’t a crisis. It is a challenge. But it is also an opportunity. This is our house and we’re about to have guests. So how are we getting ready?&lt;/p&gt;&lt;p&gt;The Fire Department&lt;/p&gt;&lt;p&gt;I want to set a clear expectation: from June 1 to September 15, moderation will be strict. Usually there is some slack in the system and we use that slack to do things like give people the benefit of the doubt, give people second chances, and let borderline cases slide. But the point of moderation is to make the community a nice place. And from June 1 to September 15, there won’t be slack in the system.&lt;/p&gt;&lt;p&gt;While Stardance is running, please don’t try and find the exact line between acceptable and unacceptable behavior. Treat that line like a cliff: don’t stand on the edge. Instead of asking yourself “can I get away with this?” ask yourself, “how can I make our house a great place for newcomers?”&lt;/p&gt;&lt;p&gt;The Fraud Squad&lt;/p&gt;&lt;p&gt;The Special Activities Division&lt;/p&gt;&lt;p&gt;The Nest Admins&lt;/p&gt;&lt;p&gt;You&lt;/p&gt;&lt;p&gt;As the People Who Were Here First, you are about to be drafted as role models. Newcomers do not know how to act. They will look to you for answers. I’m challenging you to be Good, not just Not Bad. Treat people better than you have to. Show people’s opinions more respect than you feel they deserve. Stay calm even in situations where you’re justified in getting angry.&lt;/p&gt;&lt;p&gt;Do you want Hack Club to be special? Do you want it to be life-changing? Do you want it to be the best community people have ever joined? This is your house; how do you want people to see it?&lt;/p&gt;&lt;p&gt;I said this is an opportunity. I mean it&apos;s an opportunity to change lives. I remember once, in #welcome-to-hack-club, someone said &quot;I&apos;m just processing that a place like this exists&quot;. You all have made something that doesn&apos;t and cannot exist anywhere else, and I&apos;m so excited to watch you share the magic with new people. Thank you.&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>How Hiring Works</title><link>https://news.hackclub.com/essays/how-hiring-works/</link><guid isPermaLink="true">https://news.hackclub.com/essays/how-hiring-works/</guid><description>Consider the following situation: You are in class, and your teacher tells you to work in groups of 3. This is a big project that will be worth 10% of your final grade, so choose your people wisely! You got Jimmy and Cassy, two of your best friends, to the left of you. You also have John and some other kid whose name you forgot the name of to your right. Ignoring the #meta threads for a second, who are you realistically picking? If you pick your friends, you work on the project, and since everyone is already on the same wavelength, you do great. If you pick John and the unknown, you are picking a gamble between a productive group and a total flop.</description><pubDate>Fri, 29 May 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;Editor&apos;s note: this piece was submitted pseudonymously&lt;/p&gt;&lt;p&gt;Greetings Slacker News,&lt;/p&gt;&lt;p&gt;Consider the following situation: You are in class, and your teacher tells you to work in groups of 3. This is a big project that will be worth 10% of your final grade, so choose your people wisely! You got Jimmy and Cassy, two of your best friends, to the left of you. You also have John and some other kid whose name you forgot the name of to your right. Ignoring the #meta threads for a second, who are you realistically picking? If you pick your friends, you work on the project, and since everyone is already on the same wavelength, you do great. If you pick John and the unknown, you are picking a gamble between a productive group and a total flop.&lt;/p&gt;&lt;p&gt;I have seen quite a lot of posts and comments about how Hack Club hires/chooses people to run programs. Some of the terms I see thrown around are &quot;elitism&quot; and &quot;picking only their friends.&quot; I believe this is not a problem limited to Hack Club, but life in general. I am personally involved with HQ on some of their big programs, so I think I could offer some advice. I&apos;m aware I might be the wrong person to say this is all fine, given that I did, in fact, end up inside the thing, but I don&apos;t want to see talented people discouraged from asking how to help just because they don&apos;t know anyone on the inside. After all, you have to start from somewhere!&lt;/p&gt;&lt;p&gt;This is a feature of human nature: taking risks can be scary, and I get that. From an outsider&apos;s point of view, it sucks! I was in the job market (eww employment) too, and seeing beginner jobs that require experience feels like such a rug pull!&lt;/p&gt;&lt;p&gt;Two-panel &quot;Mr. Incredible becoming uncanny&quot; meme. Left panel shows a cheerful, brightly colored Mr. Incredible with the caption &quot;seeing &apos;entry-level&apos; in job title.&quot; Right panel shows a dark, distorted, unsettling version of the same face with the caption &quot;seeing &apos;5+ years experience&apos; in job description.&quot;&lt;/p&gt;&lt;p&gt;But let&apos;s take the role of the people hiring for a second. If you are leading a team at Hack Club (or literally anywhere), you are looking for people who are super hyped up and excited about their work, but you also want people who are dependable and reliable. People who can really commit the time required to do the job and align with your vision for the thing. The problem is that this is naturally a small group of people. People who are hiring are likely to go with someone they have worked with before and had a good time with, rather than take the gamble on someone new.&lt;/p&gt;&lt;p&gt;Many months ago, I tried to hire a review team for one of the big YSWS events, and after hearing complaints about favoritism, I decided to let anyone and everyone join if they asked. I would try to personally hand-hold them through the process, get the setup in place, and help check their reviews as needed. It started out great, but quickly grew into a mess that required more people to wrangle and control. The first problem is that we had people join the team, do 10 or 20 reviews, and then just disappear into thin air. I could not depend on them to do their job, so I had to hire more people. The next problem was more silent, but the quality of reviews varied wildly from person to person. I could not trust that the same project would get the same decision if I asked two different people, so I had to spend more time on training. Finally, since everyone had different perceptions of what a &quot;good&quot; project was, more time was spent arguing over who was right than actually sending our reviews, so I had to be the final arbiter on every minor dispute.&lt;/p&gt;&lt;p&gt;Would all of this have been avoided by just hiring people I&apos;d worked with before? Probably not fully, but enough of it that I get why people default to it. Cool things like delegation and documenting everything could help, but the majority of the decisions you make in your position come from experience, not from a Slack Canvas telling you how to think.&lt;/p&gt;&lt;p&gt;The good part is that the way in is easier than you might think. People do get added to teams, programs, and review roles all the damn time! Some of them were complete strangers a month ago! The issue is that nobody has ever written down where the door is. You can&apos;t ask Amp &quot;how get on (insert program) team?&quot; Wanna know what the path is really like from the inside? Someone does good work, someone notices, someone mentions them to someone else, and eventually they get asked. Sounds shrimple! Except the &quot;someone notices&quot; step kinda assumes you&apos;re already somewhat close to the people doing the noticing. If you&apos;re not active in the right channels, shipping things publicly, or asking the right people, you can be genuinely cracked and be invisible at the same time. This is not on purpose, and we don&apos;t have a group of people going &quot;fuck this guy in particular.&quot; It&apos;s more that the system runs on visibility, and visibility requires knowing how to be visible, which requires knowing the system. (recursion anyone?)&lt;/p&gt;&lt;p&gt;The good news is that you can get around all that mess by just asking directly. The bad news is that you have to know who to ask, what to ask for, and how to present yourself, which brings me back to the part where I actually try to be helpful.&lt;/p&gt;&lt;p&gt;You might be asking: &quot;well okay, you complained that hiring is hard and getting hired is hard without giving me a real solution, the hell am I supposed to do with just that!?&quot; and you would be right! I don&apos;t make all the hiring decisions, so I can&apos;t give you the secret method that will get you into any position you want for free (legit + working 2026 + not scam), but here are a few quick pointers that should help you get the edge over others.&lt;/p&gt;&lt;p&gt;Hopefully, these pointers will help in your adventures of getting involved with HQ. The skills you gain from Hack Club will help you in real life, not just the programming skills, but much more. I have personally learned how to work better with people, how to give and accept good feedback, how to formulate arguments more effectively, and how to be a better person overall, and I hope the same is true for you, too. The reality is that the world is built on connections. Both fiber optic and flesh + feelings. Learning to leverage it is what separates ordinary people from real rockstars.&lt;/p&gt;&lt;p&gt;Until next time,&lt;/p&gt;&lt;p&gt;Villarante&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>What Do New Users Think about the Slack?</title><link>https://news.hackclub.com/news/slack-nunps-april-2026/</link><guid isPermaLink="true">https://news.hackclub.com/news/slack-nunps-april-2026/</guid><description>Every month, I survey people who joined the Slack in the preceding month.</description><pubDate>Wed, 27 May 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;Every month, I survey people who joined the Slack in the preceding month.&lt;/p&gt;&lt;p&gt;NPS by Month&lt;/p&gt;&lt;p&gt;How Did You Join the Slack?&lt;/p&gt;&lt;p&gt;NPS by Join Method&lt;/p&gt;&lt;p&gt;I also include prose feedback questions. In general, the themes of positive and negative comments have remained the same all year.&lt;/p&gt;&lt;p&gt;What We&apos;ve Done So Far&lt;/p&gt;&lt;p&gt;Even though we have not &quot;fixed the Slack&quot;, I do think these efforts have made a difference. For example, people who say they joined through slack.hackclub.com have the second-highest NPS of any join method, and their NPS has increased over time. My theory is that new user NPS is currently dominated by factors outside of our control. But this does not mean it always will be. When we finally find huge improvements to new user experience, then those will become the big drivers of NPS. By analogy, the health of the plants in your yard is mostly due to factors beyond your control, like the weather. But if you weed and water, then their health will mainly be about factors within your control.&lt;/p&gt;&lt;p&gt;My Wishlist&lt;/p&gt;&lt;p&gt;People often ask me, &quot;How can I help?&quot; That&apos;s really special and I never stop feeling grateful to work in a community like this. Sometimes I have tasks on hand. Other times I don&apos;t, because in my mind, there is a disconnect between what I want, and what I think is possible.&lt;/p&gt;&lt;p&gt;On reflection, that&apos;s silly. Who am I to say what you can and can&apos;t pull off? You keep surprising me. So, here are some things that I think would make the Slack an amazing place for new users, that I have not pursued because I don&apos;t know how to make them happen:&lt;/p&gt;&lt;p&gt;While we&apos;re at it, here are a few items from my wishlist for improving Hack Club in general:&lt;/p&gt;&lt;p&gt;Some of these are quite ambitious. Can they be done? Maybe. Perhaps you, dear reader, will be the one to prove they can.&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>How to Get Good Project Ideas</title><link>https://news.hackclub.com/opinion/how-to-get-good-project-ideas/</link><guid isPermaLink="true">https://news.hackclub.com/opinion/how-to-get-good-project-ideas/</guid><description>I get people asking me for project ideas. I also see a lot of projects that have already been built many times. Meanwhile, I am up to my elbows in projects I wish people would build. (I am working on a piece which lists some of them).</description><pubDate>Wed, 27 May 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;I get people asking me for project ideas. I also see a lot of projects that have already been built many times. Meanwhile, I am up to my elbows in projects I wish people would build. (I am working on a piece which lists some of them).&lt;/p&gt;&lt;p&gt;Thinking about this mismatch, I&apos;ve decided that the market is oversaturated with solutions to general, obvious problems, but is quite undersaturated with solutions to specific problems.&lt;/p&gt;&lt;p&gt;Many of you know that I used to work in debate. One of my jobs there was to figure out who qualified for the New York Debate League championship. I needed to look at students&apos; performance in every NYDL tournament across an entire school year, to find every individual student who went 3-1 or 4-0 in the varsity division at least once. This is harder than it sounds. The results are all public on tabroom.com, but in a format that is inconvenient and subtly wrong for my purposes. What I really needed was a tabroom API. I found two, but neither one appeared to work, at least for what I was doing.&lt;/p&gt;&lt;p&gt;This is just an example. But notice how specific it is.&lt;/p&gt;&lt;p&gt;Matt Bruenig, a writer I enjoy, recently made an AI-powered legal research tool. Its job is to query US labor law, which mostly consists of documents published by the National Labor Relations Board. AI spending has reached levels that made &quot;we are in an AI bubble&quot; a mainstream opinion. Yet somehow, nobody else thought to do what Bruenig did, and now he has 20 paid subscribers. Why? &quot;Do more AI!&quot; is general. &quot;Use AI to query the NLRB&apos;s published documents&quot; is specific.&lt;/p&gt;&lt;p&gt;Peter Thiel--who would not like Matt Bruenig, and vice-versa--wrote Zero to One, a famous book about entrepreneurship. He comments, &quot;All happy companies are different: each one earns a monopoly by solving a unique problem. All failed companies are the same: they failed to escape competition.&quot;&lt;/p&gt;&lt;p&gt;If you want to make something inspired, something special and different, or just something that attracts paying customers, my advice to you is to go find people who are busy trying to get something specific done. Even better if they aren&apos;t technical. They will have unmet needs you can be the first to fill.&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>What is #meta Actually for?</title><link>https://news.hackclub.com/opinion/what-is-meta-for/</link><guid isPermaLink="true">https://news.hackclub.com/opinion/what-is-meta-for/</guid><description>#meta exists for &quot;improving &amp; discussing Hack Club&quot; through constructive discussion.</description><pubDate>Fri, 15 May 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;#meta exists for &quot;improving &amp;amp; discussing Hack Club&quot; through constructive discussion.&lt;/p&gt;&lt;p&gt;But over time, I think something interesting has developed: &quot;constructive&quot; has increasingly become associated with criticism specifically.&lt;/p&gt;&lt;p&gt;That is not necessarily bad. Criticism is important. Some of the best changes in Hack Club came from people pointing out flaws, others proposing alternatives, and discussing problems in the community openly. A community without criticism would not improve, and would really just fall all over the place.&lt;/p&gt;&lt;p&gt;But recently, I&apos;ve noticed a different kind of tense situation forming.&lt;/p&gt;&lt;p&gt;A few days ago, there was a post in meta about the growing negativity there. The poster wanted to lighten the overall mood of the channel. The original post wasn&apos;t really proposing any changes or improvements. It was mostly about appreciation. People shared their stories about finally getting access to hardware, finding friends with similar interests, and learning skills they couldn&apos;t afford to explore before Hack Club, which many of us have experienced, and generally expressing their gratitude for the community.&lt;/p&gt;&lt;p&gt;Then the discussion shifted.&lt;/p&gt;&lt;p&gt;Instead of talking about those experiences, people started debating whether the post itself belonged in meta at all.&lt;/p&gt;&lt;p&gt;Some argued that positivity alone isn&apos;t constructive discussion. That meta should primarily exist for actionable feedback, criticism, proposals, and improvement. Others argued that culture, morale, and community reflection are also part of improving an organization.&lt;/p&gt;&lt;p&gt;And honestly, I think both sides had a point.&lt;/p&gt;&lt;p&gt;If meta becomes pure positivity, it would lose its usefulness quickly. &quot;Hack Club is awesome&quot; repeated forever doesn&apos;t help anyone improve anything. But if criticism becomes the only thing considered constructive, people slowly become (and are) hesitant to post anything sincere there at all.&lt;/p&gt;&lt;p&gt;At that point, meta risks turning into a place optimized entirely for analysis instead of understanding.&lt;/p&gt;&lt;p&gt;What makes this especially interesting to me is how the original post became an example of the exact thing it was discussing. The conversation stopped being about how Hack Club affects people, and became about whether emotional posts deserve space in meta.&lt;/p&gt;&lt;p&gt;That feels less like toxicity, and more like an identity question: What is meta actually for? Should it only optimize for criticism? Or is reflection on culture, morale, and community experience also part of improving Hack Club?&lt;/p&gt;&lt;p&gt;I don&apos;t think there&apos;s a perfect answer here. The best meta posts in terms of improvement of the community are probably neither pure praise nor pure criticism. They help us understand Hack Club better, including both its systems and its people.&lt;/p&gt;&lt;p&gt;A community that only celebrates itself becomes shallow and loses its seriousness, but a community that only critiques itself becomes dark and exhausting.&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>Hack Club Attempts to Defraud Itself</title><link>https://news.hackclub.com/news/red-teams/</link><guid isPermaLink="true">https://news.hackclub.com/news/red-teams/</guid><description>@Felix Gao is organizing a red-teaming exercise for the Fraud Squad. We are looking for community members to apply. All applicants must be approved by Felix and @eps.</description><pubDate>Tue, 12 May 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;@Felix Gao is organizing a red-teaming exercise for the Fraud Squad. We are looking for community members to apply. All applicants must be approved by Felix and @eps.&lt;/p&gt;&lt;p&gt;What we are doing&lt;/p&gt;&lt;p&gt;Why we are doing it&lt;/p&gt;&lt;p&gt;The Fraud Squad has a hard job.&lt;/p&gt;&lt;p&gt;Some fraud cases are clear-cut. But others lack definitive proof one way or the other. There are unverifiable excuses; some people might be breaking rules accidentally. It&apos;s hard to be sure.&lt;/p&gt;&lt;p&gt;But fraud is too common to just give people the benefit of the doubt. Flavortown had 1335 unique shippers, but 324 cooked fraudsters, meaning that roughly 24% of people who made it to the submission stage were trying to commit fraud. Twenty-four percent! The numbers aren&apos;t perfect, but they make it clear that fraudsters will rob a YSWS blind if we let them.&lt;/p&gt;&lt;p&gt;And we can&apos;t take people at their word, either. I have seen people swear up and down that they are innocent, post passionate screeds against the Fraud Squad all over the Slack, try to go over the Fraud Squad&apos;s head and protest to adults at HQ, and then, when I look into their case, the proof of their guilt is so obvious I can literally watch a minute-by-minute replay of the fraud they committed. Some fraudsters confess. Others are shameless liars.&lt;/p&gt;&lt;p&gt;But at the same time, false positives do happen. They seem rare, but right now it&apos;s hard to tell.&lt;/p&gt;&lt;p&gt;This tradeoff between false positives and false negatives has no easy answer. We probably can&apos;t eliminate either. But we can reduce both, and the first step is producing verified examples so we can see what went wrong.&lt;/p&gt;&lt;p&gt;Come do crimes with us&lt;/p&gt;&lt;p&gt;We&apos;re looking for volunteers! Please DM @Felix Gao and @eps to apply.&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>YSWS Quality &amp; Integrity Weekly Update #3</title><link>https://news.hackclub.com/changelogs/ysws-progress-report-3/</link><guid isPermaLink="true">https://news.hackclub.com/changelogs/ysws-progress-report-3/</guid><description>849 projects were approved across YSWS programs between May 1 and May 8. Of those. 769 passed cleanly, 49 were flagged for changes, and 21 were rejected. 58 fines were issued and 58 projects were eliminated.</description><pubDate>Mon, 11 May 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;What happened this week&lt;/p&gt;&lt;p&gt;849 projects were approved across YSWS programs between May 1 and May 8. Of those. 769 passed cleanly, 49 were flagged for changes, and 21 were rejected. 58 fines were issued and 58 projects were eliminated.&lt;/p&gt;&lt;p&gt;Coverage&lt;/p&gt;&lt;p&gt;Of the 839 checked this week: 91.7% passed the automated check cleanly, 5.8% were flagged for changes, and 2.5% were rejected. 6.4% were reviewed in a second pass, and 9.5% of them were reviewed thoroughly in a third pass. This is where I check the repo,demo and heartbeats, and make sure the hours approved correlate with the project. I&apos;m aiming to scale this part of the process to around 15% by the end of the month.&lt;/p&gt;&lt;p&gt;Cumulative totals&lt;/p&gt;&lt;p&gt;Since the spot check pipeline started: 22,133 total checks, 173 fines issued, 286 projects eliminated.&lt;/p&gt;&lt;p&gt;Breakdown by program&lt;/p&gt;&lt;p&gt;P = Passed, NC = Needs Changes, R = Rejected. Projects approved May 1 to May 8, 2026.&lt;/p&gt;&lt;p&gt;Resolution: 50 of its 77 projects were fined this week. 36 of them were flagged as Needs Changes on third pass and 3 were rejected, with 6 rejected on second pass.&lt;/p&gt;&lt;p&gt;BakeBuild continues to have the same issue as last week: all 9 projects were flagged on first pass because the repo format didn&apos;t match what the automated check expected. All 9 passed on second review.&lt;/p&gt;&lt;p&gt;HC: The Game: 11 of its 64 projects were flagged on first pass. All 11 passed on second review as they were correctly justified.&lt;/p&gt;&lt;p&gt;Hardware stuff&lt;/p&gt;&lt;p&gt;@notaroomba is running experiments to detect cases of double-dipping on hardware projects, where the same physical build gets submitted to multiple YSWS programs. This is a gap in the current pipeline since the automated checks are optimized for software repos and don&apos;t handle hardware project they way they should be.&lt;/p&gt;&lt;p&gt;I&apos;m also trying to figure out a better way to track hardware projects in general. If you have ideas on how to improve hardware project tracking and verification, please DM me at @lfd on Slack.&lt;/p&gt;</content:encoded></item><item><title>New Code of Conduct</title><link>https://news.hackclub.com/news/new-code-of-conduct/</link><guid isPermaLink="true">https://news.hackclub.com/news/new-code-of-conduct/</guid><description>We&apos;ve drafted a new Code of Conduct for Hack Club. This new code is not yet in effect. You can see it below, and discuss it here.</description><pubDate>Thu, 07 May 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;We&apos;ve drafted a new Code of Conduct for Hack Club. This new code is not yet in effect. You can see it below, and discuss it here.&lt;/p&gt;&lt;p&gt;Changes&lt;/p&gt;&lt;p&gt;Why Change it?&lt;/p&gt;&lt;p&gt;The new code is not meant to be a different set of rules. It is meant to be the same rules, but simpler and easier for new Hack Clubbers to follow.&lt;/p&gt;&lt;p&gt;The Code of Conduct applies in all Hack Club spaces. This means, for example, that it applies at a Hackathon. When people go to Campfire, they are supposed to know and follow the CoC. The current code has information that doesn&apos;t apply to them. We have to be fair and realistic about how many rules we are asking new people to take on.&lt;/p&gt;&lt;p&gt;Clarity vs Specificity&lt;/p&gt;&lt;p&gt;The new code is meant to be clear and simple. But that&apos;s in direct conflict with having the code be detailed and specific. People don&apos;t want to cross the line, and don&apos;t want to be forced to guess where the line is, so they want the line drawn clearly. This is important.&lt;/p&gt;&lt;p&gt;The Slack has more rules than anything else in Hack Club, because it&apos;s older and more complicated than other Hack Club programs. This results in a lot of rules and details that are only relevant to the Slack. Those rules need to live somewhere, but they shouldn&apos;t be part of the slide we present to a first-time hacker attending a Horizons meetup.&lt;/p&gt;&lt;p&gt;So we will create a separate Slack Rules page, which provides detail for the people who need it, without imposing on the people who don&apos;t.&lt;/p&gt;&lt;p&gt;Public Comment&lt;/p&gt;&lt;p&gt;I am putting this out before it goes into effect so that we have a chance to talk about it. I said this is not supposed to be a change to the substance of the rules. If you feel that it is, I would like to hear about it.&lt;/p&gt;&lt;p&gt;For reference, the current code is here. The new code is below.&lt;/p&gt;&lt;p&gt;The Whole Point&lt;/p&gt;&lt;p&gt;Most online spaces are somewhere between a gas station and a nuclear waste dump. At best, people come, take what they need, and leave. At worst, people poison each other, themselves, and everything around them.&lt;/p&gt;&lt;p&gt;It doesn&apos;t have to be like this. An online community can be a place where people respect you, and care what happens to you. It can be the best community of your life. That is what we are doing at Hack Club. When you join us, you are committing to help us make that kind of community. This is hard, but worth it. Your job is to follow these principles:&lt;/p&gt;&lt;p&gt;These principles are always good, but not always clear, so click on each one to understand how we apply it in practice. Those are the rules, but the point of the rules is the principles. No set of rules can perfectly capture the right thing to do in every situation. We will always hold you, and ourselves, to these values. If you do not follow these values, we will try and get you to change. If you do not change, we will remove you from Hack Club.&lt;/p&gt;&lt;p&gt;The code of conduct applies to everyone who participates in these spaces, including Hack Clubbers, volunteers, staff, and alumni.&lt;/p&gt;&lt;p&gt;We may still take action when Hack Clubbers break the code of conduct while interacting with each other in non-Hack Club spaces.&lt;/p&gt;&lt;p&gt;The wrong way to do Hack Club is to ask &quot;what is the minimum needed to stay within the rules?&quot;.&lt;/p&gt;&lt;p&gt;The right way to do Hack Club is to ask &quot;what would a good person do in this situation?&quot; and then do that, even if you don&apos;t want to, and even if you think the rules don&apos;t require it.&lt;/p&gt;&lt;p&gt;We all fall short sometimes. When it happens to you, don&apos;t try to excuse it to yourself or others by saying &quot;it&apos;s not against the rules&quot;.&lt;/p&gt;&lt;p&gt;You can contact us by:&lt;/p&gt;&lt;p&gt;Reports are confidential. Reporters&apos; identifying information is not shared outside the Working group without direct consent.&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>Ads at Hack Club</title><link>https://news.hackclub.com/essays/ads-at-hack-club/</link><guid isPermaLink="true">https://news.hackclub.com/essays/ads-at-hack-club/</guid><description>Yesterday, I got an email from Jared Friedman, a partner at Y Combinator. I met him a few weeks ago when he did an AMA with us. He was reaching out to invite you to apply for Y Combinator Startup School, and told me that Hack Clubbers’ applications would be given special consideration.</description><pubDate>Sat, 02 May 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;Yesterday, I got an email from Jared Friedman, a partner at Y Combinator. I met him a few weeks ago when he did an AMA with us. He was reaching out to invite you to apply for Y Combinator Startup School, and told me that Hack Clubbers’ applications would be given special consideration.&lt;/p&gt;&lt;p&gt;This is great, I thought! So many Hack Clubbers would be interested in this! Where do I announce it?&lt;/p&gt;&lt;p&gt;I could only think of three ideas.&lt;/p&gt;&lt;p&gt;First, #present, the dedicated ads channel. Nobody reads #present. Second, replying to the original announcement. That thread had 42 replies. Third, my personal channel, which has ~210 people. Altogether that&apos;s telling fewer than 260 people.&lt;/p&gt;&lt;p&gt;We have a great opportunity for you, and can&apos;t tell you about it. Something is amiss.&lt;/p&gt;&lt;p&gt;The Case Against Ads&lt;/p&gt;&lt;p&gt;I use an adblocker. I obsessively unsubscribe from promotional emails. One time, when a company didn’t offer a way to unsubscribe, I reported them to the state of California.&lt;/p&gt;&lt;p&gt;In simple terms, the case against ads is that they are annoying. They disturb my mental quiet. The advertiser takes some of your time and attention–both of which are precious and finite–and in exchange you receive awareness of their product. In my opinion, this transaction is generally good for the advertiser and bad for the audience. Most products are not worth my money, and therefore ads about them are not worth my time.&lt;/p&gt;&lt;p&gt;The Fire Department has rules against spam, on the simple idea that anything besides the point of the channel degrades the quality of the channel, by watering down its purpose. This is the same reason why you often see one subreddit for memes and shitposts about a topic, and then a second subreddit for all other discussion of the topic. The memes and shitposts have to be separated out, or they would drown out other interests.&lt;/p&gt;&lt;p&gt;The Case for Ads&lt;/p&gt;&lt;p&gt;Multiple Hack Clubbers have told me that their first hackathon was a life-changing experience. If a postcard gets someone to go, isn’t that worth it? And if you get an unwanted postcard, isn’t that a worthwhile price to pay for someone else having a life-changing experience? It’s the tiniest of tiny sacrifices.&lt;/p&gt;&lt;p&gt;You probably joined Hack Club because of an ad. Most people do. Ads are how people find out what we’re doing. And when you’re in Hack Club, ads tell you what is happening next. Sometimes we have things like ysws.hackclub.com to promote YSWS, or #amas to promote AMAs, but these can’t reach everybody.&lt;/p&gt;&lt;p&gt;#announcements is actually ads. We tell you about things we want you to do. Come to this AMA. Join this YSWS. Etc. The transaction is we take your attention, and in exchange you get awareness of a product. And everybody loves it.&lt;/p&gt;&lt;p&gt;The Part Where I Explain it All&lt;/p&gt;&lt;p&gt;When people complain about ads, I think they actually mean three things.&lt;/p&gt;&lt;p&gt;First, ads that only benefit the advertiser. Vibecoded ads for vibecoded projects, people promoting some external Hackathon that you don’t want to go to and which might be a scam, etc.&lt;/p&gt;&lt;p&gt;Second, ads that get repetitive. This was the complaint in #ysws: the same ad appearing over and over, flooding the channel.&lt;/p&gt;&lt;p&gt;Third, ads that appear somewhere they aren’t expected. @thetridentguy told me that in 9th grade, he saw a FIRST Robotics poster in his school, and when he joined FIRST, the materials included a promo for Hack Club. That’s actually two ads, but nobody objects to posters in the hallway or a promo flier in your startup kit. We’re lucky Aiden saw those ads. Hack Club would be a lesser place if he hadn’t.&lt;/p&gt;&lt;p&gt;Point one is easily solved. Only run ads whose ultimate purpose is to benefit Hack Clubbers. This is easy for Hack Club, because all day long we sit around inventing new ways to give you guys our money. Everything we advertise is to enrich you, not us.&lt;/p&gt;&lt;p&gt;Point two is easily solved. Everybody knows the difference between once, twice, and spam, and the community is good at Shrouding it when it happens.&lt;/p&gt;&lt;p&gt;Point three is the actual source of tension. Too many places for ads and we disturb your mental quiet. Too few, and we cannot reach you with information that benefits you. The key is carving out ad space that everybody sees, but that doesn’t get in the way.&lt;/p&gt;&lt;p&gt;The Hack Club Solution&lt;/p&gt;&lt;p&gt;Hopefully this will give you an easy way to see things that make your life better, without clogging up your favorite channels.&lt;/p&gt;&lt;p&gt;DM me if you want to volunteer.&lt;/p&gt;&lt;p&gt;You can apply to Y Combinator Startup School here. Be sure to mention that you’re from Hack Club.&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>Hack Clubbers Debate Prediction Markets</title><link>https://news.hackclub.com/news/prediction-markets-debate/</link><guid isPermaLink="true">https://news.hackclub.com/news/prediction-markets-debate/</guid><description>On April 28th, four Hack Clubbers held a public debate on whether prediction markets do more good or harm. @Rowan and @Sahil argued in favor of the idea that they do more good than harm, while @Eternal and @Maxstellar argued against.</description><pubDate>Fri, 01 May 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;On April 28th, four Hack Clubbers held a public debate on whether prediction markets do more good or harm. @Rowan and @Sahil argued in favor of the idea that they do more good than harm, while @Eternal and @Maxstellar argued against.&lt;/p&gt;&lt;p&gt;Editor&apos;s note: a recording of the debate is available on Slack here&lt;/p&gt;&lt;p&gt;For the purposes of this debate:&lt;/p&gt;&lt;p&gt;Every debater had 5 minutes to make a statement supporting their point, in an alternating pattern. In between each speech, a discussion was held. At the end, a “free” final discussion was held, then each rebuttal had a maximum of 2 minutes.&lt;/p&gt;&lt;p&gt;The Case Against: Prediction Markets Distort Reality and Exploit Participants&lt;/p&gt;&lt;p&gt;Eternal opened the debate by making a point that separates prediction markets from news outlets: unlike news, real-money prediction markets can change reality. They noted the WNBA incident – when someone threw an inappropriate object onto the court, Polymarket created a market on whether it would happen again. It did, repeatedly. Once Polymarket stopped creating those markets, the behavior stopped too. This shows how financial incentives had been actively encouraging the harmful behavior. They also extended this to war. For instance, someone reportedly made $400,000 betting on Maduro&apos;s capture. If a bad outcome is profitable, someone may be motivated to make it happen.&lt;/p&gt;&lt;p&gt;Max further built on this idea in his speech. He argued that prediction markets present themselves as fair and centralized, when in reality they are structurally rigged against most participants. He cited a study showing that approximately 70% of all Polymarket trading addresses have realized net losses, while fewer than 0.04% of addresses captured over 70% of all realized profits, a collective $3.7 billion.&lt;/p&gt;&lt;p&gt;Sahil challenged these points, noting that you don&apos;t need to bet to benefit. The odds are publicly visible to anyone at no cost. He also pushed back on fairness as a meaningful standard. A market where nobody knew anything would just be a casino. What makes prediction markets different is that participants each contribute their own piece of the puzzle. In an election, a pollster knows something a donor doesn&apos;t, who knows something a journalist doesn&apos;t. Different people know different things that contribute to it, and the theoretical limit of this information is that when a significant fraction of those perspectives contribute to the market, a proxy for the &quot;truth&quot; is revealed.&lt;/p&gt;&lt;p&gt;The Case For: Prediction Markets Reveal Useful Outcomes&lt;/p&gt;&lt;p&gt;Sahil argued that prediction markets work because the money creates accountability. Bad traders lose money and exit, leaving the market populated by genuinely informed participants. The aggregate result is more accurate and more real-time than traditional forecasters, who are incentivized to tell engaging stories rather than accurate ones. He framed insider trading as a feature; insider information itself factors into markets as a signal that others rely on. When insiders &quot;sell&quot; info, that in and of itself becomes a signal that others can see and understand, therefore democratizing access to that knowledge.&lt;/p&gt;&lt;p&gt;Sahil also cited Waymo as evidence of prediction markets&apos; value. Their internal market was shut down not because it failed, but because leadership didn&apos;t want the transparency it produced.&lt;/p&gt;&lt;p&gt;Rowan also pointed out that in the last NYC mayoral election, for example, news networks were calling it a toss-up on election night, while Polymarket had been saying for weeks that Zohran Mamdani had a 95% chance of winning. He also argued that farmers could use commodity price markets to make planting and purchasing decisions more confidently than futures contracts allow. On insider trading, he contended that stock markets and futures markets are equally susceptible, making singling out prediction markets a double standard.&lt;/p&gt;&lt;p&gt;Max challenged the core argument that prediction markets produce valuable information, by pointing out that polls, expert panels, and superforecasters already provide accurate data without requiring ordinary people to lose money. Since only 3.14% of traders drive all credible price discovery, the rest are simply funding an elite that functions no differently than a paid expert panel, except at everyone else&apos;s financial expense.&lt;/p&gt;&lt;p&gt;Eternal added to this by stating that certain actors do not merely predict information. They can also create it. A politician controlling a lockdown, or a general controlling a strike, can manufacture the very event they bet on.&lt;/p&gt;&lt;p&gt;Analysis Both sides agreed that prediction markets are gambling, and that insider trading is real. The core disagreement was whether the informational benefit justifies the financial harm to retail participants. The audience narrowly voted against prediction markets—which Rowan and Sahil said they predicted.&lt;/p&gt;&lt;p&gt;What are your thoughts?&lt;/p&gt;&lt;p&gt;Editor&apos;s note: you can now submit pieces as responses to other pieces. Have something to share on prediction markets? Submit it to @eps&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>YSWS Quality &amp; Integrity Weekly Update #2</title><link>https://news.hackclub.com/changelogs/ysws-progress-report-2/</link><guid isPermaLink="true">https://news.hackclub.com/changelogs/ysws-progress-report-2/</guid><description>550 projects were approved across YSWS programs between April 24 and May 1. Of those, 529 have been through at least the first spot check pass. 434 passed cleanly, 82 were flagged for changes, and 13 were rejected outright. 13 fines were issued and 8 projects were eliminated.</description><pubDate>Fri, 01 May 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;What happened this week&lt;/p&gt;&lt;p&gt;550 projects were approved across YSWS programs between April 24 and May 1. Of those, 529 have been through at least the first spot check pass. 434 passed cleanly, 82 were flagged for changes, and 13 were rejected outright. 13 fines were issued and 8 projects were eliminated.&lt;/p&gt;&lt;p&gt;Coverage&lt;/p&gt;&lt;p&gt;The pipeline is still three passes. First pass is automated, every project goes through it. Second pass is me resolving conflicts and correcting false positives. Third pass is the deep dive: open the repo, read the commits, cross-reference Hackatime heartbeats against logged hours.&lt;/p&gt;&lt;p&gt;Of the 550 approved this week: 78.9% passed the automated check cleanly, 14.9% were flagged for changes, and 2.4% were rejected outright. 14% made it to the second pass, and 9.6% went all the way to the third. The target for third pass coverage is at least 5%, but I&apos;m aiming for around 15%.&lt;/p&gt;&lt;p&gt;Cumulative totals&lt;/p&gt;&lt;p&gt;Since the spot check pipeline started: 21,268 total checks, 110 fines issued, 223 projects eliminated.&lt;/p&gt;&lt;p&gt;Breakdown by program&lt;/p&gt;&lt;p&gt;P = Passed, NC = Needs Changes, R = Rejected. Projects approved April 24 to May 1, 2026.&lt;/p&gt;&lt;p&gt;Ember: 50 of its 55 projects were flagged on first pass because they are updates to previous Campfire projects and were mistakenly marked as duplicates by the automated check. All 50 passed on second review once the false positive was corrected. The projects themselves are fine.&lt;/p&gt;&lt;p&gt;BakeBuild is similar: all 9 projects were flagged because the repo format didn&apos;t match what the automated check expected.&lt;/p&gt;</content:encoded></item><item><title>Responses and Followups</title><link>https://news.hackclub.com/changelogs/responses-and-followups/</link><guid isPermaLink="true">https://news.hackclub.com/changelogs/responses-and-followups/</guid><description>Slacker News began with a dream: fewer flamewars. The Slack is not a good place for hard conversations, especially public ones. You deserve better than to have your idea buried in a thread with 1000+ replies. And you deserve a fair hearing. Slacker News is the way. Few responses written carefully, instead of many responses written quickly.</description><pubDate>Wed, 29 Apr 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;Slacker News began with a dream: fewer flamewars. The Slack is not a good place for hard conversations, especially public ones. You deserve better than to have your idea buried in a thread with 1000+ replies. And you deserve a fair hearing. Slacker News is the way. Few responses written carefully, instead of many responses written quickly.&lt;/p&gt;&lt;p&gt;This is your newspaper too. I am asking you to share your thoughts. Including criticism, even of HQ. As of today, Slacker News lets stories be marked as followups or responses to other stories (as demonstrated above). This is meant to make the paper more like the conversation it is meant to be.&lt;/p&gt;&lt;p&gt;Hack Club has come a long way. Sometimes we are divided over how it should run, but we are united by the fact that we were lucky enough to find this special place. I am giving you a higher stage, I am handing you a louder microphone. I am asking you to elevate the quality of disagreement here so that it can build the even better Hack Club we all want to see.&lt;/p&gt;</content:encoded></item><item><title>YSWS Quality &amp; Integrity Progress Report #1</title><link>https://news.hackclub.com/changelogs/ysws-progress-report-1/</link><guid isPermaLink="true">https://news.hackclub.com/changelogs/ysws-progress-report-1/</guid><description>Since March, 20,630 projects have gone through the spot check pipeline. Most of that is automated, a script doing the tedious work of checking fields and flagging obvious issues. The numbers are: 426 rejected on first review, 97 fines issued, 207 projects eliminated from the database.</description><pubDate>Wed, 29 Apr 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;What happened&lt;/p&gt;&lt;p&gt;Since March, 20,630 projects have gone through the spot check pipeline. Most of that is automated, a script doing the tedious work of checking fields and flagging obvious issues. The numbers are: 426 rejected on first review, 97 fines issued, 207 projects eliminated from the database.&lt;/p&gt;&lt;p&gt;How spot checks work now&lt;/p&gt;&lt;p&gt;When I started doing this, the process was basically: open a project, look at it, decide if it&apos;s real. That works when you have fifty projects. It does not work when you have twenty thousand.&lt;/p&gt;&lt;p&gt;So I split it into three passes.&lt;/p&gt;&lt;p&gt;The first pass is automated. A script runs through every project and checks it against the rules at hack.club/ysws-rules. Missing fields, incomplete data, hours that don&apos;t add up, obvious red flags.&lt;/p&gt;&lt;p&gt;The second pass is where I come back in. The automated process isn&apos;t perfect. It flags things that turn out to be edge cases, and occasionally it misses things that aren&apos;t. So I re-review every conflict the script surfaced, correct the false positives, and catch what slipped through.&lt;/p&gt;&lt;p&gt;The third pass is the real work. I open the repo. I read the commits. I look at the Hackatime heartbeats. And I decide whether the hours someone logged actually match the work that&apos;s there. This is the pass that catches hour inflation, projects that look polished on the surface but have three commits and forty hours logged, projects where the code was clearly generated in an afternoon but the approved hours say otherwise.&lt;/p&gt;&lt;p&gt;14,236 checks happened in March. 6,393 so far in April. The volume is high because we&apos;re working through the backlog program by program, and there are a lot of programs.&lt;/p&gt;&lt;p&gt;Programs in 2026&lt;/p&gt;&lt;p&gt;Right now, ten programs account for the bulk of approved projects this year. Here&apos;s where each one stands in the spot check process:&lt;/p&gt;&lt;p&gt;\* Only the first automated pass is complete. Second and third passes have not started yet. Not every program has been through all three passes. Campfire Satellites, Blueprint, and Construct have only had the automated check so far. Their rejection, fine, and elimination numbers are going to change once I actually sit down with the repos and the commit histories. The programs further down the table, like Stasis, Midnight, and Flavortown, have been partially through the full process, and that&apos;s where you see the fines and eliminations showing up.&lt;/p&gt;&lt;p&gt;These numbers are going to look different in a few weeks. There are a lot of projects still waiting for a human to actually look at them.&lt;/p&gt;&lt;p&gt;Fines&lt;/p&gt;&lt;p&gt;97 fines have been issued so far. That&apos;s 742 hours removed from the database and $2,527 in fine money collected.&lt;/p&gt;&lt;p&gt;Here&apos;s how the math works. When a spot check finds hours that shouldn&apos;t be in the database, those hours get removed and the program gets fined $12 per hour. The program can earn $8.50 of that back by properly re-processing the project: going back to the submitter, getting the issue fixed, and re-submitting it through the normal review flow. The remaining $3.50 is permanent.&lt;/p&gt;&lt;p&gt;Eliminations&lt;/p&gt;&lt;p&gt;207 projects have been eliminated from the database. These are projects that were approved but shouldn&apos;t have been at all: fraudulent submissions, duplicates, projects that didn&apos;t meet the minimum bar. 1,328 hours removed in 2026.&lt;/p&gt;&lt;p&gt;The elimination rate is about 2.7% of this year&apos;s approvals. Low enough that fraud isn&apos;t a systemic problem, but high enough that it clearly exists and needs to be actively watched.&lt;/p&gt;&lt;p&gt;What&apos;s next&lt;/p&gt;&lt;p&gt;There are thousands of projects sitting in the queue waiting for a human to open the repo and actually look. That&apos;s going to take a while, and the numbers in this report are going to shift as it happens. :)&lt;/p&gt;</content:encoded></item><item><title>The Issue of AI Slop</title><link>https://news.hackclub.com/opinion/ai-slop-ysws/</link><guid isPermaLink="true">https://news.hackclub.com/opinion/ai-slop-ysws/</guid><description>Recently, I was a reviewer for a Hack Club program called Jackpot. The program itself was incredibly cool, and hats off to Emma for putting so much work into organizing it, but the reviews were... depressing. Emma herself said in a Slack message:</description><pubDate>Sat, 25 Apr 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;Recently, I was a reviewer for a Hack Club program called Jackpot. The program itself was incredibly cool, and hats off to Emma for putting so much work into organizing it, but the reviews were... depressing. Emma herself said in a Slack message:&lt;/p&gt;&lt;p&gt;“[A]round 80% of the reviews, was spent rejecting entire projects due to clear, full use of AI without minimal human contribution. Many of the submitted websites look almost identical, heavily vibe-coded, and in some cases include scripts designed to automatically track or generate hours.&lt;/p&gt;&lt;p&gt;I remember getting in a call with @owais and going through reviews, only for us to send every other project to each other, asking &quot;is this AI again?&quot; The worst part is that this isn&apos;t even an issue unique to Jackpot. It&apos;s also known that Flavortown faces issues with AI slop as well, to the point where Hack Clubbers joke about it quite often on the Slack. The AI issue has been getting progressively more prominent as time goes on, and it&apos;s worth a think over.&lt;/p&gt;&lt;p&gt;This isn&apos;t to say there are no good projects coming to YSWSes anymore. In fact, it&apos;s quite the opposite. During my time reviewing for Hack Club: The Game and Jackpot, I saw so many creative, high-effort, and amazing projects submitted, and it truly made me incredibly proud of our community (if not a little bit disappointed in myself for being so unaccomplished). But it&apos;s also true that a lot of slop is being submitted, and some of it even makes it past our review process. So, what can we do to reduce this?&lt;/p&gt;&lt;p&gt;What is AI Slop?&lt;/p&gt;&lt;p&gt;To address AI slop, we must first define what it is. Originally, this was a blog post that was meant to do just that: figure out what counts as too much AI usage and what is not. I put out a question in my personal channel #stelles-cozy-planet on Slack, which sparked an extremely active thread of discussion, some of which was extremely funny, but ultimately went nowhere. We failed to arrive at any consensus.&lt;/p&gt;&lt;p&gt;I&apos;ll briefly sum up what little conclusions I was able to arrive at:&lt;/p&gt;&lt;p&gt;Using this, let&apos;s together arrive at a definition for what &quot;AI slop&quot; is:&lt;/p&gt;&lt;p&gt;“A low-effort, low-quality project made primarily using AI, usually to the point where AI usage is apparent without looking at its code.&lt;/p&gt;&lt;p&gt;This is nowhere near a perfect definition of what defines AI slop; the term is honestly very subjective. For the purposes of this article, let&apos;s use mine for now.&lt;/p&gt;&lt;p&gt;Why is AI Slop So Prevalent Now?&lt;/p&gt;&lt;p&gt;It probably has to do with how big Hack Club is getting. It&apos;s not the whole cause, of course, but it would make sense. Hack Club is built on hackers -- people who build because they want to build, create because they want to create. As we expand, we gain more of a second type of Hack Clubber: the ones who join simply for prizes and rewards.&lt;/p&gt;&lt;p&gt;This isn&apos;t necessarily bad. The truth is, a lot of the hackers mentioned earlier (build because they want to build) started out as this second type of Hack Clubber. I joined looking for free stuff, and gradually fell in love with coding for the sake of coding and making for the sake of making.&lt;/p&gt;&lt;p&gt;But this isn&apos;t the case for all type 2 Hack Clubbers. Some are just looking to get prizes + get out. That&apos;s perfectly valid--but it&apos;s the methods you employ to achieve such ends that get you put into AI slop timeout corner.&lt;/p&gt;&lt;p&gt;The truth is, the fastest way to make working projects is to yell at Claude until it spits out something savory. Oh what the hack, even I&apos;m guilty of this. The code for my blog (where this was originally posted) was mostly vibecoded too, since I was too lazy to actually go and read documentation and watch tutorials on how to make one. I&apos;d like to justify it to myself, saying that I learnt it from the AI or by reading the AI&apos;s code, but it certainly doesn&apos;t beat actually learning how to make it myself, and then making it myself. If you asked me to replicate it right now... I probably couldn&apos;t!&lt;/p&gt;&lt;p&gt;What this means for us is: we&apos;re getting lots of people who are joining for prizes and prizes alone, and we&apos;re growing into an age where it&apos;s extremely easy to generate the projects needed to earn the prizes. Put two and two together... the fastest and easiest way to get prizes is to AI generate projects, and so, instead of learning, building, making, creating... people are AI slopping.&lt;/p&gt;&lt;p&gt;I don&apos;t want to make you think that &quot;ohhhh, everyone is just out to fraud hours and make slop to get prizes!&quot; Truthfully, a good amount of people may not even realize that they have made AI slop; we could do a better job of preventing AI slop from happening in the first place.&lt;/p&gt;&lt;p&gt;Sidebar - Why Did Jackpot Receive So Much More Slop?&lt;/p&gt;&lt;p&gt;Jackpot was an extremely generous program (which is great) in that its hourly rate ($6/hr) was extremely high versus other Hack Club programs, as well as the fact that the Jackpot IRL event was free to attend (no hours needed for an invite). However, I think this ultimately bit the program in the back: the direct translation of hours to money, the event being free to attend -&amp;gt; shipping solely being for prizes, and the prizes having near equal values around the board regardless of hacker value translated to the program feeling sort of like a job, even.&lt;/p&gt;&lt;p&gt;This section isn&apos;t meant to criticize Jackpot, but moreso analyze exactly why this amazing, generous, and creative program faced the issues that it did. The truth is that working with Emma and everyone else on the Jackpot was such a fun time, and I&apos;m extremely grateful they invited me to help review. I&apos;m so excited for what she and her team will do next.&lt;/p&gt;&lt;p&gt;Okay. Whew. That was a lot. Sorry. I&apos;ve been doing a whole Latta yapping, and not a whole Latta giving suggestions--so, let&apos;s talk solutions, roughly from easiest to hardest to implement.&lt;/p&gt;&lt;p&gt;Clearer AI Guidelines&lt;/p&gt;&lt;p&gt;Some programs seem to have some arbitrary percentage limit in terms of AI usage. Off the top of my head, HCTG lists a 30% AI limit and Macondo has a 40% limit.&lt;/p&gt;&lt;p&gt;In theory, these are good ways to filter through AI slop, but in practice, percentages do not work. There&apos;s no way to detect how much code was AI and how much wasn&apos;t. At the end of the day, these random numbers are just a nothing burger. As a reviewer, I look at a project and I try to gauge whether human effort was put into the project. I try to gauge if AI was used for small, minor tasks, or if it was used to generate the main functionality of the project. I try to gauge if the user has gone &quot;uhhhh claude make me a website,&quot; or sat there meticulously thinking of things to add, writing out to Claude exactly what they want and how they want Claude to implement it.&lt;/p&gt;&lt;p&gt;The solution is to detail these exactly. What are reviewers looking for? How should we (participants) be using AI? How shouldn&apos;t we be?&lt;/p&gt;&lt;p&gt;“❌ &quot;Yeah, keep it under x%&quot; ✅ &quot;Only use AI for mundane tasks! Make sure you still understand your code! Put effort into making it look human-made!&quot;&lt;/p&gt;&lt;p&gt;In fact, I&apos;ll do you one better -- here&apos;s a general modifiable template that YSWSes can use for a clearer and more tangible AI guideline.&lt;/p&gt;&lt;p&gt;“Excessive AI usage is NOT allowed. When reviewing projects, we look for genuine human effort in both the final product and the thought behind it. There is a difference between someone who typed &quot;make me a website&quot; and someone who carefully considered what to build, made deliberate decisions, and used AI to help execute specific parts. You are allowed to use AI in minor and supporting ways such as: small improvements and touch-ups simple, repetitive tasks that would be tedious by hand cleaning up messy code (just commit first so there&apos;s a record of your code before AI touched it!) A good rule of thumb: could a reviewer still see your personality on the project if AI were removed? If the core of your project (functionality, structure, style, etc) were all AI-generated, it won&apos;t pass review.&lt;/p&gt;&lt;p&gt;This eliminates the issue of vague nothing burger, clearly defining what is okay and what would get rejected. YSWS organizers, reviewers, others, feel free to add or remove bullet points as you see fit, reword the lead-in and conclusion, add more. This is completely free for you to use or take inspiration from.&lt;/p&gt;&lt;p&gt;Also, how do we as reviewers uphold a common standard of what counts as AI slop? Rubric!&lt;/p&gt;&lt;p&gt;“Metagame: All / lot of the code in a single, initial commit? AI-sounding comments? Placeholder tokens, data, or statistics? Common AI Patterns: Unnatural shoehorning of emojis, gradients? Overuse of &quot;Badges&quot; or &quot;pills&quot;? Common AI animations? Content hallucinations? Code: Overly verbose variable names? Excessive error handling / edge cases no one but an AI would think of?&lt;/p&gt;&lt;p&gt;Note that this rubric is not exhaustive and is meant for use as a tool. It&apos;s not designed to evaluate projects perfectly, it&apos;s meant to help you with common signs of AI usage--the final determination and review of a project should still be up to you.&lt;/p&gt;&lt;p&gt;Intentional YSWS Design&lt;/p&gt;&lt;p&gt;No, this is not the aggressive rethinking of the weighted grant model you&apos;ve been hoping for. Many a smarter person than I have tried and failed to tackle the WG/WP system, and as such I will not be attempting to do so today.&lt;/p&gt;&lt;p&gt;The answer to AI slop is to make it impossible to make AI slop per your constraints on the program or rules for submission. This solution will not work for a good amount of YSWSes (most likely the larger ones, which is a bit counterintuitive since they are the ones facing the most AI slop in the first place), but for smaller YSWSes, this will work like a charm. Here&apos;s how:&lt;/p&gt;&lt;p&gt;1. Add an interesting constraint to your YSWS&lt;/p&gt;&lt;p&gt;For #onekey, I&apos;m challenging people to build projects that only use one key as input. Others that fit this model include #saycheese and #shrink by @Anson Chung.&lt;/p&gt;&lt;p&gt;These sorts of constraints are difficult to slop - they at the very least require the prompter to sit there and think about the project and be creative with it, toeing the line between responsible and irresponsible AI usage. You can&apos;t just sit there and say &quot;make me a website, make no mistakes&quot; and watch as Claude works away at another B2B SaaS concept website.&lt;/p&gt;&lt;p&gt;2. Submission prompts&lt;/p&gt;&lt;p&gt;Ask questions that require reflection, such as: &quot;What were some challenges you faced? What was the hardest part? What was your favorite part?&quot;&lt;/p&gt;&lt;p&gt;It won&apos;t perfectly filter out AI slop, and it won&apos;t prevent it from being submitted, but it will give reviewers somewhat of an immediate BS detector.&lt;/p&gt;&lt;p&gt;If these were implemented...&lt;/p&gt;&lt;p&gt;...our programs could be better suited to deter AI slop and incentivize what we want submitted--high quality projects that promote learning and building and growing. We would also have more interesting YSWSes to participate in, and more content to look at (namely, reflections might be interesting for something like the Hack Club Magazine).&lt;/p&gt;&lt;p&gt;VAC Bans&lt;/p&gt;&lt;p&gt;The time for blaming ourselves is over. At some point, people begin to know what they are doing when they slop. It is intentional. Calculated.&lt;/p&gt;&lt;p&gt;The idea is simple: Hackatime ban or ban-adjacent system for those who have submitted AI slop more than once.&lt;/p&gt;&lt;p&gt;Pros:&lt;/p&gt;&lt;p&gt;Cons:&lt;/p&gt;&lt;p&gt;I think the tradeoffs are worth it, and with some workshopping, the cons can be ironed out. Implementation of some sort of system, whether it&apos;s a literal Hackatime ban or some sort of system flagging offenders on the reviewer end, would stop sloppers from taking up valuable reviewer bandwidth ~~and keep reviewer faith in humanity.~~&lt;/p&gt;&lt;p&gt;Conclusion&lt;/p&gt;&lt;p&gt;The point I&apos;m trying to make is... AI slop is a big issue for Hack Club. Whether you&apos;re a Hack Clubber browsing Flavortown&apos;s explore page and observing the amount of vibecoded projects, or a reviewer rejecting your 5th vibecoded project in the same hour, or a program organizer getting fined for letting slop enter the unified DB... it&apos;s not just my problem, not just your problem, not just HQ&apos;s problem, but it&apos;s a problem for all of us.&lt;/p&gt;&lt;p&gt;This isn&apos;t a simple problem to address. The line between responsible AI use and lazy vibecode is blurry, and all of us--participants, reviewers, organizers--will get it wrong sometimes. With Hack Club growing the way it is, and Stardance right around the corner poised to attract thousands if not tens of thousands of new Hack Clubbers, it&apos;s important to acknowledge that we will never be completely free of AI slop. But if we can build a community that genuinely cares, with programs that set clear expectations, ideas that make real building worth it, and systems that stop bad actors from gaming the whole thing... maybe we can make sure that what all of us have grown to love about Hack Club--the way it turns prize-hungry kids into passionate, inspired builders--wins out over AI slop.&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>How to Get HQ to Notice Your Idea</title><link>https://news.hackclub.com/opinion/how-to-get-noticed/</link><guid isPermaLink="true">https://news.hackclub.com/opinion/how-to-get-noticed/</guid><description>This piece has been updated. Thanks to @eternal for his feedback.</description><pubDate>Tue, 21 Apr 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;This piece has been updated. Thanks to @eternal for his feedback.&lt;/p&gt;&lt;p&gt;HQ receives a lot of good ideas about things we should do. In fact, we receive more good ideas than we can really handle. This is a good problem to have. We’re lucky to have a community that cares, rather than a community that has given up. But this surplus of ideas leads to rejection, which leads to frustration.&lt;/p&gt;&lt;p&gt;I’ve put together a couple of observations about which advice gets implemented. I hope it helps.&lt;/p&gt;&lt;p&gt;I. Small asks are better than big ones&lt;/p&gt;&lt;p&gt;&quot;Here&apos;s my plan, what do you think of it?&quot; is a request I can satisfy in 5-10 minutes. &quot;Here&apos;s my goal, can you plan it?&quot; might take 1-8 hours. &quot;Here&apos;s my dream, can you do it?&quot; might take weeks or months.&lt;/p&gt;&lt;p&gt;I like helping people! This is fortunate, since it is my job. I&apos;m not writing this piece to discourage you from asking us for help. I&apos;m writing this piece to help you pick which ideas to pitch to us. Focus on things where you can do most of the work, and where you need HQ for something small. This makes it much easier for us to say yes to you.&lt;/p&gt;&lt;p&gt;II. Bring a Working Prototype&lt;/p&gt;&lt;p&gt;When I started here, I said yes to helping out with almost every idea people brought to me. But I found that most of those ideas never got finished, even when I stepped in to try and help finish them. I have talked to other HQ staff, and they have had similar experiences.&lt;/p&gt;&lt;p&gt;Now, when I ask myself how likely it is that a cool idea will be implemented, I start with the baseline observation that most cool ideas do not get implemented. This is not cynicism; this is me being frugal with your money. Hack Clubbers often ask me to fund things. I don’t have that much money at my disposal. If I said yes to every promising idea, I would go broke fast. My time is also your money, so I try to be frugal with that, too.&lt;/p&gt;&lt;p&gt;I’ve stopped funding ideas and switched to funding demonstrated achievements. I tell people, “Do it for free at a small scale to show me that it works. Then I will fund you to scale up.”&lt;/p&gt;&lt;p&gt;I can’t tell these things about you by talking with you. So the way I identify people who can get it done is by seeing who can bring me a working prototype.&lt;/p&gt;&lt;p&gt;By the way, “people who can get things done” are an open group that anybody can join. I wasn’t totally hopeless before Hack Club or they wouldn’t have hired me. But I have learned more about getting things done in four months here than I have in years working at other places. It’s actually quite simple: give yourself permission to fail. Instead of trying to think your way to the perfect idea, just try things to find out what works. And when you fail, don’t give up. Keep trying. There is other advice, but just these two things will get you very far.&lt;/p&gt;&lt;p&gt;III. Think about Opportunity Cost&lt;/p&gt;&lt;p&gt;Before Hack Club, I worked in schools. I heard a lot of opinions about what teenagers needed to learn. Whenever someone told me that schools should teach something, I always answered with: “So what would you cut?”&lt;/p&gt;&lt;p&gt;You are really busy. Saying that teenagers should learn more about X requires that you learn less about Y. There’s no getting away from it. The hard truth for anyone designing a curriculum is that there is more stuff worth knowing than there is time to learn it.&lt;/p&gt;&lt;p&gt;We are in the same situation at HQ. We have our core job responsibilities. Then we have requests from other people. Every day I get 20-40 messages, which is on the low side. Higher-profile staff members get hundreds of DMs and mentions every day.&lt;/p&gt;&lt;p&gt;In short, we all get more requests and suggestions than we can act on. Saying yes to your idea means saying no to someone else’s idea. This isn’t a criticism of any idea. It’s just a hard truth.&lt;/p&gt;&lt;p&gt;Saying yes to your idea means saying no to something else. This is really important. It is the #1 constraint on our ability to say yes to you, and it can’t be fixed.&lt;/p&gt;&lt;p&gt;It’s brutal because it means even if your idea is objectively a good idea and would make Hack Club better, that’s still not enough to guarantee one of us will say yes to you.&lt;/p&gt;&lt;p&gt;We aren’t just waiting for good ideas to implement. We are picking which good ideas to implement. Sometimes I want to tell people “I’m sorry, but I’m too busy”. It sounds rude because it sounds like I don’t care. On the contrary, “I’m busy” means “I care so much about what I’m already doing that I can’t stop to do this.”&lt;/p&gt;&lt;p&gt;IV. But Don’t Be Scared to Ask&lt;/p&gt;&lt;p&gt;This doesn’t mean you should stop suggesting ideas! Please keep suggesting ideas! Our best work comes from you all. Without hearing and choosing from your ideas, Hack Club wouldn’t be the special place it is.&lt;/p&gt;&lt;p&gt;In particular, I have noticed that some people go through life trying to be as small as possible. “Um, excuse me, but if it’s not too much trouble, my house is on fire, and I was wondering if you could put it out? Or maybe just lend me some water and I’ll do it? What am I saying, I’m sure I can get water somewhere else, and I know how busy you are. I’m sorry to have wasted your time.”&lt;/p&gt;&lt;p&gt;Other people go too far in the opposite direction, and make really bold claims on your time, asking you to do things they could do themselves. I don’t see much of this at Hack Club (thanks guys!) but I used to see it all the time when I worked in schools.&lt;/p&gt;&lt;p&gt;Members of these two groups generally believe that they are in the opposite group.&lt;/p&gt;&lt;p&gt;I worry that when people read this piece, the ones who want too much will ignore it, and the ones who don’t want enough will assume it is about them. Actually, it isn’t about anybody. My point is not “ask for less”. My point is “get really good at asking”. Here’s how:&lt;/p&gt;&lt;p&gt;I hope this post doesn’t sound like I’m complaining, criticizing, or making excuses. My goal is simply to be honest about the constraints that HQ works under, so that you have the best chance possible of getting your idea noticed within those constraints. We are here to serve you, and without your ideas, Hack Club would be lame. I’m not writing this to discourage suggestions. I’m writing it to help your suggestions succeed. We need you.&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>Changing Ads in #ysws</title><link>https://news.hackclub.com/news/new-ysws-channel/</link><guid isPermaLink="true">https://news.hackclub.com/news/new-ysws-channel/</guid><description>Most community made events start in #ysws on Slack. That first step has changed slightly a few weeks ago.</description><pubDate>Mon, 20 Apr 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;Most community made events start in #ysws on Slack. That first step has changed slightly a few weeks ago.&lt;/p&gt;&lt;p&gt;But first, what is a You Ship We Ship (YSWS) programme? YSWS&apos;s are events Hack Club runs where you &apos;ship&apos; a project and Hack Club ships something in return. This could be anything from making a website and getting $5 to buy boba or spending 40 hours making CAD projects to get a 3D printer.&lt;/p&gt;&lt;p&gt;Slack is used to promote your YSWS idea. For example, when I was searching for a sponsor for my YSWS Woof I received lots of engagement from the community through upvotes and because I posted regularly my draft&apos;s advert in #ysws. Before the new rule, you could post multiple times a week - now you are limited to once a week. This is to clean up the channel and make sure that all YSWS&apos;s can be viewed easily and make it easier for people to find events they are interested in. Also, you must not have a fillout embedded in your post as it takes up too much space.&lt;/p&gt;&lt;p&gt;There is an exciting change coming in this new system as well. Every week an update on all the current YSWS Drafts and current programs will be posted in #ysws-bulletin. This will declutter #ysws and provide an easy-to-read rundown on current programs. To add your YSWS to the queue just fill out this form.&lt;/p&gt;&lt;p&gt;Just as I was finishing writing this article a poll was posted in #ysws asking about the community&apos;s overall opinion on the changes and current problems. As of Tuesday the 21st, people who liked the changes outnumbered people who disliked the changes 10 to 1. A large group was also neutral or undecided.&lt;/p&gt;&lt;p&gt;This shows that while we don&apos;t have all the answers, we&apos;re headed in the right direction. If you have an idea for how to improve #ysws or an idea for an event then head over to the slack channel or take a look at the new bulletin.&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>What a Quality and Integrity Manager Actually Does</title><link>https://news.hackclub.com/quality-integrity-manager/</link><guid isPermaLink="true">https://news.hackclub.com/quality-integrity-manager/</guid><description>A month ago I started a new role at Hack Club called Quality and Integrity Manager, which sounds really fancy. What it actually means is that I spend my days reviewing other teenagers’ project submissions and deciding whether they are real submissions or low quality effort projects made just to get something in exchange.</description><pubDate>Fri, 17 Apr 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;A month ago I started a new role at Hack Club called Quality and Integrity Manager, which sounds really fancy. What it actually means is that I spend my days reviewing other teenagers’ project submissions and deciding whether they are real submissions or low quality effort projects made just to get something in exchange.&lt;/p&gt;&lt;p&gt;I want to explain why anyone should care about that.&lt;/p&gt;&lt;p&gt;What is even happening here&lt;/p&gt;&lt;p&gt;Quick tour, in case you’re new.&lt;/p&gt;&lt;p&gt;Hack Club is a nonprofit for teenagers who like building things. The cool part, the thing that makes it different from basically every other “learn to code” org, is that you actually get to build the stuff you’ve always wanted to build instead of just completing a course. And then you get something real in exchange for shipping it: a Raspberry Pi, a domain, a flight to a hackathon.&lt;/p&gt;&lt;p&gt;A lot of that happens through YSWS, which stands for You Ship We Ship. Someone proposes a program: “build a Minecraft mod and I’ll send you server credits.” Teenagers ship projects against it. Reviewers look at the projects and decide whether they’re real, hours logged match the project, and there’s no fraud. Approved projects go into one shared database, weighted by the hours the maker actually put in. Program authors then get funded by Hack Club based on how many weighted projects their program produced.&lt;/p&gt;&lt;p&gt;So when I say “a weighted project,” I mean a unit in that shared database. One ship, with hours attached, that has cleared the bar.&lt;/p&gt;&lt;p&gt;This concept is very interesting, because it’s the closest thing Hack Club has to a common currency.&lt;/p&gt;&lt;p&gt;The boring-sounding idea?&lt;/p&gt;&lt;p&gt;If the weighted project is going to be a currency, it should mean the same thing no matter which program it came from.&lt;/p&gt;&lt;p&gt;One hour of shipped work in program A should reflect the same effort, the same standard, the same realness as one hour in program B. If that holds, then “weighted project” stops being an accounting line and becomes something much more useful: a stable unit you can build other things on top of.&lt;/p&gt;&lt;p&gt;I think about it like money. A dollar is a dollar whether you earned it at a job or found it on the sidewalk. You don’t have to inspect it before spending it. You just trust the unit, and that trust is the thing that lets the whole economy run on top of it.&lt;/p&gt;&lt;p&gt;Right now, that trust isn’t fully there. There’s a common pattern where program X has way more weighted hours than program Y, but if you actually open the submissions, program Y’s projects are so much cooler. The submitters clearly invested more time in their projects, the work is more ambitious, the ships are more interesting. Program X just had a looser review process. On paper, X looks like the runaway success and Y looks like it’s underperforming, when the truth is closer to the opposite.&lt;/p&gt;&lt;p&gt;When the unit is trustworthy, that goes away. You can launch a brand new program and know exactly what it’s producing. Compare a program that’s been around for two years against one that’s two weeks old, honestly. Look at the database and say “huh, this kind of program is taking off, what if we leaned in.”&lt;/p&gt;&lt;p&gt;And that matters because the version of Hack Club I want to exist is one where a teenager can look at a program, decide it sucks in some specific way, and go run and create the thing that replaces it. Where every year doesn’t look like the last one. That kind of constant reinvention only works if there’s a foundation underneath it that doesn’t wobble. You can’t experiment if your measuring stick changes length depending on who’s holding it.&lt;/p&gt;&lt;p&gt;Everyone kinda knew, but nobody had it written down&lt;/p&gt;&lt;p&gt;It’s not like people had no idea what a good project looked like. Everyone had a general sense. If you saw a well-built videogame with 25 hours of work behind it, you knew that was real. If you saw a half-finished website with 40 hours logged, you knew something was off.&lt;/p&gt;&lt;p&gt;The problem was the middle. The edge cases. A project that was decent but maybe not 20-hours-of-work decent. A submission that technically worked but felt like it was thrown together in an afternoon. For those, the answer depended on which person you asked. One might say approve it, another might say reject it, and both of them would have a reasonable explanation for their call. The rules existed as a kind of shared intuition, passed around in conversations and Slack dms, and if you happened to catch the right person on the right day you’d get one answer, and if you caught someone else you’d get a different one.&lt;/p&gt;&lt;p&gt;That works fine when you have a handful of programs and a small team. It stops working when you have dozens of programs, hundreds of reviewers, and thousands of submissions flowing into one shared database.&lt;/p&gt;&lt;p&gt;So we wrote the rules down. They live at hackclub.com/ysws-rules. Every ship that lands in the database has to clear them. The point isn’t to be prescriptive about what teenagers can build (build whatever you want, that’s the whole game), it’s to take those judgment calls that used to depend on who you asked and give them one consistent answer.&lt;/p&gt;&lt;p&gt;For the past few weeks I’ve been going program by program, flagging issues to authors directly and gathering feedback as we iterate.&lt;/p&gt;&lt;p&gt;But writing down the rules only solves half the problem. The other half is: what happens when they don’t get followed?&lt;/p&gt;&lt;p&gt;The funny part&lt;/p&gt;&lt;p&gt;Imagine you’re a reviewer and a borderline project comes across your desk. It’s not great, but it’s not obviously bad either. You could reject it and move on. But if you approve it, your program gets credited for those hours, which means more funding.&lt;/p&gt;&lt;p&gt;Nobody sits there thinking “I’m going to approve bad projects on purpose.” That’s not how it works. What happens is subtler: when approving is free and rejecting has a cost, the thumb is always on the scale. Across hundreds of submissions, that tiny pressure adds up. Programs that are strict with their reviews end up with fewer hours than programs that aren’t, and the strict programs look like they’re underperforming. The incentive structure quietly rewards the wrong behavior, even when every individual reviewer means well.&lt;/p&gt;&lt;p&gt;Fines exist to fix that math.&lt;/p&gt;&lt;p&gt;When I pull a random sample from the database and find hours that shouldn’t be there, those hours get removed. The program that approved them gets fined $12 per removed hour. They can earn $8.50 of that back by properly re-processing the project. The remaining $3.50 is a permanent fine. Fine money goes into an HCB fines org.&lt;/p&gt;&lt;p&gt;The point isn’t to punish anyone for missing things. Every reviewer misses things. I miss things. A single bad approval isn’t a sign of a bad program. But fines make it so that doing the review properly is the cheaper option.&lt;/p&gt;&lt;p&gt;What I actually want&lt;/p&gt;&lt;p&gt;If we get this right, almost nobody should ever have to think about it. The database just works. A weighted project means a weighted project. Reviewers do their thing, programs run their thing, and the foundation holds.&lt;/p&gt;&lt;p&gt;And then the interesting work, the part where some 16-year-old decides that the way Hack Club runs programs is broken and goes off to build a better version, or proposes a program for something nobody’s tried yet, gets to happen on top of something solid, and we have a clear indicator of whether it succeeded or not.&lt;/p&gt;&lt;p&gt;That’s the job.&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>Hack Club Should do Better at Saying Goodbye</title><link>https://news.hackclub.com/better-goodbye/</link><guid isPermaLink="true">https://news.hackclub.com/better-goodbye/</guid><description>Last week, I posted in #meta about how Hack Club recognises contributors when they leave. The response surprised me. The post got 74 upvotes and no downvotes (quite rare in #meta), which by any measure is a pretty strong signal that this resonates with people. You can read the full thread here.</description><pubDate>Mon, 13 Apr 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;Last week, I posted in #meta about how Hack Club recognises contributors when they leave. The response surprised me. The post got 74 upvotes and no downvotes (quite rare in #meta), which by any measure is a pretty strong signal that this resonates with people. You can read the full thread here.&lt;/p&gt;&lt;p&gt;The conversation that followed was genuinely good. People pointed out that there are pages like hackclub.com/team and hackclub.com/acknowledged which exist. Someone suggested a former team page. Someone mentioned that the contributors page on GitHub recognises you. Peter made a fair point that the real privilege of Hack Club isn’t the credit, it’s the community itself, the people you meet, the 3am conversations, and that shared passion. I think that’s true.&lt;/p&gt;&lt;p&gt;However, I also think these two things can go hand-in-hand. You can love what you build here, what you learned here and still want someone to say goodbye properly when you go. That’s honestly how I feel. I like to think that my work done here was impactful but it was never really acknowledged enough by the people who really “managed” my work, which really made my work unseen.&lt;/p&gt;&lt;p&gt;What I was pointing at isn’t really about college applications or getting your name on a website. It’s about something smaller and something more personal. A cupcake. A sentence. A card. Something that says: we saw what you did here, it mattered, and we will miss you. Not a system, not a page, just a moment. That’s exactly what Hack Club was built on and stands for.&lt;/p&gt;&lt;p&gt;The people I’m talking about are the ones who ran events, brought in and mentored new members (including club leaders!), or just showed up consistently for a very long time, sometimes unpaid, and then left quietly. Hack Club is forward-looking by nature, which is normally a strength, but it means people will slip out the door without acknowledgement, and that’s a gap worth closing.&lt;/p&gt;&lt;p&gt;So why doesn’t this happen already? A couple theories: HQ is genuinely stretched thin, and a personalised farewell takes time that’s hard to find when you’re already drowning in DMs. Departures also often go unannounced, people quietly stop showing up, so there’s no natural trigger. And maybe the hardest one: Hack Club’s culture is so focused on what’s being built right now that looking back feels counterintuitive.&lt;/p&gt;&lt;p&gt;I don’t have a definitive fix, but the bar doesn’t need to be that high. A lightweight channel where departures get surfaced. A norm where team leads send a short personal note. A workflow that catches when someone goes quiet. The 74-0 suggests I’m not alone in thinking this matters.&lt;/p&gt;&lt;p&gt;Thoughts?&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>Hack Club Moves to New HQ</title><link>https://news.hackclub.com/new-hq/</link><guid isPermaLink="true">https://news.hackclub.com/new-hq/</guid><description>Last week, @indy, @msw, and @eps showed up in my kitchen by surprise. “Hack Club is where we make things together,” Chris explained. “Where is Hack Club? If you are making things, then that is where Hack Club is.”</description><pubDate>Thu, 09 Apr 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;Last week, @indy, @msw, and @eps showed up in my kitchen by surprise. “Hack Club is where we make things together,” Chris explained. “Where is Hack Club? If you are making things, then that is where Hack Club is.”&lt;/p&gt;&lt;p&gt;I started making Hack Club when I was 15, so back then Hack Club was in my bedroom in my parents’ house. But that year, I moved to the SF bay area to become a programmer. I lived in a group house for hackers. Max slept on the floor of my room, on a mattress pad he found on the sidewalk. Chris was living there too; it’s how we met.&lt;/p&gt;&lt;p&gt;It was an exciting time, but it also showed me something I didn’t like: There were institutions for hackers, and institutions for teenagers, but no institution for teenage hackers.&lt;/p&gt;&lt;p&gt;There are two support systems that should have done it: the education system, and the tech industry’s ecosystem of entrepreneurs. But both had other priorities. The education system is good at structured learning. But hacking is about unstructured experimentation. And hacking is about failing, again and again, until you find what works.&lt;/p&gt;&lt;p&gt;The logical thing is to found a new institution that does it differently. But the other support system–the tech industry’s entrepreneurial ecosystem–isn’t set up for this. If your goal is to make money, there are incubators and VCs and networking events and fellowships and a bottomless well of potential partners. But if you want to start a nonprofit, you’re swimming against an undertow. Every conversation was “What’s my equity upside?” And I would say “There isn’t one. I can pay you one-fifth of what your other pitches are offering.” I spent six months getting a single $50,000 donation, and I was so proud. That night, my roommate told me he secured a $500,000 investment for his startup from a 20-minute conversation.&lt;/p&gt;&lt;p&gt;I did find one person though. Through the San Francisco nonprofit network, I met someone who was running a worldwide network of investigative journalists. At a time when major newspapers were shuttering their foreign bureaus and cutting back on investigative reporting to save money, her reporters were publishing stories no one else would touch, from the Iraqi government prosecuting the widows of alleged ISIS fighters, to the extraordinary challenges for women serving in the then-NATO-backed Afghan military. That was Christina.&lt;/p&gt;&lt;p&gt;Christina was the smartest person in the room, and she thought about business with a level of sophistication and ambition that Hack Club desperately needed. She agreed to become a board member. Later, she joined Hack Club full-time as co-founder.&lt;/p&gt;&lt;p&gt;Along the way, it became clear that the Bay Area was not the right place for Hack Club. Our lease was up anyway, so we decided to go stay with Chris’s family in Maine. That was March 2020.&lt;/p&gt;&lt;p&gt;Everything was already shutting down for COVID, but there was one last week where some places were still open. Chris went to an army surplus store and bought a bunch of props: camouflage nets, ammunition boxes, that sort of thing. For 10 nights in a row, we streamed the COVID Command Center. Millions of teenagers were sealed away inside their homes with nothing to do, and some of them decided to take a look at Hack Club.&lt;/p&gt;&lt;p&gt;We couldn’t stay with family forever. Christina showed us that Vermont, where she lived, shares a lot of California values. The mountains of Vermont are just like my home state: filled with weirdos living out some version of their dream life. Authentic, idealistic, and unapologetic. But Vermont has far more possibility than California. This year we’ll give 40 full-time fellowships to teenagers. In California, we would have succumbed to the financial and cultural pressure, and become just like everything else.&lt;/p&gt;&lt;p&gt;Christina started an AMA series, and one after the other got some of the biggest names in the tech world to show up to our tiny digital doorstep. We stayed at a string of rental properties. First, we lived in a little house in Charlotte. That’s where we did our Elon AMA. Next, we moved to the Mt. Philo Inn. Finally, we rented out a huge house on an island in Lake Champlain. By that point, it was the only rental property big enough to hold all of Hack Club.&lt;/p&gt;&lt;p&gt;Up to that moment, we had put in six years of work and grown Hack Club to 2,000 members. In one month, we grew it to 10,000. After years of trying different things, we finally found the thing that worked.&lt;/p&gt;&lt;p&gt;In October 2020, we found the building you all know as Hack Club HQ. As Hack Club grew, the space grew with it. Each wave of gap years left their mark. HQ feels lived in, and well-loved. That makes it really special to me, and I think everyone who visits it can tell these things instantly.&lt;/p&gt;&lt;p&gt;We kept trying new things. We radically reinvented our events process. Originally, events ran on a traditional model: assign a budget, give periodic updates. Programs would sometimes take most of a year to launch, then get less than 20 Hack Clubbers. YSWS was an aggressive overthrow of the old system. We replaced traditional oversight with blue-sky freedom, and planned budgets with evolving budgets. This is the weighted project system that you all know, and while it has its flaws, it is better than anything that came before it, and it allowed Hack Club to do even more. Before, we had thousands of teenagers watching. Now we have tens of thousands of teenagers actually shipping projects, and several times that number watching and waiting to feel inspired.&lt;/p&gt;&lt;p&gt;As you joined us, Hack Club kept growing. We outgrew HQ and added Phil in 2022, then Tracy in 2023.&lt;/p&gt;&lt;p&gt;The thing I started building in my parents’ bedroom 12 years ago is real now. There is an institution by the teenagers, for the teenagers. But we aren’t done. There are so many more teenagers in the world who need Hack Club and don’t have it yet. We are going to reach all of them, and you are going to build things together that make Hack Club better than it has ever been.&lt;/p&gt;&lt;p&gt;HQ is special to everyone who has ever been there. We will always treasure it, and we will miss it. But we are only at the beginning of Hack Club’s journey, and Shelburne is running out of rental properties.&lt;/p&gt;&lt;p&gt;Hack Club is where we make things together. Where is Hack Club? Starting next month, Hack Club is at 212 Battery St, Burlington, Vermont. But Hack Club is also in your bedroom in your parents’ house, or your classroom at school, or wherever you are making things. Wherever we go, as long as we keep making things, we will always be together and we will always be Hack Club.&lt;/p&gt;&lt;p&gt;Hack Club HQ. April 7, 2026. See a 3D scan of HQ from April 8, 2026.&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019d7486-19f0-7da7-a8fc-155b50463c6c/212_battery_st.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019d7486-19f0-7da7-a8fc-155b50463c6c/212_battery_st.png"/><media:title type="plain">212 Battery St</media:title></item><item><title>Stardance - a NASA x Hack Club Experience</title><link>https://news.hackclub.com/nasa-stardance/</link><guid isPermaLink="true">https://news.hackclub.com/nasa-stardance/</guid><description>You may have noticed us dropping NASA-related hints lately. This is not a coincidence. This summer, Hack Club and NASA are joining forces to bring you something new: Stardance.</description><pubDate>Mon, 06 Apr 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;You may have noticed us dropping NASA-related hints lately. This is not a coincidence. This summer, Hack Club and NASA are joining forces to bring you something new: Stardance.&lt;/p&gt;&lt;p&gt;A few months ago, Zach and Christina had a meeting with Jared Isaacman, the current administrator of NASA. They talked about how space exploration requires a new generation of engineers, but too many teenagers are just consumers of technology and don’t know how to be makers. Hack Club is on a mission to change that. You already know this part. But since then, we’ve been working with NASA behind the scenes, and now we’re ready to tell you that this thing is really happening.&lt;/p&gt;&lt;p&gt;Stardance is coming this summer and we’re so excited to see what you do with it. But before we open the doors and let you in, we have to build it. We’re announcing now because we will be inviting community members to help us make Stardance, without tripping over the need to keep secrets.&lt;/p&gt;&lt;p&gt;For the moment, the existence of Stardance is just about all we are prepared to announce, but more is coming from here on out. Join #stardance-construction (#shhhhhh-contruction at time of writing) and you’ll be the first to know.&lt;/p&gt;&lt;p&gt;Last week, our offices stayed open late because the staff were watching the Artemis launch. I know a lot of you were watching it too. I’ve been fascinated by space for as long as I can remember, but I especially remember playing Kerbal Space Program. I always assumed that subjects like orbital mechanics would just be permanent mysteries, that I would never be smart enough for them. I’ll never forget how I felt to learn that actually, I had the power to understand them.&lt;/p&gt;&lt;p&gt;Stardance isn’t only about space. It is about the larger idea that there is still magic left to discover, and that you–yes, you–can be part of it, can go out and do something life-changing, that you never thought was possible for you.&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>Write Your Own Privacy Policy</title><link>https://news.hackclub.com/community-privacy-policy/</link><guid isPermaLink="true">https://news.hackclub.com/community-privacy-policy/</guid><description>Our Terms and Privacy Policy govern how we use your data. But what governs how everyone else uses it?</description><pubDate>Thu, 02 Apr 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;Our Terms and Privacy Policy govern how we use your data. But what governs how everyone else uses it?&lt;/p&gt;&lt;p&gt;Slack users have each other’s messages, pictures, computer activity history, contact information, and more. This leads to regular controversy, especially over sharing messages outside of the Slack, and giving AIs access to the Slack. Typically, one side argues that their privacy was violated, and the other side argues that (1) the Slack is not a private space and (2) there are no rules against what was done.&lt;/p&gt;&lt;p&gt;As often happens, the real disagreement is beneath the surface, in unspoken values. There is a spectrum of attitudes in play: You have no right to privacy on the Slack. If you don’t want something getting out, don’t say it. You have some right to privacy on the Slack, but these uses don’t violate it. You have a large right to privacy on the Slack, and these uses violate it.&lt;/p&gt;&lt;p&gt;So long as the Slack has no agreement on which of these views prevails, conflict is inevitable,when it happens, nobody will be satisfied by the other side’s arguments because they don’t touch the underlying values.&lt;/p&gt;&lt;p&gt;In short, you need to agree on how much privacy you give each other.&lt;/p&gt;&lt;p&gt;This is doubly true because the Fire Department has limited power to enforce rules here. When people ask the FD’s permission they can say no, but there is little to be done about people who don’t ask and simply do. But norms can go where rules fear to tread.&lt;/p&gt;&lt;p&gt;So we’re going to build these norms together as a community. The first step is to have a live, in-person discussion. It’s not a debate because the issue is too complicated to be reduced into two opposing sides. Debating will occur, but the goal is different:&lt;/p&gt;&lt;p&gt;We will put together several proposed community privacy policies We will put together survey instruments to see how people feel about them&lt;/p&gt;&lt;p&gt;The Forum will be held on Saturday, April 4, at 11 AM ET in a huddle in #community.&lt;/p&gt;&lt;p&gt;This will be followed by an asynchronous phase where we survey the larger community about each of the proposals. If there is one clear winner, we’ll adopt it. If there isn’t, we’ll iterate and try again. An adopted community privacy policy will have the FD’s backing, but it will really gain its force through majority support in the community.&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>Three Months at Hack Club</title><link>https://news.hackclub.com/3-months-at-hack-club/</link><guid isPermaLink="true">https://news.hackclub.com/3-months-at-hack-club/</guid><description>I joined Hack Club full time on January 5th. That’s long enough to look back and take stock.</description><pubDate>Thu, 02 Apr 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;I joined Hack Club full time on January 5th. That’s long enough to look back and take stock.&lt;/p&gt;&lt;p&gt;I am charged with making this Slack an amazing place for teenagers. A place where you learn to take agency, grow your technical skills, and make some of the closest friendships of your life. Zach gave me those goals. I added one more: that the Slack helps you become a better person.&lt;/p&gt;&lt;p&gt;Two of my key measures are the number of monthly active users, and (of course) the Slack’s Net Promoter Score. NPS measures how much people like the Slack, and thus far I have been sampling new members. With 3 months of data, I can identify real trends. And they aren’t great. Membership is basically flat. NPS is falling. It dropped in January, held steady in February, and dropped again in March. It now stands at 35. There is a bright spot: I&apos;ve started asking people how they joined, and the people who joined through slack.hackclub.com give the Slack an NPS of 50. So to everyone who contributed to the Slack site, and everyone who is staffing #welcome-to-hack-club: thank you. Your work matters.&lt;/p&gt;&lt;p&gt;Overall, I don’t think I’m making NPS worse. Overall, I think NPS is getting worse for other reasons, and my efforts have simply failed to make enough of a difference.&lt;/p&gt;&lt;p&gt;This isn’t a lament. It’s a reflection. At HQ we have clear guidance to try things, expecting to fail, and keep trying until we find what works. It’s a refreshing contrast with some of my previous employers, who were so risk-averse that I was explicitly forbidden from solving problems. It’s also the Hacker Mindset that we are always trying to get you to embrace: so what if you’re not sure you can make a game? Try anyway. Accept the risk of failure as necessary for the chance of success.&lt;/p&gt;&lt;p&gt;My ideas haven’t worked, so I need to try new ones.&lt;/p&gt;&lt;p&gt;That’s why this is a Slacker News post for all of you, and not just a note to myself. I&apos;m going to try new things, and you will be affected. Most of them will fail. Some will fail in ways you warned me would happen. I&apos;m sorry in advance, but for the first 3 months I tried to cause no damage whatsoever, and as a side effect I caused almost nothing at all.&lt;/p&gt;&lt;p&gt;On the other hand, I’ll be looking for help to make these changes, so if you’re looking to get more involved, this is your moment.&lt;/p&gt;&lt;p&gt;In the universe of possible NPS scores, 35 is pretty good. But for a Hack Club project, this is quite low. YSWSes and Hackathons tend to get an NPS of 60-80. I’m not running a tax website, I’m running a community of awesome people with extraordinary talent. I know that a better version of this Slack exists, and it is worth taking risks to find it.&lt;/p&gt;&lt;p&gt;The Slack is special, which makes it frightening to experiment on it–for me as well as for you. But it is precisely because the Slack is special that it deserves to be made as good as we can make it.&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>Hack Club Introduces Mole</title><link>https://news.hackclub.com/introducing-mole/</link><guid isPermaLink="true">https://news.hackclub.com/introducing-mole/</guid><description>If you strip away all the programs, the Slack, the memes, and the code, Hack Club has always been about one thing: Making sure that the youth of today have the tools and knowledge to build on the frontier of what&apos;s possible.</description><pubDate>Wed, 01 Apr 2026 10:57:00 GMT</pubDate><content:encoded>&lt;p&gt;If you strip away all the programs, the Slack, the memes, and the code, Hack Club has always been about one thing: Making sure that the youth of today have the tools and knowledge to build on the frontier of what&apos;s possible.&lt;/p&gt;&lt;p&gt;For years, that frontier was programming - suddenly, anyone, from a kid in San Francisco to a mother in Japan, could build the next billion-dollar startup from their house with just a laptop, an internet connection, and some free time. The computers allowed anyone to express themselves freely, interact with people from all over the world, and build real things with just words, symbols, and numbers. Hack Club was built for this world, to ensure that our future leaders deeply understood these systems, and knew how to hack on them to propel us all forward.&lt;/p&gt;&lt;p&gt;But in the past few years, the frontier has been gradually shifting. The one-person startup can now rival teams of hundreds. Programming has become less about the code and more about what the code does. Knowing how to code isn&apos;t as important as it was 10 years ago. That craft is being replaced by things like marketing, ideation, and management.&lt;/p&gt;&lt;p&gt;Hack Club is trying to prepare you for a world that is disappearing.&lt;/p&gt;&lt;p&gt;So we lie at a crossroads - either stick with what we know works well, keep pulling weighted projects, and pretend like nothing is changing, or press ahead into the unknown.&lt;/p&gt;&lt;p&gt;Hack Club is doing better than ever. We’re improving the lives of countless students across the globe, thousands of amazing projects have been shipped via our programs, and our Slack is more vibrant and active than it&apos;s ever been. Sticking with the status quo is tempting.&lt;/p&gt;&lt;p&gt;But what does that buy us? A local maximum. And while we sit happily on our little pile of ships and LOCs, we&apos;ll watch the frontier slowly drift away, further away from the programming languages of 2024 and towards craft and soul, and always wonder what we&apos;re missing out on. And the teens we pledged to serve would be left behind, dropped into a world that they don&apos;t understand.&lt;/p&gt;&lt;p&gt;Over the past few weeks, we&apos;ve been having meetings with our donor network. After sharing metrics on AI use in Hack Clubber projects, all were worried, and we&apos;re inclined to agree. If the frontier, the cutting edge, changes, we need to push Hack Clubbers towards it, even if that means making drastic changes to the programs and systems that have worked so well for so long.&lt;/p&gt;&lt;p&gt;We&apos;re choosing to press ahead.&lt;/p&gt;&lt;p&gt;We&apos;re evolving Hack Club for the new frontier of AI, embracing new kinds of software like agents and assistants and exploring the immense potential of this technology. You&apos;ll see many changes - some subtle, some not so much - as we work to redefine our organization for this new landscape.&lt;/p&gt;&lt;p&gt;We know this decision might be unpopular, and we understand, but we want to be clear: AI is not going away, and we&apos;d much rather foster knowledge and curiosity about this new tech rather than pretend it will.&lt;/p&gt;&lt;p&gt;This is uncharted territory, so we&apos;re going to make some mistakes. Some of our experiments might end up being great, others may end up horrible. Just like when Hack Club was founded all those years ago, we&apos;re venturing out into the unknown fog once again. Please bear with us - and help out if you can! - as we figure out what works and what doesn&apos;t.&lt;/p&gt;&lt;p&gt;We invite you, dear hacker, to follow along, and join us as we explore - and build - this new frontier.&lt;/p&gt;&lt;p&gt;With love and gratitude, Hack Club HQ&lt;/p&gt;&lt;p&gt;(P.S. We&apos;re starting with the community. We believe AI tools are a great fit here, due to the conversational capabilities of LLMs and their impartiality. You may have already noticed our powerful new automated moderation tools at work in the Slack. We&apos;re also working on an exciting experiment we&apos;re calling Mole - a new kind of community member. They should drop in early access later today - see you then.)&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>More Power to Prometheus</title><link>https://news.hackclub.com/prometheus-mole/</link><guid isPermaLink="true">https://news.hackclub.com/prometheus-mole/</guid><description>One of the complex challenges of any large community is the signal-to-noise ratio. As Hack Club has grown, so too has the complexity of maintaining a space that is productive, welcoming, and above all else, positive! Public channels are the town squares of our Slack, and like any town square, they require stewardship and delicate care. After months of careful deliberation, deep reflection on the nature of community, and several very long meetings, we are proud to announce a significant evolution in how we approach that stewardship: a global automod rollout for @Prometheus!</description><pubDate>Wed, 01 Apr 2026 10:57:00 GMT</pubDate><content:encoded>&lt;p&gt;One of the complex challenges of any large community is the signal-to-noise ratio. As Hack Club has grown, so too has the complexity of maintaining a space that is productive, welcoming, and above all else, positive! Public channels are the town squares of our Slack, and like any town square, they require stewardship and delicate care. After months of careful deliberation, deep reflection on the nature of community, and several very long meetings, we are proud to announce a significant evolution in how we approach that stewardship: a global automod rollout for @Prometheus!&lt;/p&gt;&lt;p&gt;The philosopher John Rawls once argued that a just society requires institutions that protect its members from harm, even harm they don&apos;t yet know they&apos;re experiencing. We took that to heart. We&apos;ve noticed low-quality posts, off-topic tangents, and certain recurring conversational patterns quietly eroding the quality of our shared spaces, so we&apos;re taking proactive steps rather than reacting. Waiting for harm to occur and cause a #meta thread before addressing it has proven to be ineffective before, so we are trying something new.&lt;/p&gt;&lt;p&gt;@Prometheus will be present in most public channels, watching over public spaces and keeping them pro Hack Club. Think of it less as surveillance and more as ambient guidance, a gentle, ever-present hand on the shoulder of conversations to help keep it productive and forward the organization.&lt;/p&gt;&lt;p&gt;Powered by our new in-house AI, Mole, Prometheus now supports extensive pattern analysis across message data (fully anonymized, I think), to identify phrases that have historically been used to derail productive conversations, introduce unnecessary friction, or generally bring vibes down. These terms have been added to the automod, and we will continue expanding this list as the community evolves and as we learn more about the specific linguistic patterns that threaten positivity. Prometheus will now automatically log these terms, but don&apos;t worry, it won&apos;t be intrusive. Most of the time, just knowing it&apos;s watching will be enough.&lt;/p&gt;&lt;p&gt;We believe this change reflects a mature, considered approach to community governance. We hope you welcome this change as we work to make your Slack experience better, more positive, and more aligned with our mission. We also warmly ask that you invite @Prometheus to your private channels as well, so we can extend this culture of proactive positivity into every corner of the community. The more ground we can cover, the better we can serve you.&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>The Tragedy of the Anticommons on the Slack</title><link>https://news.hackclub.com/tragedy-anticommons/</link><guid isPermaLink="true">https://news.hackclub.com/tragedy-anticommons/</guid><description>I got Shrouded once. For privacy, I’ll keep the details vague. In short, I was discussing a Hack Club project, and my message got reported as advertising. I deleted my message and moved on, but it was surprising. I want to respect the intent of each channel. But…what is the intent of each channel? Who is doing the intending? And, if a channel needs to change, who gets to say so?</description><pubDate>Mon, 30 Mar 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;I got Shrouded once. For privacy, I’ll keep the details vague. In short, I was discussing a Hack Club project, and my message got reported as advertising. I deleted my message and moved on, but it was surprising. I want to respect the intent of each channel. But…what is the intent of each channel? Who is doing the intending? And, if a channel needs to change, who gets to say so?&lt;/p&gt;&lt;p&gt;This is on my mind again because people have asked me to hold more debates, and I’m shopping for a venue. I’ve been using my personal channel, #eps-conduit. But the debates have the potential to bring a lot of life to wherever they are held, and I’ve written before about personal channels draining the life from public channels, so I have mixed feelings about keeping them in my own channel. But if not there, where else do I put them?&lt;/p&gt;&lt;p&gt;I don’t want to create a new channel for them. The Slack already has too many channels. It’s a big community, but even with 4500 monthly active users, I feel like we’re huddled around a trash barrel fire in the ruins of some enormous city. But I am reluctant to use any existing channel other than mine because I don’t want to step on anyone’s toes.&lt;/p&gt;&lt;p&gt;But that’s the problem: sometimes channels have so many stakeholders that in effect, nobody has the right to speak for the channel, or change the channel, even if change is needed.&lt;/p&gt;&lt;p&gt;When @Rowan introduced Prometheus, he talked about The Tragedy of the Commons. This applies to some channels. But others are subject to what Michael Heller called The Tragedy of the Anticommons, where competing claims of ownership make it so no one has a clear right of action.&lt;/p&gt;&lt;p&gt;The difference is this: in the Tragedy of the Commons, nobody fixes a problem because they all think it’s someone else’s responsibility to fix it. In the Tragedy of the Anticommons, nobody fixes a problem because they’re all scared that it’s somebody else’s right to fix it.&lt;/p&gt;&lt;p&gt;I ran into a similar problem with #confessions, where the community was divided 50/50 on how the channel should operate, so that any arrangement would leave half the users feeling dispossessed. The jury is still out on how those changes are working in terms of channel quality, but in terms of my public relations skills, it was a clear failure; in hindsight I should have talked to more people first.&lt;/p&gt;&lt;p&gt;With that lesson in mind, I saw an opportunity to solve the Tragedy of the Anticommons in #ysws. Thoughtful commenters raised the problem that the channel was getting spammy, but there was a clear divide. This time, I advised the community to poll the channel first, which revealed a clear preference towards keeping ads but limiting their frequency. Four community members stepped up to be channel owners: @anson chung, @cookie with coffee, @rohan, and @sahil. They have come up with a system to balance the interests of advertisers and audience.&lt;/p&gt;&lt;p&gt;I’m very happy with this outcome. It tells me that with proper planning, we can tackle the Tragedy of the Anticommons (and the Tragedy of the Commons).&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>New Slack Census</title><link>https://news.hackclub.com/slack-survey/</link><guid isPermaLink="true">https://news.hackclub.com/slack-survey/</guid><description>Next week, the Slack will conduct the first survey for highly active users. The Census will run monthly, and feature a mix of recurring questions and one-off investigations. The Census is going to a random sample of the most active users to avoid survey fatigue in the future. This time, that means anyone who was active for at least 20 out of the past 30 days at time of sample. Subjects will receive a DM from @Hack Club Census. Prizes will be given.</description><pubDate>Thu, 26 Mar 2026 10:57:00 GMT</pubDate><content:encoded>&lt;p&gt;Next week, the Slack will conduct the first survey for highly active users. The Census will run monthly, and feature a mix of recurring questions and one-off investigations.&lt;/p&gt;&lt;p&gt;The Census is going to a random sample of the most active users to avoid survey fatigue in the future. This time, that means anyone who was active for at least 20 out of the past 30 days at time of sample. Subjects will receive a DM from @Hack Club Census.&lt;/p&gt;&lt;p&gt;This year we&apos;ve conducted a monthly survey of newly-joined Slack users covering their NPS and written feedback on the Slack. New users naturally differ from the most active users, so surveying a distinct population will reveal different information. New users&apos; experience is helpful to understand the Slack&apos;s retention rate, which is a decisive factor in what happens to the Slack.&lt;/p&gt;&lt;p&gt;The questions on the census are as follows:&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>Against Moderation Transparency</title><link>https://news.hackclub.com/against-moderation-transparency/</link><guid isPermaLink="true">https://news.hackclub.com/against-moderation-transparency/</guid><description>Moderation transparency was introduced to me as a conflict between the Fire Department and everyone else. But I’ve finally realized that this is really a conflict between the community and itself. The FD is simply caught in the middle.</description><pubDate>Thu, 26 Mar 2026 10:57:00 GMT</pubDate><content:encoded>&lt;p&gt;Moderation transparency was introduced to me as a conflict between the Fire Department and everyone else. But I’ve finally realized that this is really a conflict between the community and itself. The FD is simply caught in the middle.&lt;/p&gt;&lt;p&gt;I try to maintain your good will: avoid things that are unpopular, do things that are popular. Increasing moderation transparency is thus very tempting for me: it would be instantly popular. But I find myself stuck on the unpopular side because my conscience won’t let me take the popular side. What I want to argue to you today is that moderation transparency is actually unethical.&lt;/p&gt;&lt;p&gt;Public Shaming&lt;/p&gt;&lt;p&gt;I’ve seen enough community logs that when I click the button to make one, I know I&apos;m making an open invitation to gossip, ridicule, and pass judgement on whomever the log is about. Every time I click that button I have an acute sense that I am harming one of the teenagers I’m supposed to protect.&lt;/p&gt;&lt;p&gt;I have seen some heartbreaking bans. People who cared about Hack Club, acted as public examples of what a good Hack Clubber should do, and did very bad things that made it impossible to trust them in the community anymore. This is the thing, people are complicated, both can be true at once. They did not deserve the added humiliation of having their worst decisions made public–and made into their legacy, because of course people remember how you leave. Or, if you come back, everyone knows what you did. It’s the digital equivalent of a room going silent when you walk in.&lt;/p&gt;&lt;p&gt;Hack Clubbers are normally very good about privacy, so it’s jarring to see your privacy so devalued here. But separately, public shaming is inimical to the mission of helping people grow and learn from their mistakes.&lt;/p&gt;&lt;p&gt;Research indicates that shame and guilt are different emotions with different effects. Guilt is focused on a specific act and tends to cause growth and change. Shame targets a person’s whole self, is marked by a feeling of being exposed in front of a real or imagined audience, and tends to cause hostility and shifting blame to others.&lt;/p&gt;&lt;p&gt;To learn from a mistake, you have to accept you made one. The harsher the criticism, the harder it is to accept. “You are a good person, but you showed bad judgement” is a line people will digest. Slowly, grudgingly, but they will. “You are a bad person which is why you did a bad thing” is much harder. Public humiliation puts people on the defensive by making them feel like they are being judged to be a bad person. Doubly so if they know the community is saying so outright. This encourages people to blame everyone else instead of looking within.&lt;/p&gt;&lt;p&gt;What Happens on Slack does not Stay on Slack&lt;/p&gt;&lt;p&gt;Separate from causing public humiliation within Hack Club, moderation transparency also risks lasting harm that follows banned users beyond Hack Club.&lt;/p&gt;&lt;p&gt;Things circulate on discord servers and signal groups. I know of two different cases of things being aired on other websites, and in one of those, people had their Slack messages screenshotted without permission.&lt;/p&gt;&lt;p&gt;I’m also going to tell you that people talk. Before Hack Club, I worked in a different community of teenagers: high school debate. In that world, rumors regularly reached me about people from other schools, sometimes people I had never met. If someone gets banned for something like fraud or unwelcome advances, that is the kind of thing that could follow them and hurt them later in life. People deserve to leave their teenage mistakes behind, including serious ones.&lt;/p&gt;&lt;p&gt;Transparency Hurts the Victims of Misconduct&lt;/p&gt;&lt;p&gt;We had a case where a Hack Clubber was being harassed. We banned the harasser, who kept making alt accounts to harass them more. This was logged. Most people were horrified by the harassment, which is good, but a few were entertained and decided to make alt accounts of their own, harassing the same victim while posing as the original harasser. That was transparency in action.&lt;/p&gt;&lt;p&gt;In another case, there was a community log with the offender and the reason. From this, people immediately deduced who reported the offender, effectively breaking the anonymity that Shroud reports are supposed to have. Again: this is bad.&lt;/p&gt;&lt;p&gt;Most Hack Clubbers would never try to do this. You, dear reader, wouldn’t ~~steal a car~~ do this. But it only takes one.&lt;/p&gt;&lt;p&gt;II. Common Defenses of Moderation Transparency&lt;/p&gt;&lt;p&gt;Does Transparency Prevent Abuse?&lt;/p&gt;&lt;p&gt;I have heard that transparency ensures the FD does not play favorites and abuse their powers.&lt;/p&gt;&lt;p&gt;This argument fails because you do not know whether the FD is abusing their power unless you know the full details of the case. What looks like bias may just be the result of taking confidential information into account.&lt;/p&gt;&lt;p&gt;I have seen several cases where someone’s penalty was condemned as too harsh, but the critics were unaware of the full scope of wrongdoing. But giving everyone that level of insight is not transparency, it is a surveillance state. Transparency and Privacy are always in tension, and here is an instance where ignoring that tension in pursuit of transparency leads to the trampling of privacy.&lt;/p&gt;&lt;p&gt;Does Transparency Reduce Speculation?&lt;/p&gt;&lt;p&gt;This is the main argument I hear: if people don’t know, they will speculate. The truth is just the opposite: transparency causes speculation. Without community logs, people speculated about whether someone was banned. Then the log was added, and people speculated about why they were banned. Then the FD started saying which rule was broken, and now people speculate about what was done to break the rule.&lt;/p&gt;&lt;p&gt;`` 10 Gossip 20 Call for transparency to stop gossip 30 Get transparency 40 GOTO 10 ``&lt;/p&gt;&lt;p&gt;This argument is chasing a mirage. The imagined future in which transparency prevents speculation will never come. By publicly announcing punishments, #community-logs helps ensure that the gossip mill is as big as possible, and by giving reasons for punishments, it ensures that speculators have more material with which to speculate.&lt;/p&gt;&lt;p&gt;This isn&apos;t working. Right now we have gossip, abuse, and mistrust of moderation. The worst of everything.&lt;/p&gt;&lt;p&gt;Transparency causes speculation. I understand there are exceptions (as with a recent YSWS), but moderators make exceptions for exceptional cases. Transparency is defensible as a tool, not as a rule.&lt;/p&gt;&lt;p&gt;Should the FD disclose when the subject requests it?&lt;/p&gt;&lt;p&gt;This is the most reasonable case-by-case transparency proposal that I’ve seen. I don’t balk at it the way I do at more aggressive proposals. But I still don’t like it.&lt;/p&gt;&lt;p&gt;I think the underlying problem is that the Slack loves gossip. This is pretty common in teenage spaces (but not inevitable!). I think that what will actually happen is anyone who declines to share will be criticized for not sharing. All the heat that the FD gets will go to them instead. “If you have nothing to hide, you have nothing to fear”, people will say.&lt;/p&gt;&lt;p&gt;The community has opinions about how bad different rule violations are. People whose violations would be easily forgiven will ask for disclosure. People whose violations would hurt their reputation will not ask for disclosure. So everyone who doesn’t ask for disclosure will be presumed guilty of something really bad.&lt;/p&gt;&lt;p&gt;There is a better world that this, where everyone who is penalized has face-saving plausible deniability about what happened, and where the community just agrees to say:&lt;/p&gt;&lt;p&gt;III. Actually, I am Not the Only One Who Can Prevent Forest Fires&lt;/p&gt;&lt;p&gt;In these discussions, I’m always struck by the way that gossip is spoken of like an unstoppable law of nature. It isn’t. It’s a personal choice.&lt;/p&gt;&lt;p&gt;In dry leaves, fire catches and spreads. In wet leaves, it doesn’t.&lt;/p&gt;&lt;p&gt;Not gossiping is extremely easy; you just do nothing. If you want to make an effort, you could respond to gossip and speculation that reaches you with, &quot;If it were me, I would hate having everyone talking about me like this.” And it doesn’t have to be every Hack Clubber doing this. It just takes enough to make the ground damp. People’s lives would get meaningfully better. You could start doing it today.&lt;/p&gt;&lt;p&gt;So will you? And if not, why not?&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>Debate to be Held on Moderation Transparency</title><link>https://news.hackclub.com/transparency-debate/</link><guid isPermaLink="true">https://news.hackclub.com/transparency-debate/</guid><description>There will be a debate on Sunday, March 22 at 10:15 AM EDT, in #eps-conduit, on the subject of moderation transparency in the Slack.</description><pubDate>Wed, 18 Mar 2026 10:51:00 GMT</pubDate><content:encoded>&lt;p&gt;There will be a debate on Sunday, March 22 at 10:15 AM EDT, in #eps-conduit, on the subject of moderation transparency in the Slack.&lt;/p&gt;&lt;p&gt;Right now, when a user is banned or shushed, or when a thread is locked or deleted, it appears in #community-logs. In the case of a permanent ban, the Fire Department provides a basic reason why, specifying which part of the Code of Conduct was violated.&lt;/p&gt;&lt;p&gt;This system is a periodic source of controversy, and attracts calls for change in opposite directions. Some have argued that reasons should be given for all penalties, or that the Fire Department should share details of cases. Others (including me) have argued that #community-logs should be discontinued, or made read-only. Users have attempted to create crowdsourced alternatives that provide more information than #community-logs.&lt;/p&gt;&lt;p&gt;The time is right to make progress on this disagreement. HQ is developing a new conduct reporting system that spans all departments within Hack Club, and inevitably, decisions will have to be made about how much of that information is public.&lt;/p&gt;&lt;p&gt;The debate will feature @cyao, @krish, and @acon arguing in favor of greater transparency; and @eps, @Tanuki, and @Scooter Y arguing against. There will be time set aside for audience questions.&lt;/p&gt;&lt;p&gt;CALL FOR SUBMISSIONS: Slacker News publishes community members. I welcome your submissions on this and other topics. I have kept my opinions out of this piece to be consistent with the requirements for a news article, but I will publish an opinion piece after the debate.&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>Slack Users Can Now Set Their Own Manager</title><link>https://news.hackclub.com/set-your-own-manager/</link><guid isPermaLink="true">https://news.hackclub.com/set-your-own-manager/</guid><description>If only you could do this in real life, too.</description><pubDate>Thu, 12 Mar 2026 16:09:39 GMT</pubDate><content:encoded>&lt;p&gt;If only you could do this in real life, too.&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>Confessions Splits into Two Channels</title><link>https://news.hackclub.com/confessions-new-owners/</link><guid isPermaLink="true">https://news.hackclub.com/confessions-new-owners/</guid><description>#confessions began as a place for Hack Clubbers to say genuinely difficult things that they need to get off their chest. This purpose is still written into the confession guidelines, but over the years the channel has drifted to include jokes and personal opinions. A new channel, #self, has been created as a space for less serious discussions. Users who make unserious posts in #confessions will be redirected to #self.</description><pubDate>Thu, 12 Mar 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;#confessions began as a place for Hack Clubbers to say genuinely difficult things that they need to get off their chest. This purpose is still written into the confession guidelines, but over the years the channel has drifted to include jokes and personal opinions. A new channel, #self, has been created as a space for less serious discussions. Users who make unserious posts in #confessions will be redirected to #self.&lt;/p&gt;&lt;p&gt;The channel owners explained it like so:&lt;/p&gt;&lt;p&gt;“We love yapping :yay:! But that’s burying what is making this channel special. That’s why #self is becoming the new home for all of your public confessions! stay in #confessions if: it’s something that you would never send somewhere else, something you need to get off your chest. move to #self if: it’s a hot take, an email you received today or if you like ice cream.&lt;/p&gt;&lt;p&gt;#confessions is becoming the first use of the new Channel Owners feature in Prometheus. The channel owners, @alice, @hna, and @an actual, living deer can now use channel pings and channel bans, delete messages and threads, and set ephemeral messages in #confessions. All three are members of the Confessions Review Team.&lt;/p&gt;&lt;p&gt;The Confessions Review Team will continue screening private confessions and #meta posts made via Prox2.&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>New Slack Readme Helps New Users</title><link>https://news.hackclub.com/slack-readme/</link><guid isPermaLink="true">https://news.hackclub.com/slack-readme/</guid><description>Hack Club is a massive org. And yet, there are no guides for newcomers to read. They&apos;re plopped in the Slack and left to fend for themselves. Hex-4 also had this frustration and started Readme (a guide to Hack Club) but left it unfinished. In early February, I asked about creating a guide to Hack Club where I was told about the existence of Readme. Seeing it unfinished, I decided to pick up where Hex-4 left off. Writing Readme turned into a bit of a rabbit hole. I asked a lot of questions in #hq and #community and did a lot of Googling. The page about Hack Club mascots and lore was even harder to write with the lore being scattered and all. I wasn&apos;t sure where to start reading. That part is being handed off to future-me. Readme lays out Hack Club like a book. It covers topics like how to make threads in Slack, what YSWS programs are, the 2 lovebirds that are Orpheus and Heidi and generally points the reader in the right direction to provide a smoother introduction into Hack Club.</description><pubDate>Tue, 10 Mar 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;Hack Club is a massive org. And yet, there are no guides for newcomers to read. They&apos;re plopped in the Slack and left to fend for themselves. Hex-4 also had this frustration and started Readme (a guide to Hack Club) but left it unfinished. In early February, I asked about creating a guide to Hack Club where I was told about the existence of Readme. Seeing it unfinished, I decided to pick up where Hex-4 left off. Writing Readme turned into a bit of a rabbit hole. I asked a lot of questions in #hq and #community and did a lot of Googling. The page about Hack Club mascots and lore was even harder to write with the lore being scattered and all. I wasn&apos;t sure where to start reading. That part is being handed off to future-me. Readme lays out Hack Club like a book. It covers topics like how to make threads in Slack, what YSWS programs are, the 2 lovebirds that are Orpheus and Heidi and generally points the reader in the right direction to provide a smoother introduction into Hack Club.&lt;/p&gt;&lt;p&gt;You can read it here.&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>Three Futures for this Slack</title><link>https://news.hackclub.com/three-futures-slack/</link><guid isPermaLink="true">https://news.hackclub.com/three-futures-slack/</guid><description>I’ve been changing the Slack, and more changes are coming, so it’s time I explained my agenda.</description><pubDate>Mon, 09 Mar 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;I’ve been changing the Slack, and more changes are coming, so it’s time I explained my agenda.&lt;/p&gt;&lt;p&gt;When a system not in state X tends to enter state X, and a system in state X tends to remain in state X, then X is an attractor state. If you drop a marble in a bowl, sitting at the bottom is an attractor state.&lt;/p&gt;&lt;p&gt;In my very first Slack message, I said communities have three attractor states: apathy, conflict, and co-operation. Today I want to expand on that, exploring each of these states and why they dominate the possible futures of the Slack.&lt;/p&gt;&lt;p&gt;First Future: the Gated Community&lt;/p&gt;&lt;p&gt;In this possible future, teenagers build cool things and make really close friendships. They do this in private channels, and you’re not invited.&lt;/p&gt;&lt;p&gt;Gated Communities become Ghost Towns&lt;/p&gt;&lt;p&gt;The Slack has built-in attrition as people age out of Hack Club. So the size of the community follows a simple equation:&lt;/p&gt;&lt;p&gt;size = current members + (new members * retention) - attrition&lt;/p&gt;&lt;p&gt;For any given rate of new users joining, there is a critical retention rate. Above this rate, the community will grow. Below this rate, the community will die.&lt;/p&gt;&lt;p&gt;Private channels are like laws against building new housing: they favor incumbents at the expense of newcomers.&lt;/p&gt;&lt;p&gt;On a practical level, here’s what this looks like: a newcomer joins the Slack, asking technical questions. No one answers her because the people who know the answers spend all their time in private channels. A newcomer joins with no friends, and never makes new ones, because the conversations where people make friends all happen in private channels. They both conclude the Slack is a ghost town, and stop checking it.&lt;/p&gt;&lt;p&gt;Zach has run online communities before Hack Club. He told me that if an online community defines itself by who is not a part of it, the community inevitably dies. I think his experience supports the theory I’ve laid out.&lt;/p&gt;&lt;p&gt;Ghost Towns are an Attractor State&lt;/p&gt;&lt;p&gt;The Slack grows in part by word of mouth. As the community shrinks, so does the influx of new members. As the community grows, so does the influx of new members.&lt;/p&gt;&lt;p&gt;This means staying the same size is an unstable state, like a ball on a windy hilltop. Small perturbations will become strong trends. The attractor states are death and growth. More on growth later.&lt;/p&gt;&lt;p&gt;Private channels do not necessarily have this effect. It depends on whether private channels merely add something new to the Slack, or whether they also take life and take energy from public channels. In other words, there’s a difference between using private channels and retreating to private channels. A retreat to private channels is a perturbation towards death.&lt;/p&gt;&lt;p&gt;The Slack is not a gated community right now. Many people have noted that the cool conversations that used to happen in public now often happen in private channels. But there are still good things happening in public channels. The question is whether the balance will keep shifting towards private channels.&lt;/p&gt;&lt;p&gt;Second Future: Drama Club&lt;/p&gt;&lt;p&gt;In this possible future, people come to the Slack for conflict: who is the bad guy in a dispute between friends? Who is the bad guy in a dispute between HQ and users? Who is to blame when something goes wrong? What is the worst, most damning, juiciest rumor about everyone you know?&lt;/p&gt;&lt;p&gt;Channels like #meta and #community-logs are a window onto this future. They have their good moments too, but if I changed the channel descriptions to capture the typical post in each channel, #meta would be “A place for complaining about Hack Club without proposing solutions”, and #community-logs would be “A place to spread rumors and make fun of people”.&lt;/p&gt;&lt;p&gt;Drama Club is an Attractor State&lt;/p&gt;&lt;p&gt;Drama begets drama. People get mad at each other, causing them to do bad things, which people then get mad about. For HQ and the FD, drama leads to misconduct, which leads to more enforcement, which leads to more drama. Also, people love drama. Can you imagine a reality TV show where all of the characters handled their problems with respectful discussion?&lt;/p&gt;&lt;p&gt;Drama also creates rival factions. Some drama happens, and forevermore, everyone involved remembers who was on which side of The Hairdryer Incident.&lt;/p&gt;&lt;p&gt;Rival factions are destructive to the systems they inhabit. When people identify with their own faction rather than the system as whole, their perceived self-interest is to serve their faction at the expense of the system. It becomes rational to make the system 100 points worse as long as your faction comes out 10 points ahead.&lt;/p&gt;&lt;p&gt;This dynamic is self-reinforcing: if a rival faction is on the path to destroying the system itself, then it is rational to destroy them, even if doing so takes you further down the same path of destruction. And they make the same calculation about you. This dynamic is currently destroying the American political system, and is a special case of a more general phenomenon called The Tragedy of the Commons.&lt;/p&gt;&lt;p&gt;Political systems are probably cursed to always have rival factions. But Hack Club does not have to be. Power is zero-sum, but hacking isn’t.&lt;/p&gt;&lt;p&gt;Drama Club is Bad&lt;/p&gt;&lt;p&gt;Drama Club is defined by conflict. Conflict is a healthy part of a community, but a community defined by conflict can never be healthy, and any conflict–however moral the cause–is unhealthy when handled wrong.&lt;/p&gt;&lt;p&gt;If the Slack’s chief export is conflict, why bother having it? “Because conflict will improve Hack Club!” Maybe. Conflict can bring change, but it can just as easily prevent change. People often tell me privately that they have something new they want to try, but they are scared they will be dragged in #meta for trying it. We are already living in a world where conflict on the Slack is bleeding away creative potential. Like I said, conflict needs to be healthy, or else we get this.&lt;/p&gt;&lt;p&gt;The Gated Community is Bad&lt;/p&gt;&lt;p&gt;Invitation to the gated community is based on how technical you are, or how cool you are. If you’re already technical, or cool, congratulations. But what if you’re a teenager who is just getting started on your technical journey? And what if you don’t fit into mainstream social dynamics?&lt;/p&gt;&lt;p&gt;I was an awkward nerd once. So were a lot of Hack Club staff. Some of us managed to find a home (for me it was the debate team) and some didn’t. But all of us want to create the place we deserved, whether or not we ever got it, because there are still teens out there who need it, deserve it, and aren’t getting it anywhere else.&lt;/p&gt;&lt;p&gt;Third Future: the Town Garden&lt;/p&gt;&lt;p&gt;So: the Slack can be defined by conflict, but doesn’t have to be. And the Slack can converge on death, or on growth. What would it look like for the Slack to converge towards growth without being defined by conflict?&lt;/p&gt;&lt;p&gt;Everyone who has been here a long time has told me about how great the Slack used to be. Here is a day in #lounge from 3 years ago:&lt;/p&gt;&lt;p&gt;This isn’t cherry-picked. I just chose the date, and this came up. I see two fun, wholesome technical conversations; one Hack Clubber helping another to solve a technical problem; and a someone questioning an HQ decision and walking away satisfied rather than bitter.&lt;/p&gt;&lt;p&gt;What would this third future look like? We can’t go back to the past, not really. But we can have some of what made that past so special. This can be a place to learn, a place to create, and a place to belong. It is possible. The Town Garden is a place where people welcome each other, help each other, work through their disagreements, and walk out as better hackers, better friends, and better people. This last point is, I think, a hugely neglected part of modern childhood–you are surrounded by conflicting advice about how to be successful, but there is far less guidance on how to be human.&lt;/p&gt;&lt;p&gt;Is the Town Garden an Attractor State?&lt;/p&gt;&lt;p&gt;I believe it can be. The Hacker Values largely boil down to “help others, and make every conflict productive”. If everyone adopted those–as values, not just as rules–then unproductive conflict wouldn’t just get punished by the fire department. It would be low-status. It would be cringe. Helping people, on the other hand, would be high-status.&lt;/p&gt;&lt;p&gt;You Decide&lt;/p&gt;&lt;p&gt;I’ve spelled out my guiding philosophy. I’m trying to make the Slack into the Town Garden. But I don’t actually know how to create it. Broadly, I think it involves people choosing freely to follow Hacker Values. I’ll be trying lots of experiments in pursuit of this goal, and I hope you’ll join me.&lt;/p&gt;&lt;p&gt;Ultimately, the future of the Slack is in your hands. You are the incumbents, and you have tremendous power in shaping the experience of newcomers. Every day, you can choose conflict, apathy, or co-operation. And the weight of your choices will accumulate into a future for the Slack. You decide which one.&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>Prometheus Brings Users More Powers to Improve Slack</title><link>https://news.hackclub.com/prometheus-distributed-care/</link><guid isPermaLink="true">https://news.hackclub.com/prometheus-distributed-care/</guid><description>Right now, most community channels on Slack are nobody&apos;s responsibility. The Fire Department holds them to a minimum standard, but there&apos;s no one to actually make them really good. Keen readers may notice that this is a great example of the Tragedy of the Commons, when everyone has access but no one has real ownership, and channels just become noise rather than meaningful discussion.</description><pubDate>Mon, 09 Mar 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;Right now, most community channels on Slack are nobody&apos;s responsibility. The Fire Department holds them to a minimum standard, but there&apos;s no one to actually make them really good. Keen readers may notice that this is a great example of the Tragedy of the Commons, when everyone has access but no one has real ownership, and channels just become noise rather than meaningful discussion.&lt;/p&gt;&lt;p&gt;So we&apos;re bringing back Prometheus, this time with official approval from Evan (@eps), who runs the Slack.&lt;/p&gt;&lt;p&gt;If you&apos;re new, here&apos;s some context. Prometheus was originally built as a tool to help people manage their personal channels by allowing them to delete messages from other users and bots. The problem was that it didn&apos;t include logs, and the sweeping power of deletion was a bit ahead of its time and lacked a real purpose.&lt;/p&gt;&lt;p&gt;A few months later, Evan reached out to bring this back! The primary focus is to give CRT more control over #confessions and the ability to moderate posts that haven&apos;t gone through Prox2. We&apos;ll expand this to other channels too!&lt;/p&gt;&lt;p&gt;So this isn&apos;t about turning everyone into a snitch or making a police state. It&apos;s about having people step up and say, &quot;I&apos;m going to make this channel great,&quot; and then giving them the tools to actually do it. We hope people can use Prometheus to shape the culture, keep things on track, and make their spaces genuinely useful rather than just noise.&lt;/p&gt;&lt;p&gt;What’s new?&lt;/p&gt;&lt;p&gt;The original bot could only delete messages, but this new version has a few new tricks up its sleeve!&lt;/p&gt;&lt;p&gt;Logging!&lt;/p&gt;&lt;p&gt;One of the major concerns was the lack of logs in Prometheus, which has since been fixed. Any action taken will be logged and only viewable by HQ staff and the Fire Department. For message deletions, the original message author and content will be logged. For thread deletions, a full transcript will be saved before deletion. Same with channel bans (more on that later!). This is to prevent abuse and help make sure Prometheus is only used to help improve the Slack rather than punish people for liking pineapple on pizza.&lt;/p&gt;&lt;p&gt;Delete Message &amp;amp; Destroy Thread&lt;/p&gt;&lt;p&gt;The OG feature, now with logs. Right-click any message -&amp;gt; Message Shortcuts -&amp;gt; Delete Message. Poof, gone. Need to go nuclear? Right-click -&amp;gt; Destroy Thread wipes an entire thread. A full transcript gets archived in a private place where only the FD + HQ staff can make sure everything is good before anything disappears, so nothing is truly gone, it&apos;s just... relocated.&lt;/p&gt;&lt;p&gt;Channel Bans&lt;/p&gt;&lt;p&gt;If you host a public channel, you can now enforce your own channel bans in case someone needs to take a chill pill for a bit. You can set a duration (1h, 2d, 1w... you get the idea) and a reason, so when someone asks &quot;why can&apos;t I post in #lounge,&quot; there&apos;s an actual answer. Use /pro channelban @user [##channel] [duration] reason to banish, and /pro channelunban @user [##channel] when they&apos;ve served their time.&lt;/p&gt;&lt;p&gt;Channel pings!!!&lt;/p&gt;&lt;p&gt;Moderators can also use @here and @channel pings with Prometheus /pro here and /pro channel . Use wisely, nobody likes being pinged 47 times a day (looking at some personal channels here)&lt;/p&gt;&lt;p&gt;Welcome!&lt;/p&gt;&lt;p&gt;When you join a channel, channel managers can now set a custom welcome message that greets you on arrival. It can either pop up just for you (ephemeral, only you see it) or slide into your DMs. Channel managers can set this up with /pro welcome set [ephemeral|dm] . Include helpful information, links to guides, channel rules, or a funny joke.&lt;/p&gt;&lt;p&gt;Manager&lt;/p&gt;&lt;p&gt;Yes, you can finally change the manager on your profile now! Run /pro manager to add someone to your profile. Groundbreaking, I know.&lt;/p&gt;&lt;p&gt;How do I use it?&lt;/p&gt;&lt;p&gt;Right now, you probably only have access to the manager command, and for this pilot test we&apos;re running with a whitelist. We plan to give people more access as we fix bugs and see how it works in the wild. For now, if you want to suggest any new features, report bugs, or contribute, the bot is fully open source at https://github.com/3kh0/prometheus. Me (Rowan) and Evan welcome any and all feedback, thoughts, and musings...&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>How to Get a Gap Year at Hack Club</title><link>https://news.hackclub.com/how-to-get-a-gap-year/</link><guid isPermaLink="true">https://news.hackclub.com/how-to-get-a-gap-year/</guid><description>Since the gap year applications opened, several people have asked &quot;How do I get one?&quot;. So I asked the gap years for their advice:</description><pubDate>Mon, 09 Mar 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;Since the gap year applications opened, several people have asked &quot;How do I get one?&quot;. So I asked the gap years for their advice:&lt;/p&gt;&lt;p&gt;Manitej and Tongyu have also written on this topic.&lt;/p&gt;&lt;p&gt;To this I will add my own observation: Hack Club hires two kinds of people.&lt;/p&gt;&lt;p&gt;The first type are people who built something impressive to Hack Club. This is both easier and harder than building something impressive to a school or employer. Easier, because Hack Club is very open-minded about what you build. But harder because it has to be something that matters to you. If your project is something you built because you wanted it to exist, that will work in your favor. If you built it to prove to Hack Club that you can code, that will work against you: why do you want to work at Hack Club? To change the world? Then why aren&apos;t you already trying to change it?&lt;/p&gt;&lt;p&gt;You can do this by making things that are useful to Hack Club. That&apos;s challenging though. If for example you want to make a tool to improve the Slack, I encourage it, but I don&apos;t have time to try out dozens of tools so that I can recommend the authors for a gap year. Your work would need to succeed without me, and come to my attention naturally through making the Slack noticeably better.&lt;/p&gt;&lt;p&gt;So that&apos;s hard. I think the easier way to impress Hack Club is simply to make what you want to see in the world.&lt;/p&gt;&lt;p&gt;The second type are people who get hired by showing the right mindset. I would put myself in this category. I&apos;ve met others too, who didn&apos;t really have any big technical accomplishments to show off. Instead of showing what we had done, we showed what we had the potential to do, given the resources. I&apos;ve said before that I got this job by going on a hike with @cwalker. Specifically, it was a multi-day hike which left lots of time to talk. And I talk a lot.&lt;/p&gt;&lt;p&gt;I talked about how we are forced to go to college by a job market that punishes you relentlessly if you don&apos;t. About how some people aren&apos;t a good fit for college, and we are failing those people. I talked about how to fix it. This became a debate. I argued my side passionately, and cited lots of evidence. I&apos;ve put a lot of energy into the subject because I sincerely care about it, and that comes through when I talk about it.&lt;/p&gt;&lt;p&gt;Basically, I showed that I have convictions, that my opinions are the product of careful thought, and that when something is important to me, I put a lot of energy into it. I think this was enough to get me to the interview stage. From there I was asked how I would solve various Hack Club problems. For instance, Zach asked me to redesign the Slack signup flow. He wasn&apos;t overly concerned with my specific solution; he wanted to see how I arrived at that solution. I paid attention to detail and thought about it really hard. You can do that too.&lt;/p&gt;&lt;p&gt;Hack Club is selective. But if you&apos;re afraid of rejection, then I&apos;ll give you one more piece of advice on how to get the fellowship: you have to let go of your fear of failure. At Hack Club, failure is expected. We are supposed to try many ideas, knowing that most of them will fail, until we finally hit on a great idea. Not by being a once-in-a-generation genius who magically knows the answer, but by being persistent enough to stumble over the answer. Anyone can do that.&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>Welcome to Slacker News</title><link>https://news.hackclub.com/welcome-to-slacker-news/</link><guid isPermaLink="true">https://news.hackclub.com/welcome-to-slacker-news/</guid><description>I have a lot to say on the Slack, but it often feels like I’m standing in an office building, shouting at the top of my lungs in the vain hope that I’ll be heard a hundred rooms away. I’m not the only one.</description><pubDate>Sun, 01 Mar 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;I have a lot to say on the Slack, but it often feels like I’m standing in an office building, shouting at the top of my lungs in the vain hope that I’ll be heard a hundred rooms away. I’m not the only one.&lt;/p&gt;&lt;p&gt;I see you all trying to have important conversations. But you face the same problem I do. People are in different rooms. Private channels, separate circles. People post in the wrong channel because they don’t know the right channel exists.&lt;/p&gt;&lt;p&gt;Under these conditions, real community is possible for individual channels, but impossible for the Slack as a whole.&lt;/p&gt;&lt;p&gt;Enter Slacker News. This is a place where you can publish news stories and opinion pieces. It is a way to get us all in one room, so we can finally stop shouting and be heard.&lt;/p&gt;&lt;p&gt;Submissions are not guaranteed to be published. Quality, tone, and significance all matter.&lt;/p&gt;&lt;p&gt;As I make changes to the Slack, I will announce them here.&lt;/p&gt;&lt;p&gt;Why We Need It&lt;/p&gt;&lt;p&gt;Slack is good at many things but productive public disagreement isn’t one of them; for that, the Slack is about as useful as a chocolate hammer. Threads move too fast for people to keep up. They get too long to reasonably be read (and too hard to scroll through) so people ignore each other. Things get derailed, or forgotten. Most harmfully, things are immediate, so people say things without stopping to reflect on them. How many times have people said something mean in a minute that they wouldn’t have said in an hour?&lt;/p&gt;&lt;p&gt;I also hope this will give the Slack a single shared informational baseline. #announcements and #happenings do good work–and have a commanding lead in fame–but they are inherently limited by being Slack channels. Slacker News is not a replacement for them. Its focus will be on going into greater detail, covering more subjects, and giving more voice to you.&lt;/p&gt;&lt;p&gt;So start drafting your submission!&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>Flavortown: Orrijjins</title><link>https://news.hackclub.com/essays/flavortown-orrijjins/</link><guid isPermaLink="true">https://news.hackclub.com/essays/flavortown-orrijjins/</guid><description>Orpheus watched with idle fascination as her second-favorite butterfly alighted upon the edge of the backyard birdbath, removed its wings, and squeegeed them off with a gentle, practiced motion.</description><pubDate>Wed, 14 Jan 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;Originally written to announce the beginning of Flavortown, our fourth &quot;Universal You-Ship-We-Ship&quot; program which began in the winter of 2025/2026.&lt;/p&gt;&lt;p&gt;Orpheus watched with idle fascination as her second-favorite butterfly alighted upon the edge of the backyard birdbath, removed its wings, and squeegeed them off with a gentle, practiced motion. It had been about seven full moons since she and Heidi first arrived upon Dummp—a name they had chosen to honor their beached vessel, Le Dumpstairè II—and the swashbuckling tomb-raiding ghost-tickling excitement of the first few months had since given way to a slower, more intentional phase of life. Sure, they still milked the occasional ghost when certain critical supplies ran low, but once Heidi realized that you can grow garbage straight from the ground if you have the right seeds… well, let’s just say that’s a pretty compelling argument for a raccoon to shift her focus to gardening. The tricky part was figuring out which part of each of her favorite things needed to be buried for it to grow and reproduce, a problem that kept her plenty occupied most days. She hadn’t yet managed to get the walkie-talkies to sprout, but her banana peel plants were coming along marvelously!&lt;/p&gt;&lt;p&gt;Heidi had just about finished raking the soil back over a pile of freshly-planted trout bones when a friendly-looking wigglebutt appeared from the west with an envelope in its mouth, which it dutifully dropped outside the front gate. “Telegram!” declared the wigglebutt as it waited patiently for a pat on the head from its neighbor, turning to wiggle its butt home to the Wigglebutt Woods once received. Heidi opened the envelope and began to read, squinting and mouthing each word as she silently sounded them out. Her pointy little claws tightened around the paper. Her eyes widened, and then bulged outward slightly from her skull. Her jaw went slack, then yo-yoed up and down, producing no noise at all until three syllables managed to clamor their way up from the back of her throat, escaping as an excited—nay, ecstatic—yelp: “OOORPHEUUUS!!!!”&lt;/p&gt;&lt;p&gt;Broken from her butterfly trance, Orpheus sprung to her hooves and cantored around from the back of the hut to find her best friend uncontrollably prancing in place. “Orpheus!! You’ll never guess who’s coming to visit!!!”&lt;/p&gt;&lt;p&gt;Orpheus stared blankly at Heidi, who seemed to be expecting something of her. Enough moments passed for it to feel a bit awkward. “…you’re supposed to guess” Heidi said, still clutching the telegram with two shaking paws.&lt;/p&gt;&lt;p&gt;“How can I guess if I’ll never guess who it is? You just told me that I’ll never guess.” Orpheus furrowed her brow in confusion. “Well, just try” said Heidi, with a tinge of annoyance. Orpheus thought for a moment.&lt;/p&gt;&lt;p&gt;“Is it… Pete Buttigieg?”&lt;/p&gt;&lt;p&gt;Heidi shook her head. “Guess again”&lt;/p&gt;&lt;p&gt;“…Oprah Winfrey?”&lt;/p&gt;&lt;p&gt;“No, it’s not Oprah”&lt;/p&gt;&lt;p&gt;“Bon Jovi?”&lt;/p&gt;&lt;p&gt;“I think he’s dead.”&lt;/p&gt;&lt;p&gt;“Beethoven?”&lt;/p&gt;&lt;p&gt;“Definitely dead. For at least twenty years.”&lt;/p&gt;&lt;p&gt;“Iron Man?”&lt;/p&gt;&lt;p&gt;“Fictional.”&lt;/p&gt;&lt;p&gt;“Method Man?”&lt;/p&gt;&lt;p&gt;“Also fictional. I think.”&lt;/p&gt;&lt;p&gt;“Florida Man?”&lt;/p&gt;&lt;p&gt;Heidi rolled her eyes, her exasperation starting to show. “That’s not even a specific individual, fictional or otherwise!!”&lt;/p&gt;&lt;p&gt;“Piano—” Heidi cut Orpheus off: “Piano Man is a song. We are not being visited by a Billy Joel song, exciting as that would be.” Orpheus began to open her mouth once more, only for it to be plugged back up by a dirty raccoon paw. “I’ll give you a hint: &apos;Man&apos; is not the second half of this person’s name.”&lt;/p&gt;&lt;p&gt;Orpheus thought for a long time. She had already said almost all of the names, at least all the ones that she knew of. She screwed her face up in concentration, awakened her auxiliary brain cell, trained it on the riddle at hand, and gave it one final shot.&lt;/p&gt;&lt;p&gt;“…Boxxy?”&lt;/p&gt;&lt;p&gt;The moment hung between them like wet clothes on a line. Heidi was speechless. Orpheus shifted uncomfortably, as she began to suspect that Boxxy was not the correct answer.&lt;/p&gt;&lt;p&gt;“It’s Alec Watson!” Heidi finally blurted out, the excitement now returning to her voice.&lt;/p&gt;&lt;p&gt;“Oh, cool! Who’s that?” Orpheus chirped, relieved that the guessing game was over. Heidi, however, was not similarly relieved by this response. “…how do you know who Boxxy is but not Alec Watson?” she asked incredulously. Orpheus got halfway through a shrug before being interrupted. “Nevermind. Don’t answer that. It’s the guy from Technology Connections! You know, the youtube channel?”&lt;/p&gt;&lt;p&gt;Orpheus thought for a moment, then brightened as an LED Christmas bulb flickered on in her head: “Oh, you mean Dishwasher Man?”&lt;/p&gt;&lt;p&gt;Tears welled up in Heidi’s eyes. “Yes, Orpheus. Thank goodness you have at least this much culture. Dishwasher Man is coming to visit our land… but before he arrives, you must understand that there is so much more to Dishwasher Man than just the dishwashers.” By this point Heidi’s eyes had acquired a far-away look, twinkling and glistening as she spoke from her outstretched gesticulating paws as much as her mouth.&lt;/p&gt;&lt;p&gt;“He’s got other appliances too, you know. Fridges. And air conditioners. And… and heat pumps!!” expounded the raccoon, chuckling as the imaginary Alec Watson that lived in her head insisted that these three objects were really the same, since each one is just a slightly different expression of the refrigeration cycle. “Stoves, electric kettles, freeze-driers, every conceivable variety of light fixture, even a whole collection of pinball machines that he keeps in his house!”&lt;/p&gt;&lt;p&gt;Orpheus had sat down and tuned out by this point. She watched as a gracefully-gliding sparrow swooped down, flipped on its left blinker, and banked toward the forest. Heidi continued her yap: “Legends say he has a whole warehouse near Chicago where he keeps all these wonderful things, and… and yet… and yet he has chosen to honor us with his presence! Here, on the Isles of Dummp, the sands that rose from ‘neath the waves of the mighty Sea of Glub, our home and non-native land!! We must ensure that he enjoys his visit!!!”&lt;/p&gt;&lt;p&gt;Heidi was picking up steam, which condensed behind her eyeballs and streaked down her soakified facefur as her eyes darted back and forth like a miniature poodle that’s eaten half a blister-pack of Sudafed: “Where will he sleep? What will he eat?! Oh my goodness, he’ll need to eat. He. Will need. To eat. But what will he eat? What do humans eat, Orpheus?! Food, I believe, but what kind?!? And how much?!?!? We’ll… we’ll have to make all kinds, just to be safe. And lots of it! A feast is what we need. A FEAST. ORPHEUS, DO YOU HEAR ME ON THE FEAST THING—”&lt;/p&gt;&lt;p&gt;Heidi was yelling by now. She dropped the telegram and grabbed her dinofriend’s cheeks, squoogling them together to make a ploomped-out dinolip soufflé. Her face was now uncomfortably close to Orpheus’s as tears and sweat dripped steadily from her whiskers onto the groundfallen paper that had triggered all this excitement. Orpheus, now very much tuned in to the manic raccoon before her, nodded to affirm her understanding of their impending Need 2 Feed. “Mwyis hecurmin?” she asked.&lt;/p&gt;&lt;p&gt;“…what?” replied Heidi, releasing her grip on the dinosaur’s cheeks.&lt;/p&gt;&lt;p&gt;“Why is he coming?”&lt;/p&gt;&lt;p&gt;“Who?” The disheveled raccoon looked as if she had just come out of a trance.&lt;/p&gt;&lt;p&gt;“Dishwasher Man. Alec. Why is he coming to Dummp?”&lt;/p&gt;&lt;p&gt;Heidi took a moment to process the question. She hadn’t actually finished reading the telegram, leaving her unsure of the answer. She looked down at the soggy, torn paper below her, only to realize that the letters were now all smeared and mostly illegible. She corrected her posture, looked back up to meet her friend’s gaze, and spoke with the kind of resolve that ye shall seldom hear but from a fangirl’t raccoon:&lt;/p&gt;&lt;p&gt;“Truth be told, I’m not sure. There are… so many things in this world I don’t know. So many things. But right now, in this very moment—the moment that we occupy currently—some may call it the present moment—there is one thing I know, something I know with unshakable, infallible certainty…”&lt;/p&gt;&lt;p&gt;Heidi drew in her breath and steadied her paws.&lt;/p&gt;&lt;p&gt;“Orpheus, we need to cook.”&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>The Summer of Making (Chapter Two)</title><link>https://news.hackclub.com/essays/som-chapter-two/</link><guid isPermaLink="true">https://news.hackclub.com/essays/som-chapter-two/</guid><description>Everyone knows a ghost is no match for a dinosaur in a fight.</description><pubDate>Mon, 11 Aug 2025 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;Originally written to announce the beginning of the Ballon Brigade, a week-long virtual hackathon within the The Summer Of Making (our third &quot;Universal You-Ship-We-Ship&quot; program).&lt;/p&gt;&lt;p&gt;THWAP! ← Oddly enough, that&apos;s the sound your average ghost makes when it slaps into the hard-packed dirt floor of an ancient tomb, taken to ground by the nigh-unstoppable force of a dino-hug. The wriggling wraith wrestled against Explorpheus Jones, but everyone knows a ghost is no match for a dinosaur in a fight. Heidi Croft leapt off a nearby rock, landed with a forward roll, cartwheeled into a handspring, and finished with a roundoff that dropped her squarely on top of their ghostly prey&apos;s wiggly tail, straddling it with her haunches to render it fully immobile. Knowing she had only a few moments to finish the job, she furiously tickled the squirming phantom&apos;s bum as if it were the armpit of a younger sibling. BLORP. For half a minute the ghost burped up a steady stream of supplies: deck screws, PLA filament, wood glue, two ipads, a load of dimensional lumber, six Korean War-era military surplus bedpans, and even a few semi-valuable pokémon cards in reasonably good condition. Turns out these bad boys are filled with all kinds of good stuff, you just gotta know how to milk &apos;em. Relieved of its contents, the ghost collapsed into the dirt for a good long nap.&lt;/p&gt;&lt;p&gt;Now, I know what you&apos;re thinking: stealing from a departed soul? That sounds unethical. But not all ghosts are created when a living creature dies without clicking “Eject” on their soul, as most of you learned in school; ghosts are merely a sort of interuniversal ectoplasmic energy bubble, and you may be surprised by the range of conditions that result in their birth. Any concentrated deposit of creative energy in one universe can bubble out into another and pinch off as a wibbly-wobbly spook that gobbles up whatever loot may be lying about. You wouldn’t believe how many get spawned here whenever a hackathon happens in your world! It’s not good for ghosts to eat this stuff though, it’s sort of like when a sea turtle ingests a plastic bag because it looks like a jellyfish if you squint really hard… or if your brain is the size of a grape. Lol, stupid turtles. Anyway. ghosts may be scavengers, but if they fill their bellies with junk for too long they can die, so our heroes are doing them a service okay?&lt;/p&gt;&lt;p&gt;Heidi Croft and Explorpheus Jones laid out their loot in rows on the dirt and took stock of their haul for the day, marveling at how much more fruitful tomb raiding was proving to be when compared to their usual dumpster dives. Heidi’s paws quivered with anticipation as she eyed a mound of cotton candy they had squeezed out of a big fat poltergeist way up on Level 2 of the tomb. Cotton candy was a personal favorite of hers, but it’s not a food that appears very often in the life of a rugged explorer. She licked her chops. Her nostrils flared. She gazed longingly at the tufts of delicious puffy sugar, just sitting over there, looking all supple and sumptuous, practically teasing her, quickly dissolving into the rising layer of water that was suddenly soaking her feet.&lt;/p&gt;&lt;p&gt;Wait, what?? Water?! Explorpheus looked urgently at Heidi. She was crestfallen, her face frozen in shock as she witnessed the rapidly-diminishing tufts of her sugary treat vanish like some sort of cruel trick played by a witch in a fable. The moral of that story? Don’t count your sweets before you eats. Heidi trembled with glistening eyes as tears gathered to soggle her whiskers. She was devastated. Explorpheus grabbed her shoulders and shook her out of her trance. “We need to get out of here, now.” Heidi looked around and felt her tummy drop into the rising waters as she realized that a daring escape would mean leaving all their goodies behind. This was a terrible day! Explorpheus—not so distracted by material things—leapt into action and hoisted the snoozing ghost over her shoulders like a Bulgarian peasant-farmer hauling a goat. Together they ran back up the tunnel toward the main chasm into which this tomb had been carved. They burst out of the entrance and looked up at the sky through the maze of bridges and caverns and doorways they had spent all day navigating to make it down here to the very bottom level, where only the juiciest phantoms retreat to.&lt;/p&gt;&lt;p&gt;Thinking quickly, Heidi Croft hatched a plan and retrieved a rope from her inventory. Blast! They hadn&apos;t brought the harnesses today, and there was no time to tie one swiss seat let alone two!! She&apos;d have to settle for a simple loop around both of their torsos—but what knot to close the loop with… a double-bowline with a Yosemite finish? Perfectly secure, but they&apos;d need to get free from the rope in a jiffy if they didn&apos;t want to visit the clouds. She needed a quick-release knot, but which one? A basic slipknot couldn&apos;t be trusted for this kind of load, and a halter hitch would be too hard to release under tension. Highwayman&apos;s hitch? Not for a safety-critical application. Heck, no quick-release knot could typically be recommended for human (or animal) loads. Siberian hitch… manger hitch… pile hitch… ring hitch… each of them had some of the properties needed, but none had all at once! Heidi&apos;s mind raced like a C++ application refactored for multithreading by an incompetent junior engineer. Just when it seemed that all hope was lost, the answer revealed itself to her tiny brain in a flash as if divinely inspired by the spirit of Clifford Ashley himself: the tumble hitch. It was so obvious, how could she not see it before?? But hang on, she needed a loop, and she&apos;d only ever seen the tumble hitch used in the context of a rigid anchor! Was there an accepted adaptation for securing the working end of a rope back to the standing end mid-line without any hardware??? Dammit, there was no time. Heidi drew a deep, uncertain breath and made a call based on her instincts. She slung the rope around herself and her pal, looped the standing end into an alpine butterfly, and tumble-hitched the working end to the butterfly’s bight. It may not be technically optimal, but it would get the job done.&lt;/p&gt;&lt;p&gt;With herself and Explorpheus snugly bound together, Heidi seized the ghost by its lips, stretched them outward, and tied them off to the running end of the rope with a constrictor knot, topologically converting the ghost into a sealed-up sphere. “Quickly Explorpheus, tickle the bum!!” she shouted. The water was up to her thighs by now. Explorpheus couldn’t tickle quite as well as Heidi on account of her hooves, but she reached up and frantically tried her best to stimulate a reaction from the bubble of ectoplasm. Mercifully, her efforts were rewarded as the surface tension on the internal ectoplasmic membrane dropped and went negative, causing the ghost to inflate into a sort of balloon with an internal volume that was now less dense than the surrounding atmosphere. The external membrane underwent some kind of curious electrochemical process as it stretched, altering the hue of its subsurface scattering, cycling through a cornucopia of colors before settling on a lovely lavender shade. The purple ghost balloon shot upwards, jerking the rope that bound our two heroes together, lifting them out of the water as they clung on desperately to their slender, tenuous lifeline.&lt;/p&gt;&lt;p&gt;Once they were clear of the rim of the chasm, Explorpheus swung her tremendous weight about to give their bundle some lateral momentum. At the apogee of their swing, Heidi Croft yanked the tumble hitch loose, sending them both tumbling into the grass and releasing the ghost balloon into a tropospheric adventure all its own. Heidi got up and shimmied off some of the water that besoaked her fur and enwettened her booty shorts. She cast her gaze down the hillside, beyond the bramble forest, over the marshmallow hills, landing upon the shoreline where this island continent first arose beneath their ship. Except, the shoreline was a little closer than it was the last time they’d seen it. In fact, it was a lot closer. That didn’t make sense. “Say, Explorpheus… are we due for an extra high tide today?” Explorpheus came to Heidi’s side and gasped at the gaspworthy vista laid out before her. “That’s no high tide.”&lt;/p&gt;&lt;p&gt;Explorpheus looked at Heidi. Heidi looked at Explorpheus. They both had a sinking feeling. Epistemologically speaking, this was the correct feeling to have as it dawned on them that the island was sinking. Explorpheus looked up at the ghost balloon sailing ever higher into the heavens above. Heidi followed her gaze and immediately knew what her buddy was thinking. Staring up at the ghostly orb above them, Heidi Croft opened her raccoony little mouth to speak.&lt;/p&gt;&lt;p&gt;“We’re gonna need a lot more ghosts.”&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>The Summer of Making (Chapter One)</title><link>https://news.hackclub.com/essays/som-chapter-one/</link><guid isPermaLink="true">https://news.hackclub.com/essays/som-chapter-one/</guid><description>Captain Trashbeard was starting to get sick of the ocean. Literally, sick.</description><pubDate>Mon, 16 Jun 2025 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;Captain Trashbeard was starting to get sick of the ocean. Literally, sick. They say you get your sea legs with time, but it takes a lot longer when you have four of them… and so she laid splattered across her bed in the captain’s quarters, bouncing violently as Le Dumpstairè II cut through steep swells like a ninety-ton timber-hulled schooner through butter. These rough seas were making her queasy and miserable, though her regular diet of literal garbage was also surely not helping.&lt;/p&gt;&lt;p&gt;The captain felt something welling up from deep inside. The feeling was sadness. Trashbeard felt sad. No, homesickness was what she felt. No… no, that feeling would be seasickness—again. Uh-oh. She ran out onto the weather deck, heaved herself over the gunwales, and ejected a stream of yellow bile in a parabolic arc that landed a solid twenty feet out from the ship. First Mate Arrpheus, ever the loyal companion, came over to hold back her whiskers for the second time that day.&lt;/p&gt;&lt;p&gt;It was about that moment when the commotion began. The presently-occupied captain didn’t notice at first, but Arrpheus instantly detected a change in the water through the tippy-toes of her delicate hooves. Moments later she saw it with her eyes, too… she could tell things were off from some of the pixels, and from seeing quite a few commotions in her time. At first it was something about the texture of the waves. Then, it was a shift in the hue. Then, it was a gigantic volcano shooting through the surface on the horizon, followed by foothills, followed by an entire continental landmass erupting from below the ship, complete with trees and lakes and boulders and—especially peculiarly—a sizable hole in a cliffside rising from the nearby dunes, positioned a meager three furlongs down the sandy beach that now cradled the hull of Le Dumpstairé II. Arrpheus ran to the captain’s quarters and retrieved a couple of spyglasses from the enormous pile of trinkets at the foot of the captain&apos;s bed. Most of these were recently shoveled into Captain Trashbeard’s AliExpress cart after a frenzied afternoon of googling things like “tariffs definition simple english wikipedia” and “what country is china in”&lt;/p&gt;&lt;p&gt;The rumbling had caused the peg to fall clean off of Arrpheus&apos;s leg, but Orpheus was too puzzled by the curious cave to notice. She raised her spyglass to a squinty lil dino eye, trained it upon the distant landform, and did her best to describe what she saw to her vomitorious friend. “Cave. Round. Too round? Looks deep. Real dark. Neat.” Trashbeard was busy pawing at her head, scanning the beach for the captain&apos;s hat that she&apos;d lost along with the contents of her stomach. At first Heidi was only minimally intrigued by her pal&apos;s description, but she raised up her stinky pukeface enough to poke a cheap plastic eyecup into her bulging eyeball… just in time to witness something that promised to change the course of their lives forever or at least for the next forty minutes probably at a minimum: a ghost rising out of the dark!! And not some crappy vintage premultiplied-alpha photobomb of an irrelevant victorian hag, cursed to eternally wander the pantry or some such. This was a thiccc, cartoony, Luigi’s Mansion-style dribble of additively-blended ectoplasm, spurting out of the subterranean dankness bleating theremin sounds from its derpy dead face. Not just a ghost, no no—this was a spOOoOoooOOOOOkyy ghost. Which meant that cave wasn’t just a cave… it was a spooky tomb!!!&lt;/p&gt;&lt;p&gt;Heidi and Orpheus shared a glance that instantly cancelled their plans for the rest of the day. Twenty minutes later they stood at the maw of the tomb, gazing into a magnificent stone void that could only be borne of intelligent hands and/or paws and/or hooves. Orpheus adjusted the brim of her trustiest hat and choked up on the handle of a sturdy and dangerous-looking bullwhip. Heidi, clad in an absurdly low-quality Temu tank top that seemed to be cardboard-levels of stiff, pulled two overripe bananas out of a filthy backpack and holstered them on either side of her booty shorts. The tiny raccoon hoisted her inventory back upon her shoulders and turned her gaze upward to the lumbering dinosaur at her side. Their eyes met. A silent nod passed between our mismatched heroes. And there the beginning came to an end; buttressed by the stainless bonds of their timeless partnership, Heidi Croft and Explorpheus Jones descended into a season of adventure set upon a continent deserted by all but the best of friends.&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>Why We Ship</title><link>https://news.hackclub.com/essays/why-we-ship/</link><guid isPermaLink="true">https://news.hackclub.com/essays/why-we-ship/</guid><description>Shipping is a habit you must cultivate to keep yourself honest; with others, but principally honest with yourself.</description><pubDate>Tue, 11 Feb 2025 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;Originally written at during High Seas, our second &quot;Universal You-Ship-We-Ship&quot; program which ran during the winter of 2024/2025. This is the last of three essays intended to introduce newcomers to some of the philosophical underpinnings of Hack Club.&lt;/p&gt;&lt;p&gt;In my last essay we talked about the hacker mindset, its role in how Hack Club works, and how you can be a part of this mission (should you choose to accept it). We covered how the twin engines of experimentation and iteration drive us toward our goals. And just like twin engines on a boat, both of these processes have cycles built around a singular moment of combustion: the ship.&lt;/p&gt;&lt;p&gt;“Shipping” means deploying a project in a form that provides an actual, real-world validation of whether your project can accomplish its goals. For a stair-climbing robot, this would mean assembling your prototype, powering it on, and actually trying to climb some stairs. For a video game, you might put a demo online, send it to some people, and ask them if it’s actually any fun. It’s always a nice moment to see stairs get climbed or players have fun, but that’s not the most important reason why you should ship. We ship to convert conjecture into truth. Remember that as hackers we don’t trust our theoretical models; the true value of shipping comes when a belt snaps and your creation tumbles down the stairs, revealing precisely what you were wrong about this time. With any luck, when you ship the next iteration you’ll get to be wrong about something entirely new.&lt;/p&gt;&lt;p&gt;Shipping is a habit you must cultivate to keep yourself honest; with others, but principally honest with yourself. Every once in a while I find myself watching something I built experience a serious failure, something beyond the minor well-controlled failures we actively seek out as part of the constructive process. Perhaps a product launches and flops, or a prototype breaks in a way that destroys something expensive. Almost all of these moments could be described as a failure to imagine the particular way in which something will ultimately break. But most of the time, a review of my decisions turns up some obvious way that a basic reality check would have made a lesson learned the hard way a whole lot easier. The greater failure there is not that I didn’t see how something would break, but rather that I convinced myself that I knew it would work.&lt;/p&gt;&lt;p&gt;It turns out that the universe is very complicated, and my capacity to model it is usually far outstripped by its capacity to surprise me—sometimes in rather embarrassing ways. As Uncle Iroh said in The Last Airbender, &quot;Pride is not the opposite of shame, but its source. True humility is the only antidote to shame.&quot; When I make something that seems to be working, or even that I just expect to work, I often feel quite proud… but if I allow that pride to seduce me, it has a way of turning into shame when my grand visionary project turns out to be kind of a dud (and wow, this has happened a lot in my life). Humility means testing our assumptions, and the best way to continuously test our assumptions end-to-end is to ship fast and ship frequently. There are many more ways for a system to break than to work; when you ship fast and frequently, you increase the odds of failing successfully, i.e. when change is merely painful instead of impossible.&lt;/p&gt;&lt;p&gt;This is the primary reason why you are required to ship projects for High Seas to receive doubloons! During Arcade, it didn&apos;t matter what you built or whether it even ultimately worked (let alone was actually any good). And while a lot of people built some really cool projects, a large percentage of the tickets other people earned came from code that went absolutely nowhere. Even among the finished working projects, a lot of them were what we&apos;ve come to call &quot;slop&quot;: products that nobody wants, not even the people who made them. Bland checklist apps, portfolio websites that were lazily copy-pasted from templates, dozens of identical tic-tac-toe and 2048 games… nobody is excited about those projects. Nonetheless, a lot of people made them anyway because that&apos;s what our system incentivized. This is one of the biggest ways we got to see our experiment fail, but it was a successful failure because after a long summer of iteration on Arcade we could turn around and incorporate our findings in the next experiment, High Seas! So this time around, we did our best to align the optimal strategy for stacking up doubloons with the experimentation and iteration model laid out in the previous essay. Let&apos;s take a look at what that optimal strategy is; consider this free advice on how to get more doubloons from High Seas, and hopefully whatever comes next.&lt;/p&gt;&lt;p&gt;Your best first move is to try a bunch of small experiments. Ship a quick MVP for each of them to see which concepts people are excited about. Sooner or later you&apos;ll hit something that resonates with your peers, and you&apos;ll see that reflected in the size of your payout. This is when you&apos;re ready to move from experimentation to iteration, and that means shipping updates instead of whole new projects. Work on new features in bite-sized chunks that people can easily understand, and ship them as updates to your project. As you stack more hours onto your project, each of those updates will get a new rating that will probably be in a similar range as your original MVP, maybe even higher… at least, for as long as you are squeezing real juice out of your updates. As your project gains more hours, it will be compared against other projects with more hours, so eventually you will probably run low on ways to meaningfully improve it and its performance will start to dip relative to the competition; after all, you can squeeze a lot of juice out of a really cool portfolio site but diminishing returns will probably come faster than something like a custom game engine, even if the portfolio beats the engine at first. This is when you may want to try some fresh experiments, informed by all your new knowledge, which starts the whole process over again.&lt;/p&gt;&lt;p&gt;This is the optimal strategy for High Seas… or at least, that&apos;s my hypothesis based on how we designed it. We designed it this way to approximate the optimal strategy for building things in the real world. But of course, I can&apos;t say for sure how this experiment will work. High Seas is our latest ship, and we&apos;re relying on you to show us all the ways it will fail. You&apos;ve already shown us quite a few, and each of those failures is a discovery of a fresh opportunity for improvement. Your experiments feed our iteration, so that our experiment can feed yours, so that step by step we may all march asymptotically together toward truth.&lt;/p&gt;&lt;p&gt;A final note: I had most of this essay written in late-August 2024. I finished it mid-December. And yet, I haven&apos;t shipped it. I haven&apos;t shipped because I didn&apos;t think it was inspiring enough; the last two essays in this series had a sort of punch to them that tied their thesis back to the world at large, and I just wasn&apos;t feeling it in the same way with this one. But by leaving it on the shelf, I am missing the point of the essay itself. So… here it is. Essay number three. It&apos;s not perfect, but it&apos;s shipped. Better late than never!&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>High Seas: The End</title><link>https://news.hackclub.com/essays/high-seas-end/</link><guid isPermaLink="true">https://news.hackclub.com/essays/high-seas-end/</guid><description>“Beep… Beep… Beep” Arrpheus said quietly to herself, pretending the ship was a great big truck as the stern of Le Dumpstairè II slowly approached the pier.</description><pubDate>Fri, 31 Jan 2025 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;Originally written to announce the ending of High Seas, our second &quot;Universal You-Ship-We-Ship&quot; program which ran during the winter of 2024/2025. Subsequent to the end of this program, teenagers all over the world organized over a hundred physical meetups to find the other High Seas participants in their area as part of a worldwide in-person connection building effort called Mystic Tavern.&lt;/p&gt;&lt;p&gt;Trashbeard and Arrpheus backed their ship into the docks at Bootymouth Bay. &quot;Beep… Beep… Beep&quot; Arrpheus said quietly to herself, pretending the ship was a great big truck as the stern of Le Dumpstairè II slowly approached the pier. Seconds later their ears were greeted by a familiar cacophony: a bellowing stomach-churning crunch, the splintering of wood, and the frightened screams of dockworkers, most of whom had barely managed to leap out of the way in time to avoid an unscheduled swimming lesson. The horrible noises concluded as the ship ground to a halt—except for the angry dock people, who still sounded very pissed off. This relative silence was the signal for our crew to disembark.&lt;/p&gt;&lt;p&gt;Arrpheus flung the rope ladder over the port gunwale and the duo climbed down to a section of dock that was still mostly intact. Captain Trashbeard gave a friendly wave to the dockworkers, who seemed curiously upset about something. Perhaps when she returned she could gift them each an old banana peel, or an empty Doritos™ bag with a few crumbs still inside, or some similar treasure as a way to lift their spirits. She was positively loaded with good stuff like that after the last haul. Arrpheus looked back over her shoulder at Le Dumpstairè II with her dinosaur dinner-plate eyes, wearing a frown that refused to turn upside-down. She was happy to be home, but she didn&apos;t feel quite ready for the adventure to be over. She stopped and turned back toward the harbor, her gaze sweeping across the water as it tangled and played with the sunset in a blazing kaleidoscopic dance.&lt;/p&gt;&lt;p&gt;&quot;Goodnight, water.&quot;&lt;/p&gt;&lt;p&gt;She took a big breath in.&lt;/p&gt;&lt;p&gt;&quot;Goodnight harbor. Goodnight docks. Goodnight sunset.&quot;&lt;/p&gt;&lt;p&gt;Her raccoon friend watched her in reverent silence.&lt;/p&gt;&lt;p&gt;&quot;Goodnight beaches, goodnight islands. Goodnight seagulls. Goodnight fish. Goodnight wind, goodnight waves, goodnight storms… goodnight kraken.&quot;&lt;/p&gt;&lt;p&gt;Arrpheus stumbled over her next breath, her chest heaving as a handful of tears made their way down her cheeks. She looked longingly at the magnificent vessel sitting nestled among the fractured beams of what used to be a pier. Her quivering voice dropped to a whisper.&lt;/p&gt;&lt;p&gt;&quot;Goodnight, ship.&quot;&lt;/p&gt;&lt;p&gt;The captain stood beside her now, looking up at the silently trembling dinosaur. A tiny raccoon paw reached up to tug gently at Arrpheus&apos;s big dumb hoof. &quot;Come on, buddy. It&apos;s time to go.&quot;&lt;/p&gt;&lt;p&gt;Arrpheus looked down—smiling at last—and nodded her assent. &quot;I&apos;m ready now.&quot;&lt;/p&gt;&lt;p&gt;Paw in hoof together, they turned once more and walked up the the hill toward the beckoning glow of the Mystic Tavern, where their friends sat waiting with stories all their own.&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>High Seas: The Kraken Strikes</title><link>https://news.hackclub.com/essays/high-seas-kraken/</link><guid isPermaLink="true">https://news.hackclub.com/essays/high-seas-kraken/</guid><description>The bobber plopped into the water like an olive in a martini glass, a final touch on a perfect concoction. Blue sky, wide ocean, fresh plunder.</description><pubDate>Mon, 18 Nov 2024 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;Originally written during High Seas, our second &quot;Universal You-Ship-We-Ship&quot; program which ran during the winter of 2024/2025. This story was used to launch a referral scheme where teenagers could get credit within the program for getting their peers to join.&lt;/p&gt;&lt;p&gt;The bobber plopped into the water like an olive in a martini glass, a final touch on a perfect concoction. Blue sky, wide ocean, fresh plunder. Captain Trashbeard was trying a new kind of bait today: cockroaches. Le Dumpstairè had thousands of them scurrying around the cargo hold ever since she pillaged that landfill in New Haven. That city was a veritable gold mine. Life was good. She delighted in how the rocking of the ship, the swishing of her tail, and the bobbing of the bobber were all in delicate phase with each other, making a sweet silent harmony with the undulations of the enormous shadowy tentacles rushing up from the depths below on either side of the vessel. Ohhhhhhh shiiiiiIIIIIIIII—&lt;/p&gt;&lt;p&gt;The next two minutes contained too much profanity to be described here. Most of it was screeched in her native raccoon tongue, but seriously it was way too obscene for us to risk you putting that into google translate.&lt;/p&gt;&lt;p&gt;By the time the narration had returned to PG-13 levels, Trashbeard and Arrpheus were watching Le Dumpstairè dip below the waves with the help of a big hug from a very snuggly kraken. Thank god they had this lifeboat. The captain originally bought it on a manic spending spree that finally ended when Arrpheus forcibly uninstalled Temu from her phone; the prospect of an app that sends garbage directly to the boat was too dangerously irresistible for Captain Trashbeard. Too dejected even to be smug about how this particular piece of junk had just saved their lives, she whimpered sadly as she watched her haul from that landfill disappear below the waterline. And… wait, her hat was gone too?! Today sucks. Oh and her ship, also that thing.&lt;/p&gt;&lt;p&gt;&quot;We need help.&quot; said Arrpheus. Trashbeard nodded.&lt;/p&gt;&lt;p&gt;&quot;Let&apos;s gather a crew when we find a port.&quot; Trashbeard nodded again.&lt;/p&gt;&lt;p&gt;&quot;How will we convince them to join us?&quot; Arrpheus said, to a still silent captain.&lt;/p&gt;&lt;p&gt;The unbehatted raccoon thought for a moment, then solemnly turned to her dinosaur friend and locked eyes. &quot;The same way Temu got me on board… a referral program.&quot;&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>High Seas: The Beginning</title><link>https://news.hackclub.com/essays/high-seas-beginning/</link><guid isPermaLink="true">https://news.hackclub.com/essays/high-seas-beginning/</guid><description>Sunbeams glint off the rippling water like brilliant daggers, stabbing your eyes in a much more pleasing way than a literal eye-stabbing.</description><pubDate>Tue, 29 Oct 2024 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;Originally written to announce the beginning of High Seas, our second &quot;Universal You-Ship-We-Ship&quot; program which ran during the winter of 2024/2025.&lt;/p&gt;&lt;p&gt;Sunbeams glint off the rippling water like brilliant daggers, stabbing your eyes in a much more pleasing way than a literal eye-stabbing. You inhale deeply. The aromas of the beach tickle your brain like a loving yet irritatingly domineering older sibling. Salt. Kelp. Rotting… fish, probably. Yup, some dead thing with fins is definitely decomposing nearby, microbes slowly transmuting it into a pungent cocktail of greenhouse gasses and putrescine aimlessly rising to heaven. Even fish can fly, if only in death 🪽&lt;/p&gt;&lt;p&gt;A tremor from below disturbs the peace. Grains of sand vibrate across your toenails like droplets of water skittering across a hot pan. Suddenly a trio of tall wooden masts breach the surface of the water, followed by sails, followed by the wooden hull of a gargantuan 18th-century ship shooting out of the water and into the air like a nerf football released from the bottom of a pool. The ship cartoonishly hangs in the air before crashing into the sea with a terrific SPLOOSH, creating a tremendous wave that rushes to shore and knocks you over with the overwhelming force of a friendly but overeager and poorly-trained doberman. The whole shebang is over in seconds, leaving you stunned, sprawled on the beach, covered in seaweed. You raise your head to see a dinosaur with an eyepatch gazing down at you from the mighty prow of the ship. A raccoon with a spyglass has climbed the rigging for a better view of your sogginess.&lt;/p&gt;&lt;p&gt;&quot;Aye, a landlubber!! Ahoy new friend!!!!&quot; cries the raccoon. The dinosaur smiles and nods excitedly, fussing with her eyepatch to get it on the other eye, both of which seem to be intact. &quot;I am Captain Trashbeard, and this is my First Mate Arrpheus!! Behold our schooner, Le Dumpstairè, the finest pirate vessel in the Caribbean, feared by all who sail these waters!! Come, come aboard!!!!&quot;&lt;/p&gt;&lt;p&gt;Arrpheus drops a rope ladder from the gunwales, the final wooden step landing in the water below with a minuscule sploosh while dinosaur hooves above awkwardly and furiously beckon you forth. You pick yourself up off the beach, unsure what to do. This sort of thing doesn&apos;t usually happen to you. You look down at your phone and open the calendar. It&apos;s empty. You look up at the pirate ship. It&apos;s full. Of possibilities. Metaphorically, anyway… you can&apos;t actually see the interior. Unease gives way to resolve; fueled by a supernatural drive for adventure, your fear is left on the beach to watch you wade into the ocean, swim to the ladder, grasp the first rung, and climb aboard this maritime relic. And so began your new life as a pirate.&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>The Hacker Mindset</title><link>https://news.hackclub.com/essays/the-hacker-mindset/</link><guid isPermaLink="true">https://news.hackclub.com/essays/the-hacker-mindset/</guid><description>There are no rigorous fundamental principles for what Hack Club does. It&apos;s something new, and we are feeling around in the dark.</description><pubDate>Tue, 27 Aug 2024 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;Originally written at the end of Arcade, our first &quot;Universal You-Ship-We-Ship&quot; program which ran during the summer of 2024. This is the second of three essays intended to introduce newcomers to some of the philosophical underpinnings of Hack Club.&lt;/p&gt;&lt;p&gt;Now let’s talk about how we actualize those definitions. Hack Club operates on the basis of experimentation and iteration. There is no grand strategy in Hack Club; that’s not how hackers operate. A key distinction between hacking and engineering is that engineers have faith in their ability to design highly complex systems from fundamental principles. That confidence is necessary because a bridge has to work the first time, and well-founded because they almost always do! Eons of experimentation and iteration have allowed us to painstakingly extract very accurate abstractions of how bridges stand—and how they fall. Perhaps the earliest bridges were built with something closer to a hacker mindset… but at some point the discipline passed through a big fuzzy gray area into the realm of engineering, where enormous complexity can be safely navigated with the aid of rigorous fundamental principles.&lt;/p&gt;&lt;p&gt;There are no rigorous fundamental principles for what Hack Club does. It&apos;s something new, and we are feeling around in the dark. We do have some fundamental principles for parts of what we do, most notably the parts that live wholly on computers. Hack Club employs many people who can (and do) build highly-scalable databases and blazingly-fast websites on the first try… but Hack Club is not in the business of databases and websites. Hackers may engage in engineering, but it&apos;s not what makes us hackers. At Hack Club, the hacker mindset becomes most important and apparent when our systems make contact with humans. This is where the darkness envelops us, and we cannot trust our ability to design complex things from fundamental principles.&lt;/p&gt;&lt;p&gt;So, how do we navigate unknown terrain in the dark? How do we find the highest peaks, and avoid the lowest valleys, when we don&apos;t have a reliable map?&lt;/p&gt;&lt;p&gt;Experimentation and iteration are the hacker&apos;s tools for exploring new territory. To solve a problem, first we formulate an idea and try it out as quickly as possible (the &quot;Minimum Viable Product&quot;, or MVP). Speed matters much more than theoretical correctness here, because we assume at this point that our theories are no good, and we expect to have to build a bunch of experiments! The purpose of an experiment is not to be right, it&apos;s to gather data; even when the result is negative, each real-world test reveals a tiny sample of truth about the overall landscape beneath our feet. Most things built in Hack Club do not work out. But eventually, inevitably, our parade of experiments will turn up something that works—even if only a little—and we can begin to iterate on our quest for the summit.&lt;/p&gt;&lt;p&gt;If experimentation is the process of looking for hills, iteration is the process of climbing them. Building and testing a single experiment tells you how well that one thing works—it gives you the height of the terrain—but a step in any direction from there tells you something more: the gradient. Every small tweak to an existing product is a step that tells you which direction leads upward. Good, quick iteration tends to rapidly improve a product… but then improvement slows down as you reach the top of the hill, which may not be very high. Most hills are not mountains, and you cannot iterate your way to Everest. It&apos;s time for another round of experiments—but this time, you know where the foothills begin.&lt;/p&gt;&lt;p&gt;This process repeats. Every time you approach the top of a hill, you jump around looking for a bigger one to climb next. Eventually, you&apos;ll find yourself on top of a mountain. Practically every good thing that has ever been built in Hack Club began as a humble, simple experiment. And among all the big, complicated, mountainous projects you see being built here—both from staff and within the community—there are hundreds of tiny, simple, nimble experiments blinking in and out of existence every day. You&apos;ll never see most of them, because most of them never go very far; but each of them is as critical to this process as the steps we take atop mountains like HCB or Arcade. Which leads us to a beautiful truth: you, dear hacker, are as much a part of this revolution as I am. You don&apos;t need to be an adult, spend years in our slack, or be some kind of wizard programmer. If you publicly try things, take small steps, and stay determined, you&apos;re doing your part. Never forget: complicated things that work are almost always evolved from simple things that work.&lt;/p&gt;&lt;p&gt;On March 27th 2024, a 16 year old in Texas named Manitej created a channel in our Slack called \#hack-hour as a place for other teenagers to use his personal pomodoro timer bot. Anyone can build a pomodoro timer. The original bot didn&apos;t even have a codebase, it was just a Slack workflow. But this random little experiment worked well enough for a few other hackers to use it, so Manitej started iterating, and it grew. He created a proper Slackbot, gave it personality, and marketed it around the channel. Eventually, Max from HQ decided to run an experiment with him where they gave out rewards for your hours. More iterations. Another experiment. Less than three months after the channel was created, they renamed it to \#hack-hour and launched what became the largest online event Hack Club has ever run, logging over 120,000 hours and distributing well over $100k worth of resources to teenage hackers all over the world.&lt;/p&gt;&lt;p&gt;This is how Hack Club works. Let&apos;s recall one other definition of Hack Club from the previous essay: Hack Club is a long-term bet that the best technical education program for teenagers can be built by other teenagers&lt;/p&gt;&lt;p&gt;That doesn&apos;t mean every bit of work in Hack Club is done by teenagers. It means that a critical mass of teenagers with a hacker mindset can be the engine of a revolution in education. We literally cannot do this without you. Neither me nor anyone else on our staff would have ever tried building a pomodoro clock, but that ultimately worked better than just about anything we&apos;ve ever done. At the same time, Arcade had many problems… we are nowhere near the summit! Many, many cycles of experimentation and iteration lie ahead of us. I hope you&apos;ll be a part of them.&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item><item><title>What is Hack Club?</title><link>https://news.hackclub.com/essays/what-is-hack-club/</link><guid isPermaLink="true">https://news.hackclub.com/essays/what-is-hack-club/</guid><description>It&apos;s actually not easy to define Hack Club. It&apos;s a lot of different things, with many separate projects running under the umbrella of one foundation.</description><pubDate>Thu, 08 Aug 2024 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;Originally written at the end of Arcade, our first &quot;Universal You-Ship-We-Ship&quot; program which ran during the summer of 2024. This is the first of three essays intended to introduce newcomers to some of the philosophical underpinnings of Hack Club.&lt;/p&gt;&lt;p&gt;In the last 8 weeks, as ~8k new people have joined our Slack Channel, we&apos;ve put a lot of effort into explaining what Arcade is (and in some ways, we still haven&apos;t done a great job there). However, we&apos;ve put almost no effort into explaining what Hack Club is. Understandably, a lot of new people have assumed that Hack Club is Arcade. Some have even asked us if the Slack will be shut down at the end of the summer! In fact, Hack Club was already 8 years old when Arcade started.&lt;/p&gt;&lt;p&gt;So what is it? It&apos;s actually not easy to define Hack Club. It&apos;s a lot of different things, with many separate projects running under the umbrella of one foundation. Some of the components that make up Hack Club are:&lt;/p&gt;&lt;p&gt;To take it one step further, we could try to summarize all those summaries like this: Hack Club is hacker culture for teenagers, institutionalized.&lt;/p&gt;&lt;p&gt;So why do we want to do that? Why are we building an institution to support hacker culture? Because hacker culture is built on the values of the hacker ethic, and we think those values are important. I considered trying to explain why, but… if you&apos;re here, chances are you don&apos;t need me to. Despite the importance of hacker ethic, there are very few institutions dedicated to propagating it, and even fewer for teenagers specifically. We want to fill that gap.&lt;/p&gt;&lt;p&gt;I could end this essay here, but I&apos;d like to cover one final definition of Hack Club, grander and more ambitious than all the others: Hack Club is the hacker-oriented arm of the public education system.&lt;/p&gt;&lt;p&gt;To unpack that, let&apos;s zoom way out and consider that the 20th century witnessed a remarkable change in the problems faced by humanity: for most of history, our greatest challenges have been imposed by nature. Disease. Hunger. Shelter. Today, however, a remarkable share of our greatest challenges are problems we created for ourselves. Climate change. Pollution. Obesity. Nuclear proliferation. Ecosystem collapse.&lt;/p&gt;&lt;p&gt;The 20th century was defined by the industrial revolution, when we just needed people to build new complex systems from the primitive blocks of nature. Today we need something more: we need people who can manipulate, adapt, extend, and sometimes even dismantle the complex systems we&apos;ve already built. We need people working within established systems in ways that go beyond their original design and architecture, because in their present configuration those systems are literally killing us. Across all levels of government, technology, agriculture, education, we need people with a different skillset and mindset than what you learn in a school system designed for the industrial revolution. In a word, we need hackers… and schools today are simply not set up to produce hackers. For all the ways the world has changed in the last century, schools have barely changed at all.&lt;/p&gt;&lt;p&gt;Hack Club is a way of hacking the education system to produce more hackers. That&apos;s our mission… and we need your help. Look around our website, slack channel, or any event with our name on it. Wherever your gaze may fall, odds are you are looking at something that was partly or wholly created by a high-schooler. Hack Club was founded by a sixteen-year-old who dropped out of high school because he knew that his school couldn&apos;t offer the skills or community that he needed. We hope you will stick around after Arcade is over, because if we&apos;re gonna build the hacker-oriented arm of the public education system, we&apos;re gonna need a lot of hackers.&lt;/p&gt;</content:encoded><media:content url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png" medium="image"/><media:thumbnail url="https://cdn.hackclub.com/019dbae9-5242-745b-acd2-3476ab3c52a3/og-default.png"/><media:title type="plain">Slacker News social preview</media:title></item></channel></rss>