why nostr dms not work as smooth as other protocols? is this something to be fixed on relay or client side? i would be happy to have your experience and ideas.
nostr:nprofile1qqspycgrhlwu3he9ddhq407h7duheqxucn4g3a7zlp7agyzzyz6dvhcpz9mhxue69uhkummnw3ezuamfdejj73cxtrz nostr:nprofile1qqs84k6jpsav0jmdeqjn2zxlpnsajaw6f8l0m2d4e9t8gjsyn53s4nspzemhxue69uhhyetvv9ujuvrcvd5xzapwvdhk6qgdwaehxw309aukzcn49ekk2qghwaehxw309aex2mrp0yh8x6tpd4ehgu3wvdhk6pw0r8j nostr:nprofile1qqsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8gprfmhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5hszxmhwden5te0wfjkccte9emk2um5v4exucn5vvhxxmmd9uq3xamnwvaz7tmhda6zuat50phjummwv5hsx7c9z9 nostr:nprofile1qqsru22d9lfnnwck54qr4phrvey50h2q33xc0gqxv5j03ftn4efu4rspzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtcppemhxue69uhkummn9ekx7mp0qythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap08rutw0
nice. the main issue is that using same relays, clients are not synced. i can't see my friends messages randomly in same client using same relays. but other client show them properly. text notes are always much more synced.
i used coop, after setting up new account it opens a white page and nothing change then.
i want to findout if there is any technical issue from relays, clients or protocol. if any actions must be taken in relay, i can work on it.
im using 0xchat and amethyst. usign jellyfish relays and some other public relays. i had situations which i was using 0xchat to 0xchat or 0xchat to amethyst and i didn't received the message on the other client.
i don't like matrix and never used irc, maybe because when i started using internet there was an stable version of modern messengers. ill try to use it. but for now i made a connection request on simplex, lets try it.
we run and develop at the same time.
developing https://github.com/dezh-tech/immortal at nostr:nprofile1qqst4k7a55r4w2ee0pfqfr48fuh08tvjkx4vqlpafcw7c96w3nwfv2spr9mhxue69uhhyetvv9ujumn0wdmksetjv5hxxmmd9undqjft and running on nostr:nprofile1qqst72lw22q3f8rux5846y4wxt63f3uxflcsspgc9aqhs5uv93ppqpcpr9mhxue69uhhyetvv9ujumn0wdmksetjv5hxxmmd9uxm4t88.
immortal had a successful test on production. there are 2 issues in database layer which soon will be fixed in v0.0.3 patch and then we will be ready to use it in jellyfish.
if you are interested to test an alpha version here is a temporary domain:
wss://immo.jellyfish.land
note: url will change, this is alpha version and super unstable and not tested yet.
next steps for jellyfish and dezh are:
1. running immo in jellyfish.
2. supporting more nips.
3. starting paid relay service.
4. guess this one...😵💫
nostr:nevent1qqsr7e0lny5ph08ketqg06jsrgla9uhu96x00jjncy0fpde5eyx566sprfmhxue69uhkjmtdduhx5etvd3ukv6tndqhxcctwvshsyg9aft37vl3fjex5jstjycwug5u4ez0kh5h8w3jzudnpyut3m7up75psgqqqqqqs3tuh3d
nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqpzamhxue69uhhv6t5daezumn0wd68yvfwvdhk6tcppemhxue69uhkummn9ekx7mp0qyghwumn8ghj7mn0wd68ytnhd9hx2tcewvzaw what is ots pending in amethyst?
#asknostr
we are all satoshi.
nostr:nevent1qqsqqqz3mrveghquljv006kxljqn5ygvu7d5au9sqxluu5n2ez0ddzsppemhxue69uhkummn9ekx7mp0qgsq4gu7tthengqq577mpdyezkxf90z25g8mvkf355ks2k67km0lwwqrqsqqqqqpu7cx0w
how you want to prevent it to be dumped? using other hardwares or just designing one?
as far as i know, every hardware can be dumped with a physical access.
we were thinking about encryption of the key and asking user for pass word or fingerprint.
there is some work in progress at nostr:nprofile1qqst4k7a55r4w2ee0pfqfr48fuh08tvjkx4vqlpafcw7c96w3nwfv2spzdmhxue69uhhwmm59e6hg7r09ehkuef0uhd59d for this. we are planning to use current lnbits software for first version. if it was successful and had enough demand, we are going for our custom software and hardware. probably supported on all devices.
try using yakihonne(?). or maybe we can make one which just inputs md and parse them as simple as possible and we can share them. if you believe in stuff that only do one thing very simple.
your welcome.
sounds cool, i would be happy to see the script if its open source now.
i agree, it can be available with a simple ui. a nostr markdown client.
irainain/persian technology community on nostr!
nostr:nevent1qqsv9r72gguawc0d6sakt26nn78nfsm56tgwcwuhky886kkq85tavmqpzpmhxue69uhkummnw3ezumt0d5hsygrhztxwpe570ht8p0ggrsjp27cj5nz09dpm9y4ndgv3sy2fw7lvvcpsgqqqqqqsv6nc9u
nostr:nprofile1qqsq4gu7tthengqq577mpdyezkxf90z25g8mvkf355ks2k67km0lwwqpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszrnhwden5te0dehhxtnvdakz7qg5waehxw309ahx7um5wgh8svrx9ehhyee09eukf6 i just found out that this blue sea dragon in your profile picture, eats jellyfishs as food. lol.
immortal will soon release a beta version. software is kind of stable now and ready to be tested on jellyfish relay.
contributions, starts, ideas and other kind of support are welcomed.
https://github.com/dezh-tech/immortal
next stage is implementing more nips, supporting search and media servers, admin panel and specific optimizing for chat services.
i'll try to do it on nostr:nprofile1qqst72lw22q3f8rux5846y4wxt63f3uxflcsspgc9aqhs5uv93ppqpcpr9mhxue69uhhyetvv9ujumn0wdmksetjv5hxxmmd9uxm4t88 soon.
wss://relay.jellyfish.land
https://github.com/dezh-tech/immortal
nip01 implemented. 11 and 9 are next nips. after finishing log and monitoring services, jellyfish start migrating to immo.
you can help and contribute by satrs, testing it or contributing to code.
ive just made an example nostr npub, which the nsec is already destroyed. this works like https://example.com and you can use it in documents, placeholders, previews and more.
nostr:nprofile1qqs2ef5zc5wyfjgyv3saur9nf0xxxwx42ckdlyrz4m5u8jj6fjs2k0qpr9mhxue69uhhyetvv9ujuumwdae8gtnnda3kjctv9u52cj2y
check this out.
ما با منابع خیلی کمتر مدت خوبیه بصورت عمومی و غیر محدود اجرا کردیم رله رو، به مشکلی به خصوصی بر نخوردیم.
و میشه حدس زد تا مقایس بیشتر هم میتونه تا حد خوبی جواب بده.
Notes by k. | export