101010.pl

Tantek Çelik<a class="" href="https://snarfed.org" rel="nofollow noopener" target="_blank">@snarfed.org</a> posted a great overview of thoughtful (and sometimes heated) discussions across blogs and the <a class="" href="https://indieweb.social/tags/fediverse" rel="nofollow noopener" target="_blank">#fediverse</a> about how freely should “public” posts & comments on the web flow across sites: “Moderate people, not code” (<a class="" href="https://snarfed.org/2024-01-21_moderate-people-not-code" rel="nofollow noopener" target="_blank">https://snarfed.org/2024-01-21_moderate-people-not-code</a>) If you are designing or creating any kind of publishing or social features on the web, this post is for you. It touches on topics ranging from <a class="" href="https://indieweb.social/tags/contextCollapse" rel="nofollow noopener" target="_blank">#contextCollapse</a> to <a class="" href="https://indieweb.social/tags/federation" rel="nofollow noopener" target="_blank">#federation</a> to <a class="" href="https://indieweb.social/tags/moderation" rel="nofollow noopener" target="_blank">#moderation</a> and everything in between. Does your choice of publishing tool set expectations about where your content might propagate, or whether it will be indexed by search engines? Should it? Do the limitations of your server (e.g. js;dr) imply limitations of where your posts go, or whether they can be searched or archived? Should they? When you post something publicly, are you truly posting it for a global audience for all time, or only for one or a few more limited <a class="" href="https://indieweb.social/tags/publics" rel="nofollow noopener" target="_blank">#publics</a> for an ephemerality? When you reply to a post, do you expect your reply to only be visible in the context you posted it, or do you expect it to travel alongside that post to anywhere it might propagate to? On the <a class="" href="https://indieweb.social/tags/IndieWeb" rel="nofollow noopener" target="_blank">#IndieWeb</a>, especially for public posts, some of these questions have easier and more obvious answers, because the intent of nearly all public IndieWeb posts is to interact across the web with other posts and sites, typically via the <a class="" href="https://indieweb.social/tags/Webmention" rel="nofollow noopener" target="_blank">#Webmention</a> protocol. However there are still questions. Are the expectations for a blog and blogging different from a social media site, whether a silo or an instance on a network? Is a personal website with posts still just a blog, or does it become something new when you start posting responses from your site, or receiving (e.g. via Webmention) and displaying responses from across the web to your posts on your site? Or is it now a “social website”? If you have a social website, what is your responsibility for keeping it, well, social? Do you moderate Webmentions by default? Do you use the Vouch extension for some automatic moderation? Are <a class="" href="https://indieweb.social/tags/POSSE" rel="nofollow noopener" target="_blank">#POSSE</a> & <a class="" href="https://indieweb.social/tags/backfeed" rel="nofollow noopener" target="_blank">#backfeed</a> different from federation or are they the same thing from a user-perspective, with merely different names hinting at different implementations? Do you allow anyone from any site to respond or react to your posts? Or do you treat your social website like your home, and follow what I like to call a “house party protocol”, only letting in those you know, and perhaps allowing them to bring a +1 or 2? I have many more questions. Each of these deserves thoughtful discussions, documentation of what different tools & services do today that we can try out, learn from, and use to make considered decisions when creating new things to post on and across websites. This is post 4 of <a class="" href="https://indieweb.social/tags/100PostsOfIndieWeb" rel="nofollow noopener" target="_blank">#100PostsOfIndieWeb</a>. <a class="" href="https://indieweb.social/tags/100Posts" rel="nofollow noopener" target="_blank">#100Posts</a> ← <a class="" href="https://tantek.com/2024/022/t1/indiewebcamp-brighton-planned" rel="nofollow noopener" target="_blank">https://tantek.com/2024/022/t1/indiewebcamp-brighton-planned</a> → 🔮 Post glossary: backfeed   <a class="" href="https://indieweb.org/backfeed" rel="nofollow noopener" target="_blank">https://indieweb.org/backfeed</a> blog   <a class="" href="https://indieweb.org/blog" rel="nofollow noopener" target="_blank">https://indieweb.org/blog</a> blogging   <a class="" href="https://indieweb.org/blogging" rel="nofollow noopener" target="_blank">https://indieweb.org/blogging</a>   comments   <a class="" href="https://indieweb.org/comments" rel="nofollow noopener" target="_blank">https://indieweb.org/comments</a> context collapse   <a class="" href="https://indieweb.org/context_collapse" rel="nofollow noopener" target="_blank">https://indieweb.org/context_collapse</a> ephemerality   <a class="" href="https://indieweb.org/ephemerality" rel="nofollow noopener" target="_blank">https://indieweb.org/ephemerality</a> js;dr   <a class="" href="https://indieweb.org/js;dr" rel="nofollow noopener" target="_blank">https://indieweb.org/js;dr</a> moderation   <a class="" href="https://indieweb.org/moderation" rel="nofollow noopener" target="_blank">https://indieweb.org/moderation</a> POSSE   <a class="" href="https://indieweb.org/POSSE" rel="nofollow noopener" target="_blank">https://indieweb.org/POSSE</a> posts   <a class="" href="https://indieweb.org/posts" rel="nofollow noopener" target="_blank">https://indieweb.org/posts</a> publics   <a class="" href="https://indieweb.org/publics" rel="nofollow noopener" target="_blank">https://indieweb.org/publics</a> reply   <a class="" href="https://indieweb.org/reply" rel="nofollow noopener" target="_blank">https://indieweb.org/reply</a> Vouch   <a class="" href="https://indieweb.org/Vouch" rel="nofollow noopener" target="_blank">https://indieweb.org/Vouch</a>   Webmention   <a class="" href="https://indieweb.org/Webmention" rel="nofollow noopener" target="_blank">https://indieweb.org/Webmention</a>

