惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
人人都是产品经理
人人都是产品经理
Cisco Talos Blog
Cisco Talos Blog
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
V
V2EX
博客园 - 三生石上(FineUI控件)
Martin Fowler
Martin Fowler
WordPress大学
WordPress大学
D
Docker
S
SegmentFault 最新的问题
博客园 - 聂微东
美团技术团队
Apple Machine Learning Research
Apple Machine Learning Research
月光博客
月光博客
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
Last Week in AI
Last Week in AI
M
MIT News - Artificial intelligence
F
Fortinet All Blogs
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
The GitHub Blog
The GitHub Blog
GbyAI
GbyAI
L
LangChain Blog
Vercel News
Vercel News
博客园 - 叶小钗
MongoDB | Blog
MongoDB | Blog
Stack Overflow Blog
Stack Overflow Blog
H
Help Net Security
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
The Cloudflare Blog
Engineering at Meta
Engineering at Meta
T
Threat Research - Cisco Blogs
T
Threatpost
Scott Helme
Scott Helme
T
Tailwind CSS Blog
Latest news
Latest news
Stack Overflow Blog
Stack Overflow Blog
Blog — PlanetScale
Blog — PlanetScale
The Register - Security
The Register - Security
罗磊的独立博客
P
Proofpoint News Feed
腾讯CDC
S
Schneier on Security
雷峰网
雷峰网
A
About on SuperTechFans
T
Tenable Blog
F
Full Disclosure
Cyberwarzone
Cyberwarzone
博客园_首页
有赞技术团队
有赞技术团队
K
Kaspersky official blog

文章列表

Compulsive curiosity, or, how I built an infinite idea machine Gift details on the subscriber portal Portal link in the archive nav The physicists who convinced Fermilab to send Brazil's emails First, add no friction: How micropayments lost and subscriptions won Filter subscribers and automations by source Automations, rebuilt What email will look like in the future Filter subscribers by bounce date and reason Email could have been X.400 times better Three features are moving behind the paywall Firewall changes and improvements Put your name and voice into your company newsletter Simplified email address settings Subscription wall Inboxes were overwhelming before we'd even named them The US government tried really hard to screw up email Public postmortem: database connection exhaustion Ask a nerd: what is the best way to unsubscribe from newsletters? Bookshop.org embeds Email was into agents before they were cool Passwordless login Rename metadata keys in bulk A spring cleaning for our legal docs Ask a nerd: what happens when you click the spam button? Passkey support for two-factor authentication How Buttondown's API versioning works Safer defaults for the email creation API How to send email to space How we enabled Content Security Policy for everyone Recovery codes for two-factor authentication Filter sent emails by engagement rate How we migrated to TypeIDs without breaking clients How we check every link in your email Use newsletter metadata in your emails Should we bring back email exploders? Sort and filter by open and click rates Custom click tracking domains More newsletter settings in the API Revamped replies Custom email templates for everyone Simplified cancellation Ask a Nerd: Does email length affect deliverability? The changelog, reborn Swedish localization Forwarding an email is not always straightforward Public descriptions for tags OpenAPI spec for archives How Rodrigo brings a humanistic view to consumer technology Subscribers can come from anywhere. Even another newsletter platform's form. Survey responses on the web How Brandon Lucas Green shares his music and supports artists Your newsletter's archives are more valuable than your list Better tag self-management Smarter automation filters Granular API keys Snippets New design settings pages Ask A Nerd: How does newsletter cadence affect deliverability? Starred views More ways to customize your archives Inbox filtering Mastodon follower analytics Ask a Nerd: What are good open, click, and response rates for an email newsletter? How we migrated our database to PlanetScale Two new archive themes Custom buttons now work in Markdown mode Ask a Nerd: Does attaching files to your newsletter hurt deliverability? Seline and Tinylytics support Unban subscribers Announcement bars for your archives Bang paths, source routing, and how email trips were planned Public postmortem: archive downtime 2025 disposables.app Russian localization Ask a Nerd: Can you improve email deliverability with a personal domain? More locale options How we interview customers at Buttondown Bluesky analytics Reply to conversations Minimum viable complexity How Jeffery Hicks goes behind-the-scenes in his newsletter Changes to our stack in 2025 2026: Emails TK reminders in the editor What the hell is a UTM? Randomize survey answer order Why we insourced analytics Scroll sync in the editor 2026: Archives How Jamie Thingelstad uses Buttondown to explore tech topics How Kelly Jensen uses Buttondown to discuss key library issues Keeping feature creep at bay Improved filters Content Security Policy in archives Open source Sniperl.ink Auto-activating RSS reader subscriptions What the hell is ActivityPub? How Igor Ranc built Berlin's largest expat tech newsletter
What the hell is a Webmention?
Matthew Guay · 2025-08-01 · via

