📗 Want to read Says Who?: A Kinder, Funner Usage Guide for Everyone Who Cares about Words by Anne Curzan ISBN: 9780593444092
📗 Want to read Mobility by Lydia Kiesling ISBN: 9781638930563
📗 Want to read How We Show Up: Reclaiming Family, Friendship, and Community by Mia Birdsong ISBN: 9781580058070
📗 Want to read Emergent Strategy: Shaping Change, Changing Worlds by Adrienne Maree Brown ISBN: 9781849352604
Fourth Avenue Pub

Link: The Recumbent Bicycle: Reasons to Buy

Bar Veloce

Gotta enjoy outdoor sipping while it’s nice!

✏️ I want the Read Write Suggest-Edit Accept-Edit Update Web.

The consumer Infinite Scroll Web leaves us feeling empty.

Too few of us participate in the Read Write Web, whether with personal sites or Wikipedia.

A week ago when we wrapped up #IndieWebCamp Portland and I was reading Kevin Marks (@kevinmarks@indieweb.social) live-tooting of the demos¹, I noticed a few errors, typos or miscaptures, and pointed them out in-person.

Kevin was able to quickly edit his toots and update them for anyone reading, thanks to #Mastodon’s post editing feature and its support of #ActivityPub Updates. But this shouldn’t require being in the same room, whether IRL or chat.

We should be able to suggest edits to each other’s posts, as easily as we can reply and add a comment.

13 years ago I wrote²:

 “The Read Write Web is no longer sufficient. I want the Read Fork Write Merge Web.”

Now I want the Read Write Suggest-Edit Accept-Edit Update Web.

The ↪ Reply button is fairly ubiquitous in modern post user interfaces (UIs).

Why not also a ✏️ Suggest Edit button, to craft a fix for a typo, grammar, or other minor error, and send the author for their review, and acceptance or rejection? Perhaps viewable only by the suggester and the author, to avoid "performative" suggested edits.

If the author’s posts provide revision histories, when a suggested edit is accepted, a post’s history could show the contributor of the edit.

Instead of asking Kevin in-person, what if I could have posted special "Suggested Edit" responses in reply to his toots, for which he would receive special notifications, and could choose to one-click accept and update (or further edit) his toots?

To enable such UIs and interactions across servers and implementations, we may need a new type of response³, perhaps with a special property (or more) to convey the edits being suggested.

There is documentation of this and similar use-cases, prior art / UIs, as well as some brainstorming on the #IndieWeb wiki:
* https://indieweb.org/edit

Our interaction after IndieWebCamp has inspired me to take another look at how can we design and prototype solutions to this problem.

For now, if you host your blog and posts as static files on GitHub (or equivalent), you could add a button like this to your posts alongside Like, Reply, Repost buttons:

✏️ Suggest Edit

and link it to an edit URL for the static file for the post.

I don’t use GitHub static files myself for posts, but here’s an example of such an edit link for one of my projects:

https://tantek.com/github/cassis/edit/main/README.md

This will start the process of creating a “pull request”, GitHub’s jargon for a “suggested edit”.

After completing GitHub’s ceremony of entering multiple text fields (summary & description), and multiple clicks to create said “pull request”, it’ll be sent to the author to review. Presuming the author likes the suggested edit, they can perform the other half of GitHub’s jargon-filled ceremonies to “Merge” or “Squash & Merge”, “Delete fork”, etc. to accept the edit.

It’s an awkward interaction, however useful for at least prototyping a ✏️ Suggest Edit button on sites that store their posts as files in GitHub. Certainly worthy of experimenting with and gathering experience to design and build even better interactions.

We can start with the shortest path to getting something working, then learn, iterate, improve, repeat.

#readWriteWeb #editableWeb #suggestEdit #acceptEdit

References:

¹ https://indieweb.social/@kevinmarks/113025295600067213
² https://tantek.com/2011/174/t1/read-fork-write-merge-web-osb11
³ https://indieweb.org/responses
The phrase “pull request” was derived from the git command: “git request-pull” according to https://www.reddit.com/r/git/comments/nvahcp/comment/h12hzj7/
“edits” in GitHub require taking far more steps, and navigating far more jargon, then say, Wikipedia pages, which come down to “Edit” and “Save”. We should aspire to Wikipedia’s simplicity, not GitHub’s ceremonies.

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

https://tantek.com/2024/242/t1/indiewebcamp-portland
https://tantek.com/2024/246/t1/adventures-indieweb-activitypub-bridgy-fed
#IndieWebCamp #Mastodon #ActivityPub #IndieWeb #readWriteWeb #editableWeb #suggestEdit #acceptEdit #100PostsOfIndieWeb #100Posts
Had a great time at IndieWebCamp Portland 2024 this past Sunday — our 10th IndieWebCamp in Portland!

https://events.indieweb.org/2024/08/indiewebcamp-portland-2024-8bucXDlLqR0k

Being a one day #IndieWebCamp, we focused more on making, hacking, and creating, than on formal discussion sessions.

Nearly everyone gave a brief personal site intro with a summary of how they use their #IndieWeb site and what they would like to add, remove, or improve.
* https://indieweb.org/2024/Portland/Intros

