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

Add auto status change after sending a message. #11

Open
floyare opened this issue Feb 1, 2022 · 2 comments
Open

Add auto status change after sending a message. #11

floyare opened this issue Feb 1, 2022 · 2 comments

Comments

@floyare
Copy link

floyare commented Feb 1, 2022

[idea] Change status to online after sending a message to any channel.

@floyare floyare changed the title Add auto status change on message sent. Add auto status change after sending a message. Feb 1, 2022
@BigFlubba
Copy link

That's nice. Sometimes I get on Discord to check if I have messages then get back off.

@RoguedBear
Copy link
Owner

I believe the cooldown timeout of high value (like 30+ seconds) achieves the same functionality too in a way.

The difference between having your status 'un-afk' when you send a message compared to un-afk when you've had discord focused for a sufficiently large time boils down to accuracy of when your status is being un-afked

changing your status when you send a message changes your status at that instant.
But with the timeout, it assumes that if you have the discord window focused for a certain time you are online. so status might not change at that time when you send a message, but it will be at a later time.

Addressing the issue of lurk, with the un-afk trigger being sending a message, you can lurk, check messages and get back to what you're doing your status wont change and you don't have to worry about a timeout.
But in the case of timeout being the un-afk tirgger, if you keep it's value quite high (like 90s in my case), you can check messages and close discord though you'd have to be alt-tabbing or unfocusing->focusing quite a few times to reset the cooldown timeout.

My point being, the functionality is still there just maybe not accurate enough.

I hope my point comes across.

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