While you should ultimately choose the best option for you, I would strongly encourage the use of #3. Microsub readers are off to a great start, and I think the biggest barrier to entry is going to be servers. Aperture opening up will be a great step, but as you said, some people will want an easy way to have their feed data on their own server. A Wordpress plug-in that Added a Microsub Server to their Wordpress install would be a HUGE leap in lowering the bar for entry into using Microsub for ordinary people.
Kind: Replies
a reply to content typically on another site
I strongly agree with Axel Bruns about Facebook’s forthcoming API changes:
While these changes may generate some positive publicity for the company and its beleaguered CEO Mark Zuckerberg, they are likely to compound the real problem, further diminishing transparency and opportunities for independent oversight. The net effect of the new API restrictions is to lock out third parties and consolidate Facebook’s position as the main analytics and advertising broker. Contrary to popular belief, these changes are as much about strengthening Facebook’s business model of data control as they are about actually improving data privacy for users.
Reply to http://boffosocko.com/2018/03/03/enabling-two-way-communication-with-wordpress-and-github-for-issues/
Great guide for posting GitHub issues directly from WordPress. Thanks for taking the time to write this, Chris!
Thanks Eddie!
I agree, #3 has me the most excited. It would be interesting to work on, useful for me, and could definitely make MicroSub more accessible. Of all the options, this is probably the most challenging, but would be worth the effort if it works out.
This is probably the direction I’ll take, and it’s nice to hear that it resonates with someone else, too!