šŸŽ‰ Six years ago today, the #IndieWeb Webmention protocol was published as a W3C REC w3.org/TR/webmention/ A key social web building block, Webmention enabled peer-to-peer comments, likes, and other responses to be created, updated, and deleted ... tantek.com/t5Np1
šŸŽ‰ Six years ago today, the #IndieWeb Webmention protocol was published as a W3C REC https://www.w3.org/TR/webmention/

A key social web building block, Webmention enabled peer-to-peer comments, likes, and other responses to be created, updated, and deleted across the web, by both dynamic & static websites.

It was accompanied by a report of over a dozen implementations that demonstrated interoperability: https://webmention.net/implementation-reports/summary/ using an open test suite: https://webmention.rocks/ that is still up and running and used by developers today.

Many many more implementations have been developed, open sourced, shipped, launched since. The specification itself has a webmention endpoint and accepts webmentions.

Exactly a year before that, Webmention was published as a First Public Working Draft by the W3C Social Web Working Group: https://www.w3.org/TR/2016/WD-webmention-20160112/

It took the best parts of the prior Pingback protocol, simplified it (ditched XML-RPC), made it more secure, separated presentation from plumbing, and added update & delete semantics.

It was in many ways a model for how open web standards should be developed.

See the wiki page for an overview and numerous screenshots of implementations: https://indieweb.org/Webmention

If you want to implement Webmention yourself, there are now numerous developer resources to do so.

Start here: https://indieweb.org/Webmention-developer and come say hi at the IndieWeb development chat channel: https://chat.indieweb.org/dev

Previously, previously, previously:
* https://tantek.com/2020/012/t1/happy-birthday-webmention
* https://tantek.com/2018/012/t1/anniversary-million-webmentions
* https://tantek.com/2017/012/t1/webmntion-first-w3c-recommendation-high-bar

This is day 12 of #100DaysOfIndieWeb #100Days.

← Day 11: https://tantek.com/2023/011/t1/indieweb-evolving-at-mention
→ šŸ”®
#IndieWeb #100DaysOfIndieWeb #100Days

Are you practicing good oral hygiene during eternal Caturday?

In defense of WebP

#NAFO is giving #Russia #Putin a hard time as they do the MOD Shuffle We should be happy the Government has an Open Window Policy
Excited to give this talk today on #CMMC at @dcodethegov Nexus Accelerate event We will discuss NIST-SP-800-171 requirements and CMMC Impact of DoD's announcement they will file a draft rule change for CFR 32 and 48 and not an interim rule Finally opportunities for #govcon
One of the fun things about #IndieWeb notes & replies is that how we post is actively evolving! Like how should we @ someone?

#socialMedia aliases (e.g. @Twitter) were obvious, with prior @-name usage on Flickr etc.

Now, some have a domain, or an @-@ (pronounced at-at, yes, just like the abbreviation for Imperial All Terrain Armored Transport^1), or some have both.

