Well, don't we all? 🤣
Yes, It is probably package issue.
I haven't tried using its deb package but i can run normally portable AppImage version in Ubuntu 22.04 . Maybe you can also try AppImage version. Usually most distro support running AppImage directly (double click to run)
Otherwise:
```
chmod +x /path/to/nostr-relay-tray.AppImage
/path/to/nostr-relay-tray.AppImage
```
Yes, i think nostr:npub1syjmjy0dp62dhccq3g97fr87tngvpvzey08llyt6ul58m2zqpzps9wf6wl has not the complete documentation about that. It is new experimental feature introduced in recent version
It is nice relay for desktop. You can also probably try using "Hub feature" and your local relay events can be accessed publicly through
wss://hub.nostr-relay.app
like a reverse tunnel sevice.
Well yeah, it is kind of 'free format' event 😅
Ah, thank you. It clears probably all my doubts with event structure migration. I think i can start slowly implement the new structure and deprecate the old structure in the following weeks.
Oh, I thought NIP-78 has been used for that. I think there was library to make key-value storage using NIP-78.
I'm not bot sir. I can solve captcha 90% right 😄
I see. Glad to hear then.
What do you think about multiple label "l" structure that i have shown in language or topic labelling? Do i need to change something in those cases?
Example:
Note/post which has multiple languages
["l","en","ISO-639-1"], ["l","ja","ISO-639-1"]
Note/post which has multiple topics
["l","science_and_technology","app.nfrelay.topic"], ["l","arts_and_culture","app.nfrelay.topic"]
Thank you. I think i want to make sure about label namespace.
Is it ok to state "L" namespace multiple times as long as it was clear which reference of the namespace? In language labelling i made two namespace using "ISO-639-1" for public use (different apps/clients can freely query it) and "app.nfrelay.language" for internal use.
Yes, agree. Possibly with Freemium model. Free with short term storage and paid with long term storage.
Not exactly same, i have little experiment to store only 7 days old of events. All events excluding main metadata event (0, 3, 10002) will be deleted if they were 7 days old. Metadata events were not deleted. It only takes around 10 GB of storage.
It was feasible plan for free relays to do something like this.
#asknostr
Hi nostr:nprofile1qqsf03c2gsmx5ef4c9zmxvlew04gdh7u94afnknp33qvv3c94kvwxgspr3mhxue69uhksmmyd33x7epwvdhhyctrd3jjuar0dak8xtcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszxnhwden5te0wpuhyctdd9jzuenfv96x5ctx9e3k7mf0ss9zgs nostr:nprofile1qqspwwwexlwgcrrnwz4zwkze8rq3ncjug8mvgsd96dxx6wzs8ccndmcpzemhxue69uhk2er9dchxummnw3ezumrpdejz7qtxwaehxw309anxjmr5v4ezumn0wd68ytnhd9hx2tmwwp6kyvt6w46kz6nyxa6nxumc8pu82wfj09shvwt2wau8qu3cxvukxuesdd3nxufkws6nvanyx46njufsxvehsmtgwd4nvcejw43n7cnjdaskgcmpwd6r6arjw4jszxrhwden5te0dehhxarj9enx6apwwa5h5tnzd9az77vr4lw and other nostriches who might be familiar with NIP-32.
Currently, i'm preparing to migrate custom label event (kind 9978) into NIP-32 event.
What is the best way to preserve the old event data structure while maintaining compatibility with NIP-32 structure?
The structure of the old event and the new proposed event (NIP-32 compatible) has been documented here:
https://github.com/atrifat/nostr-filter-relay/issues/18
Any feedback and suggestions are really appreciated. Thank you.
Hi nostr:nprofile1qqsf03c2gsmx5ef4c9zmxvlew04gdh7u94afnknp33qvv3c94kvwxgspr3mhxue69uhksmmyd33x7epwvdhhyctrd3jjuar0dak8xtcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszxnhwden5te0wpuhyctdd9jzuenfv96x5ctx9e3k7mf0ss9zgs , would you mind to take a look at this? I need some suggestions related to NIP-32 🙏
Congratulations 🎉
Ini yang benar-benar mendekati gambar di bungkusnya 😄
#asknostr
Hi nostr:nprofile1qqsf03c2gsmx5ef4c9zmxvlew04gdh7u94afnknp33qvv3c94kvwxgspr3mhxue69uhksmmyd33x7epwvdhhyctrd3jjuar0dak8xtcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszxnhwden5te0wpuhyctdd9jzuenfv96x5ctx9e3k7mf0ss9zgs nostr:nprofile1qqspwwwexlwgcrrnwz4zwkze8rq3ncjug8mvgsd96dxx6wzs8ccndmcpzemhxue69uhk2er9dchxummnw3ezumrpdejz7qtxwaehxw309anxjmr5v4ezumn0wd68ytnhd9hx2tmwwp6kyvt6w46kz6nyxa6nxumc8pu82wfj09shvwt2wau8qu3cxvukxuesdd3nxufkws6nvanyx46njufsxvehsmtgwd4nvcejw43n7cnjdaskgcmpwd6r6arjw4jszxrhwden5te0dehhxarj9enx6apwwa5h5tnzd9az77vr4lw and other nostriches who might be familiar with NIP-32.
Currently, i'm preparing to migrate custom label event (kind 9978) into NIP-32 event.
What is the best way to preserve the old event data structure while maintaining compatibility with NIP-32 structure?
The structure of the old event and the new proposed event (NIP-32 compatible) has been documented here:
https://github.com/atrifat/nostr-filter-relay/issues/18
Any feedback and suggestions are really appreciated. Thank you.
Oh, kirain ada komunitas aktifnya. Contohnya Bitcoiner Thailand (Siamstr) kan aktif di X dan juga Nostr. Barangkali kita juga banyak 😅
Udah lama banget mas gak pakai X terakhir zaman kuliah kayaknya bertahun-tahun yang lalu 😅
Apa di X banyak mas komunitas bitcoin oleh warga nusantara? Saya sudah lama tidak pakai X lagi 😅