reply
|

šŸ’¬ Replied to: Todayā€™s Project: Backup all Pages

ā€œA platform move for this blog is coming.  WordPress is frozen on ver. 4.9.9 which is fine by me, but untenable in the long term because eventually I will start missing needed security upgrades.  Also, Iā€™m beginning to suspect that my Indieweb stuff is not working everywhere with everyone and Iā€™m not willing to put the time in tracking down where the problems are on a platform I intend to leave.ā€

Brad Brad ( )

Last time I exported from a WordPress site, pages were included ā€“ you can either export them separately, or as part of ā€œall contentā€ ā€“ but itā€™s definitely good to have a manual backup, just in case!

I definitely feel your frustrations with IndieWeb on WordPress. Iā€™ve had so much trouble and spent so much time getting things setup ā€œjust so,ā€ and Iā€™m still not quite there. Iā€™m sure it wouldā€™ve been fine if Iā€™d stuck to one of the recommended themes and default plugin optionsā€¦ but then I wouldnā€™t be running my site. Even though a lot of my issues appear to be fixed now, half the time I still donā€™t trust things not to break seemingly at random.

Add to that small frictions like how hard it is to post a like/reply/bookmark type of post from mobile, and frustrations start to mount up.

Have you decided what youā€™re moving to yet?

reply
|

šŸ’¬ Replied to: Aaron Dembski-Bowden on Twitter

ā€œGood morning, dear friends, foes, and fellow skeletons vine-wrapped in veins and sheathed in steaks of muscle.

Show me your kill teams? #warmongers #40Kā€

This is my teamā€¦ very much still WIP, despite these pictures being a few months old ?ā€ā™‚ļø

note

|

Time to take a look at my lovely limited edition copy of Andy Clarkā€™s Celestine!

The packaging and presentation of the book is definitely very nice. Hopefully I can get stuck into the story later this evening!

Shared to IndieWeb.xyz

article

|

(Skip to the end for the TL;DR summary)

After an evening of debugging and rewriting sections of the HTML in ā€œKā€, I think Iā€™ve fixed the markup and parsing issues I mentioned yesterday.

It turns out that X-Ray, the parsing engine used by IndieNews, Aperture, and probably others, was only finding the sidebar h-card in my markup. The rest of the content was being ignored. Iā€™m not entirely sure why this is, to be honest, but it gave me a place to start.

Working from the (admittedly shakey) basis that if the parser was only going to find one mf2 entity on the page, then Iā€™d want it to be the main h-feed or h-entryā€¦ so I started moving around some blocks of HTML and a few classes, and stripped out a few likely redundant pieces of HTML.

Thisā€¦ worked! The feed would show up in the X-Ray output instead of the h-card, and wasnā€™t all that different in the Pin13 parser compared to yesterdayā€™s results. But it was far from ideal. The authorship information on every feed entry was screwed up; Iā€™d made a change yesterday so only one full h-card was on the page (the sidebar) and followed the recommendation to markup the h-entry author details with u-author instead. Now came the conundrum: do I add back in a dedicated h-card to every h-entry, and by doing so re-break some of the other parsers looking for a single ā€œrepresentitiveā€ h-card? I tried out adding them back in, just to see what happened. X-Ray was still fixed, but IndieWebify.me complained about it, and the IndieWeb Webring still couldnā€™t work out who I was.

I could have left it here. X-Ray was the main target, IndieWebify might not have liked it but could at least still see some details, and IndieWeb Webring was a ā€œnice to haveā€ in a way. But truth be told, it would have nagged at me. What if these ā€œminorā€ issues were the proverbial canary? I want to achieve the widest possible compatibility now, to reduce potential issues at a later date.

It was around about this point that I remembered that an h-feed itself could have its own embedded h-card, which could potentially solve the issue. After moving my ā€˜h-feedā€™ class to the body element, instead of the main Iā€™d been using up to then (so now it would use the sidebar h-card to represent the feed), it more or less did solve the issue.

