Oddbean new post about login | logout The 5-star manual entry seems very "We just figured out 1-click shopping carts".
@franzap is a 1-5 star rating system maxi
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.
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.
If there were a two way relationship between the 'application profile' in the app store NIP and the 'repository announcement' in nip34, then clients could associate those ratings with both things. currently it is one way (nip34 announcement is referenced by the application profile event).
If it were bidirectional, then I could click on a link in GitWorkshop and it would open in Zapstore and I could download the release there, right? And do we bookmark repos and rate releases? Are those two different levels of information?
Like, the ngit binaries are on the GitWorkshop web page, but they could theoretically be in the Zapstore, I think. That would mean that you could issue the binaries as an event and just display the newest event in GitWorkshop. Or does that make no sense? 😂 I haven't used Zapstore, yet.
As of yesterday they are now in zapstore. I plan to display all releases related to a git repository in gitworkshop.dev
Oh, cool! I need to check out Zapstore, I think.
Yeah, it is pretty cool
Wow, that's an exciting integration.
I know right. its the magic of nostr. it is why we keep showing up.
a repo might have an iOS, Android and Web application profile, and the opinions of those profiles should be somewhat separate because the UX might vary significantly. I think opinions are more likely to be made against the application profile than specific releases. I'm unsure of the best way to gather opinion heuristics in this area and how to display them to the user.
Ah, right, so it's one repo to n applications. 🤔
yes
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.
*rate
I like the ⭐ bookmark, idea, and combining that with the other data to create a rating. Bookmarking a repo or a movie or book seems very high-signal.
Yes, public bookmarking is extremely high signal. It's in the "Share" category for me because it can take many shapes: - share to your own public bookmarks - share/host in a community - share in Stories - ...
Zaps and replies are high signal, true, but you need relative measuring here which they don't provide. You might have an excellent app that got 2x 21 sats, vs a mediocre app that got 10x 5 sats but simply because it was discovered a bit earlier. The computation will give 2 stars to the former and 5 to the latter? Plus, you introduce another thing to trust (the computation). Ratings are signed by users and are incredibly low friction - in the context of wanting to rate something, write, zap, etc
Don't see a rating event described, yet. Don't know if the newest version is published. https://github.com/zapstore/zapstore/wiki/Sample-app-events
Not writing ratings yet, we were just talking about it. @nielliesmons 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.
Ratings statistical noise, to be honest, and not as signal-loaded as our other data. Other places need ratings because they don't have as much other data.
Sure, I will only be persuaded when I actually see a computation yielding decent ratings from zaps and comments. Sorry if I'm very skeptical.
Challenge accepted, sir. 😁
I can already tell you that the rating for this thread is off the charts 😅
Don't you think Amazon has plenty of review data? They can verify purchases. Why do they keep using stars?
Damn near impossible to roll back a primary feature that you popularized. 😂 Everyone would totally freak out, especially as they would keep generating ratings and sorting and etc. and everyone would be creeped out. Lots of apps get stuck with emotional technical debt, like that.
Besides, they do so much computational magic on the stars that it's basically closer to what we're suggesting. They only count the stars directly, if they think the rating makes sense and is useful. https://www.wired.com/story/amazon-stars-ratings-calculated/
I don't care about what Amazon does with stars. I just want a 5 star rating for books. You guys can do whatever you want with the system for other stuff... But every book app I've used has a 5 star rating system that I tend to prefer for reasons stated below.
“emotional technical debt” Nothing is purely technical and nothing is purely emotional. https://media.tenor.com/B-TP3rs3l7IAAAAC/memory-cant-remember.gif
People get emotionally attached to UX. Like how there are often fields in online forms that the company doesn't need, but they have to put them there because people get upset if they aren't there. So, they just collect it and store it, but don't use it.
Yup, exactly why 80% percent of the time copying Big Tech UI/UX isn't a graat idea. We have a chance to do something new here, where the user has to perform and understand way less actions. Big tech can only dream of letting their users reply on, zap and share literally everything, so they invented a bunch of proxy features. They had to make these features look and feel like lottery machines because otherwise no one would even use them. We don't have that problem. If you do, you're designing it wrong. Replying, sharing and zapping are examples of some if the most natural UX you can find.
#bigtechcope
Have you thought about badges?
