Psi Jabber Client

See this page for instructions on how to use Flyspray: http://psi-im.org/wiki/Flyspray

Please Note!

Please do not create tasks here without discussing your bug or feature request on the forums or groupchat psi@conference.psi-im.org, *and* getting explicit confirmation by a developer to add it to flyspray.
Tasklist

FS#471 - Prevent mass messages

Attached to Project: Psi Jabber Client
Opened by Tony Collins (knigits) - Monday, 20 June 2005, 04:06 GMT-4
Task Type Feature Request
Category Backend/Core
Status Closed
Assigned To No-one
Operating System All
Severity Medium
Priority Fluff
Reported Version 0.9.3
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I'm not sure if this should be implemented at the server or client level, but I may as well submit it here anyway.

I have friends who think that it's funny to send me two thousand Jabber messages at once, using a PHP script. Personally, I don't find it very funny at all, as Psi then consumes all available RAM amd most of my swapfile, causing my (Linux) machine to lock up.

Please make Psi detect if more than ten messages have been received from a given contact in the last one second, and drop the rest until the flood stops.
This task depends upon

Closed by  Kevin Smith (kev)
Wednesday, 18 April 2007, 09:24 GMT-4
Reason for closing:  Won't implement
Additional comments about closing:  It's no good doing this client-side, the damage is already done when the client is parsing the messages to ignore.

Psi does support privacy lists though, which would solve problems with malicious contacts.
Comment by Tony Collins (knigits) - Monday, 20 June 2005, 05:00 GMT-4
I feel that the 'ignore list' feature described in  FS#76  would also help. If I was quick enough when my 'friend' started flooding me, I could drop him into the ignore list, and the rest of the flood would be ignored/dropped.
Comment by Mircea Bardac (IceRAM) - Monday, 20 June 2005, 06:32 GMT-4
I believe this could be implemented once History (Queue Manager in particular) is overhaulled.
Comment by Mircea Bardac (IceRAM) - Monday, 20 June 2005, 06:35 GMT-4
Of course, the overhaul should take into account that only a number of messages (lets say last 10 messages) should be cached into memory. The rest should be cached to disk. This would prevent such problems.

Loading...