Avatar
Niel Liesmons
a9434ee165ed01b286becfc2771ef1705d3537d051b387288898cc00d5c885be
Designer that codes. Also #WordStudy #Dadstr #Farmstr

I thought about displaying those zap messages like that too, but as a creator I really wouldn't like zappers being able to hijack my pages like that (at least not in this app). They can put anything in there, penis butter and all, and I'm guessing creators will like the zaps but hate the spam management.

A hover like this solves the same goal in a cleaner way and allows you to show more information about the zapper without the user having to go straight to their profile.

On click (and for mobile) I'd open a modal that lists all zaps + messages and shows the total. Still have to draw that out.

"You wouldn't zap a car crash" someone very wise once told me πŸ˜‰.

Thank you again for that perfect example of the difference between paying attention to something and valuing something.

Replying to Avatar franzap

Seems like nostr:npub1u5njm6g5h5cpw4wy8xugu62e5s7f6fnysv0sj0z3a8rengt2zqhsxrldq3 is working on something very similar, did you guys sync up?

I recently shifted my thinking around these complex kind of attestations, it's going to be hard to: (1) implement with good UX to actually make it work, (2) too many different opinions on how to go about it

As an example, bitcoinmints.com is already working today with kind 38000 which is definitely an expression of trust. The WoT implementation you suggest will not take into account these events? Another, if a very trusted friend (because met IRL) heavily zaps someone you don't know, isn't that a form of trust? Third, if someone is listed as "good guest" in kind 827919 for a couchsurfing-type app, isn't that a massive vouch even without signing a NIP-77 event?

Seems to me expressions of trust take very different forms, will be application-specific and therefore we should accept them as such. I'm tending to think that "writes" should be as easy, heterogenous and scattered as possible and the heavy work should be done on "reads", probably via sophisticated algos/DVMs which: (1) return a viable set of evidence to be verified client side, (2) themselves have a reputation

Exactly! Love the Read vs Write angle you use here.

And indeed, easy writes are key. Explicit trust attestations are not easy.

Replying to Avatar PABLOF7z

(Read in nostr:npub1guh5grefa7vkay4ps6udxg8lrqxg2kgr3qh9n4gduxut64nfxq0q9y6hjy 's voice)

πŸ“’ NDK VERSION 2.7 HAS BEEN RELEASED

Massive performance improvements!

* A queueing system is now in place to fetch NIP-05 and ZAP endpoint information. Most applications should feel much faster.

* Caching of NIP-05/Zap endpoints is now in place too

* Threading utility functions to make displaying threads PROPERLY (properly defined as how nostr: npub1dergggklka99wwrs92yz8wdjs952h2ux2ha2ed598ngwu9w7a6fsh9xzpc likes it)

Along with NDK 2.7:

ndk-cache-dexie 2.3 is now live

ndk-svelte-components 2.2.11 is now live

One step closer to the asymptote

Hooooray 🧡

Loving where you're going with those chat bubbles.

I had some issues when I started trying that do I'm curious how you're solving those in the threads.

Black market farming > Self-sufficient Homesteading #farmstr

Satellite relays are shaping up to be a big deal, damn!

An elegant solution for way more than just public communities, built on a solid foundation of Nostr, Blossom and Biomimicry. #decomodditize

nostr:nevent1qvzqqqqqqypzp978pfzrv6n9xhq5tvenl9e74pklmskh4xw6vxxyp3j8qkke3cezqyghwumn8ghj7mn0wd68ytnhd9hx2tcppemhxue69uhkummn9ekx7mp0qqszzrxjnzc7ll6dx6900ddcst3vqsvhqhxyt8d6k04kn9qdvzunq8gqkq27p

Holy f*ck! nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr you beast 😍.

That's like all my suggestions πŸ‘€.

First client to incentivise #v4v zaps, awesome!

An app developed by people without the balls to walk the talk