Talk:How To - Make Friends
From The Socknet
Clearly there should be an unfriend, and unsubscribe too. --Dan 13:29, 15 September 2009 (UTC)
That's done.
Contents |
Rename functions?
Now should we rename subscription-request to subscribe and friend-request to befriend? --Dan 22:15, 22 September 2009 (UTC)
- Or even rename subscription-request to follow, since that's what it really means. --Dan 14:01, 30 September 2009 (UTC)
- No, don't bother. --Dan 16:23, 15 October 2009 (UTC)
Captchas
It has been suggested that a redirect to a captcha may be in order here. I'm not really against this, though it may be difficult to implement on some devices. The captcha could be optional: if the user fills it out then his spamminess decreases, otherwise his spamminess is unchanged, and the receiving user can still accept him as a friend. In this way, devices that do not have web browsers may still support friending (not sure if those devices will even exist in the Socknet). --Dan 14:09, 9 September 2009 (UTC)
Tell Friends when New Friend is Made?
A provider will probably send a message to friends whenever the user makes a new friend.
Should we create a function that explicitly tells friends' providers about new friends?
Pros:
- Friends could find friends more "automatically"
- Services could find friends (ie, the new function should also take services into account)
- Friends could know that strangers are less spammy automatically
However, if providers already send messages whenever a user makes friends, then the goals listed could be achieved by reading the messages and seeing who's mentioned (because their OpenID's will be included in any useful message).
--Dan 19:54, 7 October 2009 (UTC)
Voucher field?
Add an optional field to friend-request that tells which friends of the receiving user are already friends with the requesting user? Or just let the receiving user figure it out on his own?
--Dan 19:55, 7 October 2009 (UTC)
- Added --Dan 20:00, 3 November 2009 (UTC)
TODO: Provide a checking mechanism
Friend requests can expire or be canceled by the requestor but we have no way of checking. Currently, if that happens, a response results in a new request sent in the other direction. Not really the best way. We need a way to check if it's expired/canceled.
Options:
- Include an "expiration" field, but this doesn't cover cancellations
- Add a method called "check_friend_request" for this
--Dan 21:55, 5 February 2010 (UTC)