It threw me at first that X-Ray didnā€™t list a separate h-card item like Pin13 did, but instead used the feed h-card for the authorship of every nested h-entry. Removing the now redundant author h-card from the entries stopped IndieWebify from grousing about these multiples. Oh, and hereā€™s my new profile page on the IndieWeb Webring. Even my test microformat-based feed in Aperture/Monocle started displaying posts almost immediately after applying the change.

So, TL;DR: I moved my main h-card inside the h-feed, instead of it being a distinct entity on the page. By doing so I fixed pretty much all of the microformat parsing issues I was experiencing, which means ā€œKā€ has taken a big leap forwardā€¦ and I can stop pulling my hair out ?

Shared to IndieNews (maybe) and IndieWeb.xyz.

article

|

Iā€™ve been chipping away at several things over the last two weeks, mostly focussing on markup, presentation, and theme file organisation. I want to get these finalised before I look at theme customisation options. If youā€™ve visited the home page, you might have noticed the display of certain post types has been evolving, as I search for a pleasing balance of information, appearance, and not overwhelming a visitor with a wall of text. I donā€™t think Iā€™m quite there yet, so expect a few more iterations. My current thinking is to treat the home page a bit like an ā€œactivity feed,ā€ where action-type posts such as Likes are displayed in summary manner to give more emphasis to the written posts.

Of course, if youā€™re subscribed to the site RSS or JSON feeds in a reader of some description, youā€™ve probably not seen any difference!

The most challenging issue Iā€™m facing is the markup of posts and other page elements to be compliant with the specs of h-entry, h-card, and the various post kinds such as: Like, Bookmark, Reply, Repost, and so on.

Everytime I think I have the markup nailed down, something comes along to show me itā€™s broken in some way. I liked a post on Aaronā€™s site earlier, and instead of showing as the like I intended it became a regular webmention showing my avatar as a photo, as Iā€™ve clearly messed up the h-card and u-like-of markup in the last round of edits. So sorry to Aaron for mistakenly filling his responses with my face! The Pin13 parser shows the right elements as being present, but IndieWebify.me and Webmention.io both fail to pick them up. Iā€™m guessing itā€™s an issue with how Iā€™ve nested things, and/or some stray classes from previous experiments that Iā€™ve not tidied up? Iā€™ll try to get some time to look into it more tonight.

For other ā€“ minor ā€“ examples, IndieWebring also refuses to pick up my representitive h-card, even though IndieWebify.me tells me I have this setup correctly. Aperture doesnā€™t seem to pick up anything other than my h-card when I use the microformats feed instead of RSS or JSON.

If the markup isnā€™t right then IndieWeb features are unlikely to work correctly ā€“ so fixing this is key for an ā€œIndieWeb integratedā€ theme.

As an aside, and while Iā€™m on the subject of frustrations, Iā€™m having a hell of a time with the Webmentions plugin. Most of the time it feels like they just donā€™t get sent, as I frequently have to manually ping sites (such as with the earlier like post). Thereā€™s a chance this is related to the above markup issues; if the receiving site canā€™t parse the post that mentioned it, it might just throw the mention away? That feels like a bit of a stretch though.

I need to come up with a better way of testing these things, rather than ā€œjust give it a try on here and see if itā€™s worked or notā€¦ā€

But anyway, ā€œKā€ is progressing, even if it sometimes feels like one step forward/two steps back. Iā€™d hoped to have a proper ā€œreleaseā€ ready for some time in February, but at the moment I think March or April are more likely. Iā€™m only getting an hour or two a week to tinker at the moment, and I know Iā€™m going to be busier with other things in February.

Syndicated to Indieweb.xyz and IndieNews (hopefully!)

Updated to add ā€“ IndieNews still doesnā€™t like my site. ā€œError: no_link_foundā€, every time.

reply
|

šŸ’¬ Replied to: State of the Indieweb in WordPress

ā€œAll of these items reflect the coming together and polishing of a complete Indieweb experience. As we move into the end of the first month of 2019, here is what I personally am hoping to see.ā€

This is a nice summary on where things are, and where they might be heading. As someone who has only jumped into the world of ā€œIndieWeb in WordPressā€ at the end of 2018, it helps give me some context.

The idea of giving interested users more choice when it comes to integrated themes is the main reason I have been chipping away at getting my own custom theme ready for release.

