Replicant

h1. CommunityAndContact

The Replicant community has several places where people interact together.

h2. Mailing list

Most Replicant developers are on the mailing list, as it is also used to review patches. Many non-developers that are contributors or that don't contribute to Replicant are also on the mailing list.

It's being used for many things:

* Ask questions about Replicant, discuss about issues, etc.

* Discuss about Replicant in general.

* Discuss about Replicant contributions and development

* Review patches

The volume is moderate but there are sometimes spikes due to the to a huge patch set being sent.

To register you can use the "Mailman interface":https://lists.osuosl.org/mailman/listinfo/replicant .

h3. Archives

The Mailman interface has a non-searchable archive of the list: "Replicant Archives":https://lists.osuosl.org/pipermail/replicant/

There are independent projects that keep an archive of the list in a searchable format:

* "The Mail Archive - current":https://www.mail-archive.com/replicant@osuosl.org

* "The Mail Archive - old":https://www.mail-archive.com/replicant@lists.osuosl.org

* "Narkive":https://replicant.osuosl.narkive.com (seems to have stalled)

h2. Forums

The "Replicant forums":https://redmine.replicant.us/projects/replicant/boards are used for similar things than the mailing list, however:

* Patches are not reviewed on the forums

* Less developers tend to be active on the forums

h2. IRC

Most Replicant developers and contributors, as well as people who are interested in our project, are present on the Replicant IRC channel(s). People from other communities are also there as we collaborate on various things, like adding support for devices in Upstream Linux.

IRC, or "Internet Relay Chat":https://en.wikipedia.org/wiki/Internet_Relay_Chat/, is our most ephemeral communication platform, in the sense that we do not publish "message logs":https://en.wikipedia.org/wiki/Log_file#Message_logs of the channel, nor are we aware of anyone else that unofficially does so. It is, however, common for channel participants to collect and store IRC message logs on their local machines or a VPS to catch up on recently missed conversations and search older messages by keyword to help remember details of past discussions. As the #replicant channels are public, sometimes conversations with important technical information are saved mostly as-is in bug reports or on the Replicant wiki.

In practice, Replicant has three IRC channels hosted on three separate IRC chat servers, but it appears as through there is only one channel since they are all bridged together. Bridged means that a user can join only one of the channels and send and receive messages with users on all the other channels because all messages are forwarded across every channel.

Our three IRC Channels are:

* #replicant on "Libera.Chat":https://libera.chat/

* #replicant on "OFTC":https://oftc.net/

* #replicant on "HackInt":https://hackint.org

* -#replicant on "Freenode":https://freenode.net/- This channel is closed. See "the Wikipedia article on Freenode":https://en.wikipedia.org/wiki/Freenode#Ownership_change_and_conflict for more details on the issue.

Replicant has taken a number of steps in order to ensure that "Tor":https://torproject.org/ users who want to connect to our IRC channel are not discriminated against.

Due to Libera.Chat's policies, users who wish to regularly connect and engage with our Libera.Chat IRC channel via "Tor":https://torproject.org/ need to use the "SASL":https://libera.chat/guides/sasl (Simple Authentication and Security Layer) framework for authentication every time they connect to Libera.Chat's server and comply with "a couple other restrictions":https://libera.chat/guides/connect#accessing-liberachat-via-tor. Additionally, they require all new Libera.Chat accounts to be created over the "clearnet":https://en.wikipedia.org/wiki/Clearnet_(networking), which allows them to tie their user's personal IP addresses to every account on their network. Since the personal identity of a user can often be determined simply by acquiring that user's IP address, we recommend that users who want to preserve their anonymity do not create a Libera.Chat account.

The Freenode IRC channel was our first IRC channel. At the time it had similar policies to those of Libera.Chat regarding Tor users, which didn't meet all of our users' anonymity needs. In order to address this, Replicant created a second IRC channel on the OFTC IRC server. As "they clearly state":https://www.oftc.net/Tor/, OFTC "does not require users to first connect in the clear and register with services to allow connecting via Tor". While OFTC was an improvement in some ways over Freenode, it doesn't have an officially supported "Tor onion service":https://support.torproject.org/onionservices/, so Tor users that require the utilization of such a feature can't connect to OFTC's server. 

"HackInt":https://hackint.org IRC server allows anonymous connections via their officially supported Tor onion services and also allows users to register accounts through them. As such, we created a bridged IRC channel on their server as well. As an added benefit, HackInt also utilizes a privacy preserving "Hashcash":https://en.wikipedia.org/wiki/Hashcash implementation instead of a "CAPTCHA":https://en.wikipedia.org/wiki/CAPTCHA in their account creation process, as explained "on their Tor page":https://hackint.org/transport/tor/.

The Freenode channel was closed because the network was victim of an "hostile takeover" according to their former volunteer staff members. We can read more about it on the "Wikipedia's Freenode page":https://en.wikipedia.org/wiki/Freenode#Ownership_change_and_conflict.

h2. Matrix rooms

There are Matrix rooms which are bridged to our various IRC channels:

* @#replicant:hackint.org@ - "bridged to HackInt":https://hackint.org/transport/matrix

* @#_oftc_#replicant:matrix.org@ - bridged to OFTC

Fortunately you get to see all messages, from all 3 IRC networks, thanks to the "bridge bot":https://git.replicant.us/infrastructure/matterbridge/ present on all networks.

h3. Limitations

h4. Multi-line messages

The bridges on these rooms only relay multi-line messages up to a certain number of lines. HackInt up to 6 lines and OFTC up to 3 lines. Above that, messages get sent with a tiny preview and a paste link: @<matrixsomeone[m]> Hello!... (full message at <https://matrix.org/blahblahblash>)@

h4. Edits

Edited messages get resent in all or in a substitution-like format @s///@.

h4. Outdated user list

Joins and quits seem to be improperly reflected in the room's user list. As such, it may list users that are now offline and may miss users that are currently online.

h2. XMPP Multi-User Chat

HackInt provides a "XMPP MUC":https://hackint.org/transport/xmpp which is bridged to our HackInt IRC channel.

* @#replicant@irc.hackint.org@

There are bridges to OFTC and Libera.chat provided by "Cheogram":https://cheogram.com:

* @#replicant%irc.oftc.net@irc.cheogram.com@

* @#replicant%irc.libera.chat@irc.cheogram.com@

Do note that all IRC networks are bridged. You just need to enter in one of these MUCs.

h2. Mastodon

Replicant has a "Mastodon account":https://mamot.fr/@Replicant .

The main use is to relay the "blog posts":https://blog.replicant.us .

We do not check that account often. If you contact us there it might take us some time to see the message.

h2. Private contact address

We also have a private contact address for the project, for inquiries that are private / confidential. 

Very few people receive that list, and the ones that do tend to be very busy. So if your question can be answered on the "mailing list":https://lists.osuosl.org/mailman/listinfo/replicant, please use the mailing list. Unless you are writing about an explicitly private matter, we will likely advise you to write to the mailing list as we want to respond publicly when answering inquires as often as possible. We also won't forward your mail to the mailing list ourselves as otherwise we could mistakenly publish information that you wanted to keep private. See the [[PrivateContact]] page for use case and on how to use such contact address.

If you didn't manage to register to the mailing list, or if it doesn't work for you for some reasons, it's still possible to send a mail to the mailing list address without being registered. In that case we will be notified about it and we will be able to make it go through by manually going to the mailing list interface.