Avatar
Gzuuus
40b9c85fffeafc1cadf8c30a4e5c88660ff6e4971a0dc723d5ab674b5e61b451
Forever learning, continuously buidling⚡ cryptoanarchism student https://nostree.me/gzuuus #noderunner#Bitcoin | #technology | #art | #electronics

nostr:npub1xdtducdnjerex88gkg2qk2atsdlqsyxqaag4h05jmcpyspqt30wscmntxy ha sacado para nostr.band relays con filtro de idioma, si añades wss://feeds.nostr.band/lang/es a tus relays tendras un relay que agrega todo el contenido en español 👀

There are several, nostrchat, blowater, and more that I am leaving behind, I recommend taking a look around nostr.net to see more alternatives On the other hand nip42 It is more a matter of the relay than of the client, it is described in the nip42 flow ( nips.be/42 ) You also have to think that you can connect to your relay if you have a certificate, normally if this does not exist the clients will not connect to your relay

✋ i did a plugging for wordpress to integrate nostrichat in any page like a shortcode, and also had the idea to make a nostr tools wrapper for wordpress, i'll be working on it at some point

Im writing linktr in svelte too

Replying to Avatar Tony

Hey nostr:npub1zuuajd7u3sx8xu92yav9jwxpr839cs0kc3q6t56vd5u9q033xmhsk6c2uc , is there a way to add a cover image to the bookmarks list? Been discussing some categorization opportunities for content creators with nostr:npub107jk7htfv243u0x5ynn43scq9wrxtaasmrwwa8lfu2ydwag6cx2quqncxg and it would be amazing if nostr:npub1048qg5p6kfnpth2l98kq3dffg097tutm4npsz2exygx25ge2k9xqf5x3nf (or any other platform) user could create bookmarks lists with their choice of articles - say, all “Guides” articles or “Bitcoin” articles - and add a cover image to the list. That way the clients who choose to support this will be able to display these will have the lists beautifully decorated with an image. nostr:npub1yzvxlwp7wawed5vgefwfmugvumtp8c8t0etk3g8sky4n0ndvyxesnxrf8q does something like this, but they add a cover image on their own platform, and I believe it would be much better to have this feature as a native Nostr event just like lists are.

What do you think?

Just thinking about this as well, it definitely deserves to be standardised, at the moment there are several options

- nip39 style:

``` json

{

...

"kind": 30001 || >30000 && <39999,

"tags": [

["d", "Link list" ],

["avatar", "" ],

["r", "https://github.com/gzuuus", "github"],

["r", "https://link2.com/gzuuus", "link2"],

["r", "https://link3.net", "link3"],

...

],

....

}

```

- Pinstr style:

``` json

{

...

"kind": 33888,

"tags": [

[ "d", "Best Tailwind Component Libraries" ],

[ "avatar", "" ],

[ "headers", "Name", "URL" ],

[ "pin", "Tailwind Elements", "https://tailwind-elements.com/" ],

[ "pin", "Flowbite", "https://flowbite.com/" ],

...

],

...

}

```

- Yakihonne style:

``` json

{

...

"kind": 30001,

"tags": [

[ "d", "eqwpJSUA8vEh1kjCoreAN" ],

[ "c", "curation" ],

[ "title", "Bitcoin Cultural Movement" ],

[ "excerpt", "The advent of Bitcoin ..." ],

[ "thumbnail", "" ],

[ "a", "30023:8f014c5aafb425b2fa414a49eb9ab17269f155937db67a5babe7bc40f9bbae3b:aVcTJ7_S0U8QyB1e3bLPD", "" ],

[ "a", "30023:8f014c5aafb425b2fa414a49eb9ab17269f155937db67a5babe7bc40f9bbae3b:XLZbts-MILuP4eVw3tXli", "" ],

...

],

...

}

```

What do you think? From my point of view the ideal would be between nip39 style and yakihonne.

I see, even though for example in nip39 ( https://nips.be/39 ) each parameter is defined horizontally

```

{

"id": ,

"pubkey": ,

...

"tags": [

["i", "github:semisol", "9721ce4ee4fceb91c9711ca2a6c9a5ab"],

["i", "twitter:semisol_public", "1619358434134196225"],

["i", "mastodon:bitcoinhackers.org/@semisol", "109775066355589974"]

["i", "telegram:1087295469", "nostrdirectory/770"]

]

}

```

I will be studying which format to follow, to see which is more compatible with most of the protocol.

Replying to Avatar PABLOF7z

Data Vending Machine market is heating up 🔥

Here's a demo of what's coming up to nostr:npub1w0rthyjyp2f5gful0gm2500pwyxfrx93a85289xdz0sd6hyef33sh2cu4x

When you enter a video or audio it asks AIs to compete to translate it for you

This is NOT hitting a Highlighter backend. There is no backend.

This is just nostr. Meaning, ANY application can benefit, both as a customer and as a data vending machine.

Let me repeat that:

today ANY nostr application can now do audio/video transcriptions, translations, and more tapping into a free market of competing providers.

Free markets ftw.

https://www.youtube.com/watch?v=OJx6ExVTS7c

The future today 👏👏👏

Nice, I see, but a question, the format you have for making lists where you define headers in one tag and pins in others can be a bit complicated to handle and parametrize for different clients, why not something like nip51 sets up for categorized bookmarks? ["Key", "value"], and keep adding values if necessary, ["Key", "value1", "value2", "value3" ] Do you think this could be more manageable for the other nostr clients?

Replying to Avatar JeffG

🙇 Thanks guys! I'm far from it though.

Like nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft said though, I've done a lot of suffering with Svelte recently so I've learned a lot.

Feel free to ping questions at me. Happy to help where I can.

Thanks man, appreciate it :)

Btw I love your series of videos introducing ndk and teaching how to use it, do you have plans to release more videos?

It works!!🔥 Also with yarn, seems that there are this problem using npm, ill open an issue in the repo, due there is this bug using the suggested npm👌

i was tryin, but i keep having this trouble at the moment of add the dependency:

```

npm add @nostr-dev-kit/ndk-svelte-components

npm ERR! code ERESOLVE

npm ERR! ERESOLVE unable to resolve dependency tree

npm ERR!

npm ERR! While resolving: linktr-nostr@0.0.1

npm ERR! Found: svelte@4.0.5

npm ERR! node_modules/svelte

npm ERR! dev svelte@"^4.0.0" from the root project

npm ERR!

npm ERR! Could not resolve dependency:

npm ERR! peer svelte@"^3.54.0" from @nostr-dev-kit/ndk-svelte-components@0.3.2

npm ERR! node_modules/@nostr-dev-kit/ndk-svelte-components

npm ERR! @nostr-dev-kit/ndk-svelte-components@"*" from the root project

npm ERR!

npm ERR! Fix the upstream dependency conflict, or retry

npm ERR! this command with --force, or --legacy-peer-deps

npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

```

I would love to try, any suggestion?

Btw, What is the meaning of kind 33888? It is only used in pinstr?

Nice! But there are some resources? XD