Make Hackatime Great Again (MHGA)

Hack Club,

Pro-Wakapi lobbyists just launched a multi-million-dollar ad campaign calling Hackatime "dangerously radical." 👇

I have a few questions for them.

Is it “radical” to believe that we should have one auth method, Hack Club Auth?

Is it “radical” to believe that WakaTime plugins should be reformed, to make them more reliable? And that they should have automated tests to ensure they don't break over time?

Is it “radical” to believe that OAuth2 scopes should be more fine-grained and boost security?

And is it “radical” to believe that Hackatime should emit OTel metrics, so that we can have a fancy new Grafana dashboard, showing instance stats and health?

If they think any of that is “radical,” then we’ll wear that label as a badge of honor.

Here's what's actually radical: spending millions of dollars to convince Hack Clubbers that wanting security and a developer API that works for them is dangerous. That’s exactly what Wakapi’s backers are doing with $51 million in their campaign war chest.

Hack Club, we need your help to respond, and we need it fast. [Can you chip in $10 or any amount right now so we can compete over the airwaves, meet Hack Clubbers where they are, and make sure the Wakapi Super PACs don’t get the last word in?](https://hcb.hackclub.com/hq)

In solidarity,

Hack Club HQ

The issue names no files, tests, or entry points and combines authentication, plugin reliability, OAuth2 scopes, and OpenTelemetry metrics. Start by asking maintainers to split these proposals into separately scoped issues and identify the relevant entry points and tests. Done would need an agreed scope for one concrete change, with its affected code and validation defined.

Written by the indexing model from the issue text.