#ircdriven Bot Logged User list

General Technology Programming Assistance
Network: Libera.Chat
Modes:
Last Seen: 3 hours ago
Topic: IRC Driven :: https://www.ircdriven.com :: The website is considered out of beta status at this time as most features have been built :: Seeking networks and assistance with Python development :: IRC Driven is just old now. ::
#1,777
Rank
18
Users

Channel Log Archive for #ircdriven

Prev
Next
* All times are UTC
Monday, August 1, 2022
[03:22:25] Valware ahh yes, good ideas
[03:22:25] Valware lol
[03:22:44] * Valware wonders what genius3000 thinks
[03:59:37] genius3000 Other than initial thought that bot-tag could be expanded to include a manager/owner, not sure I'm liking the idea of users' bots being BotServ (services) usable. Maybe not seeing the full picture or just typical 'change is bad' initial reaction, there be my thoughts currently.
[06:38:27] * Netsplit 3 users quit: net ↔ split
Click to toggle user list
ComputerTech worm` ghostnode
[06:38:41] * Netsplit healed 2 users rejoined
Click to toggle user list
worm` ghostnode
[06:39:31] * ComputerTech joined #ircdriven
[06:39:31] * ChanServ set mode +v ComputerTech
[06:50:58] * Netsplit 2 users quit: net ↔ split
Click to toggle user list
Jobe KnownSyntax
[06:51:29] * Netsplit healed 2 users rejoined
Click to toggle user list
KnownSyntax Jobe
[07:33:20] * youngpadawan quit (Quit: youngpadawan)
[07:36:30] * Awaru joined #ircdriven
[13:42:07] * Awaru is now known as makeircgreatagai
[13:43:52] * makeircgreatagai is now known as join
[13:47:19] * join quit (Quit: join)
[13:47:34] * join joined #ircdriven
[16:29:26] + daniel2 [9:22:25 pm] <Valware> ahh yes, good ideas
[16:29:26] + daniel2 [9:22:25 pm] <Valware> lol
[16:29:28] + daniel2 I was so confused
[16:29:34] + daniel2 I thought I had someone ignored or something
[16:29:58] + daniel2 My ADHD makes it difficult for me to read stuff
[19:20:42] newton I feel like it'll be easier to get bot owners to opt into the first part, identifying who owns it, then the second part, specific ircd (protocol?)/services support
[19:22:28] newton it all sounds pretty specific to using your network and services altogether
[20:11:58] Jobe <Valware> The idea at the moment is to create a module which will allow better bot interfacing. The idea is to allow a user to mark their bot as managed by them. Initially I thought this could work in METADATA, but because of the must-know information (“this bot is managed/owned by so-and-so”) it would be better to have this information transparent in a /WHOIS, and for a deeper attempt to help
[20:12:16] Jobe my only concern, is how do you prevent a bot owner from saying a bot is managed by someone else then making that bot abusive
[20:13:56] newton seems like the person would have to claim ownership rather than the bot saying who owns it and services handling the verification through the bot and updating the WHOIS?
[20:19:52] newton I guess what I said earlier be negated if people are easily able to add a plugin to their bot (assuming they're using one of the popular open source ones) that integrates with the bots existing authentication system and knows how to respond to BotServ asking for confirmation
[20:21:17] newton /bs claim <bot> <token> -> BotServ /msg <bot> confirm-ownership <account> <token> -> confirmation
[20:23:11] Jobe I suppose a simpler and possibly more logical option would be for services to provide a command to allow authed users to "register a bot account"
[20:23:27] Jobe that would create a bot account, and at the same time mark it as owned/managed by the user who registered it
[20:36:33] newton oh yeah. much better
[20:39:47] Jobe and perhaps, for the case of existing accounts being migrated to bot accounts, an oper/admin only command to migrate, and leave the verification up to network staff
[21:40:20] * tjr4 joined #ircdriven
[21:48:16] * tjr quit (*.net *.split)
[21:48:20] * tjr4 is now known as tjr
Prev
Next