4 ms·
Webmention: Simple web standard to notify any URL when mentioned across the web
- CarelessExpert 7y agoAlso Microformats: http://microformats.org/ http://microformats.org/ And micropub: https://indieweb.org/Micropub https://indieweb.org/Micropub Webmention + microformats + micropub = distributed social comments, likes, reshares, etc, with blogs.
- corybrown 7y ago15+ years later, we will try to standardize something that's barely used anymore > This is a similar "Linkback" mechanism to the ones of Refback, Trackback, and Pingback. It uses a different protocol, though, and thus should be discoverable through its own link relation type.
- deleted 7y ago[deleted]
- miohtama 7y agoPingbacks, during the WordPress glory era, where killed by spam. Everything that is unauthenticated or weakly authenticated messaging without centralised censors will turn to a spam channel. How do new protocols avoid this?
- CarelessExpert 7y agoAt minimum Webmention requires the originating site to be hosting content that actually references the mentioned page. Spammers would then have to host the location where the spam is located, and then you can block them. But, frankly, this isn't actually a solved problem yet. I'd imagine building a spam blocking engine on top of a service like webmention.io is an obvious next step if/when this becomes an issue.
- deleted 7y ago[deleted]
- superkuh 7y agoWhen I heard about indieweb I implemented h-entry stuff for my blog but half-way through doing webmentions I realized it sucked. Webmentions requires receiving x-www-form-urlencoded data. Why they chose this convoluted and complexity increasing way is beyond me. Embedding (or encoding) it in the URL string itself would've been infinitely easier for everyone with no downsides. But no, with x-www-form-urlencoded variables you need to actually be doing some dynamic scripting to handle it. If not actually some script listening for that location/endpoint then at least a series of complex nginx directives and modules to get x-www-form-urlencoded logged with all the rest of the request. This additional complexity makes running a static website that supports indieweb standards like a tail wagging the dog in terms of the webmentions receiver's relation to the static http site. microformats2 h-entry markup is cool though. Just using class names for html elements to make some info parsing "standardized".
- CarelessExpert 7y agoEh, I'm having no trouble supporting webmentions with Jekyll (using webmention.io and a plugin). Yeah, it's a bit annoying having to integrate with a web service, but it's not that big of a deal. And bluntly: most people running blogs aren't using a static site generator, anyway, so it really doesn't matter that much.
- superkuh 7y agoThe kind of people that care about indieweb are exactly the kind of people running self hosted static websites with blogs. Few on blogspot or wordpress are going to care. Anyway, how did you manage to receive webmentions and set up an enpoint? Are you passing it off to some dynamic scripting language to handle?
- CarelessExpert 7y agoIf that's true then the whole exercise is pointless (which, I guess, is a valid claim). WordPress dominates the blogging world. Jekyll, Hugo, etc, are drops in the bucket by comparison. Winning that market over is absolutely required if Webmention is gonna gain any level of adoption.
- dredds 7y ago3 links to 3 docs all with the same title, so requires typing to save them. W3C "standards".. cough.