Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Foursquare purposefully does not expose a "cheat" bit or the user's device reported distance from a venue via the API. The vast vast majority of users of foursquare do not cheat and the majority of "irregularities" between a user's reported location and the venue's location are due to poor GPS accuracy or are because the user is making a "post-check-in" at a location they were at but forgot to check into earlier.</p> <p>My advice for developers re: cheating is to either ignore it and/or detect it after-the-fact.</p> <ul> <li><p><strong>Ignore cheats</strong>: The cost/benefit ratio of trying to detect cheating is generally not worth it. Not only is it effort to build an effective system, but you will you frequently have false positives where you penalize legitimate usage, causing you to disenfranchise users trying to use the system as intended, through no fault of their own. If you remain worried, then you can design your system such that the user either gains little by cheating (they're only depriving themselves, or the reward is physical so they gain nothing) or will have social pressures against cheating (e.g. foursquare's friend-scoped leaderboard means that it's generally clear to friends if a user is blatantly cheating, nullifying any real benefit to the cheating user)</p></li> <li><p><strong>Detect cheats after the fact</strong>: You'll have better luck/precision detecting cheating post-fact when you can look at the whole of a user's activity, rather than trying to make a decision with each check-in. A use who cheats often should be fairly easy to detect with a periodic job using simple rules. A user that cheats once out of 100 check-ins will be harder to detect, but that's going to be true no matter what mechanisms you chose to adopt (and you're better off with an occasional false negative than an occasional false positive)</p></li> </ul>
    singulars
    1. This table or related slice is empty.
    1. POHow do I verify the validity of a Foursquare Checkin?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USakdotcom
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload