Compare commits
No commits in common. "master" and "devel_content" have entirely different histories.
master
...
devel_cont
28
index.html
28
index.html
@ -28,7 +28,20 @@ There is a focus on supporting <a href="https://en.wikipedia.org/wiki/Free_and_o
|
|||||||
|
|
||||||
You can also visit us over The Onion Routing protocol at <a href="http://qzzf2qcfbhievvs5nzkccuwddroipy62qjocqtmgcgh75vd6w57m7yad.onion">our onion address.</a>
|
You can also visit us over The Onion Routing protocol at <a href="http://qzzf2qcfbhievvs5nzkccuwddroipy62qjocqtmgcgh75vd6w57m7yad.onion">our onion address.</a>
|
||||||
|
|
||||||
<a href="/rules.html">Rules</a>
|
Donts:
|
||||||
|
======
|
||||||
|
|
||||||
|
-Repeated harassment of any network user.
|
||||||
|
-Distribution of child pornography.
|
||||||
|
-Dealing of goods and using the network as a space for commericial operations.
|
||||||
|
-Any denial of service against the network or its users.
|
||||||
|
-Use of our network resources or services for malicious intent.
|
||||||
|
-Connecting to the network for any reason using a compromised machine, including as a proxy or loading trojans or bots.
|
||||||
|
-Unwanted advertisement of websites, IRC network, or channels (also known as spamming).
|
||||||
|
-Evading bans, either those placed by network staff or by individual channels.
|
||||||
|
-Impersonation of network staff or services.
|
||||||
|
-Connecting through open proxies.
|
||||||
|
-Any other behavior deemed inappropriate by network staff.
|
||||||
|
|
||||||
|
|
||||||
Services (Clearnet):
|
Services (Clearnet):
|
||||||
@ -37,8 +50,12 @@ Services (Clearnet):
|
|||||||
Communications:
|
Communications:
|
||||||
--------------
|
--------------
|
||||||
|
|
||||||
<a href="/irc.html">IRC</a> | <a href="/xmpp.html">XMPP</a>
|
<a href="/irc.html">IRC</a> | <a href="/xmpp.html">XMPP</a> | <a href="/matrix.html">Matrix</a> | <a href="https://meet.lysergic.dev">Jitsi Video Conferencing </a>
|
||||||
|
|
||||||
|
Search Engines:
|
||||||
|
--------------
|
||||||
|
|
||||||
|
<a href="https://searx.xkek.net">SearX</a> | <a href="https://yacy.xkek.net">YaCy</a>
|
||||||
|
|
||||||
Others:
|
Others:
|
||||||
------
|
------
|
||||||
@ -54,6 +71,11 @@ Communications:
|
|||||||
|
|
||||||
<a href="/irc.html">IRC</a>
|
<a href="/irc.html">IRC</a>
|
||||||
|
|
||||||
|
Search Engines:
|
||||||
|
--------------
|
||||||
|
|
||||||
|
<a href="http://searx.bsbvtqi5oq2cqzn32zt4cr2f2z2rwots3dq7gmdcnlyqoxko2wx6reqd.onion/">SearX</a> | <a href="http://yacy.bsbvtqi5oq2cqzn32zt4cr2f2z2rwots3dq7gmdcnlyqoxko2wx6reqd.onion/">YaCy</a>
|
||||||
|
|
||||||
|
|
||||||
Services (I2P):
|
Services (I2P):
|
||||||
==============
|
==============
|
||||||
@ -66,7 +88,7 @@ Communications:
|
|||||||
|
|
||||||
Contribute:
|
Contribute:
|
||||||
==========
|
==========
|
||||||
Check out the <a href="git.html">/git</a> info page or head directly to the <a href="https://git.casa/">main repository.</a>
|
Check our <a href="git.html">/git</a> info page or head directly to the <a href="https://git.casa/">main repository.</a>
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|||||||
53
irc.html
53
irc.html
@ -17,13 +17,12 @@
|
|||||||
│ │─┤ └─┐ │─┤
|
│ │─┤ └─┐ │─┤
|
||||||
└─┘ ┘ │ ──┘ ┘ │
|
└─┘ ┘ │ ──┘ ┘ │
|
||||||
</pre>
|
</pre>
|
||||||
|
|
||||||
<h3>IRC</h3>
|
<h3>IRC</h3>
|
||||||
<pre>
|
<pre>
|
||||||
|
|
||||||
<a href="/register">Registration</a>
|
<a href="/register">Registration</a>
|
||||||
|
|
||||||
<a href="/kiwi">KiwiIRC Webchat</a> | <a href="/gamja">Gamja Webchat</a>
|
<a href="/kiwi">KiwiIRC Webchat</a> | <a href="/gamja">Gamja Webchat</a> | <a href="/convos">Convos Webchat/Bouncer</a>
|
||||||
|
|
||||||
|
|
||||||
Connection Details:
|
Connection Details:
|
||||||
@ -48,15 +47,23 @@ you can access the network via
|
|||||||
|
|
||||||
Webchat via Tor is available through the links on the top - KiwiIRC will offer the best experience.
|
Webchat via Tor is available through the links on the top - KiwiIRC will offer the best experience.
|
||||||
|
|
||||||
|
2. I2P
|
||||||
|
|
||||||
|
Guide to setting up i2p <a href="/i2p.html">here</a>
|
||||||
|
|
||||||
|
Use the samle configuration shown above.
|
||||||
|
Destination: fzsgc66e52ve5phrcktrekqtko423ihau42u72v4cfg6bg4osuda.b32.i2p
|
||||||
|
Port: 6668
|
||||||
|
SSL/TLS: False
|
||||||
|
|
||||||
Account registration FAQ
|
Account registration FAQ
|
||||||
========================
|
========================
|
||||||
|
|
||||||
1. How do I register my nickname / account?
|
1. How do I register my nickname / account?
|
||||||
|
|
||||||
Use this command, substituting your desired password:
|
Use this command, substituting your desired password and e-mail address:
|
||||||
|
|
||||||
/msg NickServ register mySecretPassword
|
/msg NickServ register mySecretPassword
|
||||||
|
|
||||||
You can also register on this page <a href="/register">here</a>
|
You can also register on this page <a href="/register">here</a>
|
||||||
|
|
||||||
@ -65,11 +72,14 @@ Once you register your nick it becomes your account name. It is the name with wh
|
|||||||
|
|
||||||
2. How do I authenticate to my nickname?
|
2. How do I authenticate to my nickname?
|
||||||
|
|
||||||
You should enable SASL in your client.
|
You should enable SASL in your client. For clients like Hexchat the Username field needs to be populated with the name that you registered.
|
||||||
|
|
||||||
|
|
||||||
- If your client doesn't support SASL, then update to a good client!
|
If your client doesn't support SASL, there are potential workarounds;
|
||||||
- Alternatively, you can use the "PASS" method
|
you may be able to script your client to authenticate to NickServ
|
||||||
|
automatically, with `/msg NickServ identify nickname password`.
|
||||||
|
|
||||||
|
Ask in #help for support with this.
|
||||||
|
|
||||||
3. What are the benefits of registering my nickname?
|
3. What are the benefits of registering my nickname?
|
||||||
|
|
||||||
@ -82,11 +92,34 @@ as an "IRC bouncer" on your behalf. Specifically:
|
|||||||
c. Optionally, the server can keep you present on the server even if
|
c. Optionally, the server can keep you present on the server even if
|
||||||
you have no connected clients. To enable this, use the following command:
|
you have no connected clients. To enable this, use the following command:
|
||||||
`/msg NickServ set always-on true`
|
`/msg NickServ set always-on true`
|
||||||
d. You will be able to receive <a href="https://github.com/ergochat/ergo/blob/master/docs/USERGUIDE.md#history">history</a> playback.
|
d. You will be able to receive history playback (see below).
|
||||||
|
|
||||||
|
You can also request a vhost in the channel #help (i.e., a fake hostname that will be displayed
|
||||||
|
in place of your cloaked IP-based hostname).
|
||||||
|
|
||||||
|
|
||||||
|
4. History Playback.
|
||||||
|
|
||||||
|
1 If you set your client to `always-on` (see the previous section for details), you can set a "device ID" for each device you use. Oragono will then remember the last time your device was present on the server, and each time you sign on, it will attempt to replay exactly those messages you missed.
|
||||||
|
2 You can set the SASL Username as `nick@phone` or `nick@laptop` while connecting. This allows you to fetch history based on your "DeviceID" which is `phone` or `laptop` in these cases.
|
||||||
|
3 If you only have one device, you can set your client to be always-on and furthermore `/NS SET autoreplay-missed true`. This will replay missed messages, with the caveat that you must be connecting with at most one client at a time.
|
||||||
|
4 You can autoreplay a fixed number of lines (e.g., 25) each time you join a channel using `/NS SET autoreplay-lines 25`.
|
||||||
|
5 You can manually request history using `/history #channel 1h` (the parameter is either a message count or a time duration). (Depending on your client, you may need to use `/QUOTE history` instead.)
|
||||||
|
6 You can also enable history for private messages called `DMs` by passing the following command: `/NS SET dm-history true`.
|
||||||
|
|
||||||
|
#### Sessions and Clients
|
||||||
|
|
||||||
|
- You can check how many of your sessions are online with `/NS SESSIONS `and the idle times for those.
|
||||||
|
- You can list your clients in further detail with `/NS CLIENTS list`
|
||||||
|
- You can use `/NS CLIENTS logout client-id/all` to either logout a single session or all sessions.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
For more information checkout the <a href="https://github.com/ergochat/ergo/blob/master/docs/USERGUIDE.md">UserGuide</a> and
|
|
||||||
the <a href="https://github.com/ergochat/ergo/blob/master/docs/MANUAL.md">Manual</a>.
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|||||||
45
matrix.html
Normal file
45
matrix.html
Normal file
@ -0,0 +1,45 @@
|
|||||||
|
<!DOCTYPE html>
|
||||||
|
<html>
|
||||||
|
|
||||||
|
<head>
|
||||||
|
<meta charset="UTF-8">
|
||||||
|
<link rel="stylesheet" href="styles.css">
|
||||||
|
<title>LibertaCasa</title>
|
||||||
|
</head>
|
||||||
|
|
||||||
|
<body>
|
||||||
|
<pre>
|
||||||
|
┬ ┌┬┐ ┬─┐ ┬─┐ ┬─┐ ┌┐┐ ┬─┐
|
||||||
|
│ │ │─│ │─ │┬┘ │ │─┤
|
||||||
|
┘─┘ └┴┘ │─┘ ┴─┘ │└┘ ┘ ┘ │
|
||||||
|
|
||||||
|
┌─┐ ┬─┐ ┐─┐ ┬─┐
|
||||||
|
│ │─┤ └─┐ │─┤
|
||||||
|
└─┘ ┘ │ ──┘ ┘ │
|
||||||
|
</pre>
|
||||||
|
<h3>Matrix</h3>
|
||||||
|
<pre>
|
||||||
|
|
||||||
|
Connection Details:
|
||||||
|
===================
|
||||||
|
|
||||||
|
The only fully featured Matrix client is Element. Our instance is available at <a href="https://element.liberta.casa/">https://element.liberta.casa</a>.
|
||||||
|
|
||||||
|
After having created an account in Element, it is possible to connect other Matrix clients using the Homeserver address <code>matrix.liberta.casa</code>.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
<footer>
|
||||||
|
<a href="mailto:hello@liberta.casa"> Contact </a>
|
||||||
|
</footer>
|
||||||
|
</pre>
|
||||||
|
</body>
|
||||||
|
</html>
|
||||||
53
rules.html
53
rules.html
@ -1,53 +0,0 @@
|
|||||||
<!DOCTYPE html>
|
|
||||||
<html>
|
|
||||||
|
|
||||||
<head>
|
|
||||||
<meta charset="UTF-8">
|
|
||||||
<link rel="stylesheet" href="styles.css">
|
|
||||||
<title>LibertaCasa - Rules</title>
|
|
||||||
</head>
|
|
||||||
|
|
||||||
<body>
|
|
||||||
<pre>
|
|
||||||
┬ ┌┬┐ ┬─┐ ┬─┐ ┬─┐ ┌┐┐ ┬─┐
|
|
||||||
│ │ │─│ │─ │┬┘ │ │─┤
|
|
||||||
┘─┘ └┴┘ │─┘ ┴─┘ │└┘ ┘ ┘ │
|
|
||||||
|
|
||||||
┌─┐ ┬─┐ ┐─┐ ┬─┐
|
|
||||||
│ │─┤ └─┐ │─┤
|
|
||||||
└─┘ ┘ │ ──┘ ┘ │
|
|
||||||
</pre>
|
|
||||||
<h3>Rules</h3>
|
|
||||||
<pre>
|
|
||||||
|
|
||||||
Donts:
|
|
||||||
========
|
|
||||||
|
|
||||||
-Repeated harassment of any network user.
|
|
||||||
-Distribution of child pornography.
|
|
||||||
-Dealing of goods and using the network as a space for commericial operations.
|
|
||||||
-Any denial of service against the network or its users.
|
|
||||||
-Use of our network resources or services for malicious intent.
|
|
||||||
-Connecting to the network for any reason using a compromised machine, including as a proxy or loading trojans or bots.
|
|
||||||
-Unwanted advertisement of websites, IRC network, or channels (also known as spamming).
|
|
||||||
-Evading bans, either those placed by network staff or by individual channels.
|
|
||||||
-Impersonation of network staff or services.
|
|
||||||
-Connecting through open proxies.
|
|
||||||
-Any other behavior deemed inappropriate by network staff.
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
<footer>
|
|
||||||
<a href="mailto:hello@liberta.casa"> Contact </a>
|
|
||||||
</footer>
|
|
||||||
</pre>
|
|
||||||
</body>
|
|
||||||
</html>
|
|
||||||
45
sso.html
45
sso.html
@ -1,45 +0,0 @@
|
|||||||
<!DOCTYPE html>
|
|
||||||
<html>
|
|
||||||
|
|
||||||
<head>
|
|
||||||
<meta charset="UTF-8">
|
|
||||||
<link rel="stylesheet" href="styles.css">
|
|
||||||
<title>LibertaCasa - git</title>
|
|
||||||
</head>
|
|
||||||
|
|
||||||
<body>
|
|
||||||
<pre>
|
|
||||||
┬ ┌┬┐ ┬─┐ ┬─┐ ┬─┐ ┌┐┐ ┬─┐
|
|
||||||
│ │ │─│ │─ │┬┘ │ │─┤
|
|
||||||
┘─┘ └┴┘ │─┘ ┴─┘ │└┘ ┘ ┘ │
|
|
||||||
|
|
||||||
┌─┐ ┬─┐ ┐─┐ ┬─┐
|
|
||||||
│ │─┤ └─┐ │─┤
|
|
||||||
└─┘ ┘ │ ──┘ ┘ │
|
|
||||||
</pre>
|
|
||||||
|
|
||||||
<h3> Single Sign On </h3>
|
|
||||||
<pre>
|
|
||||||
<p> With a growing list of services, it becomes apparent that multiple logins aren't LUSER friendly.
|
|
||||||
This is being attempted to be resolved by a Single Sign On system. It is a work in progress with many services already having been integrated.
|
|
||||||
These are currently: IRC (opt-in), XMPP, Gitea, Etherpad, Confluence.</p>
|
|
||||||
|
|
||||||
Registering for SSO
|
|
||||||
=====================
|
|
||||||
|
|
||||||
1. Click <a href='https://sso.casa'>here</a> and then click on the "Manage" button.
|
|
||||||
2. Fill up the fields and ensure the email is valid as it shall recieve a confirmation link.
|
|
||||||
3. Click the "Register" link to complete the procedure and recieve the confirmation email.
|
|
||||||
3. Once you Verify your account you can log into the sso-enabled services using the same credentials.
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
<footer>
|
|
||||||
<a href="mailto:hello@liberta.casa"> Contact </a>
|
|
||||||
</footer>
|
|
||||||
</pre>
|
|
||||||
</body>
|
|
||||||
</html>
|
|
||||||
16
xmpp.html
16
xmpp.html
@ -26,24 +26,20 @@
|
|||||||
|
|
||||||
|
|
||||||
There are quite a few clients available. You can check the overview <a href="https://xmpp.org/software/clients.html">here</a>.
|
There are quite a few clients available. You can check the overview <a href="https://xmpp.org/software/clients.html">here</a>.
|
||||||
|
You can register by choosing a "name", which will make for the first part of the JID.
|
||||||
|
|
||||||
You can use our XMPP server and federate to others by using your <a href="https://sso.casa/">LibertaCasa SSO credentials</a>.
|
JID: name@liberta.casa
|
||||||
|
(and the password of your choice).
|
||||||
JID: username@liberta.casa
|
|
||||||
Password: your SSO password
|
|
||||||
|
|
||||||
Currently, you can use any XMPP/Jabber client to connect to the following server:
|
|
||||||
|
|
||||||
Host: xmpp.liberta.casa
|
Host: xmpp.liberta.casa
|
||||||
Port: 5222
|
Port: 5222
|
||||||
TLS/SSL: Enforced
|
TLS/SSL: Enforced
|
||||||
|
|
||||||
Installing a desktop client, i.e. <a href="https://dino.im/">Dino</a> or <a href="https://gajim.org/">Gajim</a> is recommended. Mobile client in the form of Android, i.e. <a hreF="https://conversations.im/">Conversations</a>, or iOS, i.e. <a href="https://siskin.im/">Siskin</a>, clients are viable options as well.
|
If you don't feel like installing any additional software,
|
||||||
|
you can register for an account <a href="https://xmpp.liberta.casa/register_web">here</a>, and
|
||||||
|
use the <a href="https://liberta.casa/candy/">Candy webchat</a>, however keep in mind that this makes for an extremely rudimentary experience.
|
||||||
|
|
||||||
Alternatively, you can use the <a href="https://xmpp.lib.casa/">Converse.JS</a> or <a href="https://liberta.casa/candy/">Candy webchat</a>, however keep in mind that those are both highly experimental services, making for an extremely rudimentary experience with no guaranteed functionality.
|
|
||||||
|
|
||||||
<br><br><br>
|
|
||||||
<a href='https://compliance.conversations.im/server/liberta.casa'><img src='https://compliance.conversations.im/badge/liberta.casa'></a>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|||||||
Loading…
Reference in New Issue
Block a user