home.social

#webmention — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #webmention, aggregated by home.social.

  1. ✍️ New post: Buckle Up

    I recently added a “Failed Webmentions” view to my Craft CMS #Webmention plugin. Opened it before #IndieWebCamp Düsseldorf and found line after line of automated probing. Just shipped v1.3.0 to deal with it and wrote a bit about it:

    matthiasott.com/notes/buckle-up

  2. Naty @eclecticpassions ·

    025 is out (not as late as last week)!
    2026: Week 17/52 (Apr 20 – Apr 26)

    ➡️ burgeonlab.com/weeknotes/2026/

    Some site updates, adding a digest section, streamlined link roundup creation and a sneak peek at my remote participation!

    This is post 35 of
    📈 burgeonlab.com/tags/100daystoo

  3. /RSVP pages – an indie idea

    You’ve heard of /now pages and maybe even /me pages. I’d like to present to you another idea – /RSVP pages (or /rsvp if lower casing matters to you).

    RSVP is short for the French phrase “Répondez s’il vous plaît”, meaning “please respond” (literally “respond if it pleases you”). RSVP is most common on invitations where the host wants to know numbers. But I think it applies here too.

    The purpose of this page is to list articles, posts, or other content with a WebMention endpoint attached. They indicate pages that you are specifically inviting people to reply to.

    This allows for the discovery of mentionable content that is, according to you, good for replying to. Open-ended questions come to mind.

    I’ve used an RSVP tag for mine. I added a redirect so node.lordmatt.co.uk/RSVP also takes you there.

    #French #RSVP #stealThisIdea #WebMention

  4. I am trying to set up webmentions for my blog but it seems cloudflare pages is blocking brid.gy and webmentions.io. I'm searching for a way to disable it in their dashboard but no luck so far. How do I fix this issue?

    #bridgy #webmention #cloudflare #cloudflarepages #indieweb
  5. 🎉 Eight years ago today, the #IndieWeb Webmention protocol was published as a W3C REC https://www.w3.org/TR/webmention/

    As a social web building block, #Webmention was designed to work with various other building blocks. Small pieces, loosely joined. Every year developers find new ways to work with Webmention, and new subtleties when combined with other building blocks.

    The primary uses of Webmention, peer-to-peer comments, likes, and other responses across web sites, have long presented an interesting challenge with the incorporation and display of external content originally from one site (the Webmention sender), on another site (the Webmention receiver).

    There are multiple considerations to keep in mind when displaying such external content.

    Two examples of external content are images (e.g. people’s icons or profile images from the author of a comment) and text (e.g. people’s names or the text of their comments).

    For external images, rather than displaying them in full fidelity, you may want to compress them into a smaller resolution for how your site displays the profile images of comment authors.

    If you accept Webmentions from arbitrary sources, there’s no telling what might show up in author images. You may want to pixelate images from unknown or novel sources into say 3x3 pixel grids of color (or grayscale) averages to make them uniquely identifiable while blurring any undesirable graphics beyond recognition.

    For external text, one thing we discovered in recent IndieWeb chat¹ is that someone’s comment (or in this case their name) can contain Unicode directional formatting characters, e.g. for displaying an Arabic or Hebrew name right-to-left. Text with such formatting characters can errantly impact the direction of adjacent text.

    Fortunately there is a CSS property, 'unicode-bidi', that can be used to directionally isolate such external text. Thus when you embed text that was parsed from a received Webmention, possibly with formatting characters, you have to wrap it in an HTML element (a span will do if you have not already wrapped it) with that CSS property. E.g.:

    <span style="unicode-bidi: isolate;">parsed text here</span>

    Though even better would be use of a generic HTML class name indicating the semantic:

    <span class="external-text">parsed text here</span>

    and then a CSS rule in your style sheet to add that property (and any others you want for external text)

    .external-text { unicode-bidi: isolate; }

    Previously: https://tantek.com/2023/012/t1/six-years-webmention-w3c


    This is post 7 of #100PostsOfIndieWeb. #100Posts #socialWeb #openSocialWeb

    https://tantek.com/2025/004/t1/micro-one-onramp-open-social-web
    → 🔮


    Glossary

    HTML class name
      https://tantek.com/2012/353/b1/why-html-classes-css-class-selectors
    IndieWeb chat
      https://indieweb.org/discuss
    pixelate
      https://indieweb.org/pixelated
    small pieces, loosely joined
      https://www.smallpieces.com/
    Unicode directional formatting characters
      https://en.wikipedia.org/wiki/Bidirectional_text#Explicit_formatting
    unicode-bidi CSS property
      https://developer.mozilla.org/en-US/docs/Web/CSS/unicode-bidi  


    References

    ¹ https://chat.indieweb.org/dev/2025-01-05#t1736092889120900

  6. @point5a @Vivaldi @johnbeen So, I happened to get my #VivaldiMail address, after all. I previously did it, but I still need to set it up in on my #MacBook app for downloading. Meanwhile, I also now have a secondary #Mastodon account at #VivaldiSocial.
    I have also been completing my #Fediverse, #Mastodon, #BlueSky, and other connections at #WordPress, thanks to #ActivityPub, #Jetpack, #Webfinger, #Friends, #Hum, #Webmention, and other #plugins. Thanks also to people like @pfefferle and many others who have been making these plugin applications happen over the years. Big improvements! Almost there in my setup… getting better everyday. I’ve been incredibly productive, and on the way! Thanks to the community here!! @mastodonmigration too.

  7. The team @micro.blog have done it again.

    They soft-launched https://micro.one yesterday¹.

    This may be the most accessible onramp to the open social web ever.

    Cost: $1 a month. Yes you read correctly.

    This is the simplest and cheapest (where you are the customer, not the product) way to own your identity and content online².

    Stop posting in someone else’s garage³.

    Time to export your Twitter, and migrate your Mastodon handle to your own home on the web.

    Of course you can bring your own domain name. Additionally:
    * blog posts, naturally, both articles and microblogging notes
    * photos
    * podcasting
    * custom themes
    * web-clients and native mobile posting clients
    * WordPress, Tumblr, Mastodon, Medium import
    More details (and alternatives) at https://micro.one/about/pricing

    And yes, it interoperates with the open #socialWeb, including:
    * #ActivityPub support, #Mastodon and #fediverse compatibility
    * #IndieAuth to sign-in to third-party apps
    * #microformats support in all built-in themes
    * #Webmention for sending and receiving replies across websites
    * #Micropub standard posting API, supporting dozens of clients
    * #Microsub standard timeline API, supporting social readers
    More #indieweb support details at https://micro.one/about/indieweb

    Did I mention the the superb micro.blog (and micro.one) Community Guidelines?
    * https://help.micro.blog/t/community-guidelines/39

    Well done @manton.org and team.

    This is post 6 of #100PostsOfIndieWeb. #100Posts #ownYourIdentity #ownYourData #openSocialWeb

    https://tantek.com/2025/003/t1/lastfm-year-in-review-playback24
    https://tantek.com/2025/012/t1/eight-years-webmention


    Glossary

    IndieAuth
      https://indieweb.org/IndieAuth
    microformats
      https://microformats.org/wiki/microformats
    Micropub
      https://indieweb.org/Micropub
    Microsub
      https://indieweb.org/Microsub
    Webmention
      https://indieweb.org/Webmention

    References

    ¹ https://www.manton.org/2025/01/03/microone-was-effectively-a-softlaunch.html
    ² https://tantek.com/2025/001/t1/15-years-notes-my-site-first
    ³ https://tantek.com/2023/022/t2/own-your-notes-domain-migration

  8. No I did not block you on the #fediverse / #Mastodon / #Misskey etc.

    If you were following me @tantek.com on your client/server/instance of choice but noticed you were no longer doing so, that was due to a recent software bug in my fediverse provider which accidentally caused everyone’s #ActivityPub servers to unfollow me (bug details below).

    No it’s absolutely not your fault, you did nothing wrong.

    We need a variant of Hanlon’s Razor¹ like:

    “Never attribute to malice that which is adequately explained by a software bug.”

    Take another look at my posts if you want (directly on @tantek.com or try searching for that on your instance) and if you like what you see or find them otherwise informative and useful, feel free to refollow. If not, no worries!

    Also no worries if you ever unfollow/refollow for any reason. I mean that.

    I always assume people know best how to manage their online reader/reading experiences, everyone’s priorities and likes/dislikes change over time, and encourage everyone to make choices that are best for their mental health and overall joy online.

    Bug details:

    This was due to a #BridgyFed bug² that deleted my profile (“ActivityPub actor”) from (nearly?) all instances, making everyone’s accounts automatically unfollow me, as well as remove any of my posts from your likes and reposts (boosts) collections. It also removed my posts from any of your replies to my posts, leaving your replies dangling without reply-contexts. Apologies!

    The bug was introduced accidentally as part of another fix about a month ago³, and was triggered within the following week.

    Anyone following me before ~2024-09-22 was no longer following me. A few folks have noticed and refollowed. Any likes or reposts of my posts before that date were also undone (removed).

    Ryan (@snarfed.org) has been really good about giving folks a heads-up, and apologizing, and quickly doing what he can to fix things.

    Bugs happen, yes even in production code, so please do not post/send any hate.

    I’d rather be one of the folks helping with improving BridgyFed, and temporary setbacks like this are part of being an early / eager #IndieWeb adopter.

    This bug has also revealed some potential weaknesses in other ActivityPub implementations. E.g. deleting an “actor” should be undoable, and undoing a delete should reconnect everything, from follows to likes & reposts collections, to reply-contexts. Perhaps the ActivityPub specification could be updated with such guidance (if it hasn’t been already, I need to double-check).

    To be clear, I’m still a big supporter of #BridgyFed, #ActivityPub, #Webmention, and everyone who chooses to implement these and other #IndieWeb related and adjacent protocols as best fits their products and services.

    All of these are a part of our broader open #socialWeb, and making all these #openStandards work well together (including handling edge-cases and mistakes!) is essential for providing #socialMedia alternatives that put users first.

    References:

    ¹ https://en.wikipedia.org/wiki/Hanlon%27s_razor
    ² https://github.com/snarfed/bridgy-fed/issues/1379
    ³ https://github.com/snarfed/bridgy-fed/commit/4df76d0db7b87cabbd714039546c05b3221169be
    https://chat.indieweb.org/dev/2024-09-22#t1727028174623700

    This is post 26 of #100PostsOfIndieWeb. #100Posts

    https://tantek.com/2024/285/t1/io-domain-suggested-steps
    https://tantek.com/2024/306/t1/simple-embeds

  9. 🆕 📜: Get webmentions with shell script using jq & yq

    Here is my new blog post of how I manage on website to fetch and sync new webmentions, using shell script and `jq` and `yq` to parse and set the data

    maw.sh/blog/get-webmention-wit

  10. @henrikjernevad Looks like I'd need to add IndieAuth support to my (WriteFreely) web site before I could use webmention.io. Probably not worth the effort.

  11. I started to create a new #HTML5 and #CSS4 boilerplate, mainly for my personal use. I'm aiming for the following:

    1. #A11y / #Accessibility support / #ARIA

    Often forgotten. This time, it's deeply personal, it's now a must for me.

    2. Avoid #IconFonts, use #SVG instead.

    Same as the first item, but deserves to be mentioned separately.

    3. #Microformats support

    For #IndieWeb, #Webmention, #Fediverse, and related support.

    4. Use the ‘rel’ attribute where appropriate

    Same as those in the previous items.

    5. Styling using style classes only. Not microformats classes, as those can be reused for other purposes.

    I used to, and I also noticed others doing the same, use microformats classes for styling. And then just override it if the same microformat class is reused elsewhere. Makes everything confusing; and hard to track, especially if you're using someone else's theme/template/skin.

    6. Avoid using advance CSS selectors as much as possible; without resorting to multiple styling classes.

    Multiple classes, as well as, advance CSS selectors, can and do slow down rendering. It's easy to fall into this trap because it makes things easier. I'm guilty of it.

    7. Drop deprecated stuff; and only use future-proof ones.

    Like backwards compatibility with anything IE.

    Also, many CSS resets are actually no longer needed.

    8. Less JavaScript as possible.

    If something can be done without scripts, use that method. Everything else is optional. The site should work with or without scripts.

    Remember, we're creating a boilerplate that we can reuse. We build on top of it.

    9. As semantic as possible.

    For example, use “article”, “main”, “nav”, “aside”, “section”, where applicable, instead of “div” with a “role” and/or “id/class”.

    We requested for those when HTML5 was being developed, but only few actually use it (especially blog templates).

    10. BEM methodology

    ---

    I hope those are everything worth applying in this journey.

    Some notes:
    * For #SchemaOrg, I prefer #JSON than embedding it in the HTML code through classes or itemprop.
    * I understand there are a few with some of the goals I listed already implemented, but I prefer to learn along the way, not “how to use” this and that.

    #YourOnlyOne

  12. @maffeis #ActivityPub is for federation whereas #micropub and #microsub are for interacting with your instance, so they are not really exclusive though.

    Micropub is already supported by tools like micro.blog, @ia Writer and such.

    Not sure if anyone has implemented it on top of an ActivityPub backend though.

    #Webmention, #WebSub and #Microformats would be the more direct #IndieWeb “competitor” to ActivityPub, but eg @snarfed.org and @pfefferle are both showing that the two can be bridged

  13. Im Foo­ter die­ser Web­site steht „Stolz prä­sen­tiert von Wor­d­Press“. Das Wor­d­Press mei­ne Sei­te stolz prä­sen­tie­ren kann, ist vie­len Plugins zu ver­dan­ken, denn ein Stan­dard-Wor­d­press kann zwar wun­der­bar Bei­trä­ge ver­öf­fent­li­chen, aber so ins­ge­samt feh­len vie­le wich­ti­ge Din­ge, um ein Wor­d­Press ordent­lich zu betreiben

    https://jascha.wtf/maschinenraum-teil-3/

  14. I love the layout and the fantastic live UI examples on this page.

    There are a few missing pieces for the primacy of some of these ideas. The broader concept of the commonplace book predated Nelson and Bush by centuries and surely informed much (if not all) of their thinking about these ideas. It’s assuredly the case that people already had the ideas either in their heads or written down and the links between them existed only in their minds or to some extent in indices as can be found in the literature—John Locke had a particularly popular index method that was widely circulated.

    The other piece I find missing is a more historical and anthropological one which Western culture has wholly discounted until recently. There’s a pattern around the world of indigenous peoples in primarily oral cultures using mnemonic techniques going back at least 40,000 years. Many of these techniques were built into daily life in ways heretofore unimagined in modern Western Culture, but which are a more deeply layered version of transclusion imagined here. In some sense they transcluded almost all of their most important knowledge into their daily lives. The primary difference is that all the information was stored visually and associatively in the minds of people rather than on paper (through literacy) or via computers. The best work I’ve seen on the subject is Lynne Kelly’s Knowledge and Power in Prehistoric Societies: Orality, Memory and the Transmission of Culture which has its own profound thesis and is underpinned by a great deal of archaeologic and anthropologic primary research. Given its density I recommend her short lecture Modern Memory, Ancient Methods which does a reasonable job of scratching the surface of these ideas.

    Another fantastic historical precursor of these ideas can be found in ancient Jewish writings like the Mishnah which is often presented as an original, more ancient text surrounded by annotated interpretations which are surrounded by other re-interpretations on the same page. Remi Kalir and Antero Garcia have a good discussion of this in their book Annotation (MIT Press, 2019).

    Image of a super-annotated page of Torah from chapter 3 of Annotation (MIT Press, 2019) by R. Kalir and A. Garcia

    It would create a more layered and nuanced form of hypertext – something we’re exploring in the Digital Gardening movement. We could build accumulative, conversational exchanges with people on the level of the word, sentence, and paragraph, not the entire document. Authors could fix typos, write revisions, and push version updates that propogate across the web the same way we do with software. 

    The Webmention spec allows for resending notifications and thus subsequent re-parsing and updating of content. This could be a signal sent to any links to the content that it had been updated and allow any translcuded pages to update if they wished.

    Annotated on February 09, 2021 at 02:38PM

    In this idealised utopia we obviously want to place value on sharing and curation as well as original creation, which means giving a small fraction of the payment to the re-publisher as well.We should note monetisation of all this content is optional. Some websites would allow their content to be transcluded for free, while others might charge hefty fees for a few sentences. If all goes well, we’d expect the majority of content on the web to be either free or priced at reasonable micro-amounts. 

    While this is nice in theory, there’s a long road strewn with attempts at micropayments on the web. I see new ones every six months or so. (Here’s a recent one: https://www.youtube.com/playlist?list=PLqrvNoDE35lFDUv2enkaEKuo6ATBj9GmL)

    This also dramatically misses the idea of how copyright and intellectual property work in many countries with regard to fair use doctrine. For short quotes and excerpts almost anyone anywhere can do this for free already. It’s definitely nice and proper to credit the original, but as a society we already have norms for how to do this.

    Annotated on February 09, 2021 at 02:46PM

    Transclusion would make this whole scenario quite different. Let’s imagine this again… 

    Many in the IndieWeb have already prototyped this using some open web standards. It’s embodied in the idea of media fragments and fragmentions, a portmanteau of the words fragment and Webmention.

    A great example can be found at https://www.kartikprabhu.com/articles/marginalia

    This reminds me that I need to kick my own server to fix the functionality on my main site and potentially add it to a few others.

    Annotated on February 09, 2021 at 02:59PM

    We can easily imagine transclusions going the way of the public comments section. 

    There are definitely ways around this, particularly if it is done by the site owner instead of enabled by a third party system like News Genius or Hypothes.is.

    Examples of this in the wild can be found at https://indieweb.org/annotation#Annotation_Sites_Enable_Abuse.

    Annotated on February 09, 2021 at 03:04PM

    #annotations #anthropology #archaeology #fragmentions #judaism #lynne-kelly #media-fragments #micropayments #mishnah #orality #transclusion #ui #webmention

    https://boffosocko.com/2021/02/09/55786828/

  15. If one is worried about link rot for transclusion, why not just have a blockquote of the original in excerpt form along with a reference link to the original. Then you’ve got a permanent copy of the original and the link can send a webmention to it as a means of notification? If the original quoted page changes, it could potentially send a webmention (technically a salmention in function) to all the pages that had previously mentioned it to create updates. Automatic transclusion can also be more problematic in terms of original useful data being used as a vector of spam, graffiti, or other abuses. As an example, I can “transclude” a portion of your page onto my own website as a reply context for my comment and syndicate a copy to Hypothes.is. If you’ve got Webmentions on your site, you’ll get a notification. For several years now I’ve been considering why digital gardens/zettelkasten/commonplace books don’t implement webmention as a means of creating backlinks between wikis as a means of sites having conversations? Note: I’ve also gone in and annotated a copy of Maggie Appleton’s article with some additional thoughts that Aquiles Carattino and others may appreciate.

    #commonplace-books #salmention #transclusion #webmention

    https://boffosocko.com/2021/02/09/55786823/

  16. Things I know I'd want to use / open to contributing to:

    * a dedicated #ActivityPub vlogging platform (think single-user, multiple-channel/feed in likes of Vimeo, YouTube etc) with mobile clients

    * federated podcasting platform similar to simplecast.com with mobile clients and plugs to silos

    * a federated music scrobbling tool / option with clients

    * a general purpose social reader

    oh + all support nomadic identities (DiD), p2p file storage, #Microformats2, #Webmention, #WebSub