Bug 170358

Summary: Implement optional delayed pasting
Product: [Applications] konversation Reporter: Toni Helenius <helenius.toni>
Component: generalAssignee: Konversation Developers <konversation-devel>
Status: RESOLVED WORKSFORME    
Severity: wishlist CC: hein
Priority: NOR    
Version: 1.1   
Target Milestone: ---   
Platform: Ubuntu   
OS: Unspecified   
Latest Commit: Version Fixed In:

Description Toni Helenius 2008-09-04 09:14:55 UTC 
Version:           1.1 (using KDE 3.5.10)
Installed from:    Ubuntu Packages

I really liked this feature on mIRC (& nnScript) back on my Windows days: DELAYED PASTE. You can get kicked out even if you are in a query with someone else and "flooding". DCC text is sometime too clumsy for quick reference.

When pasting multilined text, in option to current "edit" option, the user could enable delayed pasting. Which by default could occur when pasting more than 3 lines (configurable) so that each line is send with a 1,5 second (configurable) delay.

I'm very limited on time but eager to try help implementing this to Konversation KDE 4 version...
Comment 1 Eike Hein 2008-09-04 10:46:55 UTC 
Konversation 1.1 has a pretty sophisticated outbound traffic scheduler that is capable of throttling to avoid flooding while still retaining acceptable latencies by reordering messages appropriately. If you have problems with flooding with the default settings, please check out the tuning interface by using the '/queuetuner' command and lower the sendout rates for the normal queue. 

With the generic throttling, I think that an explicit "delayed pasting" is not necessary (in the end, pasting is just sending messages as well).
Comment 2 Toni Helenius 2008-09-04 11:02:57 UTC 
Oh, thanks for the info. I'll try that.

But still I'd stick for my proposal, it would be more fine tuned solution. If I understood correctly this will add a delay to all of my messages? So if I type in small sentences they are each sent with a delay? I don't want that... Would seem like heavy lag with 1,5s delay.

Can't test this option right now, but if it is equipped with such intelligence that it in fact don't slow down every message I type, just when there is lot on the queue, it would be sufficient. In this case how about presenting this delay to the user in the GUI...?