Kind replies

 Reply

Ooh nice! I've been using https://github.com/PlaidWeb/webmention.js for my client-side webmentions and have found it really nice ☺

 Reply

I'd recommend publishing to your own site first, and then sharing links to it on sites such as Twitter and https://lobste.rs, and maybe also sharing on https://dev.to but primarily owning it yourself to build up the followers there

 Reply

Sorry to hear that - I think part of it is due to my feed including most things on my site, which I need to fix at some point - if you want to just subscribe to my blog posts, https://www.jvt.me/posts/feed.xml should do it for now!

 Reply

Ah no - since getting involved in the #IndieWeb I've been trying to use my site as the owner for my content, wherever it's for, and then pushing it out to silos after

 Reply

In terms of how I get the data? I publish content to my site first, then syndicate it elsewhere afterwards https://indieweb.org/POSSE - which mostly happens automagically

I do this even for things like https://lobste.rs which doesn't have an API so I manually post it with a link back to the comment on my site

 Reply

Can you not just swap out the Desktop Environment you're using without swapping distro?

 Reply

I'm not sure I agree. Speaking about your health allows everyone to be a bit more open about everything - one reason I blogged about my ruptured appendix was that it would show others what I'd gone through, what they could learn from it, and understand just how sucky it was for me.

Additionally, speaking about mental health is incredibly important, as most folks suffer from it, just don't talk about it, and awareness of it can help folks get diagnosis / help if they're not aware of it.

 Reply

I don't think so no. I've done this on my Micropub side, so it stores it in the same content format as the actual post. I guess we'd likely do something similar, or when loading the page pulling that data from Granary?

 Reply

It's the MF2-JSON that Granary provides, I store that as-is, then render it as I need to 👍🏽

 Reply

I'd gone in 2017 but not 2018, then went in 2019 and felt pretty uncomfortable as a half Indian man. After being so used to diverse and inclusive spaces it was incredibly jarring, so I'm sorry for how worse it would've been for you!

 Reply

I like that with Jeremy Keith auto saves any link from his site to archive.org. So even if the link itself is broken, it should be possible to find it there.

I like the idea of the site itself trying to fix it.

For some time I had my site fail to build if any broken links were found, but as I interact with more sites, and push more content daily, it's a bit difficult to do that.

 Reply

As shared in a separate comment in the thread, there's the Microformats2 specification (see https://microformats.io) which reduces duplication seen with some of the other Semantic Web formats.

You can see an example of a parsing result at http://php.microformats.io/?url=https%3A%2F%2Fwww.jvt.me%2Fmf2%2F2020%2F01%2F2mylg%2F which produces a standardised structure for the resulting JSON, which makes interconnectivity much simpler.

Us folks in the IndieWeb (https://indieweb.org) have been using it for some time with great benefit, but it's always great to hear others reactions too!

 Reply

Re:

TLDR: Nearly everyone who wants micropub support writes their own library, endpoint, or whole cms or blog engine.

I believe part of this is because Micropub requires intimate knowledge of how your own site is set up, so unfortunately can't be written as a generic solution, because most folks won't have things set up the same way, even on ie WordPress using common IndieWeb plugins

It's still a good point that maybe we need to look at creating an out-of-the-box Micropub endpoint for some of the common tech stacks.