5 ms·

Not implementing server-level blocklists is almost a guaranteed method of getting your instances added to federated blocklists. I see that this is not Activity

Not implementing server-level blocklists is almost a guaranteed method of getting your instances added to federated blocklists. I see that this is not ActivityPub compliant, so presumably this would only federate with other Chatternet instances? If that's the case, I recommend hurrying to implement a solid product vision, because otherwise "no deplatforming" is your primary sell, and the people who are buying are perceived as folks who have been deplatformed already. It's a hard problem right now to get some people to separate "free speech" and "hate speech" in social media, and until that's got a solution I'm not sure a slightly-different protocol will move the needle.

garrinm 4y ago
You bring up some good points. Indeed Chatter Net as-is isn't able to fully integrate in the Fediverse. I think it'll be possible to get there, and I'd like to see the project get there, but in the meantime its more of a standalone network. The only real difference between the Fediverse and Chatter Net is that in Chatter Net all messages are signed. To know the origin of a message you simply verify the signature. Whereas in the Fediverse you have to trust that the server authenticated the user and stored the data correctly. The consequence is that in Chatter Net federation happens user-to-server, not server-to-server. That's because a server can trust messages coming from any arbitrary user, so long as it has a valid signature. The server can choose to filter messages from unknown users of course. I think maybe a more important selling point, from that perspective, is that as a user of Chatter Net, you consume messages only from identities you trust (follow). So you can completely filter out unwanted communities. This will take a lot more work to correctly describe in the docs. And the implementation isn't fully sorted out yet either.
nathias 4y ago
A hard problem is selling it short, it is impossible to separate them, because they are one and the same.

garrinm 4y ago

You bring up some good points. Indeed Chatter Net as-is isn't able to fully integrate in the Fediverse. I think it'll be possible to get there, and I'd like to see the project get there, but in the meantime its more of a standalone network. The only real difference between the Fediverse and Chatter Net is that in Chatter Net all messages are signed. To know the origin of a message you simply verify the signature. Whereas in the Fediverse you have to trust that the server authenticated the user and stored the data correctly. The consequence is that in Chatter Net federation happens user-to-server, not server-to-server. That's because a server can trust messages coming from any arbitrary user, so long as it has a valid signature. The server can choose to filter messages from unknown users of course. I think maybe a more important selling point, from that perspective, is that as a user of Chatter Net, you consume messages only from identities you trust (follow). So you can completely filter out unwanted communities. This will take a lot more work to correctly describe in the docs. And the implementation isn't fully sorted out yet either.

nathias 4y ago

A hard problem is selling it short, it is impossible to separate them, because they are one and the same.