Thank you, nostr:npub1rzg96zjavgatsx5ch2vvtq4atatly5rvdwqgjp0utxw45zeznvyqfdkxve

nostr:npub10pensatlcfwktnvjjw2dtem38n6rvw8g6fv73h84cuacxn4c28eqyfn34f 's reason for rejecting Freerse's funding application is truly unbelievable.

They claim to fund "open-source projects," but their reason for rejecting us wasn't that Freerse isn't open-source, but rather—that we didn't have those "little green dots" on our GitHub.

Their only publicly stated requirement was "must be open-source," but their actual evaluation criterion was the activity record on GitHub.

For a year and a half before applying, we had been developing locally and publicly releasing all progress and version updates on Nostr nostr:npub1tqjvq0ff6detxfmuczmvkvk52sgs9fa0ppjmmgu0hnk7cn29fmaq9mz588 Freerse users also came forward to speak up and testify on our behalf. I explained all of this to the opensats staff.

But opensats completely ignored these real development records and user feedback. They only cared about the little green dots on GitHub.

The absurdity is that this "unwritten rule" wasn't included in any application guidelines. They didn't even bother to try the applicant's product, look at the code, or consider user feedback; they only stared at the GitHub page.

If opensats is truly going to insist on this formalism,

then they should just change their name to "Little Green Dot sats."

—Because in their eyes, a row of little green dots is more important than real users and product value.

They would rather fund projects that nobody uses but have many little green dots on GitHub than listen to the voices of real users.

https://freerse.com/

Reply to this note

Please Login to reply.

Discussion

you got an explanation of why it was rejected? how?

The reason for the rejection was that Freerse's GitHub repository lacked development and update records.

This was because the development had previously been done locally. The code was only uploaded to GitHub when applying for funding.

I am now going to start committing every line of code individually so I can get more funding.

GitHub last updated on: "Semisol is typing" 🤣

You've mastered the secret. You will succeed. 😂

Build nonsense roadblocks get nonsense solutions

Truth

I wonder if you can just backfill "activity" by just setting the time on your commits:

Generate a list of all the files in the git repo.

Delete the .git dir

git init

Commit each file with a date in the past with some kind of bash one liner feeding each file into:

git add filename && git commit --date "X day ago" -m "wrote filename"

git remote add origin

git push -f -u origin main

Moss, just do that. Start committing a bunch of small changes and reapply. This is the type of hoop jumping that has to be done in the fiat world to get around nonsense regs. Ironically very similar vibes here.

Should make a commit announcing the completion of a feature, but then over the course of 6 months every day commit again. Each commit is a bug fix and slightly obfuscates your code, with each commit being a small patch becoming reading more haggered and despaired. At the end, the commit messages just read "please work, just this once"

Productivity™️

Do we get extra grants for nice art in commit contribution graph?

https://github.com/mattrltrent/github_painter

Thats the spirit! 😂

Just because you are developing locally doesn't mean you wouldn't have a large number of commits over a long period of time when you do push it.

I don't know how you can build something non-trivial if you aren't doing commits every time you solve a problem. If you don't work this way, how do you step through commits for debugging etc, and how do you checkout a previous commit to figure out where something broke?

We actually developed Freerse in a private GitLab repository, and only made the code publicly available on GitHub when applying for OpenSats funding.

Our development workflow included numerous local and private commits, which is why the full development history isn’t visible on GitHub.

The stability and full functionality of the Freerse app, along with real user feedback, are the clearest proof of our continuous development work—even if the commit history wasn’t publicly visible from the start.

It's funny that you can get those little green dots just by having a pipeline that successfully prints Hello World, yet has no bearing in the correctness of your code or the successful creation of build artifacts. Amateurs 😂

incredible

Oh those green dots

Vibe coded something 😅

https://github.com/blckbx/green-dot-scam

Little Green Dot ✅

You gotta vibe the other thing. I didn't understand which green dots they wanted. Actually, they wanted the commit history to have daily green dots.

nostr:nevent1qqsxldj6ddjwe2ctzuf2w9wss57ezzkgue9ahlvsrxljuepjctrk7xspz3mhxue69uhkummnw3ezummcw3ezuer9wcpzqlkh6hp6hur058qq7u0c0xzkw605dtyjx4xp9xe764tz2p5j0csqqvzqqqqqqyqczte6

Haha you are right. It works. CI updated to backfill 365 days of commits.

🤣🤣

variance needed

To fool opensats? Perhaps not.

absolutely

You effortlessly accomplished what took us a year and a half to build.

nostr:npub10pensatlcfwktnvjjw2dtem38n6rvw8g6fv73h84cuacxn4c28eqyfn34f is basically funding those little green dots.

Oh hahaha I just saw what it did 👌👌👌👌