Only works in Europe right?
This guy... the epitome of how *not* to live
If it's all from your perspective, what is the usecase here? Or you want to store all possible permutations? Sounds like a lot of events
What's beautiful about open protocols and free markets is that anyone can build however they please.
You will see the openest of open and the closest of closed and everything in between.
Yes, however sometimes this leads to eternal bikeshedding and I prefer spending that time building
I look forward to seeing your product including your DVM-NIP. I could easily offer PageRank, GrapeRank, follower lists, and all sorts of other scores by API to devs because it’s an easy thing to do, once the graph db is running.
But API was never my end goal. I love nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z ‘s suggestion of publishing the data using NIP 85, kind 30382 events.
That's great!
What is the tl;dr on NIP-85?
This is true, but freedom tech implies exactly that! You will get all sorts of approaches to solve different problems. Isn't that why we love free markets?
It is perfectly fine to do something behind a closed door for a little while and then open up to public discussion.
The "closed" period will be a blip in the timeline of what we want to do, so in practical terms it doesn't matter
My gut feeling tells me that this stuff should be done in a nostr-native way, ie with DVMs or similar.
Each server we add is just a cobblestone of the path that will eventually lead us back to hell, so we either have to do it locally or with stuff that's easily and dynamically replaceable.
Thoughts? CC nostr:nprofile1qqs04xzt6ldm9qhs0ctw0t58kf4z57umjzmjg6jywu0seadwtqqc75spz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz9mhwden5te0wfjkccte9ec8y6tdv9kzumn9wshszxnhwden5te0wpuhyctdd9jzuenfv96x5ctx9e3k7mf0dv4ph5 nostr:nprofile1qqsfnw64j8y3zesqlpz3qlf3lx6eutmu0cy6rluq96z0r4pa54tu5eqpz9mhxue69uhkummnw3ezuamfdejj7q6hdgd nostr:nprofile1qqszv6q4uryjzr06xfxxew34wwc5hmjfmfpqn229d72gfegsdn2q3fgpr3mhxue69uhhxct5v4kxc6t5v5hxs7njvscngwfwvdhk6tcpzfmhxue69uhkummnw3e82efwvdhk6tcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsk7wj75
I am building nostr:nprofile1qqstq4j6pk2sgaupru6l7ah9nq0dueafq356jllwcy7uzlek9yx7hlspz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz9mhwden5te0wfjkccte9ec8y6tdv9kzumn9wshsz9mhwden5te0wfjkccte9ehx7um5wghxyctwvshs4kprv3 with nostr:nprofile1qqs0dqlgwq6l0t20gnstnr8mm9fhu9j9t2fv6wxwl3xtx8dh24l4auspz4mhxue69uhkzat5dqhxummnw3erztnrdaksz9rhwden5te0wfjkccte9ejxzmt4wvhxjmcpzemhxue69uhhyetvv9ujumn0wd68ytnzv9hxgxmpqkh to provide nostr profile and relationship information ("web of trust") in a usable and actionable format for clients to enhance their applications, such as spam prevention, ordering by relevance, getting follow recommendations, etc.
Every single service is a DVM and I am finishing drafts for a DVM-NIP that I want to propose, and get community feedback. nostr:nprofile1qqsw2feday2t6vqh2hzrnwywd9v6g0yayejgx8cf83g7n3ue594pqtcpzfmhxue69uhhqatjwpkx2urpvuhx2ucpz4mhxue69uhhyetvv9ujumt0wd68ytnsw43qz9rhwden5te0dehhxarj9ehhsarj9ejx2as0shs37
This is the way - not proprietary APIs.
Read it. Agree with the general idea and I'm definitely not against corporate led initiatives. I think it's also misleading to associate nostr with the bazaar that is described there. Just like with the Linux kernel, there is strong protection of NIP-01 (and a few others) here. It is not up for grabs.
A major omission here is: protocols. We are talking about networks and network effects not products, as most of the examples he gives.
Regarding growth, I don't know where those numbers come from but I'm sure nostr has a way bigger brand than Pubky. It's simpler to understand, too. I perused Pubky docs and there is not a single hint on how to build anything. I'm also lost with so many brands: Holepunch, Pear stack, Keet, Synonym, Hypercore, Pubky, etc.
And John is a perfectionist. I understand because I am too. It has its good and bad sides. Specifically to bootstrap a network and get network effects a perfectionist approach does not help. Just to give two examples OSI was technically more perfect than TCP/IP, Betamax was technically more perfect than VHS - and they both lost. I'm focusing on building something great but NOT at the protocol level.
Not very comfortable with having only one player directing the protocol. Seems risky to build anything on there
Can't seem to find this on zapstore nostr:nprofile1qqs8y6s7ycwvv36xwn5zsh3e2xemkyumaxnh85dv7jwus6xmscdpcygprpmhxue69uhkv6tvw3jhytnwdaehgu3wwa5kuef0ekucf3 or is this/just a desktop thing?
It's alpha software, but I'm hoping at some point they will publish it
nostr:nprofile1qqs8y6s7ycwvv36xwn5zsh3e2xemkyumaxnh85dv7jwus6xmscdpcygprpmhxue69uhkv6tvw3jhytnwdaehgu3wwa5kuef0ekucf3 the dev of Blitz wallet is having trouble publishing to zapstore. Not 100% sure what the issue is but perhaps you could assist?
Thanks, what is the issue? I don't use telegram. Can you tell them to reach out to me or open an issue on our repo?
It's hit or miss. European VPN locations often work for me
A series of endpoints for nostr clients to enhance trust in their apps. I've been building this with nostr:nprofile1qqs0dqlgwq6l0t20gnstnr8mm9fhu9j9t2fv6wxwl3xtx8dh24l4auspz4mhxue69uhkzat5dqhxummnw3erztnrdaksz9rhwden5te0wfjkccte9ejxzmt4wvhxjmcpzemhxue69uhhyetvv9ujumn0wd68ytnzv9hxgxmpqkh . Coming soon!
What would you sign and how would you verify signatures?
A zipped PWA yes
So #pubky has baked in tagging and web of trust...interesting.
No one tags content. Remember the semantic web?
Good news is you can do discovery and algos regardless
Web of trust: you bootstrap it by shitposting but who shitposts on pubky?
Now you can zap developers in your Nostr appstore! ⚡
nostr:nprofile1qyxhwumn8ghj7mn0wvhxcmmvqy8hwumn8ghj7mn0wd68ytnddakszynhwden5te0wp6hyurvv4cxzeewv4esz9rhwden5te0wfjkccte9ejxzmt4wvhxjmcpzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgqpqxpuz4qerklyck9evtg40wgrthq5rce2mumwuuygnxcg6q02lz9mssce5p3 nostr:nprofile1qyv8wumn8ghj7enfd36x2u3wdehhxarj9emkjmn99uqzqun2rcnpe3j8ge6ws2z789gm8wcnn056wu734n6fmjrgmwrp58q390rp63 congratz!
🫂
Holy shit 395k zapped on first post
A lot more interesting content than just a few months ago.
Our #nostr is growing!
2025 gonna be yuge. Just watch.
Lmao do they have any credibility left?
Not to mention a db can strip out lots of useless data that relays can't
Yeah Kotlin is nice, not possible to do that in Dart.
The are tradeoffs with the citrine approach. And it all depends on what local dbs are storing. For apps and releases, for example, it's better to do in an in-process db
Sync: blocking, async non-blocking. I'm interested in this for a specific API design. Communicating with other Android apps is necessarily async. But I'll think about it.
I see the advantage of using a device relay but I'm unsure of the UX. Are you going to ask your users to download and continually run citrine in order to use your app? It will also depend on the overlap - for Amethyst and Zapstore it's probably none
Not that I know of, but this kind of specific request is what I'd like to go through nostr:nprofile1qqs83nn04fezvsu89p8xg7axjwye2u67errat3dx2um725fs7qnrqlgzqtdq0 to find the right builders (or recommenders)
Does it feel wrong to access memory synchronously?
It all depends on the i/o operation, where and for how long it's blocking. Nostrdb should be crazy fast, way faster than sqlite3 whose most popular bindings are...also sync.
Sync allows for API design that async does not, and I want that flexibility at this lower level. You can always turn sync into async but not the other way round.
