Biomedical and Electrical Engineer with interests in information theory, evolution, genetics, abstract mathematics, microbiology, big history, and the entertainment industry including: finance, distribution, representation
OwnYourSwarm is awesome! #indieweb #FTW I love the fact that one can use the fantastically and cleanly engineered mobile UIs of services like Swarm/Foursquare and Instagram, but still also manage to own all of the related data (including GPS) on one's own website. Tools like OwnYourGram and OwnYourSwarm really show the power and value of micropub for the future of the internet.
@cdevroe I was thinking about this very phenomenon the other day having heard someone utter the phrase "Live an Instagrammable life." While in some sense I do miss the beautiful Instagram feeds of yore when it was mostly professionals, it's more interesting now with friends who use it to capture small snippets of their lives. Hopefully it doesn't get as nasty as "regular" life, especially as it seems lately.
I find that I use it quite a bit more now that I can use it as a mobile app to post to my own website with PESOS services like http:/
I think the biggest hurdle to wider adoption is simply the fact that there are so many individual plugins and this takes up far more mental space for the user than it should.
So, another option which I'd like to suggest and advocate for is to **bundle all the plugins into one big single plugin** instead of sub-plugins. You could almost sell it as "the part of WordPress core you always wished you had" and now you can with two clicks: download and activate. (That's got to sound good, even to your mom who's still figuring out how to upload her profile picture.)
From the user's standpoint, this wouldn't require much more than some slightly better UI/descriptions. (And I'm more than happy to write them.) This could consist of a single main settings page with on/off toggles for Post Kinds, Syndication Links, Webactions(?), Micropub, Hum, and IndieAuth. A tabbed interface on this same page with tabs primarily for settings/set up and usage description for all of these (except for maybe Webactions?) would complete the cycle.
Most of the sub plugins don't have many (if any) actual settings other than installation/activation right now which is creating the biggest part of the (mostly mental) hurdle for every day users. I think the average WordPress user probably wouldn't know that they had Webmentions, Semantic Linkbacks, or Webmentions for Threaded Comments installed because they "just work", require no configuration, but are far prettier than any of their predecessors. Why make them carry the mental overhead of what they are and what they do aside from a few subtle lines that they exist? In fact, treating them as if they should have been in WordPress core all along may actually make it more likely to happen.
Additionally things like Micropub which would only have an on/off toggle wouldn't be noticed or used by many unless they had interest in alternate posting interfaces. (And based on the popularity and growth in Twitter interfaces/apps a few years ago, I'm surprised WordPress didn't do this, though perhaps it's part of the reason they're adding a more robust API over the past few years?)
It also means having slightly better or more intuitive explanations of what the individual pieces are (mostly Syndication Links and Post Kinds) near their on/off toggles to better explain what is being activated. Much of this can be taken from the current interface or from the WordPress wiki pages, or added on the individual tabs for the settings for these portions.
I would suggest that doing this would not only make it easier on end users who then wouldn't have to spend the mental space and capacity to keep track of what 10 individual plugins are doing (in addition to the space these take up on the plugin admin page and the fact that, once activated, they disappear from the IndieWeb plugin's list of plugins), but that it would actually dramatically increase the uptake of the single big plugin and its functionality and simultaneously the use of the all the sub plugins individually.
I'd argue that bigger plugins like Yoast SEO or something like PressForward have huge numbers of options and settings and could have been done as separate sub-plugins (the way IndieWeb Plugin is now), but that their value proposition is such that it's well worth spending the handful of minutes reading through the interface to know what the options are, what they mean, and using them to their fullest advantage. I think that Indieweb (and the suite of tools offered on WordPress) is at this tipping point in terms of offering must-have functionality for the future web and that having a simpler integrated set up would help to push it over the edge to broader adoption. (Certainly simpler than the old WP-Social, which users have indicated that they thought was far simpler than Indieweb plugin, though Social actually required more set up.) Additionally all of the seemingly dense text in the "getting started" page could be moved into smaller bit-sized chunks relating to individual portions on a tabbed-interface, for example.
I come to this in part after having spent part of the weekend revamping a bit of the IndieWeb.org documentation on getting started with WordPress and setting up Bridgy with WordPress. A lot of the description is "get this plugin, install, and activate" which takes up a big piece of mental space for the user as well--particularly for the Gen2, 3, 4 users who want a plug and play experience. Far better would be to install one plugin and then modify these handful of settings.
If this is done, then the only remaining (small) hurdle is making sure that the underpinning rel-me data input required of the user is done in a more explicit manner, because this seems to be the lynch-pin holding a lot of it together and making it work. As a result, I'd recommend unbundling the reliance on the User Profile page and put all the rel-me URL fields on their own page in the settings interface for such a single plugin (with all important links just underneath them to encourage users to visit, for example, Twitter's edit profile page to include their website URL in either the website field or in the bio field to enable the bi-directional rel-me.)
Finally a "Tools" tab in the settings page could provide pointer links to additional things like the H-Card Widget or the IndieWeb-PressThis bookmarklets.
When all of this is done, it could also be a simple manner of adding another settings tab to the interface to set up Bridgy with one button links from the plugin to the set up pages for each of the main backfeed services there. Bridgy then automatically checks for the webmention endpoint and checks for rel-me to do it's work, so that part is already automated and relatively user friendly too.
The one caveat I can imagine is that making it all into one big plugin potentially means some small added overhead in development with maintaining some of them as stand alone pieces. I'd recommend keeping them as standalone objects as I honestly believe that pieces like webmentions and micropub are so fundamental to the web, that they should be part of WordPress core and maintaining them separately could help speed this along.
David is right, you'll have to add some code to your set up for it to happen automatically. For one workflow I've got via IFTTT.com, I do include the URL into the code so it's easy to copy and past over manually after the fact.
You could also consider using OwnYourCheckin [https:/
For extending things a bit, be sure to check out: http:/
One of the things that made using my Known site much more addictive was being able to do so more easily on mobile. I wrote up a few thoughts here that you might appreciate: http:/
If you don't like the writing interface you might consider using Quill https:/
You'll find lots of fellow devs and users of Known at https:/
Good luck and let us know if you need help!
Issue un-authenticating while moving from one site to another · Issue #29 · aaronpk/OwnYourGram https:/
I was moving my Instagram posting target from a WordPress install to a Known install.
For my WP install, on IG I revoked access from OYG and then reauthenticated for my Known site at http:/
Is there something else I need to do to deactivate ownyourgram from publishing to my WordPress install?
Is it possible that OwnYourGram holds the same authentication for two separate sites using the same Instagram account? This could mean that one would need an "off" switch through the ownyourgram interface to deauthorize one site. It could also separately be the case that Instagram didn't flush a cache which allowed my last IG post to the WP site to slip through.
So it sounds like you really want is the https:/
I don't think brid.gy automatically puts the syndicated link into the field, so you'd have to do it manually. Other plugins like Social Network Auto Poster (SNAP) or using micropub with clients like OwnYourGram or OwnYourCheckin have intercompatibility with Syndication Links and those URLs will be sucked in automatically.
If you find issues like this, please file them in the github issues repositories for the appropriate plugin so that the issues are known and can potentially be fixed. (Naturally if you can code well enough, you may be able to patch them with a pull request too.)
5 min read
I just wrote up a quick description for the IndieWeb plugin for WordPress. As a native IndieWebber, I thought I'd PESOS it from GitHub and share it out for those who might be interested. It's also a somewhat self-contained description why one should join the movement and points to some great resources.
The IndieWeb Plugin for Wordpress is a bundled installer for a core set of IndieWeb-related plugins. It's meant to be a one-stop shop to help WordPress users quickly and easily join the growing IndieWeb movement (see below). Some of these sub-plugins are required while others are optional.
Some of these plugins allow you to:
The IndieWeb is a people-focused alternative to the ‘corporate web’ that allows you to be the humb of your own web presence. It's been written about in Wired, The Atlantic, Slate, and Gigaom amongst others.
When you post something on the web, it should belong to you, not a corporation. Too many companies have gone out of business and lost all of their users’ data. By joining the IndieWeb, your content stays yours and in your control.
Your articles and status messages can be syndicated to all services, not just one, allowing you to engage with everyone in your social network/social graph. Even replies and likes on other services can come back to your site so they’re all in one place.
Interested in connecting your WordPress site to the IndieWeb? Let us help you get started.
IndieWeb for WordPress includes a plugin installer program. A Getting Started Guide can be found under Plugins->IndieWeb.
A group of web developers (including those knowledgeable about WordPress, among many other web technologies) can be found discussing and working on IndieWeb related technologies in the wiki at IndieWebCamp.com or in the #IndieWeb IRC on Freenode. WordPress specific portions of the IndieWeb camp can be found at WordPress, Getting Started on WordPress, Examples, and other plugins.
If you need additional assistance, feel free to reach out to any of the WordPress Outreach Club members via the website, our individual websites, or our social media presences -- we're happy to help!
Find more information and details for the motivations for joining the IndieWeb at http:/
If you think we missed a plugin reference, please file an issue on Github.
One could certainly download, install, and activate some or all of these plugins separately, but it is much quicker and easier to utilize the interface provided by this IndieWeb plugin to install and activate them. Note that some of these plugins may only be available on GitHub and are not yet on WordPress.org.
Also posted to GitHub:
wordpress-indieweb/readme.md at ee1cfb72203f1feef05b9225c4bb465abc82e094 · chrisaldrich/wordpress-indieweb https:/
Support Featured Image (and other common WordPress functionality) · Issue #24 · snarfed/wordpress-micropub https:/
I'm not sure if it's something that would fit in here or quite how -- perhaps a setting toggle?, but for clients that push photos (OwnYourGram.com, https:/
Other potential settings-based functionalities I can imagine being useful (based on experience with Twitter clients) include
* being able to set future posting times
* saving posts as draft, private, pending, etc. rather than automatically publishing
* allowing one to set Post Format (or if using the IndieWeb Post Kinds plugin: Post Kind)
Naturally supporting some of this would also depend on the posting client having support for these options as well.
@kraftbj already responded, but for completeness: also suggested here: http:/
(This also relates to jetpack_allow_per_post_subscriptions for email and alternate posting methods to WP including via email and [micropub](https:/
Glad to know that JetPack is on GitHub :)