Space separated tags not appropriate for WordPress multi-word tags

Filed an Issue Omnibear (GitHub)
A Micropub browser extension. Contribute to keithjgrant/omnibear development by creating an account on GitHub.

WordPress installs will frequently use multi-word tags/categories, thus there is no way to send those tags when Omnibear defaults to space separated tags. Comma, semi-colon, or other separators may be better in these situations.

Syndicated copies to:

Reply to Release Version 2.0 of Micropub plugin · Issue #150 · snarfed/wordpress-micropub

Replied to Release Version 2.0 of Micropub plugin · Issue #150 · snarfed/wordpress-micropub (GitHub)
Version 2.0 is merely the name I'm using for all the changes thus far. Since I have decided I'm not going to pursue any further enhancements before releasing a new version, using this issue to track anything left to do before releasing this version as stable.

Micropub errors for OYS 8-25-18 (using master branch from 2018-08-24 ef76125)

[25-Aug-2018 18:42:04 UTC] Micropub Error: 403 forbidden - Unauthorized
[25-Aug-2018 18:42:04 UTC] REST request: /micropub/1.0/endpoint: {"type":["h-entry"],"properties":{"published":["2018-08-24T17:44:13-07:00"],"syndication":["https:\/\/www.swarmapp.com\/user\/11479\/checkin\/5b80a65de0c0c9002c0c8589"],"content":["Being lazy for dinner tonight."],"photo":["https:\/\/igx.4sqi.net\/img\/general\/original\/11479_Z5VSLqOla8M3LhlRo_7QKUXeiGvaufQM1NTUYg32Dp0.jpg"],"checkin":[{"type":["h-card"],"properties":{"name":["Gerrish Grill"],"url":["https:\/\/foursquare.com\/v\/5b66159f2db4a9002ce66d2b"],"latitude":[34.1745],"longitude":[-118.09457],"locality":["Pasadena"],"region":["CA"],"country-name":["United States"],"postal-code":["91107"]},"value":"https:\/\/foursquare.com\/v\/5b66159f2db4a9002ce66d2b"}],"location":[{"type":["h-adr"],"properties":{"latitude":[34.1745],"longitude":[-118.09457],"locality":["Pasadena"],"region":["CA"],"country-name":["United States"],"postal-code":["91107"]}}]}}(Header Absent)
[25-Aug-2018 18:42:04 UTC] REST result: /micropub/1.0/endpoint: {"error":"forbidden","error_description":"Unauthorized"}(403) - null(User ID: 0)
[25-Aug-2018 18:42:04 UTC] PHP Warning: Invalid argument supplied for foreach() in /htdocs/wp-includes/rest-api/class-wp-rest-server.php on line 1259
[25-Aug-2018 18:42:08 UTC] PHP Notice: Array to string conversion in /htdocs/wp-includes/formatting.php on line 1045
[25-Aug-2018 18:42:08 UTC] PHP Notice: Array to string conversion in /htdocs/wp-includes/formatting.php on line 1045
[25-Aug-2018 18:42:08 UTC] PHP Notice: Array to string conversion in /htdocs/wp-includes/formatting.php on line 1045
[25-Aug-2018 18:42:09 UTC] PHP Notice: Array to string conversion in /htdocs//wp-includes/formatting.php on line 1045
[25-Aug-2018 18:42:12 UTC] PHP Notice: Array to string conversion in /htdocs/wp-includes/formatting.php on line 1045
[25-Aug-2018 18:42:12 UTC] PHP Notice: Array to string conversion in /htdocs/wp-includes/formatting.php on line 1045
[25-Aug-2018 18:42:14 UTC] http://nominatim.openstreetmap.org/reverse?format=json&extratags=1&addressdetails=1&lat=45.53548&lon=-122.621244&zoom=18&accept-language=en-US
[25-Aug-2018 18:42:15 UTC] http://nominatim.openstreetmap.org/reverse?format=json&extratags=1&addressdetails=1&lat=45.53548&lon=-122.621244&zoom=18&accept-language=en-US

Syndicated copies to:

Bug: My Profile link in footer directs to incorrect URL

Filed an Issue gRegorLove/indiebookclub (GitHub)
indiebookclub is a simple app for tracking books you are reading https://indiebookclub.biz

When logged in the “My Profile” button in the footer of my page directs to https://indiebookclub.biz/users/www.boffosocko.com which gives a “Page not found notice”.

If I go to https://indiebookclub.biz/users/boffosocko.com instead, then the page resolves and shows the profile page I would expect.

Syndicated copies to:

Feature Request: OwnYourSwarm posts should trigger weather lookup

Filed an Issue dshanske/simple-location (GitHub)
simple-location - Adds Basic Location Support to Wordpress

Currently OwnYourSwarm will allow crossposts with GPS data that allows Simple Location to display. Though OYS doesn’t send the weather data, I presume it could be possible that upon receipt of the OYS data that Simple Location could still be triggered to do a weather lookup so that the checkin could display both the location as well as the weather data for that checkin.

Taking things a half step further, perhaps any micropub or other incoming post creation tool that includes location data could automatically trigger a weather lookup? Then OwnYourGram, DsgnWrks Instagram Importer, or other similar tools that create new posts with location data could provide weather as well.

