@carlos99
stacking since: #1051
Awesome!
Did you already add it to https://github.com/aljazceru/awesome-nostr ?
Happened to me too sometimes from Safari/iOS but worked on Android.
Sorry about that, looking into it. Some sort of issue with the hoster. Maybe try from a different browser and/or device.
Hey k00b, I hear BOLT12 plans to support messages without payments.
Onion Messages Using the same onion mechanism we use to send payments, without the actual payment part. You can (and people do!) use fake payments to send messages today, but it's 3x slower and consumes far more resources on each hop. https://bolt12.org
Might be useful for decentralizing SN.
102 sats \ 1 boost \ 0 replies \ @carlos99 OP 7 Oct 2021 \ parent \ on: [RFC] Shroom Node v0.1 released bitcoin
Thanks k00b, good questions.
LN as transport is something I'm exploring. I want to use it as much as possible, but I think for some use cases I might have to use it only for signalling and transfer actual data over something else, like a websocket.
On the one hand, it has some interesting benefits, like:
- you only need a pubkey to contact someone (they could change IPs, switch over to tor and back, etc -- still reachable via same pubkey)
- "data bound to payment" = cost of sending = native spam prevention
- "data bound to payment" = receiving data implies receiving a payment = economic incentive to offer services (for which the inbound messages can be "requests for service")
On the other hand, limitations:
- latency: you can't quite "stream data" over LN (maybe not yet? or maybe its not necessary, a side-channel can be used for low-latency requirements?)
- bandwidth: same as above
- payloads are persisted (indefinitely?) as invoice metadata in the LND DB = could eventually clog the DB
- makes one-to-many scenarios harder to implement (a chat group where each message = N payments, one to every other group participant, makes no sense)
- same for many-to-many
Will probably end up using it as a hybrid (transport in some cases, signalling in others).
Don't think this can help much with decentralizing SN though.
Echo adds a newline to the output, see https://stackoverflow.com/a/34430808
So your first command is actually hashing "R\n" while the 2nd one is hashing "R"
Incentives.
Rather than have users sacrifice sats to downvote, have the poster stake sats with every post. If the post is not marked as spam within X days, they get the staked sats back.
Sphinx uses this concept, seems to work well.
This guy might know more: https://twitter.com/crackXBT/status/1432289251551416321
nostr) to filter.