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 Requests] Editing messages, fancy quotes, fancy formatting. #299
Comments
Don't you think editing the previously sent messages is a dangerous possibility? |
Not really, but if you're worried you can enable revision history. A new message would have to be sent anyways to send the edit. You can just have a clock icon that shows the edits in a diff form. |
Seems complex. |
It does, but this and no group A/V chat are really the only things keeping me from using Tox instead of Skype. I'd love to see Tox become a drop-in replacement for Skype, and this is how I see it doing that. |
Perhaps let the receiving user choose how to show him edited messages: either just edit the old message (like in Skype), or show new message: "XXX has edited his message [hh:mm:ss]: {edited message}". I think the second should be default. |
I wonder why none of you speaks about the deliberate falsification of the previously sent messages. Many people (including me) are really concerned about such possibility. |
That's what the edit history is for. To show all of the previous edits to one message. I'd be fine if it wasn't default, but how would the client handle it if someone you're talking to has it on and you don't? Disable for both? |
I like there to be revision history, like in the StackExchange chat (example of edited message revision history). I use message editing (in Skype, on Github) very often. It avoids annoying corrective messages for |
I have previously brought up these issues with the Venom developer, @naxuroqa, but I'd like to know your stance on these. From my other post:
The link is to the full discussion, and has suggestions and more elaborated requests.
Thanks in advance!
The text was updated successfully, but these errors were encountered: