Conversation

Notices

1. Embed this notice
   Token (coin@asimon.org)'s status on Thursday, 26-Jan-2023 10:45:54 JST Token

   • 寮
   @ryo your IRC is being spammed. help do something. make the room voiced only
   • Embed this notice
     寮 (ryo@social.076.moe)'s status on Thursday, 26-Jan-2023 10:45:53 JST 寮

     in reply to
     Mind explaining how to make it voiced only?
   • Embed this notice
     寮 (ryo@social.076.moe)'s status on Thursday, 26-Jan-2023 11:54:58 JST 寮

     in reply to
     I ended up having to enforce nick registrations.
     I updated the 地下広場 page accordingly explaining how to do that.
   • Embed this notice
     Token (coin@asimon.org)'s status on Thursday, 26-Jan-2023 11:54:59 JST Token

     in reply to

     • 寮

     @ryo After a quick search according to this page you set the room to +m and it makes it so anyone who is not voiced (+) and above can’t talk. This does mean that new users who join #izakaya wouldn’t be able to start chatting unless someone voices them.

     Also, these bots have been spamming users in private message too, and I currently don’t have any solution off the top of my head for that.

   • Embed this notice
     Token (coin@asimon.org)'s status on Thursday, 26-Jan-2023 13:04:55 JST Token

     in reply to

     • 寮
     @ryo Getting an error "ACCOUNT REQUIRED you must log in with SASL to join this server"
     
     Well I can't create an account if I can't enter it first.
   • Embed this notice
     寮 (ryo@social.076.moe)'s status on Thursday, 26-Jan-2023 13:04:55 JST 寮

     in reply to
     Do you have an XMPP account? Or otherwise are you available at another IRC server?
     Because I don't think it's a good idea to give you a username and password over something everyone can read.
     Or otherwise PM me, because I can't pick your name for whatever reason.
   • Embed this notice
     Token (coin@asimon.org)'s status on Thursday, 26-Jan-2023 13:04:56 JST Token

     in reply to

     • 寮
     @ryo Gotcha. At the moment I seem to be having trouble reconnecting to the server. I'll register when I am able to.
   • Embed this notice
     Token (coin@asimon.org)'s status on Thursday, 26-Jan-2023 13:16:25 JST Token

     in reply to

     • 寮
     @ryo Well. I don't think it's a good idea to fix it manually. If it happens to me, it could happen to another new person to might want to join. Have you asked the others (if you can contact them) if they can rejoin the server?
   • Embed this notice
     寮 (ryo@social.076.moe)'s status on Thursday, 26-Jan-2023 13:16:25 JST 寮

     in reply to
     Well, morena tried to, and contacted me via ilita to have an account created for him, and so I did.
     I'd prefer to solve it a different way, but until a better idea gets found, I'll keep mandatory nick registrations up for now.
     
     Because muting and voicing users only works per channel, bots can still send you on-on-one messages, which is the reason why I went with mandatory nicks.
   • Embed this notice
     Token (coin@asimon.org)'s status on Thursday, 26-Jan-2023 13:20:14 JST Token

     in reply to

     • 寮
     @ryo Are you able to employ a Nickserv service bot that allows first timers to join and registers after logging in?
   • Embed this notice
     寮 (ryo@social.076.moe)'s status on Thursday, 26-Jan-2023 13:20:14 JST 寮

     in reply to
     Any bot you can suggest?
   • Embed this notice
     寮 (ryo@social.076.moe)'s status on Thursday, 26-Jan-2023 13:29:42 JST 寮

     in reply to
     Obviously, that's what I'm using too.
     But in order to use NickServ, you must already be connected.
     But in order to connect, you must already be registered.
     That's where the problem lies.
   • Embed this notice
     Token (coin@asimon.org)'s status on Thursday, 26-Jan-2023 13:29:43 JST Token

     in reply to

     • 寮
     @ryo That's what it's called Nickserv. It's how big networks like Libera Chat use to get people to register. I also know Rizon uses it, and possibly most big/old networks as well.
   • Embed this notice
     Token (coin@asimon.org)'s status on Thursday, 26-Jan-2023 13:40:53 JST Token

     in reply to

     • 寮
     @ryo Thing is, even if I had credentials. It booted me off automatically. I didn't have a chance to input anything. I had everything setup correctly from the tunnels.conf and the connection info. Is the server using the same port number?
     
     God I wish I knew more about this :ablobthinking:
   • Embed this notice
     寮 (ryo@social.076.moe)'s status on Thursday, 26-Jan-2023 13:40:53 JST 寮

     in reply to
     I made no changes on the I2P side.
     Dunno why it happens.
     
     In the ergo config:
     # account options
     accounts:
     # is account authentication enabled, i.e., can users log into existing accounts?
     authentication-enabled: true
     
     # account registration
     registration:
     # can users register new accounts for themselves? if this is false, operators with
     # the `accreg` capability can still create accounts with `/NICKSERV SAREGISTER`
     enabled: true
     
     # can users use the REGISTER command to register before fully connecting?
     allow-before-connect: true
     ...
     # enable login to accounts via the PASS command, e.g., PASS account:password
     # this is useful for compatibility with old clients that don't support SASL
     login-via-pass-command: true
     
     # require-sasl controls whether clients are required to have accounts
     # (and sign into them using SASL) to connect to the server
     require-sasl:
     # if this is enabled, all clients must authenticate with SASL while connecting.
     # WARNING: for a private server, you MUST set accounts.registration.enabled
     # to false as well, in order to prevent non-administrators from registering
     # accounts.
     enabled: true
     
     But if you already had an account, simply add your SASL username and SASL password to the config file of your client, and then connect.