Found a yuge memory spike in the zap.store app during APK hash computation.
Good news: replaced the read-file SHA-256 digest with a streaming one and memory remains flat! Also, no apparent memory leaks after an hour of profiling, constant ~100MB. Hoping this will solve crashes and sluggishness some of you experienced 🤞 will go in next release 0.1.3 soon
Keep me in the loop guys
Hard problems 😅
Sure we'll incorporate multiple curators (so nostr:npub1r0rs5q2gk0e3dk3nlc7gnu378ec6cnlenqp8a3cjhyzu6f8k5sgs4sq9ac can use it).
Idea is to show various trust metrics (I also dislike scores) for the user to make a decision whether to trust/install the app or not. Domain names are fiat crap, sure, but they have value so they're shown. The app itself can completely change how trust is assessed, you might not care at all for an alarm clock app but care a lot for a bitcoin wallet.
But no matter how you slice it, the web of trust will ALWAYS be involved. Curators are simply someone you decided to trust. "Known people in the space" are also because people you trust, trust them and we need to validate that. I can assure you I can spin a full clone of the existent ~25k and ~180k connections in have in trustgraph and have Gigis, Odells, etc.
Re: avoiding impersonations, it's my next plan for trustgraph (i.e. probability of impersonator, given your 2-3 hop graph) - I was discussing that with Niel the other day.
It could serve to connect with people and discover spots in your own city, without ever traveling
GM nostriches ☀️
(nostr:npub1a00wj229auzjswlq4s77y4u8eqdx5k9ppatgl8rtv8va65f6mwksum9q3h speed up production before I go blind!)
Not saying it's wrong to have a closed-source product in the freedom tech space.
But it's uncommon and fishy. Especially if you're dealing with money and personal data.
How about having the guts to openly explain why you're NOT open source?
Maybe that would inspire more confidence in your product?
nostr:npub1uq70uqgas9pyhds2zt57kr9se8rg3s68ztphjnq82ts8rzeknmeql7u0c2 mind explaining us why you are not open source?
https://github.com/fedibtc/fedi-alpha looks open to me? Most native apps hold the nsecs like you said. Very few apps support Amber. Amethyst and 0xchat are the only two that come to mind? I wish more did. Having a built in NIP-07 signer is amazing. That makes me incredibly excited because the vast majority of Other Stuff apps on the web are not used or when used, people enter nsecs into them. This will be a massive help to Other Stuff adoption and be secure for users.
Got it. Fedi is acting like a sort of Amber with a browser with window.nostr - I love the idea.
However, Amber is free and open source code and afaik has reproducible builds.
But that Fedi repository has zero code. Just a README file? I don't even know why they have one. They could easily be sweeping people's nsecs and no one would know.
How would we design a Nostr-only phone? nostr:npub1qny3tkh0acurzla8x3zy4nhrjz5zd8l9sy9jys09umwng00manysew95gx
I'd rather have a freedom phone, where I can use nostr if I want to
That latest version of nostr:npub1uq70uqgas9pyhds2zt57kr9se8rg3s68ztphjnq82ts8rzeknmeql7u0c2 is powered by Nostr. I didn't know this. Fedi accounts are Nostr npubs. Fedi also includes a NIP-07 signing extension allowing you to browse and use the Other Stuff of Nostr with ease. I saw a handful of Nostr apps included on this "apps tab". They just work. You can also export your private key to use the key in other apps. And soon, you'll be able to import your existing private key. Mind is blown. Super bullish.
"Fedi accounts are nostr npubs" means they hold the nsecs, or you can log in with Amber or similar? And they are still closed-source? What makes you so bullish?
Thanks to my friends nostr:nprofile1qy88wumn8ghj7mn0wvhxcmmv9uq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tcqypuu9jhpzn4z32vpua2eknl8s49ywdfp4rfz5e4m4w06yj8tsg8lvp59hvv and nostr:nprofile1qy88wumn8ghj7mn0wvhxcmmv9uq3zamnwvaz7tmwdaehgu3wwa5kuef0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qgewaehxw309aex2mrp0yhx6mmddaehgu3wwp5ku6e0qyt8wumn8ghj7un9d3shjtnddaehgu3wwp6kytcpzemhxue69uhk2er9dchxummnw3ezumrpdejz7qgcwaehxw309ahx7umywf5hvefwv9c8qtmjv4kxz7gpzdmhxue69uhhyetvv9ujue3h0ghxjme0qyw8wumn8ghj7un9d3shjtngd9nksmrfva58getj9e3k7mf0qyd8wumn8ghj7un9d3shjtn8v46xzmrz0yhxxmmd9amrzqpqvwymuey3u7mf860ndrkw3r7dz30s0srg6tqmhtjzg7umtm6rn5eqn7um26 for encouraging me today to take a break. I've been feeling burnt out lately, despite the absolute privilege of being able to develop on nostr, so for the first time in probably around 8 years I'm going to take a 2+ week vacation this summer. No code, no nostr, no email.
This will hurt me more than it will hurt you. But it'll allow me (Lord willing) to come back fresh and ready to tackle the next steps of making Coracle the nostr client it needs to be.
Not sure yet what I'm going to do with myself for two weeks — but I have a hunch taking my 8 year old son on a backpacking trip might be part of it. I've always wanted to see Mt Rainier up close.
Super important, enjoy!
This is fucking cool nostr:npub1q3sle0kvfsehgsuexttt3ugjd8xdklxfwwkh559wxckmzddywnws6cd26p . Congrats.
I really like the UI. Signing a ton of random events, not so much.
Can't wait to implement zaps in zap.store. Really hoping this will move the needle for independent developers
nostr:npub1arkn0xxxll4llgy9qxkrncn3vc4l69s0dz8ef3zadykcwe7ax3dqrrh43w is a daylight enjoyer w/ nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft
He meant scrolling **nostr** 😂
jealous ngl
Found in my drafts archive 😆 #goals
LLM that summarizes github issue threads?