Replies (134)
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.
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.
My worry is that it's going to be a hot data mess to wade through, if we end up with ratings in different types of events. I mean, you can always crunch the numbers, but it seems like a waste of processing, if we just have to crunch because we didn't bother to write down a suggestion for where/how to document it.
They already finished the librarian app, with ratings in it, and that data is going to be swirling around, already.
But, whatever, Nostr will melt the glaciers. 😏
Like, we could end up with Bookmark ⭐ , Label ⭐, Kind 01 ⭐, Embedding ⭐, Emoji ⭐ (overloading the other emojis, see it coming), etc.
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
- ...
Ah, right, so it's one repo to n applications. 🤔
Oh, cool! I need to check out Zapstore, I think.
Wow, that's an exciting integration.
I'm trying to figure out which events you're using, so that we can be interoperable.
Yeah, that's what we're saying. Rather than promote the idea of 5⭐, we can just do ⭐bookmark, like you were planning, and combine it with all of the other data we have.
My question is: where to put the 🌟?
😂 Devs will be putting the 🌟 all over the place.
🫂 fr fr no cap
That's true. 😂
Did you see that I accidently gave my own relay only a 3-🌟 rating? 😂
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.
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
Ah, okay, so we're doing ratings in labels. That's where I would put them, too.
Have you thought about badges?
I've never used fediverse stuff so I'm not very inclined to start at this point. But thank you for pointing it out as that might be something else to look at for inspiration!
Challenge accepted, sir. 😁
That's cool... But exactly what I don't want to do. I don't want to use email for anything anymore. I want to be able to use my key pair.
😂
My stupid phone was having trouble loading, so I accidently clicked the wrong star and didn't notice. 😂
Yeah, I was just curious about whether that was on your roadmap.
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.
WIRED
What Do Amazon's Star Ratings Really Mean?
Amazon says an item's stars reflect the “average customer review,” but the calculation gets more complicated than that.
I do. Often. I prefer a 5 star system based on this:
1 star: just bad
2 star: meh
3 star: ok
4 star: good
5 star: excellent
Given my original use case for this, books, a 5 star system is pretty much mandatory, IMO. 1 is not enough as it just signals that it's of interest, but not WHY. Three is better as you can indicate positivity, neutrality, or negativity, but nothing more. Ten stars is dumb and I have no use for it. Therefore, I prefer and will always advocate for a 5 star rating system for books. Other types of media are fine with a 2-3 indicator system. (Old school thumbs up/down are useful, and effectively a 3 indicator system given that you would have to really like it dislike something to bother with giving a thing a thumbs up or down.)
Testflight... Meaning iOS... Right?
😮💨
And including bookmark ⭐, of course, which is essentially a recommend on/off.
Does fountain actually work correctly as a podcast platform, though? I really can't stand an app that crashes all the time in the middle of just playing an audio stream. I'm weird. I don't like the idea of that much nostr on an podcast app, and... AntennaPod is just a better interface and it's 100% reliable.
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.
Are you putting the ratings in labels, like Zapstore wants to do? Is it an integer from 1-5 or something?
Or are you just using bookmarks, for a binary rating? Or are you using 👍🏼👎🏼 emojis?
We have an Android and web app, API soon, too. The community is open source, the rest we’ve been working on since 2018 and is already a C Corp in DE, so the recommendation app is private repo. A version of the API will be open source. I’ll be doing a demo on HiveTalk soon.
Oh dear... Look at what I've started. Sorry not sorry. 😏
The Beave
I want there to be a bookstr app, kinda like goodreads, but without the gross big tech BS, utilizing the interoperable nature of nostr keys to be able to connect with others and do all the bookworm stuff that one can do.
I currently use openreads (find it on F-Droid) to track books I've read. I wonder if that could be used as a starting point?
#daydreaming #otherstuff #bookstr #goodreads #foss #builditbetter #devs #reading #books #avidreader
View quoted note →
Oh, dang! Go you!
Yeah, I know. 🫂
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.
5 star rating systems are used by data driven tech companies which have huge resources to study their effectiveness, such as Amazon. The fact that they haven't moved away from it is signal that its useful.
We use a 5 star rating system in the LibrarianBrain.com data set
Okay, if it's closed source, but can you tell me which events you're using?
Which event kind do you store the rating in? Like, which NIP are you using for documenting the rating?
I don't know that they _can_ move away from it, as people really enjoy clicking on the stars and actively "voting". It's cathartic, for the user. So, the usefulness is probably more about retaining user loyalty than merely gathering high-signal information.
A lot of the ratings are just garbage, like trolling mobs, bots, the competition, or idiots complaining about the package being dropped by the postman, or whatnot. They quietly drop or underweight all the garbage, and overweight their power users and real customers, to keep the overall rating relevant.
alright😄
100%
I couldn't care less about that. I just want to use a 5 star system on a book app. Big tech gets everything "wrong." let's not bother with that fiat mindset.
interesting
1-4 is bad bad bad. 4-5 is good. It's actually a binary system because almost everyone who doesn't hate it, gives it a 4 or 5.
Items with lots of ratings usually have 4+ because of the way things average out, whereas newcomers and small businesses tend to have terrible ratings because one bad rating can skew the whole scale. You can terrorize or bankrupt small companies or creators with a few bad :star ratings. So, if they get some bad ratings, they will often ask friends, employees, etc. to login and give it some more good ones. 😅
I get attached to UI because of functionality. I hate big changes. Prime example for me: Waze. It's really gross now.
I read, somewhere, that a perfect rating is actually 4.7 because 5 sounds too good to be true, so some companies write a couple fake bad reviews, to get below a 5.0. 😅
That makes sense to me.
I think it's funny that you think the bad thing is not the 5⭐ system, it's Amazon's attempt to protect small business owners from malicious and idiotic raters.
Anything strictly numeric, with little or no cost, will be gamed.
I get that the incentives are skewed. but they are pretty effective at attracting and retaining large number of users. to achieve this they do heavily surveillance on user activity, many iterations of a+b testing tweaks to their UI to create UX. If we can learn lessons from them, so long as we critically evaluate knowing they are prioritise attention and retention above satisfaction and well being.
completely agree
*sighs*
There's a lot to unpack in that one statement, as usual.
1. IDGAF about businesses, in general. The app/system I want is not a business. I want to be able to rate and share book recommendations with fellow nostriches.
2. I can parse BS reviews from others. I know that's not a universal quality. I am ignorant of how things can be "gamed" since I don't think about things like that and am more honest than most.
3. I suppose my view of this is rather myopic since I don't expect this to be used by very many people for a very significant period of time. I'm overall very skeptical of nostr super-adoption, so... I can deal with a preferably simpler system at the beginning that is coded to be flexible enough to add in enough Pow to prevent gaming later. Start simple, but start!
All of that is only relevant if you're building a business to make profit.
This is not that.
Stop bringing that stuff into the nostr protocol. It will poison the well.
What do you mean by that stuff?
I'm a big privacy advocate and hate the heavily surveillance of user activity which is used to dominate and control us. but we can use their learning to improve user retention and provide better experiences.
IDGAF about "user retention."
A better experience is just a very simple, clean, easy to understand UX that just works. I know how that should function at the user. The bank end stuff is what I don't know Jack about.
A clean, simple, straightforward user interface will do the most to "keep users coming back."
You only need to stick to:
-automagic book lookup by title, author, barcode, or ISBN
-automagic cover lookup for said titles, as an option. I know some don't care for the clutter of book covers in a clean list view.
-three lists: reading, to read, read
-ratings upon completion
-it's not hard, I guess, to also allow written reviews but I don't think that's necessary for a first iteration
-nostr connectability to the whole ecosystem, but specifically to be able to share links to books, reviews of books, and curate a separate list of connected npubs to "follow" and possibly another list of npubs to "push notifications to" when I book is finished/reviewed/added to the list "to read" list
-further iterations might include a user curated and "recommended list" that others can easily add to their "to read" list, in part or total
But at this point I really should be doing my fiat mining job instead of building out all the app features.
My point is that I really don't care about concerns of retention. That's not at all a metric that matters to me, as a user.
Another thing to consider is that people can rate the raters. The information is bidirectional. (Like, on AirBnB, people who have left others bad ratings are more likely to be turned down by the next place. Or an author that leaves bad reviews on other people's books opens himself up to having them leave bad reviews on his books. Someone who rates products as sub-4 might find that other companies send him out-of-stock notices, instead of sale confirmations.) And this bidirectionality would be even more leveraged, on Nostr, as it would hurt your overall WoT score and follow you around.
That means there's a natural disincentive to give bad ratings, as they can boomerang, so you either need to be such a top expert, that you can afford to be critical (and hardly anyone is) or you only give good ratings or no ratings.
I'm pretty immune to issues like that since I have very little concern for "my reputation" at large, only that my friends know that I am trustworthy. Outside of that, IDGAF. If something is bad, it's bad. I can separate a badly written book from one that I disagree with. I have very little issue going against those types of incentives.
I know that I'm rare in that way, but... It annoys me that those are even consideration that people worry about.
Keep things simple, iteratively improve. Deliver a working product then improve.
1. Authors are creators and therefore producers. That's a business, even if they aren't expecting monetary profit. It's negligent to put something so destructive into place, without even thinking through the consequences.
2. Has nothing to do with honesty and everything to do with decades of experience in data analytics and UX. It would take someone 1 hour to create a script that just spits out fake ratings from random npubs.
3. Once you get everyone used to the 5 ⭐ system, you can't roll it back in your app.
4. The ratings are only useful, if there are a lot of ratings. The thinner the volume of the ratings, the easier they are to game. That's why a lot of websites actually hide ratings until they have at least n number of high-quality ratings on the item.
I was there and it was a fun discussion 🙋🏻♂️
I will have to bow to your decades of experience in this field. I couldn't care less about most of what you mention, too be honest. As an aspiring author, and one with strong opinions and also the tendency to put very unpopular ideas into my writing, I expect that my books won't be popular with certain (woke) subsets of readers, and could expect bad reviews from many people. I just don't care.
I suppose it is still wise to take prudent steps to mitigate scripting attacks. One stupidly easy way is to have a simple "freemium" model where you can use the entire app for free, but if you wish to push your reviews to others/in public, you would need to pay a significant but not egregious amount of sats in order "go public."
This would also help fund development while simultaneously preventing tons of new bots from ransacking the system like the Goths in Rome. If someone wanted to spend that much to leave bad reviews, cool. It's funding the app. I would still consider that a win for the overall system.
Thoughts?
As a creator of tools which I hope will bring value to those who use them, user retention is a useful measure of whether user received value enough to return.
The product you want has already been built. Use that one.
How would you figure that out without being intrusive? (That's mostly a rhetorical question to get me to think about how I would do it.)
I'd rather use sats as an indicator. If people will pay for it, it's valuable.
See my reply to one of Stella's notes.
No, it has not.
I'm going to start a new thread for Building the MyLibrarian Community in Public #buildinpublic and share information there.
Communities in nostr: ew. (currently, hopefully not for much longer)
Have you checked out Ditto
No.
I am annoyingly churlish about wanting to only use two clients. I DETEST trying to do stuff on what should be a fully interoperable protocol on multiple clients eating away at my battery in the background. It's exceptionally inefficient and the reason why I also detest using skads of the raspis to do stuff when one, more efficient and much more powerful VM server can handle all of those things.
I love nostr, in theory. I hate nostr as currently implemented.
Yes, I realize this is unproductive and childishly stubborn. 🤷♂️
You’re 🎯 about the hot data mess. No way around that, ever. We may as well come to grips.
Which means that as a consumer of the hot mess, you’ll have to interpret data that comes packaged in multiple formats. Each external format needs to be interpreted into a *single common format of your choosing* so that you can synthesize them all together in a way that is of maximum utility to you.
I thought of the same thing, or even something simpler, like zap-to-rate, so that you have to pay the author, in order to post a rating. Then only someone highly-motivated would bother. Freemium would have the advantage that malicious raters could get their contract cut and their ratings removed, so that would pressure them to be behave and stay constructive.
But I don't know. I understand that some users like giving the ratings, but others find the pressure to rate really irritating and refuse to do so (which reduces the signal of each rating, as it's a self-selected subgroup giving the ratings), and I question whether other users benefit from the ratings on-net. They seem to mostly be a way to press the advantage of big players (number of ratings leads to higher average ratings, in addition to their natural advantage of simply having lots of reviews and customers/users/bookmarkers), and reduce the visibility of newcomers, as everyone sorts the results by stars.
I'm not saying that I'm 💯 against it, but I'd be very cautious in implementing it and I'd be aware that the implementation burns all data bridges. You put it in there, you have to leave it in there forever. No take-backs.
I can't stand Micro-transactions. One and done for me, thank you very much.
You did bring up an interesting twist, though... If somehow an author of a book is verified (my goodness, that hurts me brain thinking about), them getting a cut of review sats makes sense.
So now I'm conflicted. 😅 Thank you.
We have built this in a database we call the Librarian Brain, currently in Postgres, on which our apps run. Our social community is on Nostr. So events for social with NIP-57 for sure. Still starting to build ✨⚡️
Yes, but if the majority are interoperable, that raises the pressure on others to use the same event type for the same data type, unless they can prove that they have some novel use case that requires a different tactic. Which is possible.
Like, if Zapstore is using labels for ratings, I'll just use labels. I don't need to invent a new "rating kind", just to be a jerk about it. My incentive is to just go along, to retain interoperability and not preclude future use cases. That's part of the magic of Nostr.
Simplistically, if someone starts posting git events but then stops, then they havn't been retained.
Ah, okay. Postrgres sounds like ditto, right? We were looking into that, recently.
Well, I mean... would you mind people giving you bad ratings, if they had to pay you for the privilege of doing it? Authors could even determine their own price, right? Half a Bitcoin for a 1⭐ and you can put whatever crap in the comment and we're good. 😅 Two comments and I retire.
It’s true that if everyone else is using some specific format or nip for ratings, then it’s in my interest as a dev to adopt the same system. This is how we avoid a Tower of Babel type situation.
But it will never boil all the way down to a single global format that we are all forced to use. There will always be multiple formats. If we know how to synthesize multiple formats from multiple data sources together to answer a single question, like what’s does my WoT put at the top of my rec list, that’s a good thing.
Problem: how does my WoT rank widgets from top to bottom?
Data source 1: vendor follows, mutes, zaps
Data source 2: 5 star ratings of the widget from store A
Data source 3: emoji reactions on adverts of that product on a nostr classified ads client
And I’m sure we can think of MANY more data sources than those 3.
Edit:
Data source 2: 5 star ratings of the widget from stores A, B, C, and D, plus 0-100 point ratings from store E written by some pain in the ass nonconformist weirdo dev who uses a different format for reasons you may or may not agree with or even understand
So, if an npub goes dark. OK. That makes sense.
Answer: the grapevine method synthesizes all these data sources into a single score. If you want to buy a widget and your fav nostr store has listings of 1000 widgets from 1000 vendors, why not use ALL of the above data sources to rank those 1000 products from top to bottom?
That's, again, a lot deeper than I was thinking.
But, that could also be a bad thing. I don't think that it should be possible to set a minimum price per star rating. It would be better to have one price to rate at any star. If that's the system to go with.
That's a complicated set of math to do.
Yes but quite doable. Too much to do on the fly on the front end, but the heavy lifting can be done ahead of time on the back end.
I built a front end demo using only two data inputs (follows and mutes) which is how I realized it’s too much for the front end.
@npub1manl...n9tn streamlined the download process into a single click and you can try it out here:
http://grapevine.my
It will output the top 1000 recommended pubkeys minus the ones you already follow as a NIP-51 list which you can upload to a few clients (Coracle, Amethyst, nostrudel maybe?) and browse the feed when you get tired of you follows feed. Great way to discover new high quality follows.
@npub10npj...tl5h and
@npub1manl...n9tn and I are working on replicating the above but calculating scores on the back end using a relay that already has follows and mutes data, so no need to dump all of that onto the browser, much better UX.
So I did that and have no clue how to view that list on amethyst. Not your problem, just, trying to see the output.
Start out going to listr.lol and see if you have a list with “Grapevine” in the title
Can any #Amethyst users help a beaver out? How to import a NIP-51 list and browse a feed and whatever else you can do with it?
#askNostr
Your “My Grapevine Reccomended Follows” list was published to Nostr from grapevine.my. You can confirm this using listr. I haven’t personally tested on android (yet) but I believe you can make custom feeds in Amethyst, using Nostr user lists?
Ah. I see. It's just a filter that you apply, basically. I can't see see the list itself, it is just applied as a filter. That's... Not exactly useful. I don't see anyone new on that feed at all.
Yes. I just was thinking that I could view the list itself, not the filtered results of the list. Not as useful.
No one new? It should omit the pubkeys you’re already following when it builds the list. Did it not do that?
Didn't seem to. Mostly just my own stuff comes up. 😅
Yup. It's literally a feed of me. Kinda weird, TBH
I find listr useful to view the list itself. It’s easy to scroll down and check who you’re following and who you’re not.
At first we just exported the top 1000 and you’d get a mix of current follows and suggested follows, but then we figured we’d omit current follows so you’d get a fresh feed from high quality pubkeys.
Soon you’ll be able to generate multiple lists. With / without current follows; Grapevine page 1, page 2, etc
I see your list — yeah, didn’t populate it at all except for your pubkey. Check out my Grapevine list on listr to see what it is supposed to look like.
When you built the list were you signed in using an extension? Smartphone?
Yes it is complicated. But there are a “finite” set of these data types (Nostr event kinds that interact with other events in ways that may be interesting for WoT) to calculate.
There doesn’t need to be a standard of “which data types” should be used “in which manner” by clients. Some de facto standards may arise, while other algo inputs will only increase in complexity. Standards are not as important as adaptability.
For the foreseeable future, developers of WoT recommendation engines will have to keep their ears to the ground to adapt their algo inputs accordingly. But this complication does not need to be developed all at once or overnight.
Mind you, this is a new perspective for me. It’s much easier to just say “let’s make a standard”, to make development easier. But life IRL does not work this way. Life adapts. So we must learn to adapt as Nostr grows.
Today we do this. Tomorrow we do a bit more. Baby steps.
💯
The grapevine method is the best response I can think of to the XKCD on standards that we all know and love:
Yup. "Grapevine recommended"
I still can't see the list on listr. It's just... A block?
I can't figure out how to see lists via a different npub.
Yes. An extension (nos2x, IIRC) on an android phone with kiwibrowser.
+1
Let's goooow ✨
I can already tell you that the rating for this thread is off the charts 😅
So this thread kinda went haywire, but...
I still want a simple book tracking app that I can use to share and receive recommendations from fellow nostrich book lovers.
The Beave
I want there to be a bookstr app, kinda like goodreads, but without the gross big tech BS, utilizing the interoperable nature of nostr keys to be able to connect with others and do all the bookworm stuff that one can do.
I currently use openreads (find it on F-Droid) to track books I've read. I wonder if that could be used as a starting point?
#daydreaming #otherstuff #bookstr #goodreads #foss #builditbetter #devs #reading #books #avidreader
View quoted note →
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
We haven’t tested list generation on android — maybe that’s why?
On listr you can browse lists of other npubs. Search by username at the bar on the top. Or go to listr main page Activity Feed and right now I see one or two My Grapevine Recommended lists recently updated — the first two I click on seem to have worked (mostly) correctly (except only 878 items, should be 1000? 🤔)
🔥😂
🤣🤣🤣🚀
it's like -3 stars?
🤣 that burn, man
I get an error 504 when I click on your grapevine list.
I dunno what else to try. 😅
i'm getting excited
I hear that a lot.
That mostly works.
I can see the list, just not nyms or avatars, so I don't know who anyone on that list actually is.
Here’s what I see (not logged in)
lol make your dvm summarize this thread with 🌶️ rather than ⭐
Everything is populating on that list now. So that's cool.
But that's not the same as mine. It's just my npub and that's it.
Trying the grapevine thing again, it stalls.
Huh. It might have finished.
It's working now.
Using the hammer method worked. 😅
@7fqx was asking for that. 😂
Yeah you probably need to at least refresh the page once 🔨
I did... But I just had to hit it again. 😅
I still think this is a good idea.
The Beave
I want there to be a bookstr app, kinda like goodreads, but without the gross big tech BS, utilizing the interoperable nature of nostr keys to be able to connect with others and do all the bookworm stuff that one can do.
I currently use openreads (find it on F-Droid) to track books I've read. I wonder if that could be used as a starting point?
#daydreaming #otherstuff #bookstr #goodreads #foss #builditbetter #devs #reading #books #avidreader
View quoted note →
