Avatar
fmar
30782a8323b7c98b172c5a2af7206bb8283c655be6ddce11133611a03d5f1177
I like freedom and to build stuff Building dart NDK Devops at nostr:npub1getal6ykt05fsz5nqu4uld09nfj3y3qxmv8crys4aeut53unfvlqr80nfm #bitcoin #nostr #hanggliding #sailing #batucada #diy #powerwall

Don't get addicted to #nostr too much.

Put your phone down...

#handmade #moments ❤️

https://music.youtube.com/watch?v=wxcVuE8keGo&si=V_aX89_ze8NPfNVf

Replying to Avatar fiatjaf

There are no out-of-the-box implementations except in JS.

How can anyone even figure it by themselves if there is not a high-level explanation of what is that they should be figuring out? I wanted to ask nostr:npub1xpuz4qerklyck9evtg40wgrthq5rce2mumwuuygnxcg6q02lz9ms275ams to implement it on Yana, but I didn't even know how.

It's weird because he has an infinitely huge feature list and is implementing everything he can see, but perhaps he didn't realize the outbox model was a possibility?

I am aware of the gossip model nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6.

Actually when I first started using and researching nostr what I immediately imagined how it would work was what is described in this gossip/out-of-the-box.

I was actually surprised that most clients don't do it this was.

It is what it feels natural and more decentralized way of reading content from people you follow.

I realize it is much more demanding to implement in a way it doesn't explode in terms of data usage, memory consumption and overall client stability.

But I'm determined in giving it a try in nostr:npub1gp4xzpmluelsakjtayc4wtzj97fhj5kakqjvsannu00xkdlf4x8s0xdqyq. I hope others will also.

Nostr meetup today :)

Brain overdrive

Replying to Avatar fiatjaf

Yep. Written in dart/flutter.

Android and linux versions should work.

Web version doesn't still work very good on some browsers + some issues with CORS to resolve.

iOS version still to be confirmed by some apple freak that it works when sideloading the .ipa since I don't use apple stuff.

Windows and Mac can also be built either manually or using paid codemagic or similar in future if there is demand.

Hoping to get more devs/UXers to contribute.

Donated sats/zaps will be split among everybody that contributes.

I agree that for LN non-custodial on mobile like nostr:npub1mutnyacc9uc4t5mmxvpprwsauj5p2qxq95v4a9j0jxl8wnkfvuyque23vg it brings new UX challenges, but with recent work on auto-accept and more research on background services I'm convinced it'll get better.

And non-custodial non-mobile like if you're running your node on umbrel or start9 + NWC backend connected to your node its already pretty sweet one-tap zaps UX.

What do you mean "a centralizing factor"?

I don't think you should limit the flexibility of what a client can offer in terms of wallet interaction.

The same way you present on nostr:npub1mutnyacc9uc4t5mmxvpprwsauj5p2qxq95v4a9j0jxl8wnkfvuyque23vg a list of nostr profiles you zapped, a nostr client should be able to present the list of transactions you sent/received from different profiles, grouped/filtered by several preferences.

I want to break free...