Summary: | don't abuse M_T_Action for nudges | ||
---|---|---|---|
Product: | Telepathy | Reporter: | Simon McVittie <smcv> |
Component: | butterfly | Assignee: | Telepathy bugs list <telepathy-bugs> |
Status: | RESOLVED FIXED | QA Contact: | Telepathy bugs list <telepathy-bugs> |
Severity: | normal | ||
Priority: | medium | CC: | olivier |
Version: | unspecified | Keywords: | patch |
Hardware: | Other | ||
OS: | All | ||
URL: | http://git.collabora.co.uk/?p=user/jonny/telepathy-butterfly.git;a=shortlog;h=refs/heads/nudges | ||
Whiteboard: | review+ | ||
i915 platform: | i915 features: |
Description
Simon McVittie
2009-10-23 08:14:57 UTC
This prevents https://bugzilla.gnome.org/show_bug.cgi?id=599415 from being solved for Butterfly Text channels. Retitling; removing the secret nudge pseudo-API isn't strictly a requirement to have Empathy work, although I still think it's wrong. We already do this: method call sender=:1.48 -> dest=:1.28 serial=131 path=/org/freedesktop/Telepathy/Connection/butterfly/msn/jonny_40jonnylamb_2ecom/TextChannel1; interface=org.freedesktop.Telepathy.Channel.Type.Text; member=GetMessageTypes method return sender=:1.28 -> dest=:1.48 reply_serial=131 array [ uint32 0 ] 16:42 < jonnylamb> smcv: I'm confused as to what you're actually asking for in fd.o#24699 now. 16:42 < jonnylamb> smcv: You note in the Empathy bug that butterfly only returns NORMAL in GetMessageTypes(). 16:42 < jonnylamb> So surely "should not advertise Message_Type_Action unless able to deal with all messages of that type" is satisfied? 16:43 < smcv> jonnylamb: if that is the case then yes 16:44 < smcv> jonnylamb: I was wrong about the butterfly bug initially, I thought butterfly advertised Normal and Action but Action only worked for nudges 16:44 < jonnylamb> You're right about the second part -- if we're given an action message type and it's a nudge then we send a nudge over the wire, otherwise we, don't? 16:45 < smcv> (Normal, *) -> "*" 16:45 < istaz> jonnylamb: it was about the /nudge, we only return NORMAL but empathy don't check that, and /nudge is only accepted as ACTION_TYPE and don't accept if that's not /nudge 16:45 < jonnylamb> But seeing as we don't advertise ACTION, I think we can do what the hell we want if someone gives us an Action message. :-) 16:45 < smcv> (Action, "nudge") -> protocol nudge 16:45 < smcv> (Action, "dies") -> error 16:45 < smcv> jonnylamb: in principle you're right, although I still think it's an abuse of Action messages 16:46 < smcv> and the Empathy bug isn't blocked by the butterfly bug as I initially thought, but is still a rather annoying bug 16:46 < jonnylamb> I'm actually in favour of removing nudge support in butterfly. 16:46 < smcv> s/in butterfly// :-) 16:46 < jonnylamb> Maybe we should hook it up so if a contact nudges you, he or she is automatically blocked. 16:48 < jonnylamb> Anyway, I'm going to close that bug because it's not a bug. If you want the bug to mean something else, say now or forever hold your peace. 16:48 < smcv> indeed, nudging should either be ignored, or be a Channel.Interface.Annoyance or something (which Empathy would implement as the URGENT hint 16:48 < smcv> ) 16:49 < smcv> jonnylamb: would you mind re-purposing it as "don't abuse M_T_Action for nudges"? (if so you can drop the severity of course) 16:49 < jonnylamb> ok Check out my patch. review+ Thanks. This patch remove the ability to nudge completly, should'nt we accept /nudge in text channel instead? |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.