google/meta stuff.
yes. we can define how someone should interpret the expiration on an ephemeral kind.
seems fun and useful for this kind of situation.
nostr:nprofile1qqs04xzt6ldm9qhs0ctw0t58kf4z57umjzmjg6jywu0seadwtqqc75spz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz9mhwden5te0wfjkccte9ec8y6tdv9kzumn9wshszxnhwden5te0wpuhyctdd9jzuenfv96x5ctx9e3k7mf0dv4ph5 nostr:nprofile1qqs83nn04fezvsu89p8xg7axjwye2u67errat3dx2um725fs7qnrqlgzqtdq0 olas logo is not updated in zap store.
nostr:nprofile1qqsfnw64j8y3zesqlpz3qlf3lx6eutmu0cy6rluq96z0r4pa54tu5eqpz9mhxue69uhkummnw3ezuamfdejj7qg4waehxw309ahx7um5wghx77r5wghxgetk9ufgmkzm is it possible to implement pow dvm using your library?
✅ Olas 0.1.6 approved on TestFlight!
See #nostr from a different lens:
https://testflight.apple.com/join/2FMVX2yM
https://blossom.f7z.io/53697a5961bc8561318e9ee6b4449b494705e3b097bbbc48a70d0efc5f293713.webp
cool logo. is there any nostr account for olas?
then there is a high possibility for it to get expired when relay process it. we can use a expiration of 10 secs for example or one minute. isn't that do the work?
is it logical to broadcast an expired event? why?
i think it won't work. for example in immortal relay, we just check if its expired or not. for expired ones we even don't broadcast them. other ones will be stored and broadcasted at the same time.
beacuse its not logical to broadcast expired events. also adding a third status of `now` is a little confusing since in the best situation we have only 1 sec.
We are thrilled to announce our new website https://docs.dezh.tech. this website will contain all dezh technologies projects documentations. Also, in blog section we post technical reports and guides.
We will mirror this post to nostr as well using lon-form content clients and Dezh main profile.
Website blog: https://docs.dezh.tech/blog/introduction
our new documentation website. soon immortal relay, kraken manager and panda nip-05 server will be documented there.
I think the design I created for 2025 is really cute and lovely. I want to send it as a badge to the Nostr users who supported me in 2024, but I don't know how I can send it. nostr:nprofile1qqsph3c2q9yt8uckmgelu0yf7glruudvfluesqn7cuftjpwdynm2gygpz3mhxue69uhhyetvv9ujuerpd46hxtnfduq3qamnwvaz7tmwdaehgu3wwa5kuegpzpmhxue69uhkummnw3ezumrpdejqwk5cd9
I will release it at the beginning of 2025.
hi, use https://badges.page
got it. as i said on another event, if you own the domain or use a service which supports all of them, you can use same address to receive email, sats and let others to find you on nostr with this.
we are developing a nip-05 server which let you forward your lighting address to it as well. maybe we worked on it to support email address as well. i need to think about it deeply.
we are developing...
nostr:nprofile1qqsf03c2gsmx5ef4c9zmxvlew04gdh7u94afnknp33qvv3c94kvwxgspr3mhxue69uhksmmyd33x7epwvdhhyctrd3jjuar0dak8xtcppemhxue69uhkummn9ekx7mp0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7208x3z saw your nostr:nprofile1qqsdluwc0qu62t3el7nxl93387gmppe56jkvm88vcuwh3lpw4fcevwspr3mhxue69uhksmmyd33x7epwvdhhyctrd3jjuar0dak8xtcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszxmhwden5te0wfjkccte9emk2um5v4exucn5vvhxxmmd9u6jr4yz podcast right now. great job man. i wish i had seen it earlier. 🫡⚡
if you host your email and nip-05 yourself at the same time, you can do it.
basically we can't support them in nostr properly. we need to find a pointer from @name address to a pubkey, where should we search for pubkey based on name part? there is no centralized server! so we have to attach the server address to it as well. then it would be like: name@server.
about remembering, why not? someone using unique domains of themselves so its easy to remember or share. and someone are using famous providers, so you need to remember to name part only.
also we don't memorise x @ ids as well.
they have nothing to do with emails. they are a better way to memorize and share your account identifier.
is there any default relay configuration in damus or notedeck? if yes, how can we add a relay there?
