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

Feature idea: Default commands for bare links #7

Closed
bartokwiat opened this issue May 27, 2024 · 4 comments
Closed

Feature idea: Default commands for bare links #7

bartokwiat opened this issue May 27, 2024 · 4 comments
Assignees

Comments

@bartokwiat
Copy link
Contributor

By default, the bot could treat bare links (URLs without any command before them) as if they had a specific command attached. This would make using the bot faster and more convenient.

This functionality could be optional and configured through a settings file. If enabled, any link received by the bot without a preceding command would be automatically interpreted as having a designated command, like "/v" or "/a".

So to give an example, when you send

example.com/video.mp4

the bot could interpret it as

/v example.com/video.mp4

I think it would be a pretty nice addition to overall functionality.

@cccaaannn cccaaannn self-assigned this May 28, 2024
@cccaaannn
Copy link
Owner

Hi, thanks for the feedback. I might add that if I find enough free time.

@cccaaannn
Copy link
Owner

Hi, you can use this feature on new version 4.5

@asamofal
Copy link

@cccaaannn Thanks! May I ask you to reconfigure the public version of your bot to default_command: video, as seems like it's null there now (or not updated yet).

Just as an idea: this preference can be extracted to the user level, so each user can configure it himself.

@cccaaannn
Copy link
Owner

I would like to keep the public version as null, because for example I primarily use it for audio.

User level preferences can be a good feature, but if I add that I want it to be implemented in a good way which will probably require a database and that makes updating an existing bot more complicated for the maintainer.
You might need to run migrations on startup, and can't introduce breaking changes to db between versions. Also it will complicate the simple running process because you at least have to map a directory for the db.

Maybe I return back to this in the future.

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

No branches or pull requests

3 participants