Avatar
ManiMe
df67f9a7e41125745cbe7acfbdcd03691780c643df7bad70f5d2108f2d4fc200
I will never give up respecting everybody. Nostr Dev. Creative. Athlete. Optimist. Freedom lover. Know nothing nobody. Discovering myself. A little GFY is good for you. Sovereign Online Since 810018. Building WoT powered Nostr apps : - My Grapevine (https://grapevine.my) Webs of Trust recommendation engine (WIP) - Meet Me On Nostr (https://nostrmeet.me) Webs of Trust powered onboarding (WIP)
Replying to Avatar Riddler

Curious 👀

It’s really amazing how many NIPs are being proposed “out there” in various repositories and event kinds on Nostr.

NostrHub is under active development AS WE SPEAK to render ALL THE NIPs from ALL of these sources in a consistent manner, with decentralized rating and review (powered by WoT) for all of them.

Take a look 👀

nostr:nprofile1qqs8sxs4yuz47axp7uprpugrs3sfkdz5379tdg9xe2n5qfvz070a4egpz4mhxue69uhhyetvv9ujumt0wd68ytnsw43qzxmhwden5te0vakx2ctndahxzar0wghxgetk9aex2mrp0yeru66d

https://nostrhub.io

lol. It’s not git over Nostr. Sorry if that was confusing. It’s a client for developers to explore Nostr nips and apps and (nip 34) git repos. WIP.

https://nostrhub.io 👀

Is already a great client for this.

Shortly we will support WoT powered rating and review of NIP proposals submitted from across Nostr… and other repos as well. New release on its way out the door. Stay tuned.

nostr:nprofile1qqs8sxs4yuz47axp7uprpugrs3sfkdz5379tdg9xe2n5qfvz070a4egprdmhxue69uhkwmr9v9ek7mnpw3hhytnyv4mz7un9d3shjqg4waehxw309aex2mrp0yhx6mmnw3ezuur4vgzaq60d

Taking a look 👀 nostr:naddr1qqsxxmmwvdjhqar4v9kxj7nfdenj6argv5kkyctw09skuttjv4kxz7gzypld04wr40cxlgwqpacls7v9va5lg6kfyd2vz2dna42ky5rfyl3qqqcyqqq823c9lrxc8

That's a good idea. But we'd also like to be able to search by result value as well as context string. A good solution may be something like this:

["w", "", ""]

["v", ""]

Where "context" MAY be any arbitrary string, but the nip may also specify some useful "conventions". And every "w" tag SHOULD be followed by a "v" tag, which MAY contain any arbitrary (JSON safe) string. This allows BOTH context and result to be indexed.

So … the question is :

Can “multi letter key tags” be included in REQ filters and relay search results?

The NIP01 “convention” states that “all single-letter key tags are expected to be indexed by relays” and that “Only the first value in any given tag is indexed.”. I expect that relays MAY move beyond the first convention IF there is a REALLY good reason AND a clear path to do so.

If the answer is yes (which you seem to think it is?) … then i think this 👇 is the better solution that allows both “indexable” AND “arbitrary” tag keys … with an additional string as the last tag value to help communicate the result schema info.

[“wot:”, “”, “”]

If we don’t need a “single letter” at the tag 0 index (which I assumed we did … to allow searching by relays) then having an arbitrary “context” in this position can still be achieved … using a colon syntax?

[“wot:”, “”, “”]

It’s important to remember that we HAVE NOT landed on a NIP spec for the algo config event, who’s “d” tag MAY BE the “context” string for these TA results. As such nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z , some “standard” type of calculation (like “rank”) useful for clients will likely be configured differently for each user or use case … AND these different configurations MAY each have their own “context” string to identify them. So TA events will prolly need to recognize an arbitrary context string somewhere along the line …?

- I actually rewrote the entire NIP (while I was at it) for clarity. So a diff would not be as useful as you may think.

- also, the updated spec does allow for the “type” categories (index 1 in the tag) to be any arbitrary value … even if only ONE service provider supports it. These are only intended to hint at the underlying data type returned.

- given this, it does make sense to have a standard “w” label for the tag itself (index 0 in the tag) and also … for indexing purposes.

- give that the arbitrary “context” string will end up being the “d” tag value for (spec TBD) a user published “algo config” event … indexing these “w” tags makes sense for other users to discover each other’s “configured algos” … without necessarily exposing the users actual algo config.

The EXISTENTIAL opportunity of Nostr is to demonstrate that “efficiency”and “accuracy” can be “sufficiently approximated” WITHOUT the need for central authority to “establish absolutely”.

Otherwise, there are better ways than Nostr for EVERYTHING … in the REAL world.

Choose NIPs for your App like you use choose Apps for your phone ... with ratings and reviews on the NIP store.

https://nostrhub.io by nostr:nprofile1qydhwumn8ghj7emvv4shxmmwv96x7u3wv3jhvtmjv4kxz7gpz4mhxue69uhhyetvv9ujumt0wd68ytnsw43qqgrcrg2jwp2lwnqlwq3s7ypcgcymx32glz4k5znv4f6qykp8l876u5t77atk

Auf Deutsch heißt das “yein”.

Yup. nostr:npub1ldsmj0vxfe8sawnkdwu92medcqnzar5c2qfw9xazs5yd65sx0kvqghzsk3 … you may need to refresh your page.

To be clear … NostrHub has ZERO filters or limits for people to publish or view NIP proposals. The only “censorship” anybody will EVER face is at the hands of each user’s own configurable WoT settings (coming soon) which will be published as user signed events according to WoT standards (also coming soon). #wotathon

So yea … we’re 💯 here to serve you and make Nostr better for everyone. Go ahead and cry harder. We’ll keep pushing awesome code.

nostr:nprofile1qqsr7acdvhf6we9fch94qwhpy0nza36e3tgrtkpku25ppuu80f69kfqprfmhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5hszythwden5te0dehhxarj9emkjmn99u8tudrl nostr:nprofile1qqst4un6fnzd5jv38elaany4rlfmjuwfy7v4ntmzkq4hvxsy8sensnqpz3mhxue69uhhyetvv9ujuerpd46hxtnfduq3camnwvaz7tmxv4jkguewdehhxarj9e3xzmny9akk2mt9wvg94a0e nostr:nprofile1qqswum4p82uluhz2dr40nvdrflspffntgqghc58w9fs57nx6jkdkuaqpzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgqgcwaehxw309akxjemgw3hxjmn8wfjkccte9e3k7mg4ktzse nostr:nprofile1qqsfln36agetx43hsw8mgkm4hce9j46zu94m8er59nyzhv74p7gg0espzpmhxue69uhkummnw3ezumrpdejqz9rhwden5te0wfjkccte9ejxzmt4wvhxjmce0sg4u nostr:nprofile1qqsvz23tevqzl46tf56zlxu59sjvgnxyd40d8yspy3dgkm6pvtn7lnspzpmhxue69uhkummnw3ezumrpdejqz9thwden5te0v4jx2m3wdehhxarj9ekxzmnytv3cmt what yall think? We need a “cross the pond” Nostr dance off / zapathon ? 👀 ⚡️

Wait… That’s ridiculous!! Nobody wd do that?? Not even “clear” piss at burning man … for “health” reasons. Nope!

Who’s gonna vlog livestream on Nostr from Burning Man this year? nostr:nprofile1qqsvmm558ja3n3g6hpr6vm2awaph825lv0fgwfrtkkdssfl6te3hgqqppemhxue69uhkummn9ekx7mp0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7pja6mp ? Anyone else? nostr:nprofile1qqsgthcq5tm2jxz9x4xg6tvlh26qq2actdpztwh2kc86lvjc03gr36spr4mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmp0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj70hlxj2

nostr:nevent1qqstf3v3eth50vmpxa4lne6l2cnszdc7py6y4h80kr642ty8avlqwygsa88l5

Decomodifcation is a red herring. Zapping culture and Value for Value exchanges follow the same principle. The devil is in the details … the philosophy behind the exchange, not the medium of exchange itself.

Nostr is what makes this difference tangible. It’s how freedom culture gets permeated by freedom tech. Freedom culture is the glue that binds.

There’s a magic sauce here somewhere … where a Nostr onboarding camp could thrive at Burning Man.

Sovereign “webs of trust” (weighted scores based on user configurable and sharable analyses of p2p interactions) user verification will always outperform centralized gate keeping … especially under state mandate to “protect our children”, where every other solution is hamstrung out of the gate by special interests and regulatory capture.

Phishing and social engineering attacks simply disappear when your only input comes from established trust networks.

A squiggly one. An attentive one. And one just looking for the tit. Can identify.

Come for the freedom.

Stay for the people.

Nostr is a funny place.

nostr:npub1hte85nxymfyez0nlmmxf287nh9cujfuetxhk9vptwcdqg0pn8pxqxasw3d went to go get some yesterday … last I heard of him.

Yo nostr:npub1aeh2zw4elewy5682lxc6xnlqzjnxksq303gwu2npfaxd49vmde6qcq4nwx

What’s Up!!