Foursquare is a venue reviews, recommendations, and lists silo based on its previous location-based checkin support, a feature that was spunout to the separate Swarm application which still shares some data back & forth with Foursquare.
- review posts (known as "Tips")
- lists of venues, either as recommendations or reminders
- venue search, ratings, and recommendations
- 1 Features
- 2 Past Features
- 3 Export
- 4 POSSE
- 5 PESOS
- 6 Event support
- 7 API
- 8 Venue claiming
- 9 History
- 10 Criticism
- 11 Press
- 12 See Also
Foursquare supports creating and sharing lists of venues. By default, Foursquare starts you off with a "to-do" list. It is possible to create lists with any name, so there are many examples of lists of favorite places, collecting places to visit in another city, or lists of places that have something in common.
Note: most past Foursquare were included in the spin-off app Swarm. These details pertain the features available in Foursquare until they were removed.
- Checkins can optionally contain photos or notes.
- Up to four photos and notes (as comments) can also be added to existing checkins.
- Only the author of the checkin may add photos, but any of their friends may add comments.
- Foursquare provides a web hook that can run every time a user checks in. 
- Checkin notes have a length limitation of 200 characters.
- Only up to four photos can be added to a checkin
Foursquare has feed files (e.g. .ics) and an API that can be used for export.
Foursquare provides feed files of all your checkins in multiple formats: RSS, KML and ICS.
- https://foursquare.com/feeds/ when logged in will show customized feed URLs that use special tokens for access (do not share them)
- Set up a Foursquare Developer account at https://developer.foursquare.com/
- Either write your own script or use the one Michael Owens wrote to extract all of your Foursquare data to your local file system. The script works by connecting to Foursquare, counting how many checkins you have to determine the total number of pages of data it needs to download, and then it makes periodic calls to the Foursquare API to download the files to your local machine or server, staying within the Foursquare rate limits.
- Convert your Foursquare API JSON files into h-entry h-as-checkin files by writing a second script to construct meaningful HTML representations of the checkins. The script mko wrote will handle most of the conversion from a Foursquare JSON object to a h-entry JSON object. Since he uses Indie.js, the script has a decent amount of data relevant only to his purposes at this time, but it would not be difficult to convert the script into a generic converter if needed.
- Michael Owens has exported all his Foursquare checkins, and has also
imported all of my posted photos, likes, and comments, though the likes and comments haven't been converted into IndieWeb mentions yet.
- ... first check-in on werd.io that POSSEd to Foursquare?
If I check in via my site, it'll check me in via Foursquare and ignore the push response for the checkin (so I don't get duplicate checkins).Michael also supports PESOS from Foursquare:
I've got a push endpoint on my site, so anytime I check-in on Foursquare through the app, it'll check me in via my site as well.
This works in likely a somewhat controversial way. There are multiple ways to syndicate a tip to Foursquare:
- I can reply to one of my checkins, and the text of the reply is added as a tip
- I can reply to a Foursquare venue URL directly
- I can send the text of a checkin itself as a tip
Foursquare does some amount of tracking of what events are happening at venues in their venue database.
The result is that others seeing your checkin see that you also checked in at a specific event at the venue, e.g.:
See also analysis of the Foursquare API by Social Web WG:
Foursquare provides the ability for someone officially associated with a venue to "claim" that venue which then gives that person more authority over the venue, including the ability to associate events with the venue (as documented above)
- someone from the venue has to go to https://foursquare.com/venue/claim
- and claim it as a venue they manage
- they make you give a phone number to "receive a call to verify your claim". The call asks you to record a sentence stating your name and relationship to the venue. The call appears to not be manually screened, but presumably is archived.
- they'll either mail you a postcard, or you can pay $1-20 (depending on city) with a credit card to "verify" it
Foursquare was launched 2009-03-06 at the SXSW conference and festival where it quickly gained adoption.
From launch until the Swarm split, Foursquare had badges you could earn all sorts of different way, some with levels of expertise (from 2x to 10x), some only available for brief periods of time (a particular day), some of which only at very specific venues.
Your old Foursquare Badges are accessible as an Easter Egg inside the Swarm app in "Memory Lane":
(These are likely only a subset of the many badges that were available; uploaded by Tantek Çelik)
On/Around 2014-05-01 Foursquare split much of its checkin functionality off into Swarm to focus more on locations, forseeably in an effort to better compete with Yelp. Checkins via the Swarm app created their own data, while much of it was also mirrored within the Foursquare site.
- "Digital platforms like Foursquare are producing "a harmonization of tastes."" 
Foursquare only occasionally suffers from outages. E.g.
- 2012-06-29 (all day)?)
Looks like there was an error connecting to #foursquare. Try developing an #indieweb solution instead.
- Which inspired: http://opensourcebridge.org/wiki/2012/Foursquare_is_down!
- CEO Jeff Glueck discusses privacy on the Foursquare platform 
- recommendation engine
- Foursquare Style - a category of home floorplans, likely unrelated to the Foursquare service
- 2019-02-09 downtime: https://status.foursquare.com/incidents/p42cjtxmj99g
- DIY Foursquare/Swarm iCal feed
- 2019-09-08 Outage: http://web.archive.org/web/20190909065234/https://status.foursquare.com/