the-valley-discord / blimp Goto Github PK

Add a bit of code to the startup process that reads in and executes the schema file, to auto-install database upgrades.
This would require verifying that the schema is idempotent, i.e. can be executed multiple times without throwing errors or damaging the database if some conditions are already met.

sig! join and sig! leave work while sig! Join and sig! Leave do not.

If we do a clone-purge, we could make BLIMP's old OID for one channel iteration point to the new one.

Thanks to the objects table this doesn't need to waste that much space. Points to consider:

• restore roles only after screening?
• allowlist/blocklist for roles?
• maybe make it a kiosk-based feature?
• data retention

making it a per-server setting (as opposed to per-board) would probably be easier to implement and less likely to cause nasty surprises

If the only content of a boarded post is a link that resolves to an image, try setting the embed image similar to if there'd been an attachment to the message.

Should guide users through setting up and, if necessary, modifying:

• Role Kiosks
• Welcome&Goodbye
• Boards

Should offer related features (eg open triggers for tickets).

Should issue commands automatically after user reaction, using ctx.invoke_command.

• Add more than one kind/scope of logging (eg tickets, modify.discord, modify.blimp)
• Fix old/new diff embeds with text length > 1024

idea: blimp commands to replace coop roles. for example, a coop rep can do something like “setpinggroup! chungus” and users can do “joinpinggroup! chungus” so that when the coop rep wants to ping them they can do something like “notifpinggroup! chungus” to make blimp dm or ping everyone who joined the chungus group. the set command creates a group, the join command joins a group, and the notif command makes blimp dm or ping all the members

Feedback submitted by Glow Woomii#6669.

No more incomprehensible, long ass, ticket! updatecategory with seven arguments, but something like configure! <toml>, where <toml> e.g. is

[tickets.category.784671579655319552]
transcript_channel = 327076567072407552

and automagically compute a diff to apply to the database.
Add more wizard commands to make that bearable.

prior art: https://github.com/scratchyone/modbot/blob/master/submodules/slowmode.js

• wizard: note which roles will be able to see tickets when a category is selected
• implement category/class deletion
• implement category/class view command

It'd go through a category (or the current one if none is specified) and sort the channels alphabetically. pleasealphabeticallysortchannelsinthiscategory! sounds like a fine name.

How about the possibility to edit one's reminders for example by using a syntax like reminders! edit [reminder_no] [new reminder text]?