@KevinMarks @jalcine like the easy way to implement it would be to just send out a mention any time the content file gets indexed and to send any incoming mention to an email address but that would get real spammy real quick. But I want to avoid making a persistent database or filesystem important since that opens up a bunch of deployment opportunities and simplifies migration.
@KevinMarks @jalcine and the reason I was looking at bridgy was because it seemed like they provided an endpoint to use with disqus (which is already what I use on my website) but its documentation seems to focus on one-click install for existing hosted services and isn’t immediately obvious how to integrate it into a new bit of software.
@KevinMarks so hey, with the h-card microformat, is there a way to either specify "get this from another URL" or to put it onto elements that won't be visible on text-only/non-CSS browsers? I still try to make my sites work reasonably well in lynx and w3m :)
@fluffy does display:none work in lynx? You can use abbr or data elements to create hidden attributes, but it's preferred to use visible ones if possible. There is also the indieweb authorship model so you don't need to put a full h-card on every post. https://indieweb.org/authorship. Also https://indieweb.org/representative_h-card for when you have multiple, but one is key.
@KevinMarks lynx doesn’t even know what CSS is.
I’ll check the authorship model, thanks! Wish I’d found that in any of the indieweb things, before I’d plumbed all my hcard junk through my templates. :)
@KevinMarks okay wow that is confusing as heck. Can’t I just declare an appropriate <link rel> to an XML doc and call it a day?
@KevinMarks also I wish the expectation weren’t that I both put a friggun author avatar everywhere and that it be declared with an <img>. There’s just so much shoehorning happening here under the guise of “simplicity” and I’m not liking it. :/
A silly instance of Mastodon for queer folk and non-queer folk alike. Let's be friends!