What it is: A single global counter. You press when an automated system is making a real decision and you believe a human should decide instead. No account, no tracking. Optional context (e.g. loan denial , content moderation ) builds a live feed and insights.
Why: I kept hitting algorithm said no with no way to say a human should decide this. I wanted one artifact that makes that visible and a public Transparency API so researchers and companies can query anonymized aggregates.
Only press if you believe a human should decide.
Most products optimize for engagement, efficiency, or outcomes. This one doesn’t. It consists of a single button whose only function is to record that a human chose to press it. There are no accounts, rewards, or actions beyond that. A short daily observation is shown to reflect how the button is being used.
This project exists to prove that a single human action still matters, even when it does nothing.
I believe every project should have a website to showcase its offering, not to mention for SEO purposes. Whether SEO will still be relevant due to AI is another discussion.
Do you have any favourite websites that are both functional and beautifully designed?
All of you who are building a personal brand, I guess, keeping up with the onslaught of notifications is not the easiest thing to do. I personally open some notifications after a month (like today on Bluesky, Substack and Twitter), not to mention that I reply to some messages after months. It helps me keep my sanity. But it took me almost 4 hours to handle these today.
On the other hand, I manage ProductHunt and LinkedIn quite regularly.
I m preparing to open source a project I ve been working on privately for a while. It's now production-ready and has real-world impact, but I want to make sure I do it right, not just dump it into GitHub and hope for the best.
I m looking for your battle-tested frameworks and lessons learned:
What s one thing you wish you had done differently when making your repo public?
What made your repo get noticed?
What should I definitely include before launching?
Did you use templates, bots, GitHub Actions, or community rituals that helped?
How do you avoid just having a ghost town of a repo?
I'm working on an open-source project and would really appreciate your feedback before I take it further.
I ve been building a lightweight tool that lets you search and visualize audit logs from services in the Hadoop ecosystem, like Apache Ranger, Hive, HDFS, Impala, and YARN, without needing to set up an external logging stack (like ELK or Splunk).
The idea is to make it easier for data engineers, governance teams, or platform admins to answer questions like:
I've been on this platform for over 2 years, and we have to admit that the number of tools that appear here every day is truly unimaginable.
Sometimes it's hard to select the best ones, but I have to say that some that I found a few months or years ago, I still use every day because they are useful to me in some way.
I m currently building a product that blends digital efficiency with human warmth. It s designed to solve a real pain point, but in a way that respects emotion, context, and intuition.
Over the years working for agencies I've become quite familiar with tools like @asana and @Jira , also with @Trello for personal projects. But I was wondering, are these the most used or are these just the ones I've been exposed to? Are there better options? Would love to hear your thoughts down below!
