6 ms·

Eh, 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 servi

Eh, 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 ago
The 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 ago
  If 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.
  - epeus 7y ago
    There is of course a WordPress plugin for webmentions https://en-gb.wordpress.org/plugins/webmention/ https://en-gb.wordpress.org/plugins/webmention/
- CarelessExpert 7y ago
  Sorry, I updated my post with a bit of implementation detail. http://webmention.io http://webmention.io, which is a standard web service running separately from the blog itself, receives webmentions for me (it's a hosted service, though you can also self-host). A Jekyll plugin pulls them down on site build, which I run periodically on a schedule.
  - superkuh 7y ago
    Ah, thanks. But that kind of proves my point re: webmentions. The whole indieweb thing is suppose to be independent. Webmention's implementation complexity pushes people back to third party centralized services, or, vastly increased attack surface and maintenance on their own setup.
    - CarelessExpert 7y ago
      Yeah. That's why I said I could host it myself if I wanted, in a container separate and isolated from my blog. I'm just too lazy to bother. This is gonna be the case no matter how the content is passed in the request (I.e. url vs form encoding). It's dynamic content. What is your proposed solution for supporting dynamic content on a static site that doesn't involve running some kind of service on the side?
      - superkuh 7y ago
        It's not so much not running a service as not running any more services that are receiving connections of any kind from the 'net. I trust nginx. I don't trust some webmentions specific script or program. I implemented my website's (see profile) comment system based on a tiny perl script that tails the logs from my webserver. It's completely separate and no internet user is connecting to it. Any URL, followed by the string "/@say/" like, "http://what.ever/something.html/@say/Neat http://what.ever/something.html/@say/Neat something" is added to the comment page.
        CarelessExpert 7y ago
        That's a distinction without a difference. What you've done is made the webserver a blanket endpoint, where the "API" and the "database" are your web server log files. Practically speaking, what you have is a CGI script with a non-standard interface to the server. It's still subject to any bugs in your perl script, since you're still processing input from an untrusted location. It's certainly clever, though!

superkuh 7y ago

The 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 ago
If 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.
- epeus 7y ago
  There is of course a WordPress plugin for webmentions https://en-gb.wordpress.org/plugins/webmention/ https://en-gb.wordpress.org/plugins/webmention/
CarelessExpert 7y ago
Sorry, I updated my post with a bit of implementation detail. http://webmention.io http://webmention.io, which is a standard web service running separately from the blog itself, receives webmentions for me (it's a hosted service, though you can also self-host). A Jekyll plugin pulls them down on site build, which I run periodically on a schedule.
- superkuh 7y ago
  Ah, thanks. But that kind of proves my point re: webmentions. The whole indieweb thing is suppose to be independent. Webmention's implementation complexity pushes people back to third party centralized services, or, vastly increased attack surface and maintenance on their own setup.
  - CarelessExpert 7y ago
    Yeah. That's why I said I could host it myself if I wanted, in a container separate and isolated from my blog. I'm just too lazy to bother. This is gonna be the case no matter how the content is passed in the request (I.e. url vs form encoding). It's dynamic content. What is your proposed solution for supporting dynamic content on a static site that doesn't involve running some kind of service on the side?
    - superkuh 7y ago
      It's not so much not running a service as not running any more services that are receiving connections of any kind from the 'net. I trust nginx. I don't trust some webmentions specific script or program. I implemented my website's (see profile) comment system based on a tiny perl script that tails the logs from my webserver. It's completely separate and no internet user is connecting to it. Any URL, followed by the string "/@say/" like, "http://what.ever/something.html/@say/Neat http://what.ever/something.html/@say/Neat something" is added to the comment page.
      - CarelessExpert 7y ago
        That's a distinction without a difference. What you've done is made the webserver a blanket endpoint, where the "API" and the "database" are your web server log files. Practically speaking, what you have is a CGI script with a non-standard interface to the server. It's still subject to any bugs in your perl script, since you're still processing input from an untrusted location. It's certainly clever, though!