Hopefully you're not rejected for the same reason as Freerse. The #[4] board wanted a nice green GitHub stat sheet. We'd been building the product locally for the previous year and a half. They don't care if your product is used and if Nostr's users like it.
Login to reply
Replies (15)
I respect their decisions and appreciate them 🫂🙏
This can't be the only reason. Commits can easily be faked to make your GitHub all green.
I'd bet if you complain about it a few dozen more times your app will get a unique feature that's worth funding! 🙄
When did OpenSats start providing rejection reasons?
if they want you to game a metric, game the metric
@Jameson Lopp showed us the way


Testnet3. They are the same picture.
If you set up a permissionless system you should expect it to get gamed.
By Jameson 🤣
Ah, but there are consequences, for both the gamer and the gamed. You could steal something from a low security super market, but you might find myself paying a price.
In fact, this is the tragedy of a #Nostr developer.
View quoted note →
Yeah we heard. "wah wah wah"
Just do the same work you claim you can do. Not show some old shit. Big whoop
Hey old friend … remember me


You are equating a voluntary act of creation, committing to a github repository, to an act of theft and a violation of private property rights. You have gone off the rails.
Anyone using github activity as a proxy to evaluate a developer's quality of work needs to be aware that they are using an imperfect heuristic. It is extremely easy to game. This is not even remotely similar to property theft.
If you find that your shortcut heuristic is no longer reliable (which is inevitable in the long run) then you need stop using that metric and find better, more accurate signals to evaluate a developer's contributions. If the green boxes aren't cutting it, you need to do the work instead of taking a shortcut. It's as simple as that.
Goodhart's law - Wikipedia
Leaving unsolicited the personal attack to one side. You are not making a credible argument. The topic was the attack on testnet3. And you've created a false equivalence. It comes accross as a bad faith argument that is not productive, so I'll thank you for your opinion and we can agree to differ.
Ha! Very well. We are communicating ineffectively on different topics.
fwiw testnet3 was being abused by scammers. They found a way to extract value from any proof of work network so the utility of testnet3 to the bitcoin movement as a whole had fallen below zero (this is a subjective value judgement). It was overdue for a refresh because it became too hard to get new coins.
Fabian Jahr (who is awesome btw) took it upon himself to lead the charge for a new testnet4 without the protocol vulnerabilities of testnet3. He is continuing that work, most recently with a project to fork off chains of 0-difficulty blocks mined by scammers on testnet4. This last project won 3rd place at a hackathon I participated in. 🤙