nostr:nprofile1qqsdv8emcke7k3qqaldwv956tstu40ejg663gdsaayuuujs6pknw7jspp4mhxue69uhkummn9ekx7mqpp3mhxue69uhkyunz9e5k7qghwaehxw309aex2mrp0yhxxatjwfjkuapwveukjhuhk5x sounds like you're not implementing NIP 36, maybe you're relying on labels instead?
That's because it doesn't have a content warning 😂
This note has a content warning 👀
I think he's aware of nostr at least. I was listening to nostr:nprofile1qqstwz8h8yh43pqxyykr3qh8kw7qmxcg6chet7shp5yezflvufmsuhsprpmhxue69uhhyetvv9ujuumwdae8gtnnda3kjctvqyv8wumn8ghj7mrfva58gmnfdenhyetvv9ujucm0d5q3gamnwvaz7tmjv4kxz7fwv3sk6atn9e5k7nc7ks5 the other day, and it sounded like stemstr was the first pwa on there. You guys are really the first ones to transcend the protocol I think, which is a huge accomplishment
For lightning or ecash? I don't know anything about ecash
Yeah, that's what I'm thinking. What does e-cash have over lightning in this scenario?
I wouldn't call blastr "control"
Do me a solid and rate Coracle on store.app
My first ever pull request just got merged 🎉
Feeling honored and proud to be able to contribute to nostr adoption in this small way. Thanks nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn for the inspiration and nostr:npub1zuuajd7u3sx8xu92yav9jwxpr839cs0kc3q6t56vd5u9q033xmhsk6c2uc for the guidance around GitHub 🙏
The PR: a tutorial page on nostr.how for setting up your zapping wallet ⚡️
Many more of these to come!
https://nostr.how/en/guides/setup-zapping-wallet
#grownostr
#plebchain
🎉
Yes, wraps can hide the identity of the signer from the relay too. But that doesn't mean the relay doesn't know who they are. The relay can see all filters and can guess really well who is asking for that data from that IP and use that to guess who is the owner/signer of the GiftWrap.
nostr:npub12262qa4uhw7u8gdwlgmntqtv7aye8vdcmvszkqwgs0zchel6mz7s6cgrkj might add NIP-42 AUTH to make that more clear. The signer of the connection doesn't necessarily mean that it's the writer of the GiftWrap. But it can always be guessed by the relay.
Relays are always trusted services for authors. They know everything coming out of your machine.
Yes, AUTH is a fine solution if you don't care about the relay knowing about you. But a VPN or proxy and single-use connection would also obscure the identity of the sender (assuming the relay doesn't mind accepting the note for some other reason than authentication).
AUTH, but that's not a good solution. You want to avoid relay surveillance too.
This is built into your original question. Wraps can hide the identity of the signer from the relay too, but you explicitly asked for the opposite.
Blastr is ok as a stepping stone. But relays should choose what they host. The should be able to deny events from blastr, and/or scrape desired notes from other relays. Pull vs push
I used to think a lot about monetization, then I ran the numbers. For the simplest service I could monetize (image hosting), I could make about $80/mo. There are a few other things I could turn on, but it would probably not get me past $500/mo, and would introduce lots of headache. Better to build now, monetize later when we have the scale for it to matter.
Plus, I fully expect to monetize something other than my current project. Making a living off a twitter clone seems dubious, but there are many good businesses to be built on nostr.
Hey nostr:nprofile1qqsf03c2gsmx5ef4c9zmxvlew04gdh7u94afnknp33qvv3c94kvwxgspp4mhxue69uhkummn9ekx7mqpr4mhxue69uhkummnw3ez6ur4vgh8wetvd3hhyer9wghxuet5qyfhwumn8ghj7un9d3shjctzd3jjummjvunh27sl - #coracle just keeps getting better, thank you. Is there a way to increase the "timeout" for posting to relays? I get frequent timeouts, so I have to open Amethyst and hit broadcast...is there a better way? (Will zap a thank you if you have/take time to reply.)
It's not configurable, but as long as one goes through you can click through to the note and re-broadcast using the note menu. I should add a retry with a longer timeout to the dialong too. Also note that just because a timeout happens doesn't mean the relays didn't get it, only that they didn't respond
