Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Silent Tags #18

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Silent Tags #18

wants to merge 1 commit into from

Conversation

tarna
Copy link

@tarna tarna commented Dec 14, 2024

This PR adds a feature where if you send a tag as a silent message, it will delete your original message.

For example "@ silent !test". (without the space between the @ and silent)

This is useful because users sometimes send a tag and manually delete it themselves so the user it's for doesn't try to run it again. And sending the tag like this will automatically do it for you.

@SantioMC
Copy link
Owner

I like the idea of having silent tags, however I don't think having this as a way to trigger them would be a good way of doing it, I can see cases where you may want to do this but accidentally have the message deleted

@tarna
Copy link
Author

tarna commented Dec 15, 2024

I like the idea of having silent tags, however I don't think having this as a way to trigger them would be a good way of doing it, I can see cases where you may want to do this but accidentally have the message deleted

What other way could we do it? Also, what do you mean by the last part?

@SantioMC
Copy link
Owner

Another way we could possible implement auto deleting tags is by forcing the message to end with like -delete or something similar where it's very clear that the message is intended to be deleted by the bot, the issue with what's currently implemented is you could do @Santio contact !support and that would delete your message

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants