Bug 339854

Summary:	channel invitation configuration not very discoverable
Product:	[Applications] konversation	Reporter:	argonel <argonel>
Component:	general	Assignee:	Konversation Developers <konversation-devel>
Status:	REPORTED ---
Severity:	wishlist	CC:	hein
Priority:	NOR
Version First Reported In:	1.5
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description argonel 2014-10-10 21:22:18 UTC

Channel invitation flooding is still a thing I guess. In some cases folks find they have automatic acceptance of invitations enabled. To turn it off, they have to re-enable the warning dialog, receive an invite, then change the status.

It would be interesting to heuristically detect an invite flood and offer a warning dialog, but I think that'll have to wait.

Perhaps an event that has a muted warning dialog should generate a line either in the status view (or the view in which the resulting event occurred) offering a Configure... context menu option, and in the future a clickable icon. Additionally that configuration could have an button in the warning config panel.

Thoughts?

Comment 1 Eike Hein 2014-10-10 21:39:30 UTC

Yeah, I like the line idea. How about instead of a context menu option, the configure trigger is just a link in the text? A bit unorthodox, but otoh maximally un-invasive because it uses the same visual vocab as the buffer contents do anyway. Having an access point for it in the warning dialogs page sounds cool as well, nice little detail.