I think that the ActivityPub protocol is better than Twitter, Facebook, etc, but is still too many problematic and is more complicated than it should be. I can

I think that the ActivityPub protocol is better than Twitter, Facebook, etc, but is still too many problematic and is more complicated than it should be. I can see many problems, one of which is that it seems to default to HTML and some services seem to require it, and that it probably requires Unicode too, and that auth services may also need a web browser to work, which is also no good. There is NNTP, email, IRC, etc, that you can use, which I think can work better. (I invented "Unusenet" to avoid namespace collision, if needed; there are a few different ways to define names in Unusenet, one of which is reverse domain names) An implementation should not need a web browser or something as complicated as it, and should be independent of the programming language to be used (you could use C, JavaScript, etc), with optional TLS. Of course you will need to be able to block messages, or to not block them if that is what you wish, but that will be possible easily enough. ActivityPub does this too, but so does NNTP, email, IRC, etc; you can define your own filter criteria, and NNTP can have moderated or unmoderated newsgroups. Many clients can have scoring files, and a few support global scoring files (which the user can install or not at their choice, but unfortunately these do not seem to be portable across different implementations, as far as I can tell). Mailing lists are still sometimes used, but NNTP would be better, I think.