IndieWebCamp is a 2-day creator camp focused on growing the independent web


A checkin is the action of checking into a location and sharing that information. The term is often also used as a verb, to check in.

Services like Foursquare, Gowalla (shutdown after being acquired by Facebook), Dodgeball (shutdown after being acquired by Google), Google Latitude (also shutdown by Google) are social community sites specifically designed for sharing checkins.

The indieweb community is exploring how to post checkins to one's own website (likely privately), and how/when to syndicate (in POSSE style) such checkins to checkin-related community sites.



Past discussion sessions on indieweb checkins:

Pretty good notes in there that could be abstracted and captured in general form in new sections here.

use cases

personal logging

I'm entering a specific venue, I'd like to quickly/automatically capture the fact that I'm entering that venue (similarly for exiting) for personal logging / quantified self purposes.

in town

I'm visiting a city other than my home town, and rather than try to figure out who I know may be in that town at the moment and compile far too many explicit messages or a long BCC email, I'd like to announce to my friends who happen to also be in that city that I've arrived there and will be around a bit in case they'd like to meet up.

just in time social meals

I'm out at a coffee shop and want to quickly see if any friends are are nearby and might interested in getting brunch/lunch/dinner/drinks together.

IndieWeb Examples

In rough launch/implementation order:

Barnaby Walters

Barnaby Walters is using Taproot on to post notes with location data (including rev-geocoded address data) represented with an embedded h-card venue and in an embedded map, since 2013-01-24. Currently manually tagging specific check-ins with #checkin, but is working on adding richer venue information. Examples:

Tom Morris

Tom Morris is using Ferocity on to publish notes with venue data in an embedded h-card with geo microformat hyperlink (with title="lat;long") since 2013-02-02 . Examples:

Ben Werdmuller

Ben Werdmuller is using Known to post checkins since ????-??-??. e.g.:

Kyle Mahan

Kyle Mahan is using Red Wind on to publish checkins since 2014-03-24. E.g.:

Michael Owens

Michael Owens is using indie.js to post checkins with POSSE to Foursquare since 2014-09-07 e.g.,


Ben Roberts

Ben Roberts is using google maps static map to generate display in Postly since 2014-12-24. e.g.:


Some folks have experiments or prototypes of posts resembling or approximating checkins but are lacking key information in some way, e.g. explicitly marked up location information.


Tantek Çelik has manually PESOSed a couple of checkins to his site from inadvertent Twitter cross-postings from Swarm on 2015-03-28:

These posts are notes that show how a checkin could be presented in plain-text form, i.e. how a full checkin post could be POSSEd to Twitter, based on how Swarm cross-posts checkins to Twitter. Note how the Twitter copies have a permashortlink after their text content that links to the respective Swarm posts.

how to


What are best approaches to POSSEing checkins?

POSSE to Foursquare

Ben Werdmülller POSSEs his checkins to Foursquare with Known.

POSSE to Facebook

Ryan Barrett currently manually POSSEs from his site to Facebook, manually picks the venue etc.

Can likely call Facebook API to get a list of venues at a geo location.

Could also create a Bridgy Publish feature that looked checkin post with a Facebook venue URL and then POSSE the checkin to FB.


More explorations/brainstorms than FAQ yet.

just a note with a location

Is a checkin actually a separate post type?

Or is it just a note with location information?

Or does a note with location information become a checkin only when the location is a specific venue?

E.g. what are the user-expected/intentioned differences between:

The posts page has some discussion about the general question about explicit vs. implicit post kinds.


More ideas than creations, some thoughts about how individual indieweb community folks want to do indieweb checkins.

indieweb venues

Main article: venues.

I'd rather post a check-in on my own site, and have it use a venue URL that is *also* on my own site. Then at that indieweb venue URL, it can link to equivalents on Foursquare, OSM, FB, and whatever other centralized venue databases are created in the future. - Tantek [4]

Experience with Foursquare's "community generated/patrolled venues database" is that a few nitwits can pollute/damage the data quite badly, with deletions, overmergings etc. Sad to say, same thing happens with Wikipedia (excessive deletions, overmergings). Thus little hope that a "community hosted venues database" wouldn't have all the same problems, if not worse.

Just use hCard on indieweb venue URLs.

see also:

geolocation detection

In general it is good to use multiple source of geolocation information in order to increase accuracy and decrease latency to provide this information when querying for and presenting (multi-factor prompts) nearby venues.


GPS is great. Except when you are inside a building - it doesn't work. Then you go and get on the Tube, and pop out the other side. It takes time for GPS to seek. You spend much more time waiting for GPS to work out where you are than you do just typing in the name of the bar or whatnot.[5]

wifi location

wifi-assisted location determination can do better than GPS when inside a building.

velocity prediction

Last time(s) you checked in (or GPS was detected), you were moving in this direction at this pace, therefore you're likely at this location now.

pattern prediction

The last n times you checked in at place A, you checked in at place B within the next thirty minutes.

co-checkin prediction

You just checked in with friend F at location A, your friend F just checked in at location B, therefore you might be at location B as well.

see also