[Rtcomm] [Rtcomm] [Bug 6857] USSD codes are not recognized in chat
From: bugzilla-daemon at maemo.org bugzilla-daemon at maemo.orgDate: Thu Dec 17 14:17:46 EET 2009
- Previous message: [Rtcomm] [Bug 6857] USSD codes are not recognized in chat
- Next message: [Rtcomm] [Bug 6863] When a delivery report is received the conversation window opens again
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
https://bugs.maemo.org/show_bug.cgi?id=6857 ------- Comment #4 from maemo at csipa.in.rs 2009-12-17 14:17 GMT+3 ------- As for dangerous, IMO it as dangerous as any other 'regular' number, as those can harbor high fee or automated services, too. A confirmation of "This is a supplementary service call number. Are you sure ?" or sorts would be IMHO enough of a warning, but I guess it's more of a policy question. Skype/XMPP is an interesting angle - those are not related to your cellular provider, so it makes far less sense to parse them there (who would send you USSD codes ? friends ?), so, apart from the reason of consistency, it makes sense to draw a line there (however, I would suggest ignoring the whole code in that case, not treat it as partial numbers as now). I don't have enough info to say whether 4/5 sender is a good filtration or not (i.e. Can it be forged ? Are there providers who define a longer (or missing) sender ?) -- Configure bugmail: https://bugs.maemo.org/userprefs.cgi?tab=email Replies to this email are NOT read, instead please add comments at https://bugs.maemo.org/show_bug.cgi?id=6857 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
- Previous message: [Rtcomm] [Bug 6857] USSD codes are not recognized in chat
- Next message: [Rtcomm] [Bug 6863] When a delivery report is received the conversation window opens again
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]