ChipTuner on Nostr: > Run it e.g. on the Tor layer and you won't have to deal with DNS, DMARC etc. Right, ...
> Run it e.g. on the Tor layer and you won't have to deal with DNS, DMARC etc.
Right, but this limits access for the average user, HTTP connections are far less censored than SMTP traffic in reality at this point in time.
> and it's not the protocol's fault it has been heavily misused by big players on the clearnet.
Solid point. I failed to accept SMTP as a bare protocol and reusing it for client-server, but if we looked at it that way, lets just skip to HTTPS.
> it's plaintext, human-readable (except MIME extensions for attachments) and can be debugged without all those fancy tools
Which is what buttercat1791 (npub1wqf…qsyn) has been brainstorming. Get the benefits of HTTP upgrades and decades of heavy development for client-server, server-server and so on.
I'm not married to websockets, but I do think nostr fails in client performance, notifications and so on, without persistent connections, but we need clients of all types to be able to communicate directly on the network, not their own servers, over some other messy protocol.
>Nostr tries to reinvent the same functionality
This is true all over the nostr protocol. However keep in mind, a lot, if not most of us, dislike/distrust "mainstream" big-tech/government funded protocols. I'm not saying its right, or efficient, but then what is Bitcoin?
Right, but this limits access for the average user, HTTP connections are far less censored than SMTP traffic in reality at this point in time.
> and it's not the protocol's fault it has been heavily misused by big players on the clearnet.
Solid point. I failed to accept SMTP as a bare protocol and reusing it for client-server, but if we looked at it that way, lets just skip to HTTPS.
> it's plaintext, human-readable (except MIME extensions for attachments) and can be debugged without all those fancy tools
Which is what buttercat1791 (npub1wqf…qsyn) has been brainstorming. Get the benefits of HTTP upgrades and decades of heavy development for client-server, server-server and so on.
I'm not married to websockets, but I do think nostr fails in client performance, notifications and so on, without persistent connections, but we need clients of all types to be able to communicate directly on the network, not their own servers, over some other messy protocol.
>Nostr tries to reinvent the same functionality
This is true all over the nostr protocol. However keep in mind, a lot, if not most of us, dislike/distrust "mainstream" big-tech/government funded protocols. I'm not saying its right, or efficient, but then what is Bitcoin?