There were lots of informal discussions, some in the main room, on the walk to and from lunch, over lunch in the nearby outdoor patio, or at tables inside the lobby of the Hotel Grand Stark.

We wrapped up with our usual Create Day¹ Demos session, live streamed for remote attendees to see as well. Lots of great demos of things people built, designed, removed, cleaned-up, documented, and blogged! Everyone still at the camp showed something on their personal site!
* https://indieweb.org/2024/Portland/Demos

Group photo and lots more about IndieWebCamp Portland 2024 at the event’s wiki page:
* https://indieweb.org/2024/Portland

Thanks to everyone who pitched in to help organize IndieWebCamp Portland 2024! Thanks especially to Marty McGuire (@martymcgui.re) for taking live notes during both the personal site intros and create day demos, to Kevin Marks (@kevinmarks@indieweb.social @kevinmarks@xoxo.zone @kevinmarks) for the IndieWebCamp live-tooting, and Ryan Barrett (@snarfed.org) for amazing breakfast pastries from Dos Hermanos.

The experience definitely raised our hopes and confidence for returning to Portland in 2025.²


References:

¹ https://indieweb.org/Create_Day
² https://indieweb.org/Planning#Portland

This is post 19 of #100PostsOfIndieWeb. #100Posts #2024_238

https://tantek.com/2024/238/t3/indiewebcamp-auto-linking
https://tantek.com/2024/245/t1/read-write-suggest-edit-web
#IndieWebCamp #IndieWeb #100PostsOfIndieWeb #100Posts #2024_238
Nice #IndieWebCamp discussion session with Kevin Marks (@kevinmarks@indieweb.social @kevinmarks@xoxo.zone @kevinmarks) on the topic of auto-linking¹.

