{ "type": [ "h-entry" ], "properties": { "in-reply-to": [ { "type": [ "h-cite" ], "properties": { "url": [ "https://snarfed.org/2015-01-22_pesos-for-bridgy-publish" ], "name": [ "PESOS for Bridgy Publish" ], "comment": [ { "type": [ "h-cite" ], "properties": { "author": [ { "type": [ "h-card" ], "properties": { "name": [ "Kartik Prabhu" ], "url": [ "https://kartikprabhu.com/about#me" ] } } ], "published": [ "2015-01-22T20:47:26-08:00" ] } }, { "type": [ "h-cite" ], "properties": { "author": [ { "type": [ "h-card" ], "properties": { "name": [ "Ben Roberts" ], "url": [ "https://ben.thatmustbe.me/" ] } } ], "published": [ "2015-01-23T04:19:25-08:00" ] } }, { "type": [ "h-cite" ], "properties": { "author": [ { "type": [ "h-card" ], "properties": { "name": [ "Aaron Parecki" ], "url": [ "https://aaronparecki.com/" ] } } ], "published": [ "2015-01-23T09:16:49-08:00" ] } }, { "type": [ "h-cite" ], "properties": { "author": [ { "type": [ "h-card" ], "properties": { "name": [ "Kyle Mahan" ], "url": [ "https://kylewm.com" ] } } ], "published": [ "2015-01-23T21:52:12-08:00" ] } }, { "type": [ "h-cite" ], "properties": { "author": [ { "type": [ "h-card" ], "properties": { "name": [ "Barry Frost" ], "url": [ "https://barryfrost.com/" ] } } ], "published": [ "2015-01-26T05:12:21-08:00" ] } } ], "published": [ "2015-01-22T18:52:30-08:00" ], "author": [ { "type": [ "h-card" ], "properties": { "name": [ "Ryan Barrett" ], "photo": [ "https://secure.gravatar.com/avatar/947b5f3f323da0ef785b6f02d9c265d6?s=96&d=blank&r=g" ], "url": [ "https://snarfed.org/" ] } } ], "content": [ { "value": "
\n\n
\nPOSSEing silo interactions is\ngetting harder by the day,\nand Bridgy Publish is suffering as a\nresult. We could fix this by adding an\nOwnYourGram-style\nPESOS option. Should we?
\nIf you’re going to own your posts on social\nnetworks, indieweb people\nprefer to POSSE: post on your own\nsite, syndicate elsewhere. Bridgy Publish\nfollows this philosophy and provides POSSE as a service.
\nPOSSE has its disadvantages though. The Twitter app, for example, lets you\nfavorite a tweet with a single tap and ~100ms latency. Best of breed mobile\nindieweb approaches can’t touch that right now. Mine, for example, take\nmany more taps\nand 10-20s. Browser-based implementations and\nwebactions are a bit better, but not\nmuch.
\n\n
\nThe silos don’t even allow POSSEing\ninteractions consistently, if at all.\nFacebook’s 2.0 API often\nprevents commenting,\nliking,\nand resharing.\nInstagram’s API\nsupports liking but not commenting.\nGoogle+’s API is read only, full\nstop. Twitter has a fairly complete write API, but must be taken with a\ngrain of salt.
\n\nProposal: what if we added a Bridgy Publish PESOS option alongside the current\nPOSSE model?
\nThe arguments for POSSE and\nagainst PESOS are well founded.\nThey’re also aimed primarily at posts, not interactions. For interactions with\nsingle silo posts, especially likes and reposts – which rarely include additional\ncontent – PESOS ain’t so bad, and it comes with two big benefits:
\nSome of the PESOS drawbacks\nstill apply. It enables silo-first authoring and presentation and may discourage\nindie and cross-silo interactions. Those would be just as doable, though, since\nwe’d keep the current POSSE functionality.
\nThis would be a big project, but it’s doable. Bridgy would watch your silo\naccount for replies, likes, and reshares that it didn’t create. When it sees\none, it creates a matching original post on your site, via\nmicropub or whatever. (I despair at implementing even\njust the token management,\nmuch less a full micropub client, but those are literally implementation\ndetails.)
\nThoughts?
\nUpdate: To flesh this out a bit, here’s what I could and couldn’t do with each\nof the four main silos.
\nTwitter has a streaming API\nthat sends events for new favorites and tweets (including @-replies and\nretweets). Bridgy\nhas used it before.\nIt broke when Bridgy went over 100ish Twitter users,\nbut it would work for just one user. Even so,\nit’s a bit expensive on App Engine,\nso I’d probably just poll\n/statuses/user_timeline
and\n/favorites/list
.
Facebook‘s\nReal Time Updates\nshould work. I’ve already used it in\nownyourcheckin. I’d subscribe to\n/user/likes
and /user/feed
, which I think should include comments.\nI could also poll those endpoints.
Google+ has no way to get comments or +1s by user, only by post.\nAPI docs;\nfeature request;\nSO answer.
\nInstagram can get\nlikes by user,\nbut not comments.
", "html": "\n\n
\nPOSSEing silo interactions is\ngetting harder by the day,\nand Bridgy Publish is suffering as a\nresult. We could fix this by adding an\nOwnYourGram-style\nPESOS option. Should we?
\nIf you’re going to own your posts on social\nnetworks, indieweb people\nprefer to POSSE: post on your own\nsite, syndicate elsewhere. Bridgy Publish\nfollows this philosophy and provides POSSE as a service.
\nPOSSE has its disadvantages though. The Twitter app, for example, lets you\nfavorite a tweet with a single tap and ~100ms latency. Best of breed mobile\nindieweb approaches can’t touch that right now. Mine, for example, take\nmany more taps\nand 10-20s. Browser-based implementations and\nwebactions are a bit better, but not\nmuch.
\n\n
\nThe silos don’t even allow POSSEing\ninteractions consistently, if at all.\nFacebook’s 2.0 API often\nprevents commenting,\nliking,\nand resharing.\nInstagram’s API\nsupports liking but not commenting.\nGoogle+’s API is read only, full\nstop. Twitter has a fairly complete write API, but must be taken with a\ngrain of salt.
\n\nProposal: what if we added a Bridgy Publish PESOS option alongside the current\nPOSSE model?
\nThe arguments for POSSE and\nagainst PESOS are well founded.\nThey’re also aimed primarily at posts, not interactions. For interactions with\nsingle silo posts, especially likes and reposts – which rarely include additional\ncontent – PESOS ain’t so bad, and it comes with two big benefits:
\nSome of the PESOS drawbacks\nstill apply. It enables silo-first authoring and presentation and may discourage\nindie and cross-silo interactions. Those would be just as doable, though, since\nwe’d keep the current POSSE functionality.
\nThis would be a big project, but it’s doable. Bridgy would watch your silo\naccount for replies, likes, and reshares that it didn’t create. When it sees\none, it creates a matching original post on your site, via\nmicropub or whatever. (I despair at implementing even\njust the token management,\nmuch less a full micropub client, but those are literally implementation\ndetails.)
\nThoughts?
\nUpdate: To flesh this out a bit, here’s what I could and couldn’t do with each\nof the four main silos.
\nTwitter has a streaming API\nthat sends events for new favorites and tweets (including @-replies and\nretweets). Bridgy\nhas used it before.\nIt broke when Bridgy went over 100ish Twitter users,\nbut it would work for just one user. Even so,\nit’s a bit expensive on App Engine,\nso I’d probably just poll\n/statuses/user_timeline
and\n/favorites/list
.
Facebook‘s\nReal Time Updates\nshould work. I’ve already used it in\nownyourcheckin. I’d subscribe to\n/user/likes
and /user/feed
, which I think should include comments.\nI could also poll those endpoints.
Google+ has no way to get comments or +1s by user, only by post.\nAPI docs;\nfeature request;\nSO answer.
\nInstagram can get\nlikes by user,\nbut not comments.
" } ] } } ], "published": [ "2015-01-26T13:12:21Z" ], "category": [ "indieweb", "bridgy", "posse", "pesos" ], "content": [ "I've been forcing myself to like/repost tweets and Instagram photos exclusively through POSSE since 1st Jan. Although I get a self-righteous feeling of \"correctness\" it does take a few extra steps of copy-and-pasting URLs and I probably act on fewer things as a result.\n\nUsing PESOS for likes (and optionally reposts?) seems like an acceptable trade-off (I would still POSSE my replies). I already have a Micropub endpoint so in theory it should Just Work on my site, although I appreciate your audience is smaller for this. I'd certainly be happy to help test it." ], "like": [ { "type": [ "h-cite" ], "properties": { "name": [ "like of" ], "published": [ "2015-01-26T13:20:21Z" ], "like-of": [ "https://barryfrost.com/2015/01/i-ve-been-forcing-myself-to" ], "url": [ "https://snarfed.org/2015-01-26_ive-been-forcing-myself-to-likerepost-tweets-and-instagram-photos-exclusively-through-posse-since-%c2%b7-barry-frost" ], "content": [ "likes I've been forcing myself to like/repost tweets and Instagram photos exclusively through POSSE since… · Barry Frost" ], "author": [ { "type": [ "h-card" ], "properties": { "name": [ "Ryan Barrett" ], "photo": [ "https://secure.gravatar.com/avatar/947b5f3f323da0ef785b6f02d9c265d6?s=96&d=blank&r=g", "https://secure.gravatar.com/avatar/947b5f3f323da0ef785b6f02d9c265d6?s=96&d=blank&r=g" ], "url": [ "https://snarfed.org/" ] } } ] } } ] } }