Imagine, for a moment, a more limited social media. No endlessly-scrolling feed, no clickbait, no auto-playing videos. Just posts from your friends, pictures and posts you’ve been tagged in, then back to real life.

I’d bet it’d still be addictive, as long as it included mentions and notifications.

It’s fun to be talked about (in a good way, that is), nice to know that people liked what you’ve shared. Thus the dopamine hit whenever someone shares your work and tags you in the post.

That has to be at least part of the reason why social media took over blog posts and RSS feeds. The feedback loops are shorter; it’s more instantly gratifying when folks click Like, than waiting for the long tail of the web to catch up with you.

Not that they have to be. For over two decades, blogs have been able to notify each other of new posts, with Webmentions (and Trackback, Pingbacks, and other types of Linkbacks). They’re tiny steps towards decentralized networks—and bring a bit of the warm fuzzy feelings of mentions to indie publication.

A Webmention is...

...an “@ mention that works across websites.” That’s how Roney Ngala described Webmentions in 2017, five years after the first specification was written.

The idea was simple: A modernized version of TrackBacks, PingBacks, and all the other linkbacks that’d been invented in the first two or so decades of the internet. Original TrackBacks were essentially automated comments. When someone mentioned your blog post in their article, their server would comment on your post with a link to their post.

But the modern web had likes, comments, reposts, and more, and Webmentions set out to implement them all, to “enable cross-site conversations” as IndieWeb described their purpose. And so started a fork of PingBacks, designed to modernize how blogs talk to each other—and, perhaps, decentralize social networking and bring a bit of energy back to blogging.

“If you use Twitter, your friend Alice only uses Facebook, your friend Bob only uses his blog on WordPress, and your pal Chuck is over on Medium, it’s impossible for any one of you to @mention another,” wrote Chris Aldrich in A List Apart, building the case for Webmentions. What if, instead, you had an “@mention that works from one website to another,” went the proposal. It’s a dream that the earliest bloggers shared, back before WordPress had been invented.

Back to the TrackBack

The original MovableType TrackBack

It all started back in June 2002, four years after Larry Page and Sergey Brin’s Googlebot started scouring the internet for backlinks to find the best parts of the internet, with nascent blogging platform MovableType. The idea was simple: What if you were notified every time someone referenced something you wrote? It’d be backlinks that’d come to you.

TrackBacks started life with a bookmarklet. When you read something interesting, you’d click the bookmarklet for your blog and if that blog supported TrackBacks, it’d copy the link and give you a space to start blogging. And when you clicked Post, your new blog post would be published and your site would notify the original site about the post. A bit manual—but not much more than quoting a Tweet and adding additional commentary today.

“We've already thought of some examples where TrackBack can be used, the MovableType team dreamed. Build a decentralized commenting system, where the space under your article was filled with links to others’ takes on your idea. Create a guest blog section on your site, with a list of articles others wrote that referenced your product. Run surveys, with everyone’s picks published on their site for a shot at vitality. All that, a year before the BlackBerry got push notifications for email.

Possibly the world’s first Pingback, on the original Pingback blog post

A month after TrackBacks launched, Stuart Langridge had a better idea. What if the servers just automatically notified each other? “When you make a new post, your blog walks through your post and says to every URL mentioned in it: ‘I’m writing about you,’” suggested Langridge, using XML-RPC commands to ping the server. By September, an official spec was born, christened Pingback. If your site supported Pingbacks, you’d included a <link rel="pingback" href="https://domain"> in the head. Whenever a blog post mentioned you, its software would scan the header, find the Pingback link, and ping it with details about the new post.