I’ve implemented an auto_link function² that handles quite a few use-cases of URLs (with or without http: or https:), @-name @-domain @-domain/path @-@-handles, hashtags(#), and footnotes(^).

Much of it is based on what I’ve seen work (or implemented) on sites and software, and some of it is based on logically extending how people are using text punctuation across various services.

It may be time for me to write-up an auto-link specification based on the algorithms I’ve come up with, implemented, and am using live on my site. All the algorithms work fully offline (none of them require querying a site for more info, whether well-known or otherwise), so they can be used in offline-first authoring/writing clients.

I have identified three logical chunks of auto-linking functionality, each of which has different constraints and potential needs for local to the linking context information (like hashtags need a default tagspace). Each would be a good section for a new specification. Each is used by this very post.

* URLs, @-s, and @-@-s
* # hashtags
* ^ footnotes

#IndieWeb #autoLink #hashtag #hashtags #footnote #footnotes

Previously, previously, previously:

* https://tantek.com/2024/070/t1/updated-auto-linking-mention-use-cases
* https://tantek.com/2023/100/t1/auto-linked-hashtags-federated
* https://tantek.com/2023/043/t1/footnotes-unicode-links
* https://tantek.com/2023/019/t5/reply-domain-above-address-and-silo


References:

¹ https://indieweb.org/autolink
² https://github.com/tantek/cassis/blob/main/cassis.js


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

https://tantek.com/2024/238/t1/indiewebcamp-portland
https://tantek.com/2024/242/t1/indiewebcamp-portland
#IndieWebCamp #IndieWeb #autoLink #hashtag #hashtags #footnote #footnotes #100PostsOfIndieWeb #100Posts

At Bar del Pla in Barcelona

If this is hell, I don’t wanna go to heaven.

Happy Labor Day weekend y’all! 🥳

#Portland #OregonExplored

#Portland is pleased to boast many fine murals, but this one is definitely my favorite. It’s always a good day when I get to ride past. 😍 #OregonExplored

Artist: Fin DAC
you can find many other fine works of his here

A view of South Waterfront and the Aerial Tram, looking east from the OHSU medical complex.

It was pretty hazy that day, but I still think this is one swell vista!

#Portland #OregonExplored #NikonZfc

Dayum, this DJ was on fire! 🔥

At the Pearl 4th of July festival in #Portland. #OregonExplored

This lavender field (I think that’s what it is? lol) at Elizabeth Caruthers Park in #Portland was simply stunning! 🤩 #OregonExplored #nofilter

A view of #Portland, as seen from the Eastbank Esplanade. #OregonExplored

Tip: use the W3C Link Checker and fix any errors before federating with Bridgy Fed.

https://validator.w3.org/checklink

If you are using Bridgy Fed to federate your posts from your personal site, I highly recommend you first run the W3C Link Checker on a post, and verify there are no “red” errors (or fix any you find), before pinging Bridgy Fed to federate the post.

The reason is that if your post contains broken links, especially broken https: links as part of an @-mention, a weird set of timeout interactions will occur between #BridgyFed and #Mastodon that will cause any Mastodon instances following your posts to drop your federated posts as if they had not been received.

Further, those instances will also ignore any UPDATES to that post.

More discussion here:
* https://chat.indieweb.org/dev/2024-09-04#t1725421768496000
More bug details here:
* https://github.com/snarfed/bridgy-fed/issues/884#issuecomment-2327861883

#IndieWeb #federate #fediverse #interoperability

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

https://tantek.com/2024/246/t1/adventures-indieweb-activitypub-bridgy-fed
→ 🔮
#BridgyFed #Mastodon #IndieWeb #federate #fediverse #interoperability #100PostsOfIndieWeb #100Posts
Happy 12 years of https://indieweb.org/POSSE #POSSE and
19 years of https://microformats.org/ #microformats! (as of yesterday, the 20th)

A few highlights from the past year:

POSSE (Publish on your Own Site, Syndicate Elsewhere) has grown steadily as a common practice in the #IndieWeb community, personal sites, CMSs (like Withknown, which itself reached 10 years in May!), and services (like https://micro.blog) for over a decade.

In its 12th year, POSSE broke through to broader technology press and adoption beyond the community. For example:

* David Pierce’s (@pierce@mas.to) excellent article @TheVerge.com (@verge@mastodon.social): “The poster’s guide to the internet of the future” (https://www.theverge.com/2023/10/23/23928550/posse-posting-activitypub-standard-twitter-tumblr-mastodon):
  “Your post appears natively on all of those platforms, typically with some kind of link back to your blog. And your blog becomes the hub for everything, your main home on the internet.
Done right, POSSE is the best of all posting worlds.”

* David also recorded a 29 minute podcast on POSSE with some great interviews: https://podcasts.apple.com/us/podcast/the-posters-guide-to-the-new-internet/id430333725?i=1000632256014

* Cory Doctorow (@craphound.com @doctorow@mamot.fr) declared in his Pluralistic blog (@pluralistic.net) post: “Vice surrenders” (https://pluralistic.net/2024/02/24/anti-posse/):
  “This is the moment for POSSE (Post Own Site, Share Everywhere [sic]), a strategy that sees social media as a strategy for bringing readers to channels that you control”

* And none other than Molly White (@mollywhite.net @molly0xfff@hachyderm.io) of @web3isgoinggreat.com (@web3isgreat@indieweb.social) built, deployed, and started actively using her own POSSE setup as described in her post titled “POSSE” (https://www.mollywhite.net/micro/entry/202403091817) to:
  "… write posts in the microblog and automatically crosspost them to Twitter/Mastodon/Bluesky, while keeping the original post on my site."
 
Congrats Molly and well done!


In its 19th year, the microformats formal #microformats2 syntax and popular vocabularies h-card, h-entry, and h-feed, kept growing across IndieWeb (micro)blogging services and software like CMSs & SSGs both for publishing, and richer peer-to-peer social web interactions via #Webmention.

Beyond the IndieWeb, the rel=me microformat, AKA #relMe, continues to be adopted by services to support #distributed #verification, such as these in the past year:

* Meta Platforms #Threads user profile "Link" field¹
* #Letterboxd user profile website field²


For both POSSE and microformats, there is always more we can do to improve their techniques, technologies, and tools to help people own their content and identities online, while staying connected to friends across the web.

Got suggestions for this coming year? Join us in chat:
* https://chat.indieweb.org/dev
* https://chat.indieweb.org/microformats
for discussions about POSSE and microformats, respectively.


Previously: https://tantek.com/2023/171/t1/anniversaries-microformats-posse


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

https://tantek.com/2024/151/t1/minimum-interesting-service-worker
https://tantek.com/2024/237/t1/people-over-protocols-platforms


Post glossary:

CMS
  https://indieweb.org/CMS
h-card
  https://microformats.org/wiki/h-card
h-entry
  https://microformats.org/wiki/h-entry
h-feed
  https://microformats.org/wiki/h-feed
microformats2 syntax
  https://microformats.org/wiki/microformats2-parsing
rel-me
  https://microformats.org/wiki/rel-me
SSG
  https://indieweb.org/SSG
Webmention
  https://indieweb.org/Webmention
Withknown
  https://indieweb.org/Known


References:

¹ https://tantek.com/2023/234/t1/threads-supports-indieweb-rel-me
² https://indieweb.org/rel-me#Letterboxd
#POSSE #microformats #IndieWeb #microformats2 #Webmention #relMe #distributed #verification #Threads #Letterboxd #100PostsOfIndieWeb #100Posts
Twenty years ago this past February, Kevin Marks and I introduced #microformats in a conference presentation.

Full post: https://tantek.com/2024/044/t1/twenty-years-microformats

Aside: This is an even shorter summary of that post from ~200 days ago, which #Mastodon readers never got due to a Mastodon #federation bug (details in https://tantek.com/t5Yo1).

Since early 2023, here are the top three updates & interesting developments in microformats:

1. Growing rel=me adoption for distributed verification (✅ in Mastodon etc.)
 * Wikipedia, Threads, omg.lol
2. Proposal to merge #microformats2 h-review into h-entry, since in practice (e.g. on #indieweb) reviews are just entries with a bit more.
3. #metaformats adoptions, implementations, iteration
#microformats #Mastodon #federation #microformats2 #indieweb #metaformats