[tantek]the MS one is dead. they've taken down all their references to it from MSDN, and even the archived version has scant information (none) about what is required from the client
gRegorMy webmention plugin implements it if I require the vouch parameter, tested in theory years ago, but I don't have vouch required for webmentions since no one supports sending them really
LoqiWebSub is an open standard (W3C Recommendation) notification-based protocol for web publishing and subscribing to streams and legacy feed files in real time, previously known as PubSubHubbub or PuSH, and briefly PubSub https://indieweb.org/WebSub
LoqiSuperfeedr provides a variety of ways to access real-time feed updates, including a popular PubSubHubbub-0.4 compliant hub https://indieweb.org/Superfeedr
[jacky]but I'm wondering more about public feeds, I could see the case for emitting updates for unlisted posts over WebSub but if it's public then it'd be in the feed itself as well (be it RSS or not)
gRegorIt seems we'd need to run our own hub with an extra layer on it. I didn't see (on the wiki at least) to approve or deny subscribers at the hub level
[snarfed]re Superfeedr, I talked with Julien recently. short answer, he's still maintaining and running it, but only minimally. it's fading, not growing.
Loqi[preview] [snarfed] Superfeedr is unreliable these days, and I'm not confident in its future. Looking into alternatives and their pricing. Many charge per feed, which I don't think is sustainable for BF. Some charge per notification, which is better. IFTTT and Botize ar...
LoqiA portfolio on the Indieweb is a professional web page (or collection thereof) targeted at paying customers/clients that often shows examples of work and projects https://indieweb.org/portfolio
GWGIt occurs to me this isn't just a WordPress question. https://github.com/pfefferle/wordpress-webmention/issues/444 - [snarfed] originally wrote about it in here. So...a post is updated and webmentions are sent to all responses to the post, which were originally received by webmention. How should the webmention receiver act when such a mention is received? In the example, the mention is in the
GWGaaronpk I believe, noted it is because of Salmentions. But the salmention protocol says when it receives a webmention, it would resend to the original post sent webmentions to. But in this case, the original post never sent a webmention, this is a markup of a received webmention.
GWGThat doesn't apply here, but it could for a comment. Someone could reply to the response version on the original post of your comment, which should send you a webmention
GWGIf receiving a webmention in this manner, it could be assumed to consider it an update of the original post, to which you might want to change your like.
GWGRight now, RSVPs are u-in-reply-to, which are marked up on the receiving URL as u-comment h-cite. So, the simplest solution is u-comment h-cite with a p-rsvp inside is a displayed RSVP, but that seems confusing.
[tantek]Fascinating, so when I update my past 100daysofindieweb posts to link to the next post, then everyone who liked or shared the previous post gets a notification presumably, and if they have a way of looking at the diff, they might see the link to the new post!
GWG"If a response to the source URL is shown on the source URL page (e.g. as a comment), then sender SHOULD treat that as an update of the source URL and re-send any previously sent Webmentions."
GWG"This allows the recipients of Webmentions to update their display of the source document, or otherwise notify the recipient that a post that mentioned one of their URLs was updated."
[snarfed]the challenge I've been working on for BF's front page design is, right now it's very specifically aimed at IndieWeb people who want to federate their web sites into the fediverse
[snarfed]but I'm expanding BF to be more general purpose and multi-protocol, ie for fediverse users as well as IndieWeb, soon for Bluesky users too, etc.
[snarfed]"advanced setup" instructions for current features like using your own domain as your fediverse handle instance will probably get demoted to the docs
[snarfed]seems like it's the cross product of all supported networks? ie right now web => fediverse and fediverse => web. bluesky will add web => bluesky, bluesky => web, fediverse => bluesky, fediverse => web. and so on
[tantek]"I'm on" vertical column of labels on the left, from which to pick a row, and then "I want to federate with" horizontal row of labels on top, from which to pick a column
[snarfed]I'm just not sure I want to put a literal table on the front page. feels a lot to hit someone with when they first come to the site and don't fully know what it is
[tantek]I'm saying you have a 4x4 logical grid of options (with the diagonal being a link to intra-system federation docs), and there is a broad aesthetic appeal of "block" diagrams like that where the blocks are all the same shape/size
[snarfed]I'm still not sure how well that kind of grid would work for non-technical users as the main, above-the-fold home page element, but I'll definitely try it out
[tantek]little did we know when we made the microformats blocks illustration like that with orange blocks, that IndieWeb would use orange as a key color in its logo and aesthetic!
[tantek]and gray for nostr seems fine since they've chosen black with a thin light blue strip for the icon on their GitHub (and two blues might be confusing) https://github.com/nostr-protocol/nostr
Loqi 449 is an HTTP status code used by Microsoft to mean "Retry With" that is also used for webmention with vouch https://indieweb.org/449
gRegor But it sounds like this part is where the approval would come in? https://indieweb.org/How_to_publish_and_consume_WebSub#How_to_Subscribe
[snarfed] personally I've seen it gradually become more unreliable over the years, so I'm not currently planning to use it in anything new. here's a bit of my initial research on alternatives: https://github.com/snarfed/bridgy-fed/issues/550#issuecomment-1841605025
petermolnar what is portfolio
GWG It occurs to me this isn't just a WordPress question. https://github.com/pfefferle/wordpress-webmention/issues/444 - [snarfed] originally wrote about it in here. So...a post is updated and webmentions are sent to all responses to the post, which were originally received by webmention. How should the webmention receiver act when such a mention is received? In the example, the mention is in the
[pfefferle] will you file a PR for it [dshanske]?
[jacky] might be cool for those who have forms that want to persist things client-side https://darn.es/storage-form-web-component/
[KevinMarks] Mastodon sends a notification when a post you liked or shared is edited
[aciccarello] That makes sense. I was wondering how the current bridgy vs bridgy-fed selector will fit into the redesign.
[tantek] [snarfed] I will point out the blocks aesthetic at https://blueskyweb.org/ and at https://microformats.org/wiki/about are very much already a "thing" in this space, and perhaps would work well in reference