cmalI haven't tried XMPP social-networking lately, but last time I tried it was working well, even in between different clients (MOVIM <--> Salut á Toi)
aaronpkthe services my site uses are: webmention sending, webmention receiving, map generation, timezone lookup, GPS and weather logs, avatar caching, and a pubsubhubbub hub
cmalvoxpelli: when I say CMS I don't necessarily mean a centralized thingie doing everything, I mean "content managing system" as in something articulating other things so you can actually publish and read stuff :)
voxpelliEven WordPress is kind of moving to where they have client, datastore and rendering be three separate things. They have a node.js based editor and many build their sites on top of wordpress data API:s rather than WordPress themes
petermolnarvoxpelli I'm trying to move away from WordPress, also step by step; which means I'm first fixing the theme by making it (properly) twig based, removing all the WP funk from it; meanwhile moving the webmention endpoint to a service of it's own
petermolnarGWG the best setup would probably be: 1, a pubsub server, which then scrapes the content and sends all the required mentions; 2, a pluggable "forwarder" which would store/forward incoming mentions; in my case, this latter will most probably be webmention -> email
voxpelliI have a webmention endpoint one can use, as do aaronpk – and aaronpk along with some other people have services for sending webmentions as well, think aaronpk's uses PuSH-based feeds
aaronpkthe way mine works with my site is webmention.io does all the verification, then sends a POST request to my site with the verified and extracted comment text
GWGBut considering people's concern with pingbacks on WordPress, if I could write something that interfaced to webmention.io or other handlers, I probably would write it as an optional extension to the existing plugin.
voxpelliregarding u-comment issue, in the u-responses pages I added to make my comments curlable I therefore had to add the comments as top-level h-entries instead, but hard for micropub endpoint to know whether a h-entry is a received comment or a new post if one would push them both in as entries :P
LoqiPubSubHubbub (PuSH) is a notification-based protocol for publishing and subscribing to streams and legacy feed files in real time https://indieweb.org/PubSubHubbub
miklbneat. The reason I switched as more because the jekyll plugin I use for webmention.io creates a cache file so I have a static backup of the mentions. That would solve that even better. Was thinking about that possibility when I saw this https://github.com/eduardoboucas/staticman
aaronpkthe target URL is always going to be somewhere else in the payload too, but it's easier to handle if you always have it in the same place in the request
voxpelliu-source? (the target could perhaps be mp-webmention-target still, as it will be in the data anyhow, but just easier for the endpoint to have it as a clear instruction)
voxpellithe discussion basically was that it's impossible to find the source mf2 of a comment as it will point to twitter in it's u-url rather than Bridgy and thus a Salmention client can't find the true source for any received comment and thus data quality will deteriorate for each step up the lake
voxpelliKevinMarks: indeed, and it's fairly similar to Jekyll in the format of its post, so I would want to look into supporting Hugo in addition to Jekyll for my micropub endpoint
voxpellito me it doesn't matter that Jekyll is Ruby as I just use it as a tool that I run and with Hugo it matters even less that it's Go as it just gets compiled to an executable
bearruby (for me) is so painful now I have been recommending to people that if they want Jekyll to use either the NodeJS version or to use Pelican (a python tool that does the same thing)
voxpellimain problem I've seen so far is that very few, including Hugo, seems to support the Liquid templates and to me Liquid is a very big part of jekyll
bearthat is part of my refactoring process after I'm happy with a static site's flow -- anything in the templates that could be done as part of the code
KevinMarks_I had another project where I started using jinja macros, and then a front end guy got involved and managed to turn them into a huge nested set of spaghetti calls