As part of that effort, Iā€™ve been working with the IndieWeb ā€œtoolboxā€ of plugins quite closely. If I can free up a bit more free time, then I would love to use that experience to help with improving documentation.

Thanks for all your efforts in 2018, David ā€“ I know Iā€™ve benefitted from them!

article

|

I just had a weird issue where Cloudflare was blocking Bridgy from syndicating posts from my site.

Attempting to syndicate from either my WordPress editor, or the Bridgy user page would result in an error like this:

.

Now, Iā€™ve never consciously set anything to say ā€œdonā€™t let Bridgy access my site,ā€ have few settings turned on, and havenā€™t logged in to Cloudflare in months, so it felt like it mustā€™ve been that some rule update on the Cloudflare side that started flagging the requests as potentially malicious. Unfortunately, Cloudflareā€™s settings are rather opaque ā€“ especially on the free tier. More annoyingly, the ā€œRay IDā€ in the error didnā€™t match anything in the limited logs I do get access to.

But, Iā€™m nothing if not persistentā€¦ after a bit of trial and error ā€“ switching things off and testing again with Bridgy ā€“ and I was able to track down the culprit setting, in the ā€œScrape Shieldā€ section of the control panel, labelled ā€œServer-side Excludesā€:

With this turned off, Bridgy could syndicate my posts again.

Iā€™m starting to wonder if this setting is a contributing factor to the issues Iā€™ve had where Webmentions and associated posts like Replies, Likes, and others seemingly havenā€™t worked? Perhaps someone with more experience with Cloudflare or the various IndieWeb tools could shed some light?

At the very least, I hope this post saves someone a bit of head-scratching if they suddenly find their Bridgy integration stops working.

Shared to IndieWeb.xyz.

bookmark

|

šŸ”– Bookmarked: How to Fix Social Media by Injecting A Chunk of the Blogosphere by Tim Carmody

ā€œNot all hour-long podcasts are worthwhile, but I found this one by The Atlanticā€™s Matt Thompson and Alexis Madrigal to be pretty compelling. The subject: how to fix social media, or rather, how to create a variation on social media that allows you to properly pose the question as to whether or not it can be fixed.ā€

Tim Carmody (kottke.org)

Shared to IndieWeb.xyz.

read

|

šŸ“– Read: Fascist political group plans to infiltrate community councils (The Ferret) by Billy Briggs

ā€œAn extreme far right group modelled on Sir Oswald Mosleyā€™s British Union of Fascists plans to put candidates up for community council seats in Scotland.ā€

Billy Briggs (The Ferret)

I think this quote from the article sums it up well enough:

ā€œā€˜Never againā€™ was the popular slogan after the second world war against fascism. We should never forget that and never give these dangerous idiots an inch.ā€

reply
|

šŸ’¬ Replied to: Grant Richmond: My New Posting Workflow

ā€œJust wanted to say that Iā€™m enjoying the stuff youā€™re sharing on Indieweb.xyz! The ā€˜bootsā€™ quote the other day. A nice contribution to the book quotes sub.

You mentioned having some difficulty with my scraper getting identified as a malicious bot or somethingā€”any idea why I might be triggering Wordpress in that way? I can train it better.ā€

an author ( )

Thanks! I do worry sometimes Iā€™m ā€œthe new guyā€ flooding the site with links every couple of daysā€¦ ? IndieWeb.xyz has been invaluable to me lately, helping me to explore how people are using IndieWeb ideas and tools ā€“ and in giving me some cool stuff to read!

The parsing trouble I was having seems to have been entirely down to the WordFence plugin. It was consistently blocking anything coming from the indieweb.org hosts too. Unfortunately the free version of the plugin doesnā€™t give the best information or options to diagnose/fix issues. As near as I can tell, the issue seems to have been POST requests made with either a missing referrer or user-agent?

Iā€™ve disabled WordFence for now (I think it was overkill for my little site anyway) and most of my issues have disappeared. I have a lingering issue where sending Webmentions is intermittent, but thatā€™s probably user error on my part šŸ™‚

article

|

