The Handcrafted Artisanal Web

#social-computing #isles-of-blogging #john-scalzi #ryan-broderick #social-media
📗 Want to read How Infrastructure Works: Inside the Systems That Shape Our World by Deb Chachra ISBN: 9780593086599
Great article on #POSSE by David Pierce (@davidpierce@mastodon.social @pierce) @Verge:

https://www.theverge.com/2023/10/23/23928550/posse-posting-activitypub-standard-twitter-tumblr-mastodon

Several key points of POSSE explained in the article:


First, post on your own site:

 “In a POSSE world, everybody owns a domain name, and everybody has a blog. (… a place on the internet where you post your stuff and others consume it.)”
 

Second, syndicate elsewhere, appropriately for each destination:

 “Then, your long blog post might be broken into chunks and posted as a thread on X and Mastodon and Threads. The whole thing might go to your Medium page and your Tumblr and your LinkedIn profile, too. If you post a photo, it might go straight to Instagram, and a vertical video would whoosh straight to TikTok, Reels, and Shorts. Your post appears natively on all of those platforms,”

You can use Bridgy Publish (https://brid.gy/) to POSSE to many destinations, and Bridgy Fed (https://fed.brid.gy/) to #federate to #Mastodon and other #fediverse destinations, directly from your site instead of posting a copy on yet another account on yet another server.


Third, and this is a key piece that distinguishes proper POSSE setups, with original post perma(short)links back to your posts on your domain:

 “typically with some kind of link back to your blog.”
 

All copies link to (your) home.

 "And your blog becomes the hub for everything, your main home on the internet."
 

You have power over your domain (name), not outside silos.


David embedded a screenshot of one of my posts, a reply post:

screenshot of Tantek replying to a tweet by Zeldman.
in which I posted a reply *on my own site*¹ to @Zeldman.com’s tweet (itself a reply to a POSSE copy of one of my posts), and POSSEd my reply to Twitter so it would thread with his reply.

This illustrates another important detail of a proper POSSE setup:

Fourth, post *replies* and other responses from your own site, whether to other #IndieWeb sites, or to others’s silo posts (tweets etc.).

Own your data means owning your replies as well.


David also noted several challenges and good questions about POSSE. Some of these have answers & established practices, others are areas of exploration. E.g.

 "The first is the social side of social media: what do you do with all the likes, replies, comments, and everything else that comes with your posts?"
 
The short answer is #backfeed: https://indieweb.org/backfeed

Backfeed is a concept I first wrote about as “reverse syndication”².

As you syndicate your posts out to #socialMedia silos, you reverse syndicate any responses there back to your original post.

Your site can do this with a service like #Bridgy, which uses the #Webmention standard to forward such silo responses back to your site, and #BridgyFed which does same for responses from Mastodon to your #federated posts.


David asked many other questions, which are deserving of their own posts to help answer, so I’ll leave you with just one more:

 "The most immediate question, though, is simply how to build a POSSE system that works."

The short answer is: just start³.

Even if you have to do it manually (until it hurts), even if you have to edit your posts on a static GitHub site (behind your domain name of course), and then copy & paste to your silo(s) of choice, just start.

By practicing POSSE, even manually, you will learn what aspects of POSSE & backfeed matter the most to you, what aspects actually involve reaching & responding to friends and others you care about.

By doing so you will naturally focus on setting up & making what you need, and you too can join the future of web publishing, today.

Questions? Join us in the chat: https://chat.indieweb.org/ (also on Discord, IRC, and Slack)


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

← Day 45: https://tantek.com/2023/289/t1/bridgyfed-webmention-like-fediverse
→ 🔮


Post glossary:

backfeed / reverse syndication
  https://indieweb.org/backfeed
Bridgy
  https://brid.gy/
make what you need
  https://indieweb.org/make_what_you_need
manual (until it hurts)
  https://indieweb.org/manual_until_it_hurts
original post link
  https://indieweb.org/original_post_link
own your data
  https://indieweb.org/own_your_data
own your replies
  https://indieweb.org/own_your_replies
permalink
  https://indieweb.org/permalink
permashortlink
  https://indieweb.org/permashortlink
POSSE
  https://indieweb.org/POSSE
silo
  https://indieweb.org/silo
social media
  https://indieweb.org/social_media
static site
  https://indieweb.org/static_site
start
  https://indieweb.org/start
Webmention
  https://indieweb.org/Webmention


¹ https://tantek.com/2023/253/t2/
² https://tantek.com/2010/034/t2/diso-2-personal-domains-shortener-hatom-push-relmeauth
³ https://tantek.com/2023/001/t1/own-your-notes
https://indieweb.org/discuss
#POSSE #federate #Mastodon #fediverse #IndieWeb #backfeed: #socialMedia #Bridgy #Webmention #BridgyFed #federated #100DaysOfIndieWeb #100Days

Anil Dash gave a delightful keynote address at last week’s Oh, the Humanity! conference.

I checked and was not surprised to learn that Anil and I are very close in age. We were kids when personal computers were new and we were probably both in middle or high school when the web was born. We seem to have similar perspectives on the why of the open web: why building a more open web is — in addition to being fun — an important public good.

Anil’s framing is very personal, though, and I found it very moving. The full talk is available on YouTube and feels like it deserves more than its current ~650 views.

OAuth for Browser-Based Apps Draft 15

After a lot of discussion on the mailing list over the last few months, and after some excellent discussions at the OAuth Security Workshop, we've been working on revising the draft to provide clearer guidance and clearer discussion of the threats and consequences of the various architectural patterns in the draft.
was it absolutely necessary to run cables for ceiling mics in 5 rooms? definitely not. but now I am all set up to film a reality show 😂

I did the thing

Bronx Brewery

A full vegan menu

I woke up before taking a pizza out of the oven in a dream and now that's going to be bugging me all day

Bathroom remodel, day… wait what

pumpkins
Futura Coffee Roasters

at Futura Coffee Roasters

Bandcrash early alpha/beta/whatever released

Gate 30
This has to be one of the worst designed gates I've ever seen

October in New England

Omni La Costa Resort & Spa

at Omni La Costa Resort & Spa

Implemented liking/favoriting of #Mastodon posts via Bridgy Fed on my site! (Actually of any post on any site that #BridgyFed can discover an #ActivityPub endpoint to send likes to.)

Tested it by liking @evanp.me (@evan@cosocial.ca @evanpro)’s reply¹ confirming that he received a notification from my prior post². I sent a #Webmention from my like post³ to Bridgy Fed, and it #federated the like to Evan’s server, which subsequently showed up in the "favourites" list of Evan’s post:

https://cosocial.ca/@evan/111237962392745000/favourites

Every step that connects heterogenous #socialWeb systems & protocols feels like progress.

This is day 45 of #100DaysOfIndieWeb. #100Days #IndieWeb #like #likes #fediverse #favorite #favourite #favourites

← Day 44: https://tantek.com/2023/234/t1/threads-supports-indieweb-rel-me
→ 🔮

¹ https://cosocial.ca/@evan/111237962392745000
² https://tantek.com/2023/287/t1/federating-mentions
³ https://tantek.com/2023/289/f1
#Mastodon #BridgyFed #ActivityPub #Webmention #federated #socialWeb #100DaysOfIndieWeb #100Days #IndieWeb #like #likes #fediverse #favorite #favourite #favourites
Bar Verde

Last month of summer

Omni La Costa Resort & Spa

at Omni La Costa Resort & Spa