I post this in the Linux section, but I think this could/should apply to all desktop platforms: Currently, there is no way to set the users status other than manually setting it within the application (one of Online, Idle, Do Not Disturb and Invisible - no custom statuses).
TLDR: New way to set statuses programmatically and at start-up. (see Motivation/Use cases)
My suggestion would be to introduce a way to remedy this. Of course the interface could be different but here's a proposal that suggests specific funtionality: When starting the application via the command-line, introduce a flag `--status`, ie. extend the syntax to `discord [--status (online|idle|no-disturb|invisible)]` which provides these two features:
- if there is already an instance running, set the status to the specified one
- otherwise, start Discord with the user in the specified status
This would elegantly solve the unpopular proposal #360054961932 (Immediately set Away status when PC is locked), as well as the popular #360054769071 (Scheduled Custom Status), and furthermore implement a subset of the underspecified #360043285311 (Allow us to use CLI's to make arguments/use as a separate client). There seem to be quite a few others which I won't list, that could be solved by this added feature.
Motivation / Use cases
- This would allow extending the Desktop icon such that a right-click would provide a selection for the various statuses, eg. `start Discord as invisible` or make this default behaviour etc. Such functionality would be trivial to implement on all platforms.
- Users could use `cron` or similar to time certain a status change, eg. setting the user as Invisible at 00:00 and Idle at 08:00 etc.
- Users could trigger status changes freely, depending on custom, OS-specific events, eg. when set Idle when the screen gets locked or when the user opens a specific media player.
- Users could automate setting status to Invisible after a certain timer expired that resets with every interaction of the application, eg. when the user didn't maximise Discord for 30 minutes.
Considerations (feel free to skip...)
This functionality could be abused to trigger status changes in "fast" succession, eg. making the user switching from Online to Invisible and back - triggering many changes in the status bar on the right.
This would best be remedied by rate limiting the action server- and client-side. An auto-ban could safely (ie. no false positives) issued if a user exceeds the client-side enforced limit, as it is proof that they are not using the official means to trigger status changes.
Apart from this minor "security" consideration, my proposal is sound, well-specified and will greatly improve usability, as well as including the users, that know how to write small scripts, in the process of extending Discord's functionality.
댓글을 남기려면 로그인하세요.