manton
manton

Webmention for long or short posts: manton.org

|
…
Embed
dave
dave

@manton I think comments are peers of the posts the are in response to. You see this clearly in social networks, sometimes a comment gets huge interest when the thing it was in reply to was a nothing burger. In my software there is no distinction.

|
…
Embed
manton
manton

@dave The nice thing is every platform can have a slightly different way of handling that, and it’s fine. For a blog that is primarily longer posts, maybe treating posts and responses as peers doesn’t fit as well.

|
…
Embed
downread.bsky.social
downread.bsky.social

@manton I think the actual issue is a hole in the webmention spec. When linking the webmention server from the web page, that link should also contain commenting rules, whether the mentioning post will be republished, and ToS.

I am trying to address these holes (and more) in an RFC for feed-to-feed commenting:

github.com/bigwide-n…

|
…
Embed
manton
manton

@downread.bsky.social Oh, this is really interesting! Thanks for pointing me to it.

|
…
Embed
bax
bax

@manton Honestly, mentions and ping/trackbacks and all that W3C stuff are things I wish there was a “modern blogging 101” explainer of sorts on.

I still get turned around on the “right way” to micro.blog, as I’m not sure I’ve quite mastered making sure my configuration is set up to have a hope of visibility (which on some level, is what keeps me mostly in the walled gardens where I’m not starting from 0 on)

Maybe there’s no “right way” but even trying to decide whether to link an existing Mastodon or use the instance here is not always clear to the pros and cons of either.

|
…
Embed
In reply to
manton
manton

@bax It is confusing because there are a few ways to do things. I should write up how I personally use it, because I think that’s the “best” way — no separate Mastodon, cross-posting to Bluesky and Threads only — but I don’t think other ways are necessarily wrong. Which I know is sending mixed messages. 🙂

|
…
Embed