I had the need to change the status on several hundred wordpress posts by a particular author, from ā€œpublishā€ to ā€œpendingā€ (more on this in a future post). This would have taken me hours to do through the frontend, so I figured Iā€™d make my first serious use of WP-CLI, and script the job.

You can list posts using WP-CLI, and specify which columns to display, and even pass in basic filters, like so wp post list --<column>=value --fields=ID,post_title,post_status,post_author. You can also update posts. By combining these with some shell scripting, big jobs can be done fairly easily.

Easily. Oh, the hubris. The problem I ran into was:

  • The display column names are the names of the columns in the database, so to list the post author, you would refer to it as post_author.
  • The filter column names are as they are referred to in WP_Query, not how they are named in the database.

I didnā€™t catch on to this distinction at first, and the number of rows I was returning was large enough it couldnā€™t display all of them in the terminal. Yes, I should have used less to check. I should have done a lot of things, like take a backup first (wp db export ~/export.sql), but that wouldnā€™t be as good a cautionary tale.

Long story short, I ran wp post list --post_author=3 --fields=ID,post_title,post_status,post_author, saw only the results I expected because some rows were cut-off. When I fed this into a loop which would update the post_status, I ended up setting every post as pending.

wp post list --post_author=3 --format=ids \
| xargs -d ' ' -I % wp post update % --post_status=pending

The correct command should have been

wp post list --author=3 --format=ids \
| xargs -d ' ' -I % wp post update % --post_status=pending

Thankfully, having realised my mistake, I could make use of WP-CLI to fix it:

wp post list --author=2 --format=ids \
| xargs -d ' ' -I % wp post update % --post_status=publish

For everyone following along at home, my mistakes so-far were:

  • Not reading the documentation fully
  • Not taking a backup before altering a live site
  • Not double-checking my test results before running the command ā€œfor realā€

Iā€™ve returned all of the wrongly-pended posts to ā€œpublishā€ status. I do still have an issue with Post-Kinds data being missing on most of these posts; I think this is due to some wierd interaction between WP-CLI and the plugin, but I canā€™t be sure. These posts (~60) Iā€™m going to have to fix by hand ā€” I consider it a reprimand for my earlier flippant approach!

Cross-posted to /en/wordpress.

article

|

Iā€™ve been chipping away at K as time allows over the last week. Itā€™s still a long way from where Iā€™d like it to be, but itā€™s getting thereā€¦

  • All theme files should be compliant with the WordPress Coding Standards, apart from a few instances where Iā€™m planning to rewrite whatā€™s there.
  • Iā€™ve made little tweaks here and there to the markup output by the theme, and plan to revisit this continually. I made a test post to indieweb.xyz, but it didnā€™t quite parse correctly last time. This post should also be submitted ā€“ fingers crossed it goes better this time! Iā€™m also curious if IndieNews posting will be more successful.
  • Files have been refactored (albeit not yet fully reorganised), with a goal of splitting up what was a growing, monolithic functions.php into smaller logical chunks.
  • Iā€™m wrestling with how to handle all of the different kinds of posts the theme will support, from a markup and display point of view. My biggest headache at the moment is the treatment of post titles. I might write another post on this topic.
  • Iā€™ve been working on making plug-in support more optional than I had it at the outset. I make heavy use of Post Kinds and other IndieWeb plug-ins, but donā€™t want the theme to necessarily rely on them.
  • Oh, and the source code is now available on GitHub, in the spirit of ā€œselfdogfoodingā€œ. I came to the realisation there wasnā€™t anything to be gained by holding the code back, and I even ran the risk of never releasing anything if I waited until it was ā€œready.ā€

Iā€™m learning quite a bit through this exercise, which is great. Itā€™s reinvigorated some of my love of code tinkering; Iā€™m finding that some evenings Iā€™m more keen to sit down at a keyboard than I am to sit at my hobby station, which is something thatā€™s not happened in a long time!

Update 09:26 ā€“ IndieNews submission is still failing, unfortunately. Indieweb.xyz seems to be working, but I had to force a Webmention.

note
|

Just had one of the back garden fence panels implode under the high winds, and several others looking like they might go too. Just the thing I needed first thing in the New Year.