Loqi[Sean Tilley] @KitRedgrave Good read, but it kind of ends on the note of "only our stuff will solve the problem", which illustrates the very pattern they are describing....
ajordanI certainly am interested in pump.io becoming less of a monoculture but it's also worth noting that at a certain point interop comes with real maintenance costs
ajordane.g. a couple weeks ago I accepted a patch adding mf2 classes to all posts in the web UI (yay!) but I wouldn't take patches for e.g. Webmention. because it adds complexity
tantekAs aaronpk put it, you get incremental benefit from sending and/or receiving (by design) which has allowed implementations to do so incrementally as they have time to do so
tantekfor Webmention in particular, since that was developed in this working group (and both Evan and I are co-chairs, so I would hope that indicates some degree of approval / support for all our efforts here), consider...
tantekstart with just implementing Webmention sending for links and mentions in posts. that part is very straightforward and there are libraries that implement the key bits in various languages
tantekhappy to help with any questions with how to do that (I've implemented webmention sending myself, including publishing an open source PHP library to help with webmention endpoint discovery)
tantekodd thing I just noticed about Mastodon instances, different from early twitter: no obvious public timeline on instance homepage! nor on about or linked therefrom!
ajordan!tell tantek yeah, I was thinking about this last night and I've changed my mind to be tentatively in favor of at least sending Webmentions, subject to Evan's approval. it's just so simple