webmention.js updated

Comments

The fact that yesterday’s intent post ended up changing URLs (because I’d inadvertently titled it for 2020 instead of 2019) made it so that it made sense to finally add support for multiple incoming webmention target URLs. So I added this to webmention.js, and also to the sample beesbuzz.biz templates. So now I can slurp up arbitrarily many target URLs' mentions on any given page.

Incidentally, yesterday I ended up releasing a new version of Pushl which also has to do with URL updates. Gee, I wonder why these things both came up in such close proximity.

So anyway this is two IndieWeb-focused things in as many days and they aren’t even things I was intending to work on. But low-hanging fruit is just as tasty.

My IndieWeb Challenge 2019 aspirations

Comments

The IndieWeb community has an annual daily improvement challenge. Jacky posted his aspirations so I figured I’d post some of mine too.

I don’t plan on actually releasing everything every day (speaking of which I’m glad Novembeat 2019 is finally over with, holy heck!) but I definitely have things I want to get done this month.

Read more…

WebSub support update

Comments

Almost exactly one year ago, I wrote about the state of WebSub support in feed readers. I’ve noticed a few incoming mentions from folks citing it as definitive (when that was never my intention), and so I decided to check to see if things have changed. I’m happy to say that it has!

Read more…

💬 Re: Intelligent webmention sending Notes

Comments

In reply to: Re: Intelligent webmention sending

FWIW, Pushl also handles incremental webmention updates, including support for removals of targets and deletions of articles. Right now the only thing I feel like it’s missing for most IndieWeb folks is h-feed support, which should be fairly easy to add (I just need to get around to it).

It also could do with some better retry logic (namely saving failures in a queue for next time), which is also On The List.

Stop calling .org non-profit!

Comments

Yes, it sucks that the registry behind the .org gTLD has been sold to a for-profit corporation. But this article, and many others like it, keep on propagating a really messy misconception which I feel has done active harm:

The decision shocked the internet industry, not least because the .org registry has always been operated on a non-profit basis and has actively marketed itself as such. The suffix “org” on an internet address – and there are over 10 million of them – has become synonymous with non-profit organizations.

The Register is at least being careful to be technically correct1 here, in that the registrar is non-profit and has “become synonymous” with non-profit organizations. But the .org gTLD was never intended to be for non-profit organizations. In the original RFC, the intention was that the gTLDs were:

  • .gov: for government institutions
  • .edu: for educational institutions
  • .com: for commercial enterprises
  • .mil: for military use
  • .org: for everything else; the “org” was short for “organizational” as in “we don’t know where else to put it for now”

This was also when .net was created (despite not being in the RFC), referring to network services and infrastructure providers.

Read more…