Skip to main content

Biomedical and Electrical Engineer with interests in information theory, evolution, genetics, abstract mathematics, microbiology, big history, Indieweb, and the entertainment industry including: finance, distribution, representation

boffosocko.com

chrisaldrich

chrisaldrich

+13107510548

chris@boffosocko.com

u/0/+ChrisAldrich1

stream.boffosocko.com

www.boffosockobooks.com

chrisaldrich

pnut.io/@chrisaldrich

mastodon.social/@chrisaldrich

micro.blog/c

 

@BeakerBrowser Or if it had built in micropub support to my site like Omnibear does as a plugin for Chrome?
http://indieweb.org/Micropub/Clients#Omnibear

 

@BenjaminHarwood The best part is it supports cutting edge tech like webmentions & micropub out of the box as well as easy syndication to social media. It can also be quickly bundled with brid.gy to bring a lot of your social conversations back to live on your own website so you can use social media, but not rely on it being up forever. I also think it gives a better user experience on mobile as well.

While I love and use WordPress, I don't know what I'd do without Known.

 

Another interesting piece that's related to webmention and feed readers is the <a href="https://www.w3.org/TR/micropub/">W3C Micropub spec</a> that I believe was released on the same day as ActivityPub. There are already feed readers like www.woodwind.xyz that allow you to not only subscribe and read your friends who publish to their own sites, but you can use it to micropub "likes" and "replies" to those posts directly from the reader and to publish them directly to your own website if it supports the micropub spec (and yes, there's already a WordPress plugin for that). These micropubbed posts can then, in turn, send webmentions from your own site to your friends' posts to be displayed as comments there.

More details on all of these and how they can interact can be found on the wiki at https://indieweb.org.

 

Manton, after having heard/seen your microcasts (and those of others) as well as your mention of podcasting tools above, I thought I'd point out that there's a micropub tool called Screech for podcasts: https://martymcgui.re/2017/03/14/183924/. It may be down the road a tad for micro.blog support, but it's also something that micro.blog could do to change the microcasting space. It could also be a useful differentiator for competing services like Twitter, Mastodon, etc.

 

Replied to a post on github.com :

This bug mentioned in the micro.blog slack also makes it sound like posts coming in via micropub or other methods aren't automatically setting the post kind, which may be related to this issue:
https://microblogging.slack.com/archives/C422USPPT/p1494879500056086

 

Some of the issue is that WordPress has a huge number of plugins which adds a lot of additional complexity (especially for Micropub clients) which isn't always going to be handled by every client.

As for webmentions, they're being bolted onto WordPress which doesn't have (or allow) a custom comment type, so they're jury-rigged in the best manner possible. There is still ongoing work, especially with the Semantic Linkbacks Plugin which does a lot of the heavy lifting here, if you've got thoughts/ideas, you should certainly weigh in on those Github issues as they are evolving.

I know there were a handful of quirks that have been changed in Known in the past months to fix some issues with microformats that were being parsed incorrectly, and thus caused other platforms like WordPress not to let them display as nicely when received. I think most have been merged and a new release of Known was pushed yesterday and should hopefully clear up some of these issues. I think the developers of the WordPress plugins and even the Known community are very responsive, so feel free to jump in with feedback, suggestions, or even pull requests on any of the pieces which are all on GitHub.

I'm sure there will be some remaining rough edges, but in general a lot of them have been smoothed over in the past year and most improvements now seem to be geared towards making the suite of tools more user friendly or to better extend the functionality.

 

Replied to a post on github.com :

@Tamaracks There's no need to explicitly set a Post Format in WordPress as it will automatically be set based on the Post Kind setting in Post Kinds on initial publish. (You can also tweak them by hand if necessary, so for example when using the `note` kind it automatically sets the Post Format to `aside`, but I prefer to use `status`, so I replaced `aside` with `status` just under 'note' => array( in the code here: https://github.com/dshanske/indieweb-post-kinds/blob/master/includes/class-kind-taxonomy.php

I also think @dshanske fixed the proper kind settings on micropub in the latest development branch of post kinds as well. https://github.com/dshanske/indieweb-post-kinds/issues/87 (Hopefully this should take care of checkins as well.)

 
 

@louisgray I hope that open W3C specs like Webmention and Micropub can help to turn the tide.

 

Aaron Parecki's Day 97: Updated Known's Micropub Support

 

OwnYourSwarm is awesome! 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.

 

Screech, a simple client for posting audio content (such as podcasts) to your own site using Micropub, is now available publicly. You can check it out at https://screech.schmarty.net/.

 

goes with a client called Screech!! If only @SoundCloud et al could do this... https://martymcgui.re/2017/03/14/183924

 

@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://OwnYourGram.com and micropub.

 

Replied to a post on github.com :

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.