Conference item
False-Name-Proof Recommendations in Social Networks
- Abstract:
- We study the problem of finding a recommendation for an uninformed user in a social network by weighting and aggregating the opinions offered by the informed users in the network. In social networks, an informed user may try to manipulate the recommendation by performing a false-name manipulation, wherein the user submits multiple opinions through fake accounts. To that end, we impose a no harm axiom: false-name manipulations by a user should not reduce the weight of other users in the network. We show that this axiom has deep connections to false-name-proofness. While it is impossible to design a mechanism that is best for every network subject to this axiom, we propose an intuitive mechanism LEGIT+, and show that it is uniquely optimized for small networks. Using real-world datasets, we show that our mechanism performs very well compared to two baseline mechanisms in a number of metrics, even on large networks.
- Publication status:
- Published
- Peer review status:
- Peer reviewed
Actions
Access Document
- Files:
-
-
(Preview, Accepted manuscript, pdf, 271.8KB, Terms of use)
-
Authors
- Publisher:
- Association for Computing Machinery
- Host title:
- AAMAS '16: Proceedings of the 2016 International Conference on Autonomous Agents and Multiagent Systems
- Publication date:
- 2016-05-09
- ISSN:
-
1558-2914
- Keywords:
- Pubs id:
-
pubs:600069
- UUID:
-
uuid:56f6af93-a140-4aba-8d77-3060be2868cf
- Local pid:
-
pubs:600069
- Source identifiers:
-
600069
- Deposit date:
-
2016-02-10
- ARK identifier:
Terms of use
- Copyright holder:
- International Foundation for Autonomous Agents and Multiagent Systems
- Copyright date:
- 2016
- Notes:
- Copyright © 2015, International Foundation for Autonomous Agents and Multiagent Systems (www.ifaamas.org). All rights reserved. This is the accepted manuscript version of the article. The final version is available online from ACM at [https://dl.acm.org/citation.cfm?id=2936974].
If you are the owner of this record, you can report an update to it here: Report update to this record