Project:Discord Bot Improvements - Revision history

Kraaabs: /* Raconteur TODO */

2023-01-17T19:51:58Z

Raconteur TODO

← Older revision		Revision as of 19:51, 17 January 2023
Line 26:		Line 26:
	# <del>Grab embeds for messages as well (maybe embed them in the JSON log format as base64?)</del> '''DONE! (although I'm on the fence about including them in the JSON output. Boy howdy, base64 can get LARGE)'''		# <del>Grab embeds for messages as well (maybe embed them in the JSON log format as base64?)</del> '''DONE! (although I'm on the fence about including them in the JSON output. Boy howdy, base64 can get LARGE)'''
	# Containerize it! (see below)		# Containerize it! (see below)
	# MediaWiki companion bot to upload images/automatically create pages ([https://doc.wikimedia.org/pywikibot/stable/index.html it seems there are mature Python bindings for the MediaWiki API]) '''DONE! (I had to write my own MediaWiki API bindings. The bot can now create pages, and image uploads aren't far off.'''		# MediaWiki companion bot to upload images/automatically create pages ([https://doc.wikimedia.org/pywikibot/stable/index.html it seems there are mature Python bindings for the MediaWiki API]) '''DONE! (I had to write my own MediaWiki API bindings. The bot can now create pages, and image uploads aren't far off.)'''
	# Whatever else I forgot (I'm sure I'll add more as I go)		# Whatever else I forgot (I'm sure I'll add more as I go)

Kraaabs: Update status of bot stuff ~Sarah

2023-01-17T19:51:41Z

Update status of bot stuff ~Sarah

