Blame
Date:
Fri Mar 11 05:00:19 2022
UTC
Message:
Daily backup
11
2021-12-17
text=(:title Federate IRC:)%0a%0aTo maximize user freedom, each team should be able to run its%0aown IRC subnetwork to set its own policies. These subnetworks%0acan then be [[relay/relay|relayed]] together to form a true federation for IRC.%0a%0aEach subnetwork will have its own unique user and channel namespace. For example, username@example.com will be distinct from username@domain.net. IRC should take a similar approach to email/matrix/fediverse.%0a%0aIf the example.com network bans #channel, that ban will not affect #channel on domain.net. A ban of username@example.com does not affect username@domain.net.%0a%0aEach team will now be able to run its own [[census/census|IRC services]]. This will prevent complete centralized control of services while also ensuring better redundancy.%0a
15
2021-12-17
diff:1639749807:1620467598:=3,11c3,9%0a%3c To maximize user freedom, each team should be able to run its%0a%3c own IRC subnetwork to set its own policies. These subnetworks%0a%3c can then be [[relay/relay|relayed]] together to form a true federation for IRC.%0a%3c %0a%3c Each subnetwork will have its own unique user and channel namespace. For example, username@example.com will be distinct from username@domain.net. IRC should take a similar approach to email/matrix/fediverse.%0a%3c %0a%3c If the example.com network bans #channel, that ban will not affect #channel on domain.net. A ban of username@example.com does not affect username@domain.net.%0a%3c %0a%3c Each team will now be able to run its own [[census/census|IRC services]]. This will prevent complete centralized control of services while also ensuring better redundancy.%0a---%0a> Each team will have its own unique user and channel namespace so username@example.com will be distinct from username@domain.net. This is the same approach as email/matrix/fediverse.%0a> %0a> If example.com bans #channel, that ban will not affect #channel on domain.net. A ban of username@example.com does not affect username@domain.net.%0a> %0a> Each team will run its own [[census/census|IRC services]]. This will prevent complete centralized control of services while also ensuring better redundancy.%0a> %0a> The best way to achieve federation is to have separate networks linked together using an [[relay/relay|IRC relay]]. This would require the fewest changes to ngircd.%0a\ No newline at end of file%0a
18
2021-12-17
diff:1620467598:1620393649:=7,9c7,9%0a%3c Each team will run its own [[census/census|IRC services]]. This will prevent complete centralized control of services while also ensuring better redundancy.%0a%3c %0a%3c The best way to achieve federation is to have separate networks linked together using an [[relay/relay|IRC relay]]. This would require the fewest changes to ngircd.%0a\ No newline at end of file%0a---%0a> Each team will run its own IRC services. This will prevent complete centralized control of services while also ensuring better redundancy.%0a> %0a> The best way to achieve federation is to have separate networks linked together using an IRC relay. This would require the fewest changes to ngircd.%0a\ No newline at end of file%0a
21
2021-12-17
diff:1620393649:1620391569:=6,7d5%0a%3c %0a%3c Each team will run its own IRC services. This will prevent complete centralized control of services while also ensuring better redundancy.%0a
24
2021-12-17
diff:1620391569:1620391108:=1,7c1,7%0a%3c (:title Federate IRC:)%0a%3c %0a%3c Each team will have its own unique user and channel namespace so username@example.com will be distinct from username@domain.net. This is the same approach as email/matrix/fediverse.%0a%3c %0a%3c If example.com bans #channel, that ban will not affect #channel on domain.net. A ban of username@example.com does not affect username@domain.net.%0a%3c %0a%3c The best way to achieve federation is to have separate networks linked together using an IRC relay. This would require the fewest changes to ngircd.%0a\ No newline at end of file%0a---%0a> Federate IRC%0a> %0a> Each team to have its own unique user and channel namespace so username@planetofnix.com will be distinct from username@lecturify.net. The approach is similar to the way matrix/fediverse does it.%0a> %0a> If planetofnix.com wants to ban #channel on their server, it is not banned automatically on lemon.ircnow.org. I'm not sure if this should be implemented by ircnowd, or by an extra layer of glue (an IRC relay).%0a> %0a> I suspect the best way to handle this is with an IRC relay since that would require minimal changes in ngircd%0a
27
2021-12-17
diff:1620391108:1620391108:=1,7d0%0a%3c Federate IRC%0a%3c %0a%3c Each team to have its own unique user and channel namespace so username@planetofnix.com will be distinct from username@lecturify.net. The approach is similar to the way matrix/fediverse does it.%0a%3c %0a%3c If planetofnix.com wants to ban #channel on their server, it is not banned automatically on lemon.ircnow.org. I'm not sure if this should be implemented by ircnowd, or by an extra layer of glue (an IRC relay).%0a%3c %0a%3c I suspect the best way to handle this is with an IRC relay since that would require minimal changes in ngircd%0a