Skip to main content
 

Replied to a post on github.com :

Excerpt not copying properly · Issue #7 · meitar/wp-crosspost https://github.com/meitar/wp-crosspost/issues/7

When I do this:
Post something on my self-hosted WP blog without anything in the "Excerpt" field

This happens:
The crosspost that appears on WordPress.com seems to have cut and pasted a portion of the body of the original along with the notice about the original post into the excerpt field.

Complicating things somewhat is that I'm using the 2016 theme which utilizes the excerpt as a magazine-like "kicker" or subtitle, so it publishes the excerpt as a teaser line between the title of the post and the traditional body of the post. With most themes this "bug" isn't as problematic as the excerpt is used as metadata, but in my case it's publishing content in a duplicative fashion.

Example:
Original post: http://boffosocko.com/2016/06/04/55673397/
Syndicated post: https://chrisaldrich.wordpress.com/2016/06/04/55673397/

As an aside, given your personal philosophy and the motivation behind this particular plugin and your tumblr crossposter, if you're not already aware of them, I thought I'd mention the [IndieWeb movement](http://indiewebcamp.com) which is firmly behind people owning their own data (as opposed to corporate silos like Facebook, Twitter, et. al. owning it) as well as their online identities. (It's also part of the reason I've been using this particular plugin). I suspect you'll appreciate their mission and potentially be able to use portions of their opensource code and related work.

 
 

Replied to a post on github.com :

Call to undefined function extract_domain_name() · Issue #24 · dshanske/syndication-links https://github.com/dshanske/syndication-links/issues/24

After updating IndieWeb plugin and Syndication Links I get the following:

Fatal error: Call to undefined function extract_domain_name() in /wp-content/plugins/syndication-links/includes/class-syn-meta.php on line 52

This shows up in the page display where the content is usually otherwise output, so I still get the featured image, but no content and the error appears instead.

If I check the box for "Disable Syndication Links in the Content" the error disappears, but of course then the links don't show up on the page.

 

Replied to a post on github.com :

Cannot redeclare class RelMe_Widget · Issue #36 · indieweb/wordpress-indieweb https://github.com/indieweb/wordpress-indieweb/issues/36

Just updated to the newest IndieWeb plugin and got:
Fatal error: Cannot redeclare class RelMe_Widget in /wp-content/plugins/indieweb/includes/class-relme-widget.php on line 87

I hadn't gotten a chance to do the update to Syndication Links yet. Could that be related? Do they both need to be updated simultaneously?

 

@Bradamante in re: life http://etherpad.indiewebcamp.com/indieweb-life with regard to Twitter from this afternoon

I keep a primary site at www.boffosocko.com for longform and usually more substantive (whatever this means...) content while I use the Known platform through www.stream.boffosocko.com for shorter form content, checkins, status updates (Twitter), etc. Keeping my Twitter content is easier here because I don't expect any/many to subscribe to my stream site, so I'm not worried about spamming the world that may want to follow the more substantive stuff. I've tried to make using twitter with my stream as easy as possible by using a simple bookmarklet on desktop () and a simple sharing tool on mobile (http://indiewebcamp.com/Posting_from_mobile_devices)

One day, perhaps when I've over-configured my WordPress install to do things exactly the way I want them, perhaps I'll post it all to one site, but for now, it seems to work pretty well for me without being onerous for my (percieved) audience (hi mom!) :)

Fortunately there's a million ways to do all of this, you just have to find what works best for you.

 

I just finished importing all of my Instagram posts (PESOS) to www.boffosocko.com

 

Trying to play catch up on Camp Summit after a hectic morning. Anyone have the livestream? http://indiewebcamp.com/2016

 

IndieWeb Summit 2016 and what I hope to accomplish attending remotely.

 

Description and FAQ for IndieWeb WordPress Plugin

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.

Description

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:

  • send and receive comments, likes, reposts, and other kinds of post responses using your own site
  • allow comments on others' sites to show up as comments on your posts
  • help make IndieWeb comments and mentions look better on your site
  • allow support for threaded comments and webmentions
  • more easily syndicate your content to other sites to take advantage of network effects and other communities while still owning all of your original content
  • link to syndicated versions of a post so that comments on your content in silos like Facebook, Twitter, Instagram, Google+ can come back to your original post as comments there
  • allow you to add bookmarklets to easily respond/comment on other sites with one click
  • set up a MicroPub Server to use other posting interfaces. (You could potentially use services like Instagram, Foursquare, and others to post to your WordPress site.)
  • set up a personal URL shortener
  • log into your WordPress site with services like Twitter, GitHub, SMS, or even email using IndieAuth.

The IndieWeb

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.

The IndieWeb, like WordPress, feels that your content is yours

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.

The IndieWeb is here to help you be better connected

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.

Frequently Asked Questions

How do I get Started?

IndieWeb for WordPress includes a plugin installer program. A Getting Started Guide can be found under Plugins->IndieWeb.

Where can I find help? Can I contribute?

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 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!

Why IndieWeb?

Find more information and details for the motivations for joining the IndieWeb at http://indiewebcamp.com/Why

What about plugin XYZ?

If you think we missed a plugin reference, please file an issue on Github.

