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 Request: Bring Back Custom Status & Do Not Disturb from version 1.10.12 #154

Closed
autoteelar opened this issue Oct 14, 2022 · 6 comments
Labels
upstream This issue also exists in upstream

Comments

@autoteelar
Copy link
Contributor

for some reason, turt2live decided to remove some of element's best features simply because "nobody uses them", meanwhile when me and my friends found out these lab features existed we were really happy and excited and used them all the time. just because turt2live doesn't use them and may think for any reason that others don't use them, doesn't mean other people don't use them. i think that decision of his was pre mature.

anyways, if you use the version before this happened (1.10.12 or lower) do not disturb and custom status still work perfectly flawlessly.

so basically, im requesting if schildichat could keep these features, as i think they are extremely useful, fun, and cool.

and if you go to any other chat platform, say discord for example, so many people use custom status and do not disturb there too, they're pretty popular things in general.

as for the integration managers, i do not know much about them or used them, if anyone wants them back that knows about them, please say so in the comments.

source post: matrix-org/matrix-react-sdk#8521

@su-ex
Copy link
Member

su-ex commented Oct 14, 2022

Maintenance burden as mentioned on his rationale doesn't sound good. I'm already on my limit and every deviation from Element adds on top.
I might revert the removal of dnd as it looks like a small change, but I'll probably remove it again once it stops working or conflicts a lot while merging.
Also, I won't revert the removal of custom status since it is highly spec-dependant to make a proper implementation.

@su-ex su-ex added the upstream This issue also exists in upstream label Oct 14, 2022
@autoteelar
Copy link
Contributor Author

okay, well thanks for doing everything you can within reason :D much appreciated

@autoteelar
Copy link
Contributor Author

what does spec-dependant mean? spec? like computer specifications?

@su-ex
Copy link
Member

su-ex commented Oct 15, 2022

what does spec-dependant mean? spec? like computer specifications?

Status is something which should find its way into the Matrix specification so all clients have means to implement this in a proper way working across all of them.

@autoteelar
Copy link
Contributor Author

autoteelar commented Oct 17, 2022 via email

@autoteelar autoteelar closed this as not planned Won't fix, can't repro, duplicate, stale Nov 13, 2022
@darkralts
Copy link

darkralts commented Nov 16, 2022

i decided it would be better to lean this onto the element team instead, so i made a request over there. some mod or something immediately moved it from feature requests to discussions though without any 2nd thought or explanation though, so i have no idea what the future holds for this specific feature. if anything i might just make my own implementation one way or another.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
upstream This issue also exists in upstream
Projects
None yet
Development

No branches or pull requests

3 participants