- p3k - the code that runs aaronparecki.com
- Sync to Flickr
- Flickr Archiver (needs update)
- Export your Delicious bookmarks (now offline)
- Loqi - a sometimes-helpful IRC bot
- 100DaysOfIndieWeb - https://aaronparecki.com/tag/100daysofindieweb
- testing tool: https://micropub.rocks
- testing tool: https://websub.rocks
- tagged: https://aaronparecki.com/tag/indieweb
- 2016-09-30 Private Webmentions
- 2016-06-18 Videos from IndieWeb Summit 2016
- 2016-04-26 Monocle is Offline
- 2016-04-13 New integrated authorization server for p3k
- 2016-02-20 Enabling Global Webmentions with Telegraph and Superfeedr
- 2016-02-13 Going all in on self-hosting my code
- 2015-12-07 Setting up HTTPS with Letsencrypt.org
- 2015-08-29 Why I Live in IRC
- 2015-04-26 HTML Is My API
- 2015-03-05 Designing an IndieWeb Reader Based on How I Read Social Media
- 2015-01-04 Owning My Data in 2014
- 2014-06-22 IndieWeb Events June 2014
- 2014-06-06 The Importance of URLs
- 2014-06-01 Long-Term Archiving of GPS Logs
- 2014-03-23 Posting photos on my own site
- 2013-10-13 Realtime IndieWeb Comments
- 2013-10-11 The Future of Quantified Self Devices
- 2012-10-22 Creating Content on the Indie Web
- 2012-06-18 Introducing IndieAuth
- 2011-07-31 IndieWeb Messaging
- 2011-03-25 URL Shortener as a Search Interface
- 2010-12-17 How to build a multi-user Delicious clone with WordPress
- 2012-12 began receiving Pingbacks using webmention.io (called pingback.me at the time)
- 2013-05-26 added webmention support
- using a built-in webmention endpoint
- recognizes mentions, replies and likes via h-entry markup
- sending webmentions automatically for new posts
- 2013-06-23 began displaying count of received comments/likes/mentions on posts
I'm working on building the following building blocks of the Indie Web
- webmention specification and extensions such as private webmention
- indieauth specification
- micropub specification
- WebSub specification
I'm building indieweb functionality into my personal site, p3k
Things I feel like I've figured out pretty well, have shipped on my own site, can depend on, and am available to help explain to others.
- POSSE, in particular:
- webmention and pingback
- IndieAuth, in particular:
The notes below are archived after having launched the feature.
I have been using Foursquare consistently for a number of years now, and it is the authoritative source of every venue I've been. I know that if I have never checked in somewhere before on Foursquare, I actually have never been there before.
While my Foursquare feed is currently public, I'm reconsidering whether I want my indie checkins feed to be completely public. I may end up being more selective about the checkins I make public instead, and keep my full checkin history private.
Examples of public checkins often include a short note from me along with the venue for things like checking in to a venue for a public event, or checking in somewhere to say I'm going to be hacking there for a while inviting people to join me. When I check in to lunch two blocks away from my office, it's not that I don't want anyone to know I'm there, it's just that probably nobody cares and there usually isn't anything actionable that would come from them knowing anyway. Usually I'm getting something to go and don't have time to stay and talk anyway.
- a push API so I can pesos checkins to my site in real time
- lots of my friends still use it
- the app still provides fun tidbits when I check in, like "you've been here 5 weeks in a row", etc
- searching for venues is difficult to implement from scratch, and I'm not entirely happy with the OSM data, so using foursquare venues continues to be highest quality
Really getting annoyed that when Foursquare venues are renamed, merged or deleted, my own history is changed.
- Figure out how to represent a "checkin" on my own site (see Creating content on the Indie Web for more thoughts)
- Figure out how to store venues on my site (venue IDs, nice slugs, ???)
- Build a basic interface for viewing "checkin" data
- Syndicate out to Foursquare and possibly Facebook (although Facebook recently deprecated checkins in favor of attaching venues to notes)
- Repurpose the Checkie app to search my site for venues and post checkins to my site first
- Download all Foursquare history and create checkins on my site retroactively
- Checkins - I still haven't begun posting checkins on my website, the last major missing piece of my use of silos. Some details:
- Support basic checkins with photos, like checking in on Swarm
- Venues should get their own URLs on my site so I can see all checkins I've posted at a venue
- Create "lists" of venues, with tips specific to the entry in the list (example)
- Show lists grouped by city, like Foursquare
- Allow people to subscribe to notifications of my checkins at either particular regions of a map, or particular venues (e.g. let me know when you get to this area during the bar crawl)
- Monocle - an IndieWeb reader modeled after how I live in IRC
- Shoebox - a photo/media server, used as a Media Endpoint and to replace my use of Flickr, and Soundcloud
- community event calendar/aggregator
- private groups - wanting to communicate privately with some group of people. Since 2014 I have been finding private/secret Facebook groups very useful for certain things. How does this translate onto our individual sites?
- Mention App
- archive to wayback machine
- some time after publishing posts on my site, send a ping to the wayback machine to trigger archiving it
- send a ping for any pages that I link to
- gopher server for IndieNews as a follow-up to http://metatalk.metafilter.com/24019/Direct-your-gopher-client-to-gopher-gophermetafiltercom
projects that need to be renamed
I've had a bad habit of naming projects after the spec they implement. It has become apparent that this has caused more confusion than it has benefits. The worst case of this is indieauth.com, since it conflates the spec with the service that I run.
- indieauth.com (issue)
- webmention.io (issue)
- receives webmentions for you
- provides an API (and potentially a UI in the future) for displaying webmentions
Some brainstorming on private posts:
- I want to let people log in to my site, and then they can see things that are not posted publicly.
- Should additional posts appear on my home page once someone is signed in?
- Should there be a separate feed of posts that are visible only to the person who is signed in?
- I want to make some posts visible to groups of people, but might not want them to know which group they're in.
- Need some way to visually indicate that a post is not public, so that people know they should not share it as they would a public post. (screenshot or otherwise)
- Some posts I want to show the context they are posted in (e.g. POSSEing photos of my cat in the #animals channel in the XOXO Slack), but this applies also to public posts
- 2016-06-22 Standardizing the Social Web
- 2015-06-24 Micropub: The Emerging API Standard for IndieWeb Apps
- 2014-06-24 OAuth, IndieAuth, and the Future of Authorization APIs
- 2013-08-08 IndieWeb - W3C Workshop on Social Standards
- 2012-06-26 From OAuth to IndieAuth: Own your online identity given at Open Source Bridge 2012