TrackBacks might have encouraged you to write a blog post right when you were reading a site—but they were also prone to spam, with no confirmation that your blog post was actually published. Plus, anything that adds an extra step makes it harder to keep going over time.

PingBacks, by being automatic and requiring both servers to support PingBacks, simplified the blogging process and cut down spam (a bit, anyhow). That was enough to make it the de facto standard, baked into WordPress—and by extension, a growing proportion of the web—since 2005. And then it was everywhere, spammers discovered how easy it was to get a backlink just by sending a TrackBack to a popular site, and that, as Stack Overflow creator Jeff Atwood said in 2006, is what killed Trackbacks (and, for the most part, comments on much of the web).

Then creators moved on to social media, blogging went corporate, and the whole thing was ripe for reinvention.

Building a better PingBack

Don’t reinvent the wheel, though, and so “the Webmention spec began as a simplified version of the Pingback spec,” says the W3C Webmention guide. From Sandeep Shetty’s first iteration in October 2012, Webmentions replaced XML-RPC with a simpler HTTP form POST, making it easier to develop and less susceptible to hacks.

POST /webmention-endpoint HTTP/1.1
Host: bobs.host
Content-Type: application/x-www-url-form-encoded

source=http://alices.host/alice/post/42&\
target=http://bobs.host/bob/post/2

Then trust, but verify, and so when your site receives that HTTP POST with a Webmention, it’ll first check to ensure that link really exists, and only then save the mention for reference. Your server could even periodically check to ensure the mention is still there, if you want to keep your Webmentions up-to-date.

Example via Aaron Parecki’s guide to Webmentions

Links on their own don’t tell you all that much, so Webmentions expanded what could be included. You could include microformats like h-entry and u-author in your Webmention copy, to perhaps share a like or dislike, include the ID of a specific comment you’re replying to, include your name and avatar, and more. And you could include URL fragments to link directly to a specific part of a page, for Medium-style inline comments.

In the spirit of PingBacks and TrackBacks before, folks dreamed of everything. You could have comments across blogs, back and forth, with Webmentions copying the comments between sites, imagined A List Apart. “A response can be an RSVP to an event, an indication that someone "likes" another post, a "bookmark" of another post, and many others,” imagined the W3C’s spec.

And along came the software. Webmention.io can receive Webmentions on behalf of your site, without needing to add anything beyond an HTML tag to your site. Bridgy can find mentions of your site on social media, and push them via a Webmention to your site. And your favorite newsletter tool, Buttondown, supports Webmentions, so whenever you mention a blog post in your newsletter, their server will get pinged with the new mention.

Webmentions aren’t perfect. Dr. Wouter Groeneveld, an early adopter, turned off his Webmention server in 2023 thanks to the same problem that took down TrackBacks: Spam. And the non-spammy comments weren’t all that interesting, either; “about 75% of the mentions I do receive are completely useless ‘like’ messages,” Groeneveld wrote.

Yet the dream lives on. You could gather Webmentions with Webmention.io, just as a way to know who mentioned you but without sharing every mention on your site. You could perhaps build a whitelist to show your friends’ Webmentions, for a new take on a web ring (remember those?). You could take the idea and run with it, tackling spam and building something more fun in the process, as Matthias argued on Own Your Web: “This tinkering is worth the effort: seeing the replies of others appear on your site is just magical.”

Or, perhaps, you might prefer the oldest Webmention of them all: Email. “If I have to choose between spending time coding in yet another edge case or just writing and replying to a lovely email from a reader, I’d prefer the latter,” concluded Groeneveld, and we concur.

We’re proud that you can have both in Buttondown, and always thought there was something to the idea in the TrackBacks and Pingbacks of old. And just maybe, as Bluesky and Mastodon and a thousand networks bloom, we’ll eventually land on a universal way to @mention each other on the web.

Spam, though? Might have to wait for the heat death of the universe to cure that one.