WeChat ID
aaronpk_tv
#bridgy
-
A Brief Intro to My Website Architecture
This is a description of all the pieces and tools that I use to post to my website and handle comments and responses. Many of the pieces are open source and/or based on open protocols that you can implement yourself.WritingI write posts using an app called Quill. It's an open source application that I wrote. I run a hosted version at quill.p3k.io, and you can run it on your own server if you want as well. Quill provides an interface for posting longer blog posts with embedded images like this, as well as short text notes, and a handful of other kinds of posts like bookmarks.Quill doesn't actually store any posts itself. It is just an interface for writing posts.When I click the "post" button in Quill, it sends a Micropub request to my own website, which then creates the post and displays it on my website. Micropub is an API standard for creating short notes and posts, and it supports photos and videos too!You can start using Quill if your website supports Micropub. There are some Micropub plugins for various CMSs, and it's also not too hard to write an endpoint yourself if you're into that sort of thing.Posting to Twitter/FacebookI never write posts directly on Twitter or Facebook. Instead, I write a post in Quill, and then check the boxes for where I want to syndicate the post.continue reading... -
Bridgy updates (indiewebcamp.com)
retrying responses is much improved. it retries *all* URLs, works harder to find candidate URLs (including syndication URLs), and you can page through old responses so you can retry them for finding your user page: along with remembering your accounts when you log into them, it now also lets you type your username, full name, or domain instead of user id in the URL (for silos where it needed that before)
-
For a while I was doing my own PESOS for my tweets so that I could still reply to people from the Twitter app and get those back on my site as posts. I quickly ran into a problem where I was sometimes re-importing a tweet that I had originally POSSE'd and would end up with two identical posts on my site. I wouldn't even know where to begin to try to do that with Facebook. If bridgy solves this well, I would probably use it, because I gave up running that code myself because of all the edge cases I encountered.
I am planning on doing PESOS of my Instagram, Twitter and Flickr likes, since I still often find myself in a situation where I'm reading something on one of those silos and it's quicker to just tap their button. I would happily use a Bridgy version of that as well.
You shouldn't be afraid of writing a micropub client for this, since it's basically a version of OAuth 2.0 which you've already dealt with on Instagram and Facebook. Also most people so far have implemented non-expiring access tokens on their sites. If you wanted to make this explicit, you could add a scope to the authorization request that would indicate such. -
"Because I've already got webmentions on my site, Brid.gy worked straight out of the gate--a lovely demonstration of some small pieces, loosely joined." - @adactio on posting notes from his own website: http://adactio.com/journal/6826/
