This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/members-discuss@ripe.net/
[members-discuss] Promote the use of IRC
- Previous message (by thread): [members-discuss] Promote the use of IRC
- Next message (by thread): [members-discuss] Promote the use of IRC
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Daniel Baeza (Red y Sistemas TVT)
d.baeza at tvt-datos.es
Wed Aug 12 13:34:14 CEST 2015
Seems like all who answered said yes, in the case this go forward, how should we proceed with RIPE? The Network structure, in my opinion, should be: irc.ripe.net (The actual working one) - HUB services.ripe.net - Network Services (Anope), hosted by RIPE.(*) more.irc.servers - Hosted by RIPE Members(**) (*) Services should be configured to use MySQL, then RIPE can make some integration between RIPE Users and IRC Users. Of course, that is if we want to have some kind of association so nobody can be suplanted. (**) The IRC Servers that link to the RIPE IRC Network should accomplish some rules (tbd) and I recommend to spread them. I mean, having 10 servers in France dont make sense. Also, having 10 servers for 40 users dont make sense too. Number of servers to link should be relative to number of users using the IRC. Another note is, in this structure, should be another HUB server, hosted outside of RIPE where all slave servers connect if the RIPE one goes down. Suggestions? --Daniel
- Previous message (by thread): [members-discuss] Promote the use of IRC
- Next message (by thread): [members-discuss] Promote the use of IRC
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]