4 ms·

I really like the thought. Very fresh! First things that come to mind are based on the User Experience. How will it function without being obtrusive? Can you

I really like the thought. Very fresh! First things that come to mind are based on the User Experience. How will it function without being obtrusive? Can you build a relationship with the Check-in user and the publisher/content provider? This is something Facebook cannot currently do with it's like button. I.E. I click the Like button on your site makes it visible to My friends, but it won't create a "personal connection" between Me and you. Can your check-in mechanism solve this? I'm bookmarking this, cause I'd like to see where this goes. It's certainly an intriguing proposition.

famfam 16y ago
UX wise, I figured that the user will travel around with a 3rd party cookie from our main domain. The site operator will install a simple <script> tag. The script tag will fire off a jsonp request to our server. If there's no cookie present, the resultant js will either do nothing, or at the site operator's discretion invite them to join our system. If the cookie is present, and a valid session is detected, and they haven't logged in in the last 24 hours the resultant js will popup a small "notification" (or just use html5 notifications if available) that you've checked in. If there's a cookie, but no session, the js will, at the site operator's discretion, either do nothing or invite them to login (inline) and claim their checkin. I'm not sure what you mean by relationship, but we will know who the user is and what the site is, so we would obviously be tracking a relationship there. Thanks for the feedback!