pull down to refresh

16 sats \ 5 replies \ @k00b 11 Aug 2022 \ on: When stacker news on nostr ? nostr
I'm very excited about nostr. It has all the signs of bottom-up protocol development that I would want to see in something we use to decentralize.
It's going to be the first thing I investigate when we begin working on decentralizing SN, which we'll probably begin working on after I create user generated subs.
That said, being bottom-up and very early and has quite a few unsolved problems afaict:
  1. discovery
    • how do I find which relay you're on?
    • how do I find the data I want?
  2. data availability
    • how do I know a relay will continue to host my messages without trusting them?
  3. DoS/spam prevention
    • how do we prevent the system from suffering as it scales and becomes beneficial to attack?
Further, how do we get these properties trustlessly?
I think these are solvable in layers, but afaict aren't solved and I'll need to have at the very least hints of solutions before I begin building into it.
write
preview
1000 sats \ 3 replies \ @fiatjaf 11 Aug 2022
Can you take a look at this NIP proposal please? https://github.com/nostr-protocol/nips/pull/31 (sorry for the mess, that is a PR from the bolt.fun guy to another branch that had the original proposal from me, but you'll get the idea)
I'm hoping Stacker News could publish events that would conform to that NIP and reference URLs (since all stacker.news comments already are references to URLs) and also to previous events when necessary. Then these events could show up in clients like Damus with the URL context attached to them. That would be pretty nice already.
Stacker News doesn't have to "run a relay" for this, it can just listen to Nostr requests from clients, conjure the events based on data from its internal database and return these to clients, and never accept any event from the outside (although in the future you might want to accept comments to Stacker News posts that come from the external Nostr network based on whatever criteria you choose).
If you could comment there on that proposal just to make sure we aren't missing anything that could be specified better that would be great.
reply
1 sat \ 2 replies \ @k00b 11 Aug 2022
Commented!
I agree, publishing/duplicating SN stuff to nostr automatically would be awesome independent any other change.
reply
0 sats \ 1 reply \ @jb55 12 Aug 2022
Stacker News doesn't have to "run a relay" for this
sure, I was just responding to the question about data availability. if they feel ok with broadcasting all their data to public relays and hoping they won't be deleted then broadcasting would be fine and easy.
reply
0 sats \ 0 replies \ @fiatjaf 12 Aug 2022
I wasn't contradicting you, I was just trying to contest the popular understanding that "to run a relay" means to have a dedicated storage and server and accept events from everybody and their cousin.
reply
159 sats \ 0 replies \ @BlueSlime 21 Nov 2022
1a. Similar to Lightning, have a pubkey@relayaddress that can also resolve from customname@relayaddress or name@customdomain with .well_known authentication
1b. Everything is tagged with date, author pubkey, plus any tags you like. Easy to filter.
  1. Pay for hosting or get a guarantee (requires authentication)
  2. Authentication, maybe web of trust? :-D
reply