Where are they from and where are they heading?
And something that occurred to me just now: make sure it’s possible to block reporters as well, to prevent report-spam.
I think blurring or collapsing reported content and showing the report reason and text, is a very sensible approach. Then let the user decide whether they want to see it or not.
Do you mean silent following? Or posting posts only readable to followers?
nostr browser will have to become a project sooner or later
Before translations, we should start adding tags for the language the post was authored in (on mobile, I guess you can query for the keyboard and auto complete language setting?)
Like [ “LCID”, “en-us” ]
Religion is what emerges, when God’s children try to build a home on earth instead of thriving in the joy of feeling at home with Him in heaven.
note1jq3x72a93fta8meu5t0y72fe96fmatcfv9udpz4cahtj87ggvxxst3h8ej
Going #zapsonly #onlyzaps is premature if there is no direct wallet integration yet. Only place I would go zaps only right now is in my browser with Alby.
Ah it’s a silent mention, not sure what that will yield
gossip master branch does it too (if it knows the relay for the mentioned note)
I think it’s highly unlikely that SBF has ever been in a gym
@nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s and @nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z if you are looking to build a notification relay, check out what I just found on Threema's github: https://github.com/threema-ch/push-relay
Do you also laser images on them?
Huge if true and what we hope it will allow
We just need to convention a parameter that can be passed to the LnURL server so that the invoice will be created accordingly. Like passing in the resource URI and the server would know how to look up the price. It’s all quite simple, just needs to be spec’d and built.
#Google doesn't even know how to convert sats to BTC correctly





