Ticket #4488 (reopened enhancement)

Opened 8 weeks ago

Last modified 7 weeks ago

Feature request : REALLY block a JID

Reported by: louizatakk Owned by:
Priority: normal Milestone:
Component: None Version:
Severity: normal Keywords: discussed
Cc: OS: All

Description

When you block + delete someone, he can still "spam" you with adding requests ("jid@… wants to blabla, would you let him talk to you ?"), it could be great to refuse EVERY request/message/spam/anything from a particular JID (even the adding request) (yes, notifixious is a BIG SHIT :()

A list of unauthorized/authorized people would be great, to manage these people.

Attachments

Change History

Changed 8 weeks ago by Nyco

  • status changed from new to closed
  • resolution set to invalid

Use the privacy lists: Menu Actions, Advanced, For account, Edit privacy lists.

Changed 7 weeks ago by Dag

  • keywords discussed added
  • status changed from closed to reopened
  • resolution invalid deleted

I note that when you "block" someone in Gajim, it really adds the JID to the block privacy list. Why does OP still receive queries? Well, by default only messages, queries and outgoing presence is blocked, not incoming presence. "Adding requests" are really presence of type subscribe.

Should perhaps incoming presence also be blocked by default?

Changed 7 weeks ago by bpete

  • milestone 0.13 deleted

Changed 7 weeks ago by Nyco

http://xmpp.org/extensions/xep-0016.html Incoming presence can be blocked, in the XEP and in Gajim.

Changed 7 weeks ago by Dag

In deed, but seems to not be the default behavior of the "block" feature of Gajim. I can see why that is, if you have someone in your roster you might still want to see their presence if you block them, but as OP notes if you block+unsubscribe, they can flood subscribe presences to you.

Changed 7 weeks ago by asterix

the problem with what yuo request is the GUI. There is no easy way to unblock a contact that you removed from your roster. So if you want to add it again to your roster it's not possible. For that you need to edit the privacy list, which is not for noobs.

  • Maybe a solution would be to make 2 lists: block and block_definitly. But I don't know how to present that in the GUI. A new menuitem will confuse the user.
  • Another solution would be to add a blocked user list in the GUI, so that it's more easy to remove a user from the block list. This way we can default to block presence in the block list.

Changed 7 weeks ago by steve-e

I don't think that we should really enhance the block feature beyond its current scope.

It is simple and easy to understand. Everything else can and should be done with privacy lists.

We should better invest into an easier privacy list GUI than bloating this one.

Changed 7 weeks ago by asterix

I agree, but the problem with privacy lists is that only one can be active at the same time. So using a user-made privacy list will make the one done by GUI unused ...

Changed 7 weeks ago by steve-e

Is there a way for us to solve that programatically, because the issue isn't only limited to user-defined lists?

Just try the following:

1. Connect as Invisible
2. Block a contact
3. Change status to online

The blocked jid will receive our new presence, though it should not :-/

Changed 7 weeks ago by asterix

Have you tested? I think we re-enable bloc list when we come back online, don't we?

Add/Change #4488 (Feature request : REALLY block a JID)

Author



Change Properties
<Author field>
Action
as reopened
as The resolution will be set. Next status will be 'closed'
to The owner will change. Next status will be 'new'
 
Note: See TracTickets for help on using tickets.