An indie reader (I probably shouldn’t have used caps. Haha) is an attempt at getting the Facebook/Twitter like experience into feed readers. So that one can control what content they read and yet enjoy the reply/like/save functionality that exists in modern social media. This page provides some additional info: https://indieweb.org/reader
FYI in terms of easy and iOS. One option on Jekyll or Wordpress is Micropub (https://indieweb.org/Micropub). Wordpress has plugins and Jekyll has options (https://indieweb.org/Jekyll). Then you can use Indigenous (https://indieweb.org/Indigenous_for_iOS) to post
Awesome! Those are some great updates! Especially the automatic webmentions (something I want to do soon) and the h-card embedded of person tags.
Change for a time
Indieweb and webmentions. Posts originate on my site, then syndicate to Twitter. I’m replying from my site to your tweet now. 🙂
First off, thanks for writing this up! Often times discussions that happen on IRC can remain locked up in there when no one takes the time and effort to write their thoughts from the IRC conversations out onto their blogs (which is a key component to everything we are discussing, using our blogs for thoughts. haha)
I think a key issue that people producing clients (like swentel and I with the Indigenous clients) will run into is that when generation 3 or 4 people download our apps they can often be scared off by the discussion of protocols, even if those protocols are easily accessible through a user-friendly service. At the same time, you can’t AVOID using protocol names in discussing client compatibility. I think the key is finding the middle ground. This was actually brainstormed by schmarty that the key is beginning by mentioning popular services that support the protocol and only then following up with the protocol. For example “You can use this with Micro.blog, Known or any other Micropub compatible server”. It starts with the terms that a user might already know and aren’t as scary, but it also doesn’t shy away from the fact that the real compatibility lays in the Micropub compatibility.
These are great thoughts to be thinking through, how we can better aim IndieWeb-focused technologies toward a wider audience. I think one of the reason you found so much push back regarding protocols is because the IndieWeb group tends to be practical in the understanding that not all sites and/or people will use the protocols that we use. The goal is to interoperate as much as we can and when possible push for support of IndieWeb-focused protocols. That means often times people can attempt to distance themselves from the protocols because while they are vital to what we do as a community, we don’t want to be limited by them either. (Hence our push of POSSE and PESOS). Rather than saying everyone that wants to follow us has to read our h-feed, we often times will run services that convert our h-feeds into RSS feeds or JSON feeds so we can interoperate with services like micro.blog that supports Micropub and Webmention but doesn’t parse h-feeds.
Same, I used to pay for crossposting without using it as a way to “donate”. Now I pay for a microblog without using it. haha, but that’s because it allows me to “donate” and use it as I test out my Indigenous micropub client.