#aaronpki was looking for brainstorming on webmentions for checkins but i can't find it
#aaronpkwell it's not a huge leap to imagine including the venue's website in your checkin post, and then you'd send a webmention to their site to tell them you checked in
#aaronpkthat would let the venue know who is checking in, and do the thing that Bailey's taproom has where the TV shows the faces of everyone who's checked in there
#aaronpkbut of course it's easy to fake a checkin post. the foursquare app makes it a little difficult, but it's still possible.
#aaronpkso imagine on the TV screen that shows who's checked in, that it also shows a 4-digit code on the screen, and you have to include the code in your checkin post. that code would then change as soon as it's been used.
KevinMarks and mlncn joined the channel
#Loqi[indieweb] "Brainstorming "verified" IndieWeb checkins" on 2016-10-15
#[kevinmarks]Aaronpk - send your feed through unmung and see if you like the html that comes out?
rhiaro_, terminalpixel_, kants, Salt, bear, Gold, friedcell, pindonga and ricardokirkner joined the channel
#Loqi[indieweb] "Check out the meet-up page for the Homebrew Website Club #Brussels #indieweb" by Rick Mendes on 2016-10-15 http://meetu.ps/c/2QcvM/wC0hz/d
pindonga, friedcell, mlncn, sebilasse, KevinMarks, awolf, Pierre-O, cjk101010, brianloveswords, halorgium, ncollig, begriffs and KevinMarks_ joined the channel
#bear@aaronpk the 4 digit code idea would annoy anyone who tries to checkin along with 3 or 4 others IMO - why not just have a barcode that they scan that then becomes the token used like in private posts
#aaronpkScannng a barcode is more obtrusive to the flow
#aaronpkI've been in many situations where it would have been awkward to point my phone at something to check in, but just typing on my phone was fine
#bearjust thinking of a way to have a unique code but not make it easy to "share"
#bearif people have name tags, then it's just part of the tag
#bearI was even thinking for "high value" places the check in process would require a person at a desk, who is checking people in, to be the one to trigger the flow so the code can be kept secret
#GWGI think the idea is to make it not easy, but not impossible to spoof.
#GWGSo, you add a cost to doing it which turns away most.
#bearyep, which is why I like this webmention method - the cost being added is the cost of a personal domain that you use indieauth with to send the webmention
#bearthe small increase in complexity I'm adding just for my own examples of a higher value conference instead of something like a camp or meetup
#GWGAt a conference it is easy to have a temporary value. At a more permanent thing, it is harder
#bearoh, your talking about foursquare like checkins to a place - sure. I was speaking only to the event type
#bearfor those I would just insist on geo coordinates and not worry about those folks who spoof gps
#GWGbear: I was speaking of both more broadly. I don't usually check in to anywhere on anything, to be honest. The closest I get is posts when I visit interesting places. I would adopt those.
#GWGBut the idea of reporting attendance at a conference as well is intriguing.
#GWGI also wanted to document Indorsements at some point, which we discussed at NYC2
#tantek!tell aaronpk the extra 4-digit code thing sounds like "work", and as a user I'd always just blow it off, or blow off anything that required it, unless there was a very good incentive to bother with it (e.g. coupon / discount at the venue)
#Loqiaaronpk: tantek left you a message 1 minute ago: the extra 4-digit code thing sounds like "work", and as a user I'd always just blow it off, or blow off anything that required it, unless there was a very good incentive to bother with it (e.g. coupon / discount at the venue)
#tantek!tell aaronpk also, "easy to fake a checkin post" is hardly any sort of a high-priority problem to solve, it's one of those minutae things that either only devs worry about (not really a UX problem), or is only a problem once a service hits some massive scale. So I'd punt on it, or if you prefer, capture it in a "Brainstorming" section and move on
#aaronpki was starting with the assumption there was a situation in which the user is getting some extra value by publishing "verified" checkins
#Loqiaaronpk: tantek left you a message 1 minute ago: also, "easy to fake a checkin post" is hardly any sort of a high-priority problem to solve, it's one of those minutae things that either only devs worry about (not really a UX problem), or is only a problem once a service hits some massive scale. So I'd punt on it, or if you prefer, capture it in a "Brainstorming" section and move on
#tantekconcrete example of the 4 digit code laziness problem. Coffee Bean & Tea Leaf (California based coffee / cafe chain) used to have a 4 digit code on their TVs for logging into their captive portal for their free wifi. They eventually got rid of it.