| Summary: | Contacts both on Allow List and Block List: Not Removed | ||
|---|---|---|---|
| Product: | papyon | Reporter: | ancanus |
| Component: | general | Assignee: | papyon-bugs |
| Status: | RESOLVED NOTABUG | QA Contact: | |
| Severity: | minor | ||
| Priority: | medium | ||
| Version: | unspecified | ||
| Hardware: | x86 (IA32) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
ancanus
2010-11-29 20:42:05 UTC
They are indeed not really removed, I'm mimicking official client behavior. How things are working: - You receive the contacts from your address book (web service) - You receive contacts memberships (Allow, Block, Pending) (another web service) - You connect to messenger server and send your contact list with memberships So the Allow membership is only removed from the final contact list we sent to the Live Messenger server (that is sent each time you connect) but not from the Address Book (permanent storage for contacts). Conclusion: that's a harmless warning and I still prefer not to screw up the address book. aMSN actually removes the contact from the AL on the server, because a contact in AL+BL is clearly a corruption/inconsistent status. It is probably caused by a connection drop while blocking/unblocking a user, and I don't think it should keep the inconsistent state once it detects it.. if you show the user as blocked, then remove him from the AL on the server.. otherwise you might even get an error later on if the user says 'unblock' and you do 'add to AL' which returns 'contact already exists' then, hopefully you'd need to handle that error case... IMHO, it's better to just fix the error rather than ignoring it. Agree? Disagree? |
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.