Syndicated copies to:

Swarm checkins appear as notes

Filed an Issue dshanske/indieweb-post-kinds (GitHub)
indieweb-post-kinds - adds support for responding to and interacting with other sites using the standards developed by the Indieweb Community

Perhaps I’m missing a setting somewhere, but since I’ve gotten OwnYourSwarm working (using JSON as opposed to the “Simple” setting, the post data arrives as expected, however, Post Kinds is defaulting the post to be a note instead of a checkin as I would expect. (In general, I would think that all posts arriving from OYS would always default to be checkins despite the fact that they may have note-like content as well as photos.)

In the settings on my site, I’ve even got the “Default Kind for New Posts” set to checkin, as I use it often, yet the posts still show up as a note.

Ideas about what may be missing or going wrong?

As a small caveat, I’ll note that this install is running Post Kinds Version 3.0.6, but I suspect that nothing has changed since about June that might fix or affect this issue.

Syndicated copies to:
Replied to user-secret.svg replacing default avatar? · Issue #178 · pfefferle/wordpress-semantic-linkbacks (GitHub)
While I don't mind that this plugin offers its own avatar for unassigned gravatar photos, I wish it would present me the option to choose it on wp-admin/options-discussion.php under Default Avatar. With the latest update, all my default avatars are being overridden with user-secret.svg.

In version 3.8.1 it currently appears that comments from WordPress and Micro.blog (both of which have Gravatar as a commonality) appear to be automatically using the default mystery person avatar even though there is a separate avatar defined within the Avatar fields for Semantic Linkbacks Data.

If I add my my email address within the comment editing interface, then the appropriate Gravatar is pulled and displayed as expected. This leads me to believe that somehow SL either isn’t finding/pulling the Gravatar URL that it’s storing, or the code is potentially skipping looking for it within its logic structure.

I’ve noticed this also seems to be the case for other WP sites which I have reason to suspect are running this same version as well.

Webmentions from other non-Gravatar related sites don’t seem to be affected by this and they’re displaying the proper avatar images as defined within their h-cards.

Syndicated copies to:

Facepiles no longer working for RSVPs

Filed an Issue pfefferle/wordpress-semantic-linkbacks (GitHub)
More meaningfull linkbacks

They’d previously been working, but for some reason, with the setting set to facepile all the RSVP types in settings, none of the RSVPs are facepiling like they’re supposed to now.

Syndicated copies to:

QuantaMagazine.org orphans all annotations

Filed an Issue hypothesis/h (GitHub)
Annotate with anyone, anywhere.

Steps to reproduce

  1. Annotate any particular individual article on https://www.quantamagazine.org/
  2. Links to the annotations are redirected back to the root domain and not the individual page

Expected behaviour

The links should direct to the canonical URL of the article

Actual behaviour

All the annotations to individual pages seem to automatically become orphans and are associated with the root domain instead of the individual permalinks.

Example: The annotations at https://hyp.is/lUpgtn15EeivjHMsJK03Tg/www.quantamagazine.org/ and https://hyp.is/6C98en11EeieFgMy1hP9tQ/www.quantamagazine.org/ on the page https://www.quantamagazine.org/mathematics-shows-how-to-ensure-evolution-20180626/ don’t resolve properly because of the orphaning issue on this website.

Browser/system information

This is happening to me on a variety of browsers on Windows 8.1 and Windows 10 including: Chrome 67 and Firefox Quantum 60.0.2 (64-bit).
It also appears to be an issue on both the current versions of Chrome/Firefox on Android v8.0.0

Additional details

I’d guess that the issue is site specific to quantummagazine.org somehow.

Syndicated copies to:

Errors on update to 3.8.0

Filed an Issue dshanske/syndication-links (GitHub)
Add and Display Syndication Links

After updating to the most recent version 3.8.0 of Semantic Linkbacks I’m getting the following error in the Comments sections of both posts and pages:

Warning: in_array() expects parameter 2 to be array, string given in htdocs/blog/wp-content/plugins/semantic-linkbacks/includes/class-linkbacks-walker-comment.php on line 25

It seems to be throwing the error the same number of times that there are comments on the post. Additionally the comments section is showing both the raw mentions and facepiled versions. I’ll have to test some additional posts, but it also seems to have changed some mentions that were previously moderated out to now be showing.

Syndicated copies to:

Reply to Allow reading friends feeds in a feed reader

Replied to Allow reading friends feeds in a feed reader · Issue #16 · akirk/friends by Alex KirkAlex Kirk (GitHub)
We can do this by providing a download for a OPML file.

Perhaps better than allowing simply the download of an OPML file, it would be nice to have the ability to provide a link to an OPML file as well? This way feed readers like Inoreader that support OPML subscription would be able to auto update themselves when new feeds/friends are added to the list?

Depending on your infrastructure, you could potentially leverage the old Link Manager within WordPress which provided OPML outputs as well as outputs arranged by category. This would prevent you from needing to rebuild the side-files unless you’re doing that already.

Syndicated copies to:

Facepiles not displaying avatars

Filed an Issue pfefferle/wordpress-semantic-linkbacks (GitHub)
More meaningful linkbacks

Apparently the v3.7.7 update seems to break the display of avatar images in facepiles for likes, bookmarks, etc. Instead of showing the expected avatar image, it’s showing the author’s name wrapped with an href for the originating site.

It’s not just my site either as I notice that the facepiles at https://ramblinggit.com/2018/05/241/ (using Sempress) are also displaying the same way.

I’d simultaneously updated the Webmention plugin and tried uninstalling and reinstalling both plugins as well as checking a variety of settings (including the discussion setting for showing Avatars) and uninstalling a variety of potential conflicting plugins, but to no avail.

I know there were recent changes for privacy related pieces, perhaps this is the cause?

Syndicated copies to:

Read doesn’t have an option to facepile in discussion settings

Filed an Issue pfefferle/wordpress-semantic-linkbacks (GitHub)
More meaningful linkbacks

It looks like the new “read” functionality for mentions automatically facepiles them anyway, but I’ve noticed that the settings at /wp-admin/options-discussion.php#semantic_linkbacks doesn’t include a checkbox for reads.

This really isn’t an issue (at least for me), but you may want to be aware of it or tweak it for parity’s sake.

Syndicated copies to:

Reply to vishae’s issue Affects the status of private posts

Replied to Affects the status of private posts · Issue #70 · dshanske/simple-location by vishaevishae (GitHub)
I've noticed this issue for a little while now but it's only today that I took the time to try and weed out the source. Whenever I update a post marked as private (visibility set to private), the post would get published to the public instead. Even when I edit the post to try to set it to private again, it still remains public. I have to go to the All Post (edit.php) page and quick edit the post to change the privacy there. It's only when I deactivated simple-locations this issue stopped happening and I can update and change the privacy of my posts in the indvidual post editing page.

I could have sworn I filed this as an issue before myself, but I’m not seeing it in the queue. Perhaps I mentioned in chat somewhere?

Simple location’s privacy setting seems to override the post’s public/private settings on my site as well. Perhaps it’s a naming conflict (function/filter/etc.) with WP’s core content visibility code?

In any case, I can’t make a post private while Simple Location is installed/activated either. This seems to happen regardless of other plugins. I do seem to be able to use @vishae’s method of using the quick edit option to change a post to private. I’m not sure if this may indicate a potential solution to the issue based on what is firing on a post save/update versus what fires on a quick edit save.

Additionally, I don’t seem to be able to mark a particular location as “private” in a post either as upon saving it it defaults back to public in the UI. I only seem to be able to use “public” or “protected” options for locations.

Syndicated copies to:

UI suggestions for watches

Filed an Issue dshanske/indieweb-post-kinds (GitHub)
Adds support for responding to and interacting with other sites using the standards developed by the Indieweb Community

It would be nice if there were a way to distinguish between various watch types to differentiate between films, television, and internet based streaming media — perhaps with a data field and a toggle along with three appropriate icons for each of these rather than the single watch icon now (a generic “play” button).

Further, most of the current meta data fields are fairly solid for the most often used fields, but I often find that it would be nice to have fields for Season # and Episode # for television shows.

The last “big” piece that would be nice to have is a quickly usable ratings field of sorts so one could provide a rating 1-5, 1-10, or 1-100 rating field? Maybe it could be a simple numerical data field that calculates/displays a rough 5 star-based scale? h-review markup could also come into play here as well, though it would be nice to capture the raw data even if there is no UI display built for it.

Syndicated copies to:

Reply to More IndieWeb compatible themes #2

Replied to More indieweb compatible themes · Issue #2 · indieweb/wordpress-feature-requests (GitHub)
Currently SemPress is listed as the only theme that is fully microformats2 compliant, but its style is very distinct and will not appeal to everyone. Many indieweb WP sites use twentysixteen or Independent Publisher. I have tried many combinations of the last 2 with the mf2 plugin, and ended up having to edit the theme code to get everything working. Would be great to have more options for themes that "just work". :)

A few random tips/pointers:

@GWG has put out a very customized version of his Twenty Sixteen Theme on Github. For those who have some development skills or are willing to look at examples to try changes themselves, the commit history of this particular theme is very enlightening and does a reasonable step-by-step job of providing snapshots of what he changed in Twenty Sixteen to make it more IndieWeb-friendly. For most themes, one may not want to go as far as he did to remove Post Formats in favor of Post Kinds for greater flexibility, but most of the rest is pretty useful and solid as an example if one is converting/forking other popular themes to make them more IndieWeb friendly.

There are a number of very IndieWeb-friendly themes and even child themes listed on the Themes page of the wiki. Most of these should “just work” though a few may have small bugs which could be filed to their respective repositories to improve them.

It’s generally recommended not to use the mf2 plugin with themes which are already very IndieWeb-friendly as it can cause issues or have unintended consequences. That plugin is generally better used when themes only have the minimal microformats v1 code which is added by WordPress core.

There are also lots of details and brainstorming for improving themes in general on the wiki page for WordPress/Development/#Themes.

Syndicated copies to: