-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Message tray refinement, simplification/improvement #16333
Comments
Closing as I believe this is covered by #5693 |
not really, the second issues was not adressed. @SimonBrandner please stop closing issues without any logic behind it Cheers. |
@irelativism I agree with @SimonBrandner's decision to close here, it seems like the main concern is resolved. If you see further issues, please open a new issue which is tightly focused on a single problem. |
there are 2 problems presented here @jryans : |
The challenge is that meta-issues like this which combine several problems are not very actionable. One part might be valid, while another might not, etc. One part might get prioritised while another might not. There's no way to reflect that when they are all jammed together. That's why I am suggesting you should file a new issue for anything that seems unresolved, as that one will then be more tightly scoped. |
Unfortunately when I was discussing this and try to reach-out to people involved in this work on the related room design, to try to separate it in 2 issues while still creating a meta-issue with a small syntheses, was pushed out and in a way censored just because I'm not part of the element team. So in the end and so the idea didn't got lost, or went straight to the bin. I rushly scramble everything here @jryans, before shutting down my matrix server and migrating/focusing my efforts in tox-project. So you can do as you perfer. But Im most definitely not for this targeted closing of my issues by Simon, this has been happening the last few days and I'm afraid there is some kind of bias involved, ego's should be kept out of this matters. |
No one is targetting your issues specifically, and I do not see any evidence of bias. Simon happened to close it because he's diligently triaging our issues at the moment. I would have done the same. Please stop making assumptions and accusations. Open a new issue if you wish. If you insist on continuing this off topic conversation here on the issue tracker, we may ban your GitHub account from our org. |
@jryans is hard to have a different approach when you have been in justly banned from other communications channels just because you presented a alternate solution to travis MSC, favouritism is a very problematic thing, but at the end again the only one that looses is the element team. Please do that if you wish to I dont really care anymore honestly. Wouldnt suprise me to see yet another abusive action by another element team member. Getting back to the topic Simon decided to close all issue posted regarding this topic just after my ban from matrix rooms, which I think is self evident by itself. So please read carefully again the reasons I believe this Closure is unsubstantiated. If you are not sure about what I talking about I would advise you go check the logs and other issues closed. Is very easy to say "assumptions and accusations" if you didnt actually bother to check it. That is all I have to say, if you wish to correct the situation great there is at least some integrity in the team, if not oh well I will focus my efforts on an alternative like TOX or GNUjami, and write an article about this abusive actions. Cheers nontheless. |
@irelativism this continued abuse will not be tolerated. You are no longer welcome to comment on our issues. |
Currently in element,
The message tray has 5 options/buttons attachments, emoji, stickers, voice-call, conference-call.
I believe such should be simplified to 3 buttons so attachments, emoji, calls.
PROPOSAL:
This 2 improvements would make the overall app more refined, and less noisy and hard to use, simpler, straight to the point. and overall a fluid and smooth experience.
CURRENTLY:
IMPROVEMENTS:
The text was updated successfully, but these errors were encountered: