From: Bone Baboon <bone.baboon@disroot.org>
To: guix-devel@gnu.org
Subject: Freenode Administration
Date: Wed, 19 May 2021 13:54:45 -0400 [thread overview]
Message-ID: <87tumybod6.fsf@disroot.org> (raw)
I received this message on Freenode:
```
-jess- [Global Notice] Hi all. It feels like my moral responsibility
to inform all users that administrative control of freenode and
its user data will soon change hands, and I will be resigning from
freenode staff effective immediately. It's been an honour to help
you all.
```
Below are some resignation letters I have seen.
I think this event presents an opportunity for reassessment of
<https://guix.gnu.org/en/contact/irc/>. Two interesting areas to
explore are Freenode alternatives and IRC alternatives / compliments.
# Freenode Alternatives
Here are some Freenode alternative questions I have:
Will Guix continue to use Freenode?
Will Guix create #guix channels on other IRC networks? (Several of the
resignation letters refer to <https://libera.chat/>)
Will Guix start it's own IRC server(s)?
# IRC alternatives / compliments
Some criteria that I have come up with are:
* Free software
* Can be used without a graphical user interface as many GPUs are not
compatible with Linux-libre and can not run Xorg or Wayland window
managers / desktops.
* Peer to peer as a way to avoid the issue of a centralized
administrator changing their administration in undesirable ways.
Some alternatives that come to mind that would need further
investigation include the following. I do not know if any of these meet
all the criteria I mention above.
* Scuttlebutt
** https://scuttlebutt.nz/
** Is there a client that works without a graphical environment?
* DAT
** Are there messaging application for DAT?
** https://www.datprotocol.com/
* IPFS
** Are there messaging application for IPFS?
** https://ipfs.io/
* Jami
** https://jami.net/
** Swarms specifically
*** https://jami.net/swarm-introducing-a-new-generation-of-group-conversations/
*** Swarms are fully distributed and peer-to-peer text conversations,
with a potentially unlimited number of participants.
** <Lutices[m]> on Freenode #jami said:
"https://github.com/AmarOk1412/jami-cli/ no video/audio support but
support swarm"
* RetroShare
** http://retroshare.cc/
** Is there a client that works without a graphical environment?
# Resignation Letter
These are some of the resignation letters I have seen.
https://www.kline.sh/
https://swantzter.se/freenode-resignation/
https://coevoet.fr/freenode.html
https://mniip.com/freenode.txt
https://blog.bofh.it/debian/id_461
https://gist.github.com/JonathanD82/6518b93708e0aaf4b8f92c8e7200816d
https://gist.github.com/jesopo/45a3e9cdbe517dc55e6058eb43b00ed9
https://gist.github.com/pinkisemils/39d4ded8b1639b6f39dcab15618649f5
https://gist.github.com/edk0/478fb4351bc3ba458288d6878032669d
https://fuchsnet.ch/privat/fn-resign-letter.txt
This is an open letter <https://gist.github.com/shadowcat-mst/998cea12794768bdb3da2daeff31baad>.
next reply other threads:[~2021-05-20 0:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-19 17:54 Bone Baboon [this message]
2021-05-20 5:40 ` Freenode Administration Bone Baboon
2021-05-22 23:48 ` raingloom
2021-05-26 2:43 ` Bone Baboon
2021-05-25 22:36 ` Bone Baboon
2021-05-20 8:29 ` François
2021-05-21 16:28 ` Bone Baboon
2021-05-25 22:52 ` Bone Baboon
2021-05-20 10:26 ` Tobias Geerinckx-Rice
2021-05-27 14:33 ` Bone Baboon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tumybod6.fsf@disroot.org \
--to=bone.baboon@disroot.org \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.