Well, it's easy to implement and simple to understand. You could add those into the subjective, overall score.
Where are you writing the ⭐⭐⭐⭐⭐ @franzap
In a label? I'm assuming that zapstore will let us rate repos.
Login to reply
Replies (4)
If I rate a repo on GitWorkshop, can that get included in the Zapstore score? Don't want to have to rate the same sort of thing in 15 different apps.
Don't see a rating event described, yet. Don't know if the newest version is published.

GitHub
Home
The social permissionless app store. Contribute to zapstore/zapstore development by creating an account on GitHub.
You don't want to rare anywhere.
Zaps, replies and shares are enough. They are universal things you can do on any content type. They are high signal and users do them anyway fir other reasons.
LLM's and other types of computation can pick it up from there and show you whatever kind of synopsis stuffed to the aircofuck content type / user preference.
If you prefer your synopsis to have some kind of ⭐⭐⭐⭐⭐ rating, go for it. But I'm not entering those.
Not writing ratings yet, we were just talking about it. @Niel Liesmons is totally against them. I'm not, I think it's a short way of expressing an otherwise written opinion (plus its low friction).
I would use NIP-32 (on a NIP-94 file metadata) for rating a release. I don't think it's equivalent to rating a whole repository. First because it's fine grained (release) and because it's the actual product the user is using. The repo is way more general and upstream.