it is helpful since i have a natural personality that gets addicted to things. This is why i have reactions turned off, i find myself trying overthinking why one post did better than another. I end up gamifying everything instinctively.
nostr allows me to craft an experience where i can just post my thoughts without falling into my bad habits.
#onlyzaps
nostr:note13mny52me5uc7x924qe98ywxuwfcac9fey34p3cepuqq79saef4qqsypze0
I can't imagine what his feed is like, but I'm totally addicted to Nostr. I love talking to y'all so much that I now spend my touching-grass time meeting up offline. 😂
now i’ve replaced reactions with zaps… i like to think its better somehow but maybe its not. At least its higher signal… or something
We won’t know until we try
I have to disagree with this. This is not part of the protocol this a decision of the app developers. Sure you can have that experience but not developing search or discovery algorithms on top of Nostr does affect discoverability and for a person who is not privacy or Bitcoin focused Nostr seems dead
i think the point is that Nostr affords client choice and therefore enables this for those who want it.
Had this issue when I first joined, took a lot of work to find content not bitcoin or even Nostr related.
Don’t see the avg person taking the time I did. With that said, I think more engaging apps will be built soon
definitely it's a client thing, and there is a particular culture among the client devs that is sticky and in some ways stupid.
i don't think there is anything wrong with notification alerts but practically everything on the internet these days those things hardly work anywhere anyway, so it's not even that abnormal actually, that the clients aren't writing this into their apps.
the other thing is that the client devs are terrible at actually programming properly threaded everything, most of them couldn't even handle that background worker stuff to actually implement it.
even among relay devs there is a pretty cruddy understanding of how to do multithreaded stuff, it's either over the top ridiculous or nonexistent. in my work i plot a middle course where i avoid threading unless the task calls for it. queries, for example, should not be threaded because they are supposed to be sorted before delivering, but fiatjaf and his forkers all use event queries that randomly spew events back in whatever order the database returns them. this is an example of where they are putting threads where they don't belong. and in part the reason for it is their database query engineering skills are also underdeveloped, so very often the queries don't run properly reverse chronological order because out-of-order storing of events that happen to match a query that is made later come out in the same order they went in, not in the sort order the spec says they should.
so there's a LOT of problems behind what you see on the surface, and a lot of cope, justifying their incompetence with shitly implemented clients and relays, by some aspirational contrarian take. the reality is they are amateurs and have barely a CS degree (even at today's lax standards) between them.
🦄🦒🐬♐️🏔️🚂🐸
I do find reactions make me overthink as well. I always thought comments was a higher signal anyways. I’ll try turning them off. The only time I used them is by mistake anyways
