4 ms·
I was slightly surprised to get all the way through the article without seeing a single mention of NNTP.
by erpellan 6y ago
I was slightly surprised to get all the way through the article without seeing a single mention of NNTP.
- hinkley 6y agoAs a solution or as something that was tried before? Spam as a term transitioned from, “flooding a communication channel with the same message” to “ads sent indiscriminately” due to a green card advertisement on NNTP. What we need along with federation is federated moderation. There are some characterizations of content where we can agree to a label but not whether the label is bad. You might trust me to label gore accurately, I might trust you to label incitement to doxing. We might never agree on what constitutes baiting. Or the crossover point where a flame war should be filtered. So you might ban an individual who I think is “keepin it real” or vice versa. But ten of us shouldn’t have to do the exact same moderation in order to maintain a federation. N log n would be great, 3N would probably be tolerable.
- wmf 6y agoIn retrospect NNTP and IRC, where every message is replicated to every server, are not a good style of federation.
- toast0 6y agoDoes IRC replicate every message to all servers? It's been many years since I was active on IRC, but I thought it was only sending messages along the network tree where needed. So a message to a user would be sent by the sender's server to the recipient's server, or, if not directly connected, to a server one hop closer to that server. And for messages to channels, those only go along the tree if there is a user in the channel from that side of the tree. With today's IRC user count and today's server capabilities, you might have an easier time running on a single server, but there's maybe some latency benefits for users with geographically diverse servers (maybe with support for a server to server mesh instead of a tree, to avoid multi-hop message paths)