What plugins are included in this package? Can I install them separately?

  • Webmention (Required) - allows you to send and receive by adding webmention support to WordPress. Mentions show up as comments on your site.
  • Semantic Linkbacks (Required) - makes IndieWeb comments and mentions look better on your site.
  • Webmention for (Threaded) Comments - Adds support for threaded comments for webmentions.
  • Webactions - Adds webaction markups to WordPress elements.
  • Post Kinds - Allows you to reply/like/RSVP etc to another site from your own, by adding support for kinds of posts to WordPress.
  • Syndication Links - Adds fields to a post to allow manual entry of syndication links as well as automatically from a supported syndication plugin. Fully supports Social, partial support for NextScripts: Social Networks Auto-Poster (aka SNAP).
  • MicroPub - A MicroPub Server
  • IndieWeb Press-This - Adds IndieWeb markup to the WordPress Press-This bookmarkets to allow you to respond on your site with one-click.
  • Hum URL Shortener - A personal URL shortener.
  • Indieauth - The plugin lets you login to the WordPress backend via IndieAuth. It uses the URL from the profile page to identify the blog user.

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://github.com/chrisaldrich/wordpress-indieweb/blob/ee1cfb72203f1feef05b9225c4bb465abc82e094/readme.md

 

B0RG, if you need it you can read some of the details I've sketched out at:
https://github.com/chrisaldrich/wordpress-indieweb/blob/ee1cfb72203f1feef05b9225c4bb465abc82e094/readme.md

Let us know if you need any additional help!

 

Replied to a post on github.com :

Mostly I'm just thinking about this from the IndieWeb "Own Your Own Data" perspective, so if I'm reading this all correctly, the way the plugin is handling things, it's relying on Twitter's long term existence to serve up the physical content of the tweet?

I would suggest that using the blockquote method with the associated .js may be preferable for IndieWeb users as it saves the content of the tweet as a blockquote with the associated metadata. At worst, if Twitter disappeared, then one would at least "own" the text of the original which would minimally fallback to display as a simple blockquote rather than the fancier embedded Twitter card.

 

Replied to a post on github.com :

Embed for Tweets versus Blockquote (html/js) with Text? · Issue #10 · pfefferle/wordpress-indieweb-press-this https://github.com/pfefferle/wordpress-indieweb-press-this/issues/10

I've noticed that the IndieWeb Press This bookmarklet uses something like [embed]https://twitter.com/ChrisAldrich/status/707313378268618752 [/embed] in the main body of the content rather than the Twitter html/js embed method
(a la: <blockquote class="twitter-tweet" data-lang="en"><p lang="en" dir="ltr"> etc... )

I suspect that WordPress is doing some processing on the back end with the [embed] short code to fetch and display the twitter card and thus isn't technically saving the actual content of the tweet the way the blockquote embed method does. In the event of a Twitter silo death, this could spell trouble for users losing the data.

Cross reference: http://techlifeweb.com/bookmarklets-for-indieweb-favorites-and-retweets/ and http://stream.boffosocko.com/2016/scott-i-love-the-concept-of-your-bookmarklets-and-how

 

Replied to a post on github.com :

Rich Embeds for silos like Twitter might actually be somewhat useful when using post kinds "like" and "repost" as the Twitter card would then display in the post in a nice visual fashion. The tougher question, however, is: Is the actual content of the Tweet being copied over as a blockquote with the full text (similar to what one would cut/paste from Twitter when clicking on their "embed" option within a Tweet) or is it using something like [embed]https://twitter.com/ChrisAldrich/status/707313378268618752 [/embed] which happens with the [IndieWeb Press This](https://github.com/pfefferle/wordpress-indieweb-press-this) plugin? If this is the case, then I imagine that if Twitter experienced a site-death then the proverbial "backup copy" of the plain text of the original liked/reposted tweet would be gone and the [embed] portion would be utterly useless thereafter, no?

Cross reference: http://techlifeweb.com/bookmarklets-for-indieweb-favorites-and-retweets/ and http://stream.boffosocko.com/2016/scott-i-love-the-concept-of-your-bookmarklets-and-how

 

Scott, I love the concept of your bookmarklets and how they work!! I particularly like the way that WP blockquotes the original and copies over the actual text of the tweet. Sadly after configuring it for use, when I cut and paste I don't get the actual tweet, but end up with a blockquote that literally reads "+document.title+" instead of the text of the tweet. I'm also using it in Chrome, but not sure what is going wrong that I'm seeing this quoted text instead of the actual tweet. Is there something else I need to configure?

I like the way your bookmarklet works compared to the https://github.com/pfefferle/wordpress-indieweb-press-this bookmarklets which work fine, but rather than do a full embed of the actual text in blockquote style, it puts in something like `[embed]https://twitter.com/ChrisAldrich/status/707313378268618752[/embed]` which WordPress then processes to display the tweet. I'd worry that if Twitter experienced a site death, that the content on my site would no longer show the original content of the tweet!

The third potential method of doing all this could be to use David Shanske's Post Kinds plugin https://github.com/dshanske/indieweb-post-kinds which provides the ability to create a bookmarklet that supports URL parameters using the URL http://www.YOURSITE.com/wp-admin/post-new.php?kind=like&kindurl=@url or http://www.YOURSITE.com/wp-admin/post-new.php?kind=repost&kindurl=@url where the variable "@url" is the permalink of the tweet. The post kind is then set appropriately as well as the referenced URL which then does the embed, but I suspect it's using the [embed] method, which again doesn't seem like it will work sustainably in a possible post-Twitter world.




 

@TechLifeWeb Not sure if you'd run across it yet, but are you attending Camp in LA this year? http://indiewebcamp.com/2016/LA