Aaron Parecki

It's true that not all webmention targets are HTML documents. Because of this, I think it's reasonable to clarify the text, changing

> The sender MUST fetch the target URL (and follow redirects [FETCH]) and check for an HTTP Link header [RFC5988] with a rel value of `webmention`, or an HTML `<link>` or `<a>` element with a rel value of `webmention`.

to

> The sender MUST fetch the target URL (and follow redirects [FETCH]) and check for an HTTP Link header [RFC5988] with a rel value of `webmention`, and if the content-type of the target URL is HTML, the sender MUST also check for an HTML `<link>` or `<a>` element with a rel value of `webmention`.

Requiring all senders to check for the HTTP `Link` header provides the largest opportunity for interop among implementations, since it's possible to publish a Link header regardless of content type.

If you have specific examples of wanting to advertise a webmention endpoint in a non-HTML document, please document them and suggest a (as you said) "standards-compliant way" of advertising the endpoint in the document.

I'm just going to point back to what @sandhawke said:

> Abandoning your early adopters before establishing a new user base means you have nobody.

The time to suggest a 100% breaking change to the spec has long passed. There is already a lot of written and deployed code that sends webmentions using form-encoded syntax. It's not a matter of simply making a "tiny" change to switch to JSON, since it will affect senders as well as receivers, some of which are using libraries on both sides, not to mention the fact that this software is deployed quite widely and in places where a single person can't even mandate that it be updated. Such is the situation when a spec gets widely implemented.

@rrmutt You can sign up for the weekly newsletter! https://indiewebcamp.com/this-week

@obensource Speaking of audio, are you free tonight? It'd be great to see you at this! https://www.eventbrite.com/e/xoxo-podcast-studio-visioning-workshop-tickets-25070419299

@obensource @denormalize Perfect! This will be a good chance to test out my new bike-sized recording rig!

@denormalize Sure thing! Who should I get in touch with to coordinate?

ugh I just did this today (the first time this year) and it was way too confusing

@hmans Please do! Would love to hear more feedback. Also see https://indiewebcamp.com/generations for some more thoughts on this.

@hmans We're well aware, and would appreciate any help making it more accessible! It is a wiki after all! #indiewebcamp

so what you're saying is you only know the good parts of PHP?

Most people probably don't know you made silo.pub ;-) You could always share that.

@calum_ryan Very cool! My site shows weather in the header right now, but it's been a TODO forever to show that per post! Can't wait to see!

@SprocketPodcast Does this mean it's time for another live episode for #300? 🎥😄🎙

hah yeah... you'll get the hang of it :-) If you really want to get thrown for a loop, try using a Windows keyboard on your mac.

Yeah, having never eaten meat before, I don't know what the fake meat products are trying to imitate, so they aren't really appealing.

I have always been a vegetarian and I don't see why anyone would want to eat fake meat.

cmd is for everything you used to use ctrl on Windows for. ctrl is for things you used ctrl on UNIX for.

There's always :facepalm:

@webrocker @jkphl @iwontsignuphere Teespring should take care of all the shipping/tax so you should try! If it doesn't, we can do a new one

@m_ott Thanks! Bookmarking that one for sure!