Since trying to follow a more “slow web” approach this year I’ve found it working out quite nicely. It’s started to highlight things for me that I would’ve brushed over before-Things that now start to rankle.
When home I use my Nexus 7 tablet. Uninstalling both Twitter & Instagram apps means I use the web-based versions. The differences are clear:
- Less, or no, advertisments
- No “stories” (videos) on Instagram
- Consciously wanting to see image/videos in Twitter Lite (3 clicks sometimes)
- Slow to load
But the timeline issues still remain.
Neither have a reverse chronological version. It’s all algorithmically driven, which makes both of them a nightmare to try and follow anything real-time. Twitter has so much cruft filling it up (I don’t want to know what anyone “liked”) that I’m starting to think using Lists may be the way to go. Add to that my yearly pruning of whom I follow may clear it up even more.
Glad my post struck a chord Colin 🙂
Looking at your list…
- Post status updates, posts, audio bits, and photos to Facebook
- Post photos to Instagram
- Be able to retweet or quote tweet posts easily from my site (no idea how to do this)
- Show Twitter likes, replies, retweets, quote tweets on my site
- Show Facebook likes, replies, shares on my site
- Show Instagram commends and likes on my site
…I think you can get some quick wins by connecting with Brid.gy, if you haven’t already. That will make it a lot easier to pull in comments, likes, etc. automagically from those silos.
I’m using David Shanske’s ‘Bridgy Publish‘ WP plugin to send my posts to Twitter. You also have the option to send them to Facebook and Flickr with it too.
You can’t post to Instagram from you blog (AFAIK), so I post direct and use PESOS to pull it in via Brid.gy. I also have IFTTT set up to post it as a native Twitter photo tweet. This means manually copying the link from Twitter back on your blog.
IndieWebify.me has the microformats listed on it’s front page to get replies etc. going. I’ve been trying TextExpander and have set those up as snippets so I can drop them right in when posting.
<p>in reply to:
<a href="" class="u-in-reply-to"></a></p>
Here’s a visual of how it all flows to/from my blog currently.
Doing this from mobile devices is a pain point. Tantek & I chatted about that very thing not so long ago. That’s why I’m trying from only my laptop.
The #Indieweb IRC is a good place to chat, and I’m more than happy to hop on a call if you want to discuss further 🙂
in reply to:
The slow web and POSSE
For 2017 I’m planning on returning to the “slow web”. A web of a few years ago. The web of choosing what, and when, I respond.
The Slow Web Movement has been around for some time now. Jack Cheng and Rebecca Blood wrote about this about 6 years ago. I’ve been mulling it around for some time and the more I put into practice IndieWeb methods, the more appealing it becomes.
Value, not addiction or lock-in. We’re not trying to make people hate themselves. We also can’t assume actual value creation based on engagement with the product. We have to connect the engagement to actual impact.
If you search for ‘slow web movement’ there really isn’t much written after 2014. But I think that a lot of the products and methods we’re seeing today; turning off notifications, blue-light filters, snoozing emails, sleep apps, are a indirect manifestation of that slow web thinking.
I’ve had virtually all notifications off for years now, apart from Twitter DM‘s. I treat those with the same import as a text message.
This year all of my posts, replies, and retweets on Twitter will be coming from this blog and not using the Twitter app (#OwnYourData). That probably means doing it at the end of the day. I’m hoping that will make them more considered (something we may all want to be in the coming years).