permacomputing

Source repository for the main permacomputing wiki site
git clone http://git.permacomputing.net/repos/permacomputing.git # read-only access
Log | Files | Refs

commit d71a9df55ca1d639787141a0350c5bd51025cf5e
parent de8536e7f5fb7bfcca1d8bfc289cd6f2cbfdd709
Author: Ville-Matias Heikkila <viznut@low.fi>
Date:   Sat, 23 Jul 2022 18:23:39 +0300

typo

Diffstat:
MIRC.mdwn | 2+-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/IRC.mdwn b/IRC.mdwn @@ -21,7 +21,7 @@ Cons: * Breaking of inter-server connections cause "splits" where messages from some servers never reach the other servers. * Similarly, the clients only receive those messages that were sent when they were connected. * While the lack of a server-side message storage makes the servers more lightweight, it encourages individual users to maintain persistent connections to the servers and to keep logs of their own. Thus, the total need for computing resources ends up being higher than what it would be with server-side persistence. -* The setting up of a constant client connection is often more complicated task than using a website or an "app". +* The setting up of a constant client connection is often more complicated for a user than using a website or an "app". * The nature of purely realtime feeds and the flat structure of the messaging make it difficult to maintain several discussions on the same channel at the same time. * The difficulty of participating in "old" discussions easily contributes to the "fear of missing out" that is a major element of IRC addiction.