Alex Gleason

Why is the Discourse integration proprietary? Discourse is [GPLv2+ licensed](https://github.com/discourse/discourse/blob/master/COPYRIGHT.txt).

Okay, I'm not too concerned about Discourse. It didn't bother me at all when codeforphilly.org created me a Discourse account automatically. I'm assuming it's self-hosted and run by the same...

Why not just do local http?

Very cool @arthurfranca, that seems useful. However, I liked the atomic follow events in https://github.com/nostr-protocol/nips/pull/349 more, and I am sad that kind kind 10 and 11 got steamrolled by another...

@vitorpamplona #761 is definitely good. It's almost the same as Mastodon API's "Relationship" entity: https://docs.joinmastodon.org/entities/Relationship/ So the fact other people have done this shows a clear need for it. But...

> As for scaling, I think lots of little events has worse scaling than one big event because there is more total data. At least we can delete old events...

The scaling issue is the number of users following each other on the network, having increasingly large follow lists. Not the total amount of disk space used by relays.

I think it's a good idea. I wish relays could indicate support. `supported_nuds` ?

I like NUDs because NIPs have numerical IDs, eg `supported_nips` is a `number[]`. `supported_nuds` is a `string[]`

Plus my wife will not roll her eyes every time I say NUDs.