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

PM rejection #129

Open
MaribelHearn opened this issue May 5, 2016 · 7 comments
Open

PM rejection #129

MaribelHearn opened this issue May 5, 2016 · 7 comments

Comments

@MaribelHearn
Copy link
Contributor

Would be nice if you could reject PMs just like on the desktop client.

@danimesq
Copy link
Contributor

danimesq commented May 5, 2016

I agree. The WebClient needs be the most paired possibly with Android/Desktop versions.

@sulcata
Copy link
Contributor

sulcata commented May 5, 2016

Do you mean ignoring? Right now you can do that by right clicking the player list.

@MaribelHearn
Copy link
Contributor Author

MaribelHearn commented May 5, 2016

No, that's targetted towards a single user, and also ignores their posts on channels. I mean the global PM rejection that blocks any incoming PM rather than PMs from a single user.

@coyotte508
Copy link
Member

Is it really needed though?

PMs on the browser are a lot less annoying than in the client or the android client.

@danimesq
Copy link
Contributor

@coyotte508 do you think in a possible universal app? The web power is for this.

@coyotte508
Copy link
Member

in an universal app, it's different. It's not now. It's a theorical future. Show me one done and we'll discuss.

@danimesq
Copy link
Contributor

danimesq commented May 15, 2016

I believe in javascript power and in the fact we can build apps with a unique code, releasing a single version for various platforms. I don't believe its a theorical future, but a unavoidable. But ok, when I build the Android/Desktop build, lets discuss it.

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

4 participants