Archive of: Tag: indieweb


Reply To: 👓 Launching #IndieWeb Textpattern | Chris McLeod

“This is awesome news. I’ve started a stub page on the IndieWeb wiki that hopefully folks will be able to add to in the future.

Perhaps the quickest start for getting Webmention working is to use Webmention.io and have people add the appropriate headers. Then you can build or set up methods to either show that data directly or build a full endpoint.

Good luck!”


Thanks Chris!

Webmention.io is definitely my plan for adding webmentions initially, and will probably be the step 3 article (IndieAuth is step 2 and being drafted right now).

If, or rather, when I look into writing a plugin to send webmentions I might bring receiving into it as well… but the more I look into Webmention.io, the more I think I’ll just keep things simple by having it continue to handle all of the receiving.

Thanks for adding the wiki page – I’ll be sure to add links and other information as I finish writing it up!



Launching #IndieWeb Textpattern

I noted the other day that Textpattern might be a good fit for some people trying to build their own websites, but that there wasn’t much in the way of resources to get them plugged into the IndieWeb.

Well, I went and started to do something about that. TextPattern is a site where I will be exploring and documenting how to add various IndieWeb building-blocks to their Textpattern website. There’s not a whole lot of stuff there yet: just the mission statement, and how to add an h-card using form templates; but my intent is for the site to grow into a kind of guidebook for interested parties to be pointed to from the IndieWeb wiki and elsewhere. I was inspired by the short series of posts Gary put together about Blogger recently.

It’s been years since I last used Textpattern — possibly more than a decade(!) — so there will have to be a lot of experimenting and exploration before I figure out everything that will be needed. I want to get the “quick wins” out of the way at the start, then at some point I anticipate having to write new code as part of this project… hopefully just as Textpattern plugins, but there might be some features which need a “bridge” service to get working. I mention in the introductory post some of the areas where I think I’m going to have to write code, but for now, those are all later concerns 😅

In the more immediate future, my planned content includes: getting a site ready for IndieAuth, adding microformats to post templates, receiving WebMentions, and possibly implementing post kinds in a manual capacity. If you have any suggestions at all for the site or topics, please do let me know!



Now I’ve found a groove on Twitter I’m comfortable with, I think it’s ok for me to slightly expand my following circles to include a couple of extra topics I’m interested in. First up is the



Textpattern

Once upon a time I was heavily involved with the Textpattern community, but I haven’t used or kept track of TXP for several years now. It randomly popped into my head over lunch that Textpattern originally had an ethos which aligned really well with IndieWeb ideals.

It had a plugin system for extending the core, could define custom metadata, override how to display particular articles, and it was also easy to modify themes to add things like microformats/special meta tages, etc. Looking back, it sounds ideal for some users?

I could only find a passing mention in the IndieWeb wiki. If I find the time, I might explore and document setting up an IndieWeb-integrated site using Textpattern.



So I think I’ve finally got things setup properly, where I can tweet from my website, have any replies and likes show up on my website (after moderation), *and* have the website original linked from the tweet by a custom shortlink.



I need to take a break from the merry-go-round of mf2/parser compatibility. I excitedly thought it was fixed. But it wasn’t. I’ve made some further changes, and it might be fixed, but there’s a good chance it’s still broken in some obscure way… IndieWebify.me refuses to recognise my Like and Bookmark posts properly, even though every other parser I throw at example URLs comes back fine? Last I checked, IndieNews still refuses to return anything but “error: no link found.” Update: something I did today must have fixed this… I fixed a typo in an earlier post, and suddenly it was on IndieNews 🤷‍♂️

It’s getting a bit stressful, to be honest, and that’s means it’s time to move on to another task before it burns me out on the whole project. I’ll come back to it again in a while, hopefully have a break-through and iron out the kinks.

In better news, I do have some custom gallery markup up and running, and the h-card in the sidebar is now a fully-fledged widget. Baby steps…



“K” Theme MF2 Markup Update

(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.



“K” Theme Update 24-Jan-2019

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.



Experiences with Cloudflare blocking Bridgy

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.