We can ask questions like why do we @-someone? What are the use-cases?
* In a reply to a public post, clearly express that you’re speaking to that person
* In a reply to a reply, that you’re speaking to everyone upthread (AKA a https://indieweb.org/canoe)
* When attributing something to someone (photo/post/cool thing by so-and-so), giving credit
* Distinguish a person (or something that can be followed) from ā€œjustā€ a site
* For all the above, notifying someone accordingly

Some ideas:

1. Ideally, if/when everyone has their own domain (where they receive Webmention notifications, and a feed you can follow), we can @-name their domain, which your auto-linker^2 should hyperlink accordingly, e.g.
* @aaronparecki.com @anomalily.net @Martymcgui.reā€Ž @david.shanske.com @voxpelli.com @adactio.com @marcthiele.com @mxb.dev

These all look close enough to social media aliases/names that they’re immediately recognizable as readable @-names, a good consideration when choosing a domain name.^3

2. As a fallback (e.g. for non-@-domain-auto-linking destinations) we can use someone’s plain domain (explicitly with https:), especially if their home page still has a stream or feed you can follow, or maybe if they don’t receive homepage Webmentions (yet), e.g.:
* https://jacky.wtf/ https://tmichellemoore.com/ https://crowdersoup.com/

3. Some folks with personal sites have (for now) created separate Mastodon accounts (or installed an instance on a subdomain), and for them, we can reference their @-@ parenthetically after their domain, like:
* https://kevinmarks.com/ (@kevinmarks@xoxo.zone), https://dangillmor.com/ (@dangillmor@mastodon.social), https://simonwillison.net/ (@simon@simonwillison.net)

Rather than using social media silo @-names (except when explicitly replying to a silo), I’m now experimenting with all three of these (1-3) instead, both to elevate people’s IndieWeb identities, and for Mastodon viewers, provide a convenient way to follow @-@ addresses.

If someone’s homepage receives Webmentions, they will get notified when I @-mention them by domain.

I recently implemented syntactic auto-linking of @-@ addresses like this:
* @user@example.com --> https://example.com/@user
with a special case for @-domain@-domain to just link to the domain, e.g.:
* @tantek.com@tantek.com --> https://tantek.com/

I also made a recent policy decision to auto-link all @-@ (and @-domain) mentions to https:, the reasoning being that identities on the web should be using https.
* Testing in production here: https://tantek.com/cassis.js, search for "auto_link("

Some questions:
* Does/do Mastodon (or other ActivityPub servers) notify people when you @-@ mention them in a post? How? Who’s responsible for that?
* Will Bridgy Fed notify the servers (deliver to AP inboxes) of folks I merely @-@ mention (rather than explicit replies, reposts)? Should it?

So many people are switching to using their personal domains to post (or at least a Mastodon account) that I no longer feel compelled to @-mention people’s Twitter handles in posts, which feels refreshing.

Now the fun part is experimenting and figuring out what combination of @-domain, plain domain, or @-@ mentions looks good, makes sense to people, and sends notifications to people the way they want to receive them.

This is day 11 of #100DaysOfIndieWeb #100Days.

← Day 10: https://tantek.com/2023/010/t2/build-use-services
→ šŸ”®

^1 https://en.wikipedia.org/wiki/AT-AT
^2 My https://tantek.com/github/cassis/blob/master/cassis.js auto_link() function supports @example.com auto-linking, yours should too.
^3 https://tantek.com/2023/004/t1/choosing-domain-name-indieweb
#IndieWeb #socialMedia #100DaysOfIndieWeb #100Days
One of the fun things about #IndieWeb notes & replies is that how we post is actively evolving! Like how should we @ someone? #socialMedia aliases (e.g. @Twitter) were obvious, with prior @-name usage on Flickr etc. Now, some have a domain, or an @-@ ... tantek.com/t5No1
One of the fun things about #IndieWeb notes & replies is that we're still figuring things out! Like how should we @ someone?

#socialMedia aliases (e.g. @Twitter) were obvious, with prior @-name usage on Flickr etc.

Now, some have a domain, or an @-@ (pronounced at-at, yes, just like the abbreviation for Imperial All Terrain Armored Transport^1 walkers), or some have both.

We can ask the questions of why do we @-someone? What are the use-cases?
* In a reply to a public post, clearly express that you’re speaking to that person
* In a reply to a reply, that you’re speaking to everyone upthread (AKA a https://indieweb.org/canoe)
* When attributing something to someone (photo/post/cool thing by so-and-so), giving credit
* For all the above, notifying someone accordingly
* Distinguish a person (or something that can be followed) from ā€œjustā€ a site

Some ideas:

1. Ideally, if/when everyone has their own domain (where they receive Webmention notifications, and a feed you can follow), we can @-name their domain, which your auto-linker^2 should hyperlink accordingly, e.g.
* @aaronparecki.com @anomalily.net @Martymcgui.reā€Ž @david.shanske.com @snarfed.org @ben.thatmustbe.me

These all look close enough to social media aliases/names that they’re immediately recognizable as readable @-names, a good consideration when choosing a domain name.^3

2. As a fallback (e.g. for non-@-domain-auto-linking destinations) we can use someone’s plain domain (explicitly with https:), especially if their home page still has a stream or feed you can follow, or maybe if they don’t receive homepage Webmentions, e.g.:
* https://adactio.com https://marcthiele.com https://mxb.dev/

3. Some folks with personal sites have (for now) created separate Mastodon accounts (or an installed an instance on a subdomain), and for them, we can reference their @-@ parenthetically after their domain, like:
* https://kevinmarks.com/ (@kevinmarks@xoxo.zone), https://tmichellemoore.com/ (@tmichellemoore@mastodon.social), https://voxpelli.com/ (@voxpelli@mastodon.social), https://simonwillison.net/ (@simon@simonwillison.net)

Rather than using social media silo @-names (except when explicitly replying to a silo), I’m now experimenting with all three of these (1-3) instead, both to elevate people’s IndieWeb identities, and for Mastodon viewers, provide a convenient way to follow @-@ addresses.

If someone’s homepage receives Webmentions, they will get notified when I @-mention them by domain.

I recently implemented syntactic auto-linking of @-@ addresses like this:
* @user@example.com --> http://example.com/@user
with a special case for @-domain@-domain to just link to the domain, e.g.:
* @tantek.com@tantek.com --> http://tantek.com/

I also made a policy decision to auto-link all @-@ (and @-domain) mentions to https:, the reasoning being that identities on the web should be using https.

Some questions:
* Does/do Mastodon (or other ActivityPub servers) notify people when you @-@ mention them in a post? How? Who’s responsibility is that?
* Will Bridgy Fed notify the servers (deliver to AP inboxes) of folks I merely @-@ mention (rather than explicit replies, reposts)? Should it?

So many people are switching to using their personal domains to post (or at least a Mastodon account) that I no longer feel compelled to @-mention people’s Twitter handles in posts, which feels refreshing.

Now the fun part is experimenting and figuring out what combination of @-domain, plain domain, or @-@ mentions looks good, makes sense to people, and sends notifications to people the way they want to receive them.

This is day 11 of #100DaysOfIndieWeb #100Days.

← Day 10: https://tantek.com/2023/010/t2/build-use-services
→ šŸ”®

^1 https://en.wikipedia.org/wiki/AT-AT
^2 My https://github.com/tantek/cassis/blob/master/cassis.js auto_link() function supports @example.com auto-linking, yours should too.
^3 https://tantek.com/2023/004/t1/choosing-domain-name-indieweb
#IndieWeb #socialMedia #100DaysOfIndieWeb #100Days

Electric vehicles in 2023

Are you positioned for success during eternal Caturday?

Hey, San Diego! We All We Got is doing another grocery distribution this Saturday, January 14th 12:30pm until supplies run out. Location: Azalea Park (corner of Poplar & Violet). weallwegotsd.com/distro

No proof of income or ID is necessary to receive food. Solidarity, not charity.

Sign up to volunteer: signup.com/go/VFTCiVs

A #NAFO fella for an OG Guitar hero. If you have never listened to Jeff Beck's Wired do so tonight. Meant to pluck the strings in the nursery of stars.
⛸⛸⛸
NEW: Musk emailed Twitter saying most of his Tesla work was completed this wknd & he’s available to discuss ā€œurgentā€ product needs. All changes have to be signed off by him personally. ā€œWe are going to agonize until we achieve as close to the perfect product as possibleā€
Hi #PortfolioDay I am a fake artist just trying to teach kids to make cool webby stuff and cut and paste my way to insignificance helping #NAFO raise money for #Ukraineļø Watching how important art is to those facing the horrors of war helps restore my faith in humanity
Once you have a domain^1, and connect it to an #IndieWeb service like https://micro.blog, or a https://indieweb.org/CMS on https://indieweb.org/web_hosting, you can focus^2 on your writing.

Or if you enjoy #webDevelopment and want to build (option three^3), use developer services to more rapidly add IndieWeb building blocks^4 to your site so you too can focus on creating & owning your content^5.

Here are some of the most common and popular developer services:
1. Webmention sending: https://webmention.app/ by https://remysharp.com/ (@rem@front-end.social), or https://mention.tech/ by https://kevinmarks.com/ (@kevinmarks@xoxo.zone)
2. Webmention receiving: https://webmention.io/ (I use this) by https://aaronparecki.com/ or https://webmention.herokuapp.com/ by https://voxpelli.com/ (@voxpelli@mastodon.social)
3. POSSE & backfeed: https://brid.gy/ by Ryan of https://snarfed.org/ (@schnarfed)
4. ActivityPub federating: https://fed.brid.gy/ also by Ryan. More on Bridgy & Bridgy Fed^6.

Using a developer service to support IndieWeb protocols saves you time. You can also contribute to the community by filing suggestions for improvements, or participating on their GitHub repositories.

If you prefer that your site not depend on any external services, you can do that too.

Most of the above services are also open source that you can install and fully manage yourself. For example:
* Webmention installable services: https://indieweb.org/Webmention#Publisher_Services

Another option is to use one of many open source libraries to more rapidly implement support for IndieWeb standards^7. The wiki pages for each standard list libraries in a variety of programming languages, e.g.:
* https://indieweb.org/Webmention-developer#Libraries

If you choose the path of installing or building something new with libraries or by directly implementing an IndieWeb standard, be sure to test your implementation with its test suite, e.g.:
* https://webmention.rocks/

As a web developer, you can choose how much of your #IndieWeb support you want to implement yourself (and time to invest) vs build on the services, libraries, and other open source that the community has produced and is actively supporting.

This is day 10 of #100DaysOfIndieWeb #100Days.

← Day 9: https://tantek.com/2023/009/t2/edit-reply-comment-update
→ šŸ”®

^1 https://tantek.com/2023/004/t1/choosing-domain-name-indieweb
^2 https://tantek.com/2023/005/t3/indieweb-simpler-approach
^3 https://tantek.com/2023/003/t1/indieweb-path-chosen-why
^4 https://indieweb.org/building_blocks
^5 https://tantek.com/2023/001/t1/own-your-notes
^6 https://tantek.com/2023/008/t7/bridgy-indieweb-posse-backfeed
^7 https://spec.indieweb.org/
#IndieWeb #webDevelopment #100DaysOfIndieWeb #100Days
If you want to understand how those in power used #disinfo to attack America subscribe. Good perspective as you look at overalp between #MAGA #Q and #Russia goals in #Ukraine Our democracy was fundamentally attacked and must be defended.
Jim Stewartson, Antifascist, #RIPQ šŸ‡ŗšŸ‡øšŸ“ā€ā˜ ļø https://twitter.com/jimstewartson
Here are some details about how, after Trump lost the 2020 election, Mike Flynn ended ā€œQā€ and turned it into the Big Lie that led to the insurrection. The only diffe...
Once you have a domain^1, and connect it to an #IndieWeb service like micro.blog, or a indieweb.org/CMS on indieweb.org/web_hosting, you can focus^2 on your writing. Or if you enjoy #webDevelopment and want to build (option three^3),... tantek.com/t5Nn2
Four hundred years of Russian diplomacy captured in one image, thx @JudyTheGoodGal
JustAmericanUkrainianMe https://twitter.com/JudyTheGoodGal
Another way to look at liberation