Mikaela/mikaela.github.io
1
0
Fork 0
mirror of https://github.com/mikaela/mikaela.github.io/ synced 2024-11-19 10:29:23 +01:00
Code Issues Projects Releases Wiki Activity
fbc7418338
mikaela.github.io/pages/discuss.markdown

7.2 KiB
Raw Blame History

Discuss

I have a public instant messaging chatroom for comments to my blog and other things I do. They are connected together by Matterbridge.

As Code of Conduct, Contributor Covenant applies.
I don’t see a reason for forking it as this community is forming around me and my website while I would have separate community for any actual Open Source Software project if I begun any that grew bigger.

As for languages; English is preferred due to majority of the discussion participants speaking it, but Finnish and Esperanto are also fine.
I sadly don’t consider myself capable of holding a discussion in other languages, but I do hope to be able to grow this list in the future.

A couple of words on protocols

  • IRC was invented in 1988 and regardless of developing integrated message storage since then, it’s still trivial to setup and runs well on a toaster. IRC servers are generally easy to enable Tor support on and IRC clients widely come with proxy settings where Tor can be enabled. My personal IRC history begins in 2010 as user and since then I have also opered mostly on Charybdis+Atheme and nowadays on a couple of Ergos.
  • XMPP runs on a bit more powerful toaster and the servers talk to each other without prior approval, it was originally introduced in 1999. I don’t have a record on when I begun using it as all multi-protocol chat apps that were common even before 2010 supported it. I haven’t had a need or desire to selfhost.
  • Telegram was introduced in 2013 and is a popular instant messenger with many open source clients (not server) also on minority platforms (by third parties). It’s favoured by many for stickers and ease-to-use, while that comes with concern on security and privacy.
  • Matrix was introduced in 2014 and I started using it in 2016. Many of the client and server implementations are heavy, especially on server side requiring what to outside looks like a constant maintenance to deal with the implementation performance issues, I am not interested in even trying to selfhost a Matrix (home)server and bridges until the situation significantly improves. Matrix clients also seldom support connecting through Tor easily, while the Synapse server by Matrix.org team doesn’t support connecting through I2P or Tor at all.

And on transports, relays and bridges

  • One of the marketing points of XMPP was to connect to other protocols by means of transports. They plug into a XMPP server and can be provided either by yours or be open for other XMPP servers.
  • The word relay is often used on bots which copy messages from one protocol/network and paste (or more simply said relay) it to another. They aren’t transparent and thus the messages from them appear to be coming from bots beginning with the message sender instead of being completely transparent. This is what is commonly used on IRC to connect to other IRC networks or protocols.
  • Bridges are popularised by Matrix and are almost XMPP transports. However while XMPP transports connect to the other protocol, bridges attempt to copy everything on both sides so Matrix users see each other directly instead of through the transport on the other side and on the other side of open protocols Matrix users can be interacted with as if they were native to it.
    • Unlike XMPP, the bridges also tend to be heavy and require a full homeserver setup. The IRC bridge also generally requires blessing from the IRC network and while some public bridges exist, they move the control away from you hijacking the room to their rules and often have performance trouble compared to “local toaster matterbridge”.