To rephrase that, with nostr you *NEED* a publicly accessible server to be a full participant in the network. With P2P you can choose to run a server, even privately, to lighten the load on your end clients.
How is that better than no server, smart P2P client? Running a nostr relay requires having a publicly accessible server, and it doesn't provide access to the totality of nostr, just what has been posted to it.
The primary objections to P2P I've seen has been speed and reliability. In my experience with Freenet, speed is the real objection, reliability is imperfect, but relays will not retain every note forever either.
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2023-November/022134.html
> Our current mailing list host, Linux Foundation, has indicated for years
that they have wanted to stop hosting mailing lists, which would mean
the bitcoin-dev mailing list would need to move somewhere else. We
temporarily avoided that, but recently LF has informed a moderator that
they will cease hosting any mailing lists later this year.
...
> Many other projects have moved from mailing lists to forums (eg https://discuss.python.org/ – see https://lwn.net/Articles/901744/ ; or https://ethresear.ch/),
which seem easier to maintain and moderate, and can have lots of
advanced features beyond plaintext, maybe-threading and
maybe-HTML-markup.
>
> Who would host the forum? Would there be agreement around which forum software to use or which forum host? What about bitcointalk.org or delvingbitcoin.org?
There are many options available. Maybe what we actually want isn’t so
much a discussion forum, as an 'arxiv of our own' where anons can post
BIP drafts and the like?
Can nostr step up here? Other than the relative immaturity of the software ecosystem, it seems like a pretty good fit. The only missing piece mentioned is email notifications, and that would be easy to whip up.
I'd also suggest (again) that we need a rich text note, different from long form articles, and probably some easy way to dump a thread into a tarball for archival, but otherwise, nostr seems like a decent fit.
I guess I'm not convinced privileging servers *is* an innovation. On Freenet, SSB(?), IPFS and others, it was always possible to stand up gateway servers. Having P2P primary and servers secondary seems like a superior model, despite some insistence otherwise. It seems that most nostriches have never even used the prior systems.
At the end of the day though, I've always said the tech barely matters (past a certain point), the network of people is what matters. That's (primarily) why I gave up on Freenet.
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2023-November/022134.html
> Our current mailing list host, Linux Foundation, has indicated for years
that they have wanted to stop hosting mailing lists, which would mean
the bitcoin-dev mailing list would need to move somewhere else. We
temporarily avoided that, but recently LF has informed a moderator that
they will cease hosting any mailing lists later this year.
...
> Many other projects have moved from mailing lists to forums (eg https://discuss.python.org/ – see https://lwn.net/Articles/901744/ ; or https://ethresear.ch/),
which seem easier to maintain and moderate, and can have lots of
advanced features beyond plaintext, maybe-threading and
maybe-HTML-markup.
>
> Who would host the forum? Would there be agreement around which forum software to use or which forum host? What about bitcointalk.org or delvingbitcoin.org?
There are many options available. Maybe what we actually want isn’t so
much a discussion forum, as an 'arxiv of our own' where anons can post
BIP drafts and the like?
Can nostr step up here? Other than the relative immaturity of the software ecosystem, it seems like a pretty good fit. The only missing piece mentioned is email notifications, and that would be easy to whip up.
I'd also suggest (again) that we need a rich text note, different from long form articles, and probably some easy way to dump a thread into a tarball for archival, but otherwise, nostr seems like a decent fit.
SSB? FMS? Sone?
FMS and Sone don't even *have* servers, and I'm admittedly not very familiar with SSB's implementation details.
We need a good nostr project tracker...
Has anyone started on a Q&A nostr app? (Think StackOverflow)
Seconded on extending the gradient further left. Not sure if it even needs desaturating though, I like it!
Oh right, the transaction: https://mempool.space/signet/tx/e9dd255ef2ab4715165ef423d1124a93fe07d73f9b0cdd91f0ead6b7b4dadc10
https://gist.github.com/Ademan/95e63a7b310e51ce38c61a579e1cb8b4 instructions on how I did it, which should hopefully make some sense to someone familiar with musig, the key pairs I used for this test are here: https://github.com/Ademan/rust-musig-psbt/blob/wip/test_keys.txt (I used the first two)
I finished reworking the library to implement the draft bip https://github.com/achow101/bips/blob/musig2-psbt/bip-musig2-psbt.mediawiki and squashed everything into a new initial commit on the master branch. I'll keep the wip branch around for a while so people can see the prior mess (In general I prefer to keep history, but this history is just too messy), if they want to for some reason.
https://github.com/Ademan/rust-musig-psbt/tree/master
Oh and the test transaction I signed https://mempool.space/signet/tx/4598fef988fb1617e4f127c5ff7f115a95587cd86136c354296ce3b8acbf8e0f
I have some tests to fix this week, and many tests to add, and then I'll probably release a 0.1.0 "do not use!" edition.
Fedi has a similar problem until you start following enough people.
nostr:nprofile1qqs9pk20ctv9srrg9vr354p03v0rrgsqkpggh2u45va77zz4mu5p6ccpremhxue69uhkummnw3ez6ur4vgh8wetvd3hhyer9wghxuet59uq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tcppemhxue69uhkummn9ekx7mp069f2j4 is there a signet/testnet cashu mint? It's unclear if that's what the cashu.me default mint is. Sorry for the blatant lack of rtfm
Seriously, I just logged in earlier today, logged right back out after I saw some of the outrage bait of the day.
Has anyone written about the legal aspects of chaumian mints? (cashu and fedimint) Particularly for Americans.
I know fedimint was designed to be regulatory friendly, but I recall the consequence was the "fedi" part gets kneecapped. If I wanted to run a fedimint for my family that would be ok but it's totally useless since within my family we tend not to exchange money anyway, it's the money in and out of the family that matters.
sounds legit, all in!
nostr:nprofile1qqs04xzt6ldm9qhs0ctw0t58kf4z57umjzmjg6jywu0seadwtqqc75spz9mhxue69uhkummnw3ezuamfdejj7qgnwaehxw309ac82unsd3jhqct89ejhxtcppemhxue69uhkummn9ekx7mp00ugyzc What if kind 1s used a tag to signal they are markdown? ["ct", "text/markdown"]? Markdown is designed to be readable as plain text, so even though it probably would make fiatjaf mad (good! lol), it is pretty backwards compatible with unaware clients. It has the advantage over a new kind in that unaware clients wouldn't end up with broken threads.
I assume Coracle would handle this correctly, but the implication is that "blog reader" type clients would start seeing people's short social media posts in their feeds which is not the sort of content they want, even though it's the same nostr kind. Separating it into its own kind (even if the contents are compatible) would prevent this bleed over.
Only if it works automatically for your followers. (Doing that properly seems like it belongs in a new kind, not a note, or if in a note it should be in a standard format)