Tantek ÇelikInspiring mix of perspective expanding and personal talks at border:none (<a class="" href="https://border-none.net/" rel="nofollow noopener" target="_blank">https://border-none.net/</a> <a class="h-cassis-username" href="https://twitter.com/border_none" rel="nofollow noopener" target="_blank">@border_none</a>) the past two days. Thanks speakers, volunteers, and especially organizers <a class="" href="https://marcthiele.com" rel="nofollow noopener" target="_blank">@marcthiele.com</a> (<a class="" href="https://mastodon.social/@marcthiele" rel="nofollow noopener" target="_blank">@marcthiele@mastodon.social</a> <a class="h-cassis-username" href="https://twitter.com/marcthiele" rel="nofollow noopener" target="_blank">@marcthiele</a>) and <a class="" href="https://jkphl.is" rel="nofollow noopener" target="_blank">@jkphl.is</a> (<a class="" href="https://mastodon.social/@jkphl" rel="nofollow noopener" target="_blank">@jkphl@mastodon.social</a> <a class="h-cassis-username" href="https://twitter.com/jkphl" rel="nofollow noopener" target="_blank">@jkphl</a>). Looking forward to the next two days at <a class="" href="https://indieweb.social/tags/IndieWebCamp" rel="nofollow noopener" target="_blank">#IndieWebCamp</a> Nürnberg <a class="" href="https://tollwerk.de" rel="nofollow noopener" target="_blank">@tollwerk.de</a> (<a class="" href="https://mastodon.social/@tollwerk" rel="nofollow noopener" target="_blank">@tollwerk@mastodon.social</a> <a class="h-cassis-username" href="https://twitter.com/tollwerk" rel="nofollow noopener" target="_blank">@tollwerk</a>) of personal site demos, brainstorming sessions, and making, creating, & hacking things from UX to protocols to improve & interconnect our websites, with each other ( <a class="" href="https://indieweb.social/tags/Webmention" rel="nofollow noopener" target="_blank">#Webmention</a> ), <a class="" href="https://indieweb.social/tags/fediverse" rel="nofollow noopener" target="_blank">#fediverse</a> ( <a class="" href="https://indieweb.social/tags/BridgyFed" rel="nofollow noopener" target="_blank">#BridgyFed</a> & <a class="" href="https://indieweb.social/tags/ActivityPub" rel="nofollow noopener" target="_blank">#ActivityPub</a> ), and others ( <a class="" href="https://indieweb.social/tags/POSSE" rel="nofollow noopener" target="_blank">#POSSE</a> <a class="" href="https://indieweb.social/tags/backfeed" rel="nofollow noopener" target="_blank">#backfeed</a> ). Still a few spots if you’re in town or can hop on a train and join us Saturday & Sunday! 🎟 Tickets: <a class="" href="https://ti.to/beyondtellerrand/bordernone-2023/with/kqyaidtq92k" rel="nofollow noopener" target="_blank">https://ti.to/beyondtellerrand/bordernone-2023/with/kqyaidtq92k</a> 🗓 Event: <a class="" href="https://events.indieweb.org/2023/10/indiewebcamp-nuremberg-2023-DmXe4dYdfagc" rel="nofollow noopener" target="_blank">https://events.indieweb.org/2023/10/indiewebcamp-nuremberg-2023-DmXe4dYdfagc</a> ℹ️ More info: <a class="" href="https://indieweb.org/2023/Nuremberg" rel="nofollow noopener" target="_blank">https://indieweb.org/2023/Nuremberg</a> <a class="" href="https://indieweb.social/tags/bordernone" rel="nofollow noopener" target="_blank">#bordernone</a> <a class="" href="https://indieweb.social/tags/bono23" rel="nofollow noopener" target="_blank">#bono23</a> <a class="" href="https://indieweb.social/tags/IndieWeb" rel="nofollow noopener" target="_blank">#IndieWeb</a>

Tantek ÇelikGreat article on <a class="" href="https://indieweb.social/tags/POSSE" rel="nofollow noopener" target="_blank">#POSSE</a> by David Pierce (<a class="" href="https://mastodon.social/@davidpierce" rel="nofollow noopener" target="_blank">@davidpierce@mastodon.social</a> <a class="h-cassis-username" href="https://twitter.com/pierce" rel="nofollow noopener" target="_blank">@pierce</a>) <a class="h-cassis-username" href="https://twitter.com/Verge" rel="nofollow noopener" target="_blank">@Verge</a>: <a class="" href="https://www.theverge.com/2023/10/23/23928550/posse-posting-activitypub-standard-twitter-tumblr-mastodon" rel="nofollow noopener" target="_blank">https://www.theverge.com/2023/10/23/23928550/posse-posting-activitypub-standard-twitter-tumblr-mastodon</a> 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 (<a class="" href="https://brid.gy/" rel="nofollow noopener" target="_blank">https://brid.gy/</a>) to POSSE to many destinations, and Bridgy Fed (<a class="" href="https://fed.brid.gy/" rel="nofollow noopener" target="_blank">https://fed.brid.gy/</a>) to <a class="" href="https://indieweb.social/tags/federate" rel="nofollow noopener" target="_blank">#federate</a> to <a class="" href="https://indieweb.social/tags/Mastodon" rel="nofollow noopener" target="_blank">#Mastodon</a> and other <a class="" href="https://indieweb.social/tags/fediverse" rel="nofollow noopener" target="_blank">#fediverse</a> 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: <a class="" href="https://tantek.com/2023/253/t2/" rel="nofollow noopener" target="_blank"></a> in which I posted a reply *on my own site*¹ to <a class="" href="https://Zeldman.com" rel="nofollow noopener" target="_blank">@Zeldman.com</a>’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 <a class="" href="https://indieweb.social/tags/IndieWeb" rel="nofollow noopener" target="_blank">#IndieWeb</a> 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 <a class="" href="https://indieweb.social/tags/backfeed:" rel="nofollow noopener" target="_blank">#backfeed:</a> <a class="" href="https://indieweb.org/backfeed" rel="nofollow noopener" target="_blank">https://indieweb.org/backfeed</a> Backfeed is a concept I first wrote about as “reverse syndication”². As you syndicate your posts out to <a class="" href="https://indieweb.social/tags/socialMedia" rel="nofollow noopener" target="_blank">#socialMedia</a> silos, you reverse syndicate any responses there back to your original post. Your site can do this with a service like <a class="" href="https://indieweb.social/tags/Bridgy" rel="nofollow noopener" target="_blank">#Bridgy</a>, which uses the <a class="" href="https://indieweb.social/tags/Webmention" rel="nofollow noopener" target="_blank">#Webmention</a> standard to forward such silo responses back to your site, and <a class="" href="https://indieweb.social/tags/BridgyFed" rel="nofollow noopener" target="_blank">#BridgyFed</a> which does same for responses from Mastodon to your <a class="" href="https://indieweb.social/tags/federated" rel="nofollow noopener" target="_blank">#federated</a> 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: <a class="" href="https://chat.indieweb.org/" rel="nofollow noopener" target="_blank">https://chat.indieweb.org/</a> (also on Discord, IRC, and Slack⁴) This is day 46 of <a class="" href="https://indieweb.social/tags/100DaysOfIndieWeb" rel="nofollow noopener" target="_blank">#100DaysOfIndieWeb</a>. <a class="" href="https://indieweb.social/tags/100Days" rel="nofollow noopener" target="_blank">#100Days</a> ← Day 45: <a class="" href="https://tantek.com/2023/289/t1/bridgyfed-webmention-like-fediverse" rel="nofollow noopener" target="_blank">https://tantek.com/2023/289/t1/bridgyfed-webmention-like-fediverse</a> → 🔮 Post glossary: backfeed / reverse syndication   <a class="" href="https://indieweb.org/backfeed" rel="nofollow noopener" target="_blank">https://indieweb.org/backfeed</a> Bridgy   <a class="" href="https://brid.gy/" rel="nofollow noopener" target="_blank">https://brid.gy/</a> make what you need   <a class="" href="https://indieweb.org/make_what_you_need" rel="nofollow noopener" target="_blank">https://indieweb.org/make_what_you_need</a> manual (until it hurts)   <a class="" href="https://indieweb.org/manual_until_it_hurts" rel="nofollow noopener" target="_blank">https://indieweb.org/manual_until_it_hurts</a> original post link   <a class="" href="https://indieweb.org/original_post_link" rel="nofollow noopener" target="_blank">https://indieweb.org/original_post_link</a> own your data   <a class="" href="https://indieweb.org/own_your_data" rel="nofollow noopener" target="_blank">https://indieweb.org/own_your_data</a> own your replies   <a class="" href="https://indieweb.org/own_your_replies" rel="nofollow noopener" target="_blank">https://indieweb.org/own_your_replies</a> permalink   <a class="" href="https://indieweb.org/permalink" rel="nofollow noopener" target="_blank">https://indieweb.org/permalink</a> permashortlink   <a class="" href="https://indieweb.org/permashortlink" rel="nofollow noopener" target="_blank">https://indieweb.org/permashortlink</a> POSSE   <a class="" href="https://indieweb.org/POSSE" rel="nofollow noopener" target="_blank">https://indieweb.org/POSSE</a> silo   <a class="" href="https://indieweb.org/silo" rel="nofollow noopener" target="_blank">https://indieweb.org/silo</a> social media   <a class="" href="https://indieweb.org/social_media" rel="nofollow noopener" target="_blank">https://indieweb.org/social_media</a> static site   <a class="" href="https://indieweb.org/static_site" rel="nofollow noopener" target="_blank">https://indieweb.org/static_site</a> start   <a class="" href="https://indieweb.org/start" rel="nofollow noopener" target="_blank">https://indieweb.org/start</a> Webmention   <a class="" href="https://indieweb.org/Webmention" rel="nofollow noopener" target="_blank">https://indieweb.org/Webmention</a> ¹ <a class="" href="https://tantek.com/2023/253/t2/" rel="nofollow noopener" target="_blank">https://tantek.com/2023/253/t2/</a> ² <a class="" href="https://tantek.com/2010/034/t2/diso-2-personal-domains-shortener-hatom-push-relmeauth" rel="nofollow noopener" target="_blank">https://tantek.com/2010/034/t2/diso-2-personal-domains-shortener-hatom-push-relmeauth</a> ³ <a class="" href="https://tantek.com/2023/001/t1/own-your-notes" rel="nofollow noopener" target="_blank">https://tantek.com/2023/001/t1/own-your-notes</a> ⁴ <a class="" href="https://indieweb.org/discuss" rel="nofollow noopener" target="_blank">https://indieweb.org/discuss</a>

Recent searches

Search options

Administered by:

Server stats:

#backfeed