← Older revision		Revision as of 19:51, 17 January 2023
Line 2:		Line 2:

	== Better Discord logging ==		== Better Discord logging ==

			Status: '''The bot is currently in development, and a prototype is nearing completion.'''

	As it stands, the wiki discussion logs (such as [[Lotus Notes and Taligent Shenanigans Log]] or [[SoylentNews History Log]]) are manually copied and pasted before being either [https://gitlab.com/sarahcrowle/raccoon.rb run through a script] to convert them to WikiText, or manually formatted by hand. This approach has a few drawbacks:		As it stands, the wiki discussion logs (such as [[Lotus Notes and Taligent Shenanigans Log]] or [[SoylentNews History Log]]) are manually copied and pasted before being either [https://gitlab.com/sarahcrowle/raccoon.rb run through a script] to convert them to WikiText, or manually formatted by hand. This approach has a few drawbacks:
Line 24:		Line 26:
	# <del>Grab embeds for messages as well (maybe embed them in the JSON log format as base64?)</del> '''DONE! (although I'm on the fence about including them in the JSON output. Boy howdy, base64 can get LARGE)'''		# <del>Grab embeds for messages as well (maybe embed them in the JSON log format as base64?)</del> '''DONE! (although I'm on the fence about including them in the JSON output. Boy howdy, base64 can get LARGE)'''
	# Containerize it! (see below)		# Containerize it! (see below)
	# MediaWiki companion bot to upload images/automatically create pages ([https://doc.wikimedia.org/pywikibot/stable/index.html it seems there are mature Python bindings for the MediaWiki API])		# MediaWiki companion bot to upload images/automatically create pages ([https://doc.wikimedia.org/pywikibot/stable/index.html it seems there are mature Python bindings for the MediaWiki API]) '''DONE! (I had to write my own MediaWiki API bindings. The bot can now create pages, and image uploads aren't far off.'''
	# Whatever else I forgot (I'm sure I'll add more as I go)		# Whatever else I forgot (I'm sure I'll add more as I go)

	== Modmail/Ticketing ==		== Modmail/Ticketing ==

			Status: '''Tickets is currently being trialled on the main DisNCord server (good success so far)'''

	Currently, DisNCord doesn't have any formal modmail or ticketing for moderator concerns. Specific concerns are handled by direct messaging moderators, and communicating in the #mod-discussion channel, with [[User:NCommander]] having the final say. This may not scale well as the server continues to grow, so a proper modmail or ticketing system would be beneficial. If you have other suggestions for ticketing bots, or experience using any of these, contact [[User:Kraaabs]] (Krabs#0571 on Discord) with your thoughts!		Currently, DisNCord doesn't have any formal modmail or ticketing for moderator concerns. Specific concerns are handled by direct messaging moderators, and communicating in the #mod-discussion channel, with [[User:NCommander]] having the final say. This may not scale well as the server continues to grow, so a proper modmail or ticketing system would be beneficial. If you have other suggestions for ticketing bots, or experience using any of these, contact [[User:Kraaabs]] (Krabs#0571 on Discord) with your thoughts!
Line 68:		Line 72:

	== Bot Infrastructure ==		== Bot Infrastructure ==

			Status: '''The Wiki and Fediverse servers are currently being moved. Afterwards, further discussion of bot hosting will be done.'''

	The thing about Discord bots is that you need to host them, of course. Ideally, for ease of management, all bots would be hosted on Restless Systems infrastructure, using Docker containers.		The thing about Discord bots is that you need to host them, of course. Ideally, for ease of management, all bots would be hosted on Restless Systems infrastructure, using Docker containers.

Kraaabs at 15:48, 3 January 2023

2023-01-03T15:48:42Z

← Older revision		Revision as of 15:48, 3 January 2023
Line 46:		Line 46:
	==== Pros ====		==== Pros ====
	* Appears very robust feature-wise		* Appears very robust feature-wise
	* Comes with a handy dashboard		* Comes with a handy dashboard -- but it's discord integrated
	* Seemingly scales well		* Seemingly scales well
	==== Cons ====		==== Cons ====
	* The free version is rate-limited (although I don't think we'll hit the limit)		* The free version is rate-limited (although I don't think we'll hit the limit)
	* Features such as DM support are locked behind a paywall		* Features such as DM support are locked behind a paywall
			* UX is somewhat inconsistent and awkward
			* Piles up closed tickets as channels with no real archival
			* GDPR clause just says "contact us" with no other info

	=== [https://ticketsbot.net Tickets] ===		=== [https://ticketsbot.net Tickets] ===
Line 57:		Line 60:
	* Allows multiple support teams		* Allows multiple support teams
	* Similar to Ticket Tool, used on many many servers already		* Similar to Ticket Tool, used on many many servers already
			* Very polished interface
			* Deletes ticket channels when tickets are closed, but archives them in a thread for later viewing
			* Allows for the creation of custom forms and panels for ticket creation!
	==== Cons ====		==== Cons ====
	* Again, some features are paywalled		* Again, some features are paywalled (but nothing super essential...)
			* GDPR is handled through a discord server, which is... odd

	== Bot Infrastructure ==		== Bot Infrastructure ==

Kraaabs: /* Raconteur TODO */

2023-01-03T00:59:46Z

Raconteur TODO

← Older revision		Revision as of 00:59, 3 January 2023
Line 22:		Line 22:
	# <del>See about using user permissions for the bot, rather than any moderator permissions</del> '''DONE! (actually, the retroactive logging shouldn't require any special permissions. proactive logging needs some permissions to set up, but not to archive/create archival threads)'''		# <del>See about using user permissions for the bot, rather than any moderator permissions</del> '''DONE! (actually, the retroactive logging shouldn't require any special permissions. proactive logging needs some permissions to set up, but not to archive/create archival threads)'''
	# <del>Flesh out retroactive logging (in addition to the proactive logging already implemented)</del> '''DONE! (at least to the level of the proactive logging)'''		# <del>Flesh out retroactive logging (in addition to the proactive logging already implemented)</del> '''DONE! (at least to the level of the proactive logging)'''
	# Grab embeds for messages as well (maybe embed them in the JSON log format as base64?)		# <del>Grab embeds for messages as well (maybe embed them in the JSON log format as base64?)</del> '''DONE! (although I'm on the fence about including them in the JSON output. Boy howdy, base64 can get LARGE)'''
	# Containerize it! (see below)		# Containerize it! (see below)
	# MediaWiki companion bot to upload images/automatically create pages ([https://doc.wikimedia.org/pywikibot/stable/index.html it seems there are mature Python bindings for the MediaWiki API])		# MediaWiki companion bot to upload images/automatically create pages ([https://doc.wikimedia.org/pywikibot/stable/index.html it seems there are mature Python bindings for the MediaWiki API])

Kraaabs: /* Raconteur TODO */

2023-01-03T00:35:49Z

Raconteur TODO

← Older revision		Revision as of 00:35, 3 January 2023
Line 20:		Line 20:

	# <del>Better document the code, and open the repository up to the public</del> '''DONE! (sorta. docs aren't there yet)'''		# <del>Better document the code, and open the repository up to the public</del> '''DONE! (sorta. docs aren't there yet)'''
	# See about using user permissions for the bot, rather than any moderator permissions		# <del>See about using user permissions for the bot, rather than any moderator permissions</del> '''DONE! (actually, the retroactive logging shouldn't require any special permissions. proactive logging needs some permissions to set up, but not to archive/create archival threads)'''
	# <del>Flesh out retroactive logging (in addition to the proactive logging already implemented)</del> '''DONE! (at least to the level of the proactive logging)'''		# <del>Flesh out retroactive logging (in addition to the proactive logging already implemented)</del> '''DONE! (at least to the level of the proactive logging)'''
	# Grab embeds for messages as well (maybe embed them in the JSON log format as base64?)		# Grab embeds for messages as well (maybe embed them in the JSON log format as base64?)

Kraaabs: this looks way better bold ~Sarah

2023-01-03T00:33:50Z

this looks way better bold ~Sarah

← Older revision		Revision as of 00:33, 3 January 2023
Line 19:		Line 19:
	=== Raconteur TODO ===		=== Raconteur TODO ===

	# <del>Better document the code, and open the repository up to the public</del> DONE! (sorta. docs aren't there yet)		# <del>Better document the code, and open the repository up to the public</del> '''DONE! (sorta. docs aren't there yet)'''
	# See about using user permissions for the bot, rather than any moderator permissions		# See about using user permissions for the bot, rather than any moderator permissions
	# <del>Flesh out retroactive logging (in addition to the proactive logging already implemented)</del> DONE! (at least to the level of the proactive logging)		# <del>Flesh out retroactive logging (in addition to the proactive logging already implemented)</del> '''DONE! (at least to the level of the proactive logging)'''
	# Grab embeds for messages as well (maybe embed them in the JSON log format as base64?)		# Grab embeds for messages as well (maybe embed them in the JSON log format as base64?)
	# Containerize it! (see below)		# Containerize it! (see below)

Kraaabs: add repository link for Raconteur and update the TODO ~Sarah

2023-01-03T00:33:09Z

add repository link for Raconteur and update the TODO ~Sarah

← Older revision		Revision as of 00:33, 3 January 2023
Line 14:		Line 14:

	[[User:Kraaabs]] has written (most of) a Discord bot that can record messages to a few formats, including WikiText. After some cleanup and feature additions, it should be well suited to the task.		[[User:Kraaabs]] has written (most of) a Discord bot that can record messages to a few formats, including WikiText. After some cleanup and feature additions, it should be well suited to the task.

			[https://gitlab.com/sarahcrowle/raconteur Raconteur repository on GitLab]

	=== Raconteur TODO ===		=== Raconteur TODO ===

	# Better document the code, and open the repository up to the public		# <del>Better document the code, and open the repository up to the public</del> DONE! (sorta. docs aren't there yet)
	# See about using user permissions for the bot, rather than any moderator permissions		# See about using user permissions for the bot, rather than any moderator permissions
	# Flesh out retroactive logging (in addition to the proactive logging already implemented)		# <del>Flesh out retroactive logging (in addition to the proactive logging already implemented)</del> DONE! (at least to the level of the proactive logging)
	# Grab embeds for messages as well (maybe embed them in the JSON log format as base64?)		# Grab embeds for messages as well (maybe embed them in the JSON log format as base64?)
	# Containerize it! (see below)		# Containerize it! (see below)

Kraaabs: /* TODO */

2023-01-02T17:58:12Z

TODO

← Older revision		Revision as of 17:58, 2 January 2023
Line 71:		Line 71:
	## [[User:NCommander]] had suggested to me that we could use GitHub/GitLab actions. If we go this route, we would likely have to mirror any bots we're using in our own GitHub/GitLab project. This could pose a problem with the proprietary bots though...		## [[User:NCommander]] had suggested to me that we could use GitHub/GitLab actions. If we go this route, we would likely have to mirror any bots we're using in our own GitHub/GitLab project. This could pose a problem with the proprietary bots though...
	### Although, we don't actually need to self host those. In fact, I don't think we ''can'' (duh. coffee finally kicked in I guess)		### Although, we don't actually need to self host those. In fact, I don't think we ''can'' (duh. coffee finally kicked in I guess)
			### Also: to get this working we'd need to set up that Git{Lab\|Hub} project in the first place
	# For consistency's sake, are we going to re-containerize everything to use the same OS inside the containers, if they aren't already? (I doubt all of the bot authors involved are using the same OS)		# For consistency's sake, are we going to re-containerize everything to use the same OS inside the containers, if they aren't already? (I doubt all of the bot authors involved are using the same OS)
	## Despite all of the bots probably being written in different languages using different API wrappers, as much consistency as possible would be nice... Although that's mostly just OCD Sarah talking		## Despite all of the bots probably being written in different languages using different API wrappers, as much consistency as possible would be nice... Although that's mostly just OCD Sarah talking
	# Finally, what DO we want to host? Should we take this opportunity to self host things like YAGPDB or PK alongside Raconteur and any potential ticketing bot (if we go with a self hosted one)?		# Finally, what DO we want to host? Should we take this opportunity to self host things like YAGPDB or PK alongside Raconteur and any potential ticketing bot (if we go with a self hosted one)?

Kraaabs: /* TODO */

2023-01-02T17:55:37Z

TODO

← Older revision		Revision as of 17:55, 2 January 2023
Line 73:		Line 73:
	# For consistency's sake, are we going to re-containerize everything to use the same OS inside the containers, if they aren't already? (I doubt all of the bot authors involved are using the same OS)		# For consistency's sake, are we going to re-containerize everything to use the same OS inside the containers, if they aren't already? (I doubt all of the bot authors involved are using the same OS)
	## Despite all of the bots probably being written in different languages using different API wrappers, as much consistency as possible would be nice... Although that's mostly just OCD Sarah talking		## Despite all of the bots probably being written in different languages using different API wrappers, as much consistency as possible would be nice... Although that's mostly just OCD Sarah talking
			# Finally, what DO we want to host? Should we take this opportunity to self host things like YAGPDB or PK alongside Raconteur and any potential ticketing bot (if we go with a self hosted one)?

Kraaabs: /* TODO */

2023-01-02T17:50:29Z

TODO

← Older revision		Revision as of 17:50, 2 January 2023
Line 70:		Line 70:
	# If we want to do auto-updates (we probably do) how will we accomplish this?		# If we want to do auto-updates (we probably do) how will we accomplish this?
	## [[User:NCommander]] had suggested to me that we could use GitHub/GitLab actions. If we go this route, we would likely have to mirror any bots we're using in our own GitHub/GitLab project. This could pose a problem with the proprietary bots though...		## [[User:NCommander]] had suggested to me that we could use GitHub/GitLab actions. If we go this route, we would likely have to mirror any bots we're using in our own GitHub/GitLab project. This could pose a problem with the proprietary bots though...
			### Although, we don't actually need to self host those. In fact, I don't think we ''can'' (duh. coffee finally kicked in I guess)
	# For consistency's sake, are we going to re-containerize everything to use the same OS inside the containers, if they aren't already? (I doubt all of the bot authors involved are using the same OS)		# For consistency's sake, are we going to re-containerize everything to use the same OS inside the containers, if they aren't already? (I doubt all of the bot authors involved are using the same OS)
	## Despite all of the bots probably being written in different languages using different API wrappers, as much consistency as possible would be nice... Although that's mostly just OCD Sarah talking		## Despite all of the bots probably being written in different languages using different API wrappers, as much consistency as possible would be nice... Although that's mostly just OCD Sarah talking