lokesh/pinback is an open-source project on GitHub with 7 stars, written primarily in JavaScript. Check-ins in your calendar
Snapshot summary built from the project's own GitHub metadata — there's no written TopGit review yet. The page will update automatically when a full review is published.
WHY NO REVIEW YET
TopGit writes full reviews for the most-starred, most-requested repositories. This page is a snapshot until then — see the READ ME tab for the original README in full.
Fetches your check-in data from Foursquare/Swarm API
Converts to iCalendar format
Uploads to AWS S3
Updates the calendar files regularly via GitHub Actions cronjob
You then can subscribe to these hosted calendar files in your calendar app of choice.
Prerequisites
Node.js v22 or higher
A Foursquare/Swarm account with check-ins
AWS account (free tier works fine)
GitHub account
How to run with your own data
We'll need to do the following:
Get a Foursquare Oauth token for your user.
Save the calendar files to AWS S3.
Schedule the app to run regularly via GitHub Actions cronjob
Expected setup time: 15-30 minutes
1. Get a Foursquare Oauth token 🪙
Before we get going, run npm i to install dependencies.
You can utilize the Foursquare API with an API key that is generated with a single-click via the developer portal, but for certain data, including user check-ins, you'll need to use OAuth. This process is cumbersome, but you only have to do it once.
Go to https://foursquare.com/developers/. Create a new developer account if you don't have one.
Create a new project in their developer portal.
In the Project Settings, enter http://www.google.com in the Redirect URL field. Take note that your Client ID and Client Secret are listed just above.
You'll be redirected to Google with a URL like http://www.google.com/?code=YOUR_CODE. Copy this code value - you'll need it in the next step. Important: If there's a # symbol and additional characters after the code, don't include those. The code should only contain letters and numbers.
Run the following curl command to get the Oauth token:
Rename .env.example file to .env and populate FOURSQUARE_OAUTH_TOKEN with your access token.
Open up config.js and update the settings to your liking and then run npm run start to test the fetching and calendar generation.
Configuration Options
myCity: Your home city (used to simplify location display)
myCountry: Your home country (used for international vs domestic formatting)
eventDurationInMinutes: How long each check-in event should appear (default: 60)
defaultIcon: Fallback emoji for uncategorized venues (default: 📍)
[!NOTE]
Rather than a single ICS file for all check-ins, we create multiple files for each 5-year period. This is to avoid hitting a possible 1MB file limit for subscribed calendars in Google Calendar -- the documentation on this is fuzzy. You will need to subscribe to each of the files individually in your calendar app.
2. Save the calendar files to AWS S3 🪣
Login to AWS and click create a new S3 bucket.
Important: Uncheck "Block all public access" and acknowledge the security warning
Add these values to your .env file:
AWS_ACCESS_KEY_ID= # From top-right menu > Security Credentials > Access keys
AWS_SECRET_ACCESS_KEY= # From top-right menu > Security Credentials > Access keys
AWS_REGION= # Example: us-west-1
S3_BUCKET_NAME= # Your bucket name
Run npm run start again, this time it should not only fetch the check-ins and generate the calendar files, but also upload them to S3.
Confirm that the files are in the bucket via the AWS console. Go ahead and subscribe to the calendars in your calendar app of choice.
3. 🤖 Set up GitHub Actions to run daily
Rather than running running this app manually we'll use GitHub Actions to run the app daily for us.
Fork this repository to your GitHub account.
Add your environment variables as repository secrets:
Go to your repository's Settings
Click on "Secrets and variables" → "Actions"
Click "New repository secret"
Add each of these secrets from your .env file:
AWS_ACCESS_KEY_ID
AWS_SECRET_ACCESS_KEY
AWS_REGION
S3_BUCKET_NAME
FOURSQUARE_OAUTH_TOKEN
FOURSQUARE_API_VERSION
The GitHub Action is already configured in .github/workflows/daily.yaml to run daily at midnight UTC. You can view the runs under the "Actions" tab in your repository.
To test the setup:
Go to the "Actions" tab in your repository
Select the "Daily Update" workflow
Click "Run workflow"
Check the run logs to ensure everything worked
Verify that the files in your S3 bucket were updated
Troubleshooting
Common issues:
Calendar not updating? Most apps refresh only every 24-48 hours
GitHub Action failing? Check the Actions tab for error logs
Files not public? Double-check S3 bucket permissions
The most recent commit recorded on lokesh/pinback was 1.2 years ago, based on the GitHub push timestamp. The repository has 1 forks — one of the better signals of community interest.
How many stars does lokesh/pinback have?
lokesh/pinback has 7 GitHub stars — refresh the page for the live number, or check github.com/lokesh/pinback. TopGit mirrors GitHub's count but does not claim minute-by-minute accuracy.
Is lokesh/pinback open source?
TopGit's metadata for lokesh/pinback does not record a license. Most public repositories on GitHub ARE open source, but the exact terms vary — verify by opening the LICENSE file directly.
What is lokesh/pinback?
lokesh/pinback (lokesh/pinback) is a JavaScript project on GitHub. From the project's own README: Check-ins in your calendar
What language is lokesh/pinback written in?
lokesh/pinback is written primarily in JavaScript. GitHub's language field is based on the largest share of bytes in the default branch.
Where do I read more about lokesh/pinback?
This TopGit page is a snapshot — the READ ME tab shows the project's own README content (links stripped, images preserved). The GitHub repository at github.com/lokesh/pinback is the definitive source.
Read full README in the tab above.
Still deciding about pinback?
One click hands the question to an AI along with this page — see what it says about pinback.