Updates tagged with fediverse on stadeus!
: 🎂 Congrats @microformats.org on 20 years! #microformats20Even after 20 years, people keep discovering new ways of using #microformats:* @artlung.com: "WML, WAP, & Microformats Demo!" (https://lab.artlung.com/wml/faux)> Because WML elements may have the class attributeOriginally posted 2025-06-18: https://xoxo.zone/@artlung/114705990062730513That adds to the list of languages with working microformats examples:* HTML — modern, unversioned as well as every version since HTML4* HTML3 — see https://microformats.org/wiki/html3* SVG — see https://microformats.org/wiki/svg* XHTML — every version, 1.0, 1.1, 2.0and now also:* WML — https://microformats.org/wiki/wmlLiterally any HTML-like or XML-like language that has a space-separated class attribute can work with microformats.In constrast, every alternative to microformats (most now defunct) required adding new attributes, or worse, entirely new elements, which meant revising every language one at a time (or use of fragile XML Namespaces), resulting in supporting only 1-2 languages at most (HTML and XHTML) in practice, and nothing else.Re-using the "class" attribute based on the existing footpath that web designers made for encoding additional semantics into their HTML, and the similarly extensible "rel" attribute, was one of the best design decisions in any extension format ever.After 20 years, microformats continue to serve as another example of “loosely joined” approaches being more adaptable, reliable, resilient, and longer lasting than “tightly coupled”.More microformats 20th anniversary posts from the #indieweb personal sites (via https://stream.indieweb.org/)* @manton.org: "It’s the 20th anniversary of the launch of microforrmats.org!" (https://www.manton.org/2025/06/20/its-the-th-anniversary-of.html)* ... hashtag your post #microformats or #microformats20 and #federate (using #Mastodon or any compatible #fediverse server etc.) or webmention this post!#20thAnniversary #smallPieces #looselyJoinedPreviously, previously, previously:* https://tantek.com/2024/173/t1/years-posse-microformats-beyond* https://tantek.com/2023/171/t1/anniversaries-microformats-posse* https://tantek.com/2019/171/t1/happy-14th-microformats-org
's status on Friday, 20-Jun-2025 20:48:00 EDT
🎂 Congrats @microformats.org on 20 years! #microformats20 Even after 20 years, people keep discovering new ways of using #microformats: * @artlung.com: "WML, WAP, & Microformats Demo!" (https://lab.artlung.com/wml/faux) > Because WML elements may have the class attribute Originally posted 2025-06-18: https://xoxo.zone/@artlung/114705990062730513 That adds to the list of languages with working microformats examples: * HTML — modern, unversioned as well as every version since HTML4 * HTML3 — see https://microformats.org/wiki/html3 * SVG — see https://microformats.org/wiki/svg * XHTML — every version, 1.0, 1.1, 2.0 and now also: * WML — https://microformats.org/wiki/wml Literally any HTML-like or XML-like language that has a space-separated class attribute can work with microformats. In constrast, every alternative to microformats (most now defunct) required adding new attributes, or worse, entirely new elements, which meant revising every language one at a time (or use of fragile XML Namespaces), resulting in supporting only 1-2 languages at most (HTML and XHTML) in practice, and nothing else. Re-using the "class" attribute based on the existing footpath that web designers made for encoding additional semantics into their HTML, and the similarly extensible "rel" attribute, was one of the best design decisions in any extension format ever. After 20 years, microformats continue to serve as another example of “loosely joined” approaches being more adaptable, reliable, resilient, and longer lasting than “tightly coupled”. More microformats 20th anniversary posts from the #indieweb personal sites (via https://stream.indieweb.org/) * @manton.org: "It’s the 20th anniversary of the launch of microforrmats.org!" (https://www.manton.org/2025/06/20/its-the-th-anniversary-of.html) * ... hashtag your post #microformats or #microformats20 and #federate (using #Mastodon or any compatible #fediverse server etc.) or webmention this post! #20thAnniversary #smallPieces #looselyJoined Previously, previously, previously: * https://tantek.com/2024/173/t1/years-posse-microformats-beyond * https://tantek.com/2023/171/t1/anniversaries-microformats-posse * https://tantek.com/2019/171/t1/happy-14th-microformats-org
: Last week I published my first Cybersecurity Friday post with three key steps for indieweb cybersecurity. In summary:1. Email MFA/2FA. Add multi-factor authentication (sometimes called two-factor authentication) to everywhere you store or check email. Do not use phone/cell numbers.2. Domain Registrar MFA. Add multi-factor authentication to your domain registrar account.3. Web Host MFA. Same for your web host and any intermediate name servers (DNS) or content delivery network (CDN) service accounts.Full post: https://tantek.com/2025/052/b1/steps-indieweb-cybersecurityNext time: entropy is your friend in security.If you want my #Cybersecurity Friday posts as soon as I publish them, follow my site https://tantek.com/ directly in your reader rather than using #socialMedia or #Mastodon or some other notes-centric #fediverse client.You can subscribe to my site directly with an h-feed supporting #indieweb Social Reader, or if you use a classic feed reader, it can auto-discover my Atom feed from my home page.You can also read my article blog posts and those from other Mozillians on the Mozilla Planet:* https://planet.mozilla.org/If you look closely you might even find my not-so-secret articles-only Atom feed linked there if you prefer.This is post 9 of #100PostsOfIndieWeb. #100Posts #cyber #security← https://tantek.com/2025/020/t1/seek-2024-year-in-review→ 🔮Glossaryarticle post https://indieweb.org/articleAtom https://indieweb.org/Atomcontent delivery network https://indieweb.org/content_delivery_networkcybersecurity https://en.wikipedia.org/wiki/cybersecurityDNS https://indieweb.org/DNSdomain registrar https://indieweb.org/domain_registrarentropy https://en.wikipedia.org/wiki/Entropy_(information_theory)feed reader https://indieweb.org/feed_readerh-feed https://indieweb.org/h-feedMFA / 2FA https://indieweb.org/multi-factor_authentication sometimes called Two Factor Authentication or Second Factor Authenticationmobile number for MFA https://indieweb.org/SMS#Criticismnote post https://indieweb.org/notesocial reader https://indieweb.org/social_readerweb host https://indieweb.org/web_hosting
's status on Monday, 24-Feb-2025 19:10:00 EST
Last week I published my first Cybersecurity Friday post with three key steps for indieweb cybersecurity. In summary: 1. Email MFA/2FA. Add multi-factor authentication (sometimes called two-factor authentication) to everywhere you store or check email. Do not use phone/cell numbers. 2. Domain Registrar MFA. Add multi-factor authentication to your domain registrar account. 3. Web Host MFA. Same for your web host and any intermediate name servers (DNS) or content delivery network (CDN) service accounts. Full post: https://tantek.com/2025/052/b1/steps-indieweb-cybersecurity Next time: entropy is your friend in security. If you want my #Cybersecurity Friday posts as soon as I publish them, follow my site https://tantek.com/ directly in your reader rather than using #socialMedia or #Mastodon or some other notes-centric #fediverse client. You can subscribe to my site directly with an h-feed supporting #indieweb Social Reader, or if you use a classic feed reader, it can auto-discover my Atom feed from my home page. You can also read my article blog posts and those from other Mozillians on the Mozilla Planet: * https://planet.mozilla.org/ If you look closely you might even find my not-so-secret articles-only Atom feed linked there if you prefer. This is post 9 of #100PostsOfIndieWeb. #100Posts #cyber #security ← https://tantek.com/2025/020/t1/seek-2024-year-in-review → 🔮 Glossary article post https://indieweb.org/article Atom https://indieweb.org/Atom content delivery network https://indieweb.org/content_delivery_network cybersecurity https://en.wikipedia.org/wiki/cybersecurity DNS https://indieweb.org/DNS domain registrar https://indieweb.org/domain_registrar entropy https://en.wikipedia.org/wiki/Entropy_(information_theory) feed reader https://indieweb.org/feed_reader h-feed https://indieweb.org/h-feed MFA / 2FA https://indieweb.org/multi-factor_authentication sometimes called Two Factor Authentication or Second Factor Authentication mobile number for MFA https://indieweb.org/SMS#Criticism note post https://indieweb.org/note social reader https://indieweb.org/social_reader web host https://indieweb.org/web_hosting
: The team @micro.blog have done it again.They soft-launched https://micro.one yesterday¹.This may be the most accessible onramp to the open social web ever.Cost: $1 a month. Yes you read correctly.This is the simplest and cheapest (where you are the customer, not the product) way to own your identity and content online².Stop posting in someone else’s garage³.Time to export your Twitter, and migrate your Mastodon handle to your own home on the web.Of course you can bring your own domain name. Additionally:* blog posts, naturally, both articles and microblogging notes* photos* podcasting* custom themes* web-clients and native mobile posting clients* WordPress, Tumblr, Mastodon, Medium importMore details (and alternatives) at https://micro.one/about/pricingAnd yes, it interoperates with the open #socialWeb, including:* #ActivityPub support, #Mastodon and #fediverse compatibility* #IndieAuth to sign-in to third-party apps* #microformats support in all built-in themes* #Webmention for sending and receiving replies across websites* #Micropub standard posting API, supporting dozens of clients* #Microsub standard timeline API, supporting social readersMore #indieweb support details at https://micro.one/about/indiewebDid I mention the the superb micro.blog (and micro.one) Community Guidelines?* https://help.micro.blog/t/community-guidelines/39Well done @manton.org and team.This is post 6 of #100PostsOfIndieWeb. #100Posts #ownYourIdentity #ownYourData #openSocialWeb← https://tantek.com/2025/003/t1/lastfm-year-in-review-playback24→ 🔮GlossaryIndieAuth https://indieweb.org/IndieAuthmicroformats https://microformats.org/wiki/microformatsMicropub https://indieweb.org/MicropubMicrosub https://indieweb.org/MicrosubWebmention https://indieweb.org/Webmention¹ https://www.manton.org/2025/01/03/microone-was-effectively-a-softlaunch.html² https://tantek.com/2025/001/t1/15-years-notes-my-site-first³ https://tantek.com/2023/022/t2/own-your-notes-domain-migration
's status on Saturday, 04-Jan-2025 23:48:00 EST
The team @micro.blog have done it again. They soft-launched https://micro.one yesterday¹. This may be the most accessible onramp to the open social web ever. Cost: $1 a month. Yes you read correctly. This is the simplest and cheapest (where you are the customer, not the product) way to own your identity and content online². Stop posting in someone else’s garage³. Time to export your Twitter, and migrate your Mastodon handle to your own home on the web. Of course you can bring your own domain name. Additionally: * blog posts, naturally, both articles and microblogging notes * photos * podcasting * custom themes * web-clients and native mobile posting clients * WordPress, Tumblr, Mastodon, Medium import More details (and alternatives) at https://micro.one/about/pricing And yes, it interoperates with the open #socialWeb, including: * #ActivityPub support, #Mastodon and #fediverse compatibility * #IndieAuth to sign-in to third-party apps * #microformats support in all built-in themes * #Webmention for sending and receiving replies across websites * #Micropub standard posting API, supporting dozens of clients * #Microsub standard timeline API, supporting social readers More #indieweb support details at https://micro.one/about/indieweb Did I mention the the superb micro.blog (and micro.one) Community Guidelines? * https://help.micro.blog/t/community-guidelines/39 Well done @manton.org and team. This is post 6 of #100PostsOfIndieWeb. #100Posts #ownYourIdentity #ownYourData #openSocialWeb ← https://tantek.com/2025/003/t1/lastfm-year-in-review-playback24 → 🔮 Glossary IndieAuth https://indieweb.org/IndieAuth microformats https://microformats.org/wiki/microformats Micropub https://indieweb.org/Micropub Microsub https://indieweb.org/Microsub Webmention https://indieweb.org/Webmention ¹ https://www.manton.org/2025/01/03/microone-was-effectively-a-softlaunch.html ² https://tantek.com/2025/001/t1/15-years-notes-my-site-first ³ https://tantek.com/2023/022/t2/own-your-notes-domain-migration
: Day 1 of #IndieWebCamp #Berlin 2024¹ was very well attended!* 20 participants, more than 3x the previous one in 2022, and second highest (2019 had 22).* 18 introduced themselves² and their personal sites or aspirations for oneCollectively we proposed and facilitated 11 breakout sessions³ on many timely #indieweb topics covering #syndication, #inclusion, #longevity, #federation / #fediverse, how to best use #Mastodon with your personal site, #privacy and #security concerns of being online, #writing, how can we design better user interfaces for text authoring, and personalized reading #algorithms for staying connected with friends.Session titles (and hashtags)* How to #POSSE* How to make the web queerer / stranger. #queer* Online presence after our #death* Threat modeling #threatmodeling* Non-technical collaboration on the internet. #collab* Locations and #places check-in* Writing with images. #imagewriting* Text authoring UX. #textUX* #SSR, organizing CSS/JS* Website design without being a designer. #designfordummies* Timeline algorithms. #timelinesEtherpad notes from sessions have been archived to the wiki, with session recordings to follow!Day 2 also had 20 in-person participants, the highest IndieWebCamp Berlin day 2 attendance ever! Most everyone from day 1 came back to hack, and three new people showed up. We also had several remote participants.References ¹ https://indieweb.org/2024² https://indieweb.org/2024/Berlin/Intros³ https://indieweb.org/2024/Berlin/Schedule#SaturdayThis is post 28 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2024/306/t1/simple-embeds→ 🔮
's status on Saturday, 09-Nov-2024 08:31:00 EST
Day 1 of #IndieWebCamp #Berlin 2024¹ was very well attended! * 20 participants, more than 3x the previous one in 2022, and second highest (2019 had 22). * 18 introduced themselves² and their personal sites or aspirations for one Collectively we proposed and facilitated 11 breakout sessions³ on many timely #indieweb topics covering #syndication, #inclusion, #longevity, #federation / #fediverse, how to best use #Mastodon with your personal site, #privacy and #security concerns of being online, #writing, how can we design better user interfaces for text authoring, and personalized reading #algorithms for staying connected with friends. Session titles (and hashtags) * How to #POSSE * How to make the web queerer / stranger. #queer * Online presence after our #death * Threat modeling #threatmodeling * Non-technical collaboration on the internet. #collab * Locations and #places check-in * Writing with images. #imagewriting * Text authoring UX. #textUX * #SSR, organizing CSS/JS * Website design without being a designer. #designfordummies * Timeline algorithms. #timelines Etherpad notes from sessions have been archived to the wiki, with session recordings to follow! Day 2 also had 20 in-person participants, the highest IndieWebCamp Berlin day 2 attendance ever! Most everyone from day 1 came back to hack, and three new people showed up. We also had several remote participants. References ¹ https://indieweb.org/2024 ² https://indieweb.org/2024/Berlin/Intros ³ https://indieweb.org/2024/Berlin/Schedule#Saturday This is post 28 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2024/306/t1/simple-embeds → 🔮
: No I did not block you on the #fediverse / #Mastodon / #Misskey etc.If you were following me @tantek.com on your client/server/instance of choice but noticed you were no longer doing so, that was due to a recent software bug in my fediverse provider which accidentally caused everyone’s #ActivityPub servers to unfollow me (bug details below).No it’s absolutely not your fault, you did nothing wrong.We need a variant of Hanlon’s Razor¹ like:“Never attribute to malice that which is adequately explained by a software bug.”Take another look at my posts if you want (directly on @tantek.com or try searching for that on your instance) and if you like what you see or find them otherwise informative and useful, feel free to refollow. If not, no worries!Also no worries if you ever unfollow/refollow for any reason. I mean that. I always assume people know best how to manage their online reader/reading experiences, everyone’s priorities and likes/dislikes change over time, and encourage everyone to make choices that are best for their mental health and overall joy online.Bug details:This was due to a #BridgyFed bug² that deleted my profile (“ActivityPub actor”) from (nearly?) all instances, making everyone’s accounts automatically unfollow me, as well as remove any of my posts from your likes and reposts (boosts) collections. It also removed my posts from any of your replies to my posts, leaving your replies dangling without reply-contexts. Apologies!The bug was introduced accidentally as part of another fix about a month ago³, and was triggered within the following week⁴.Anyone following me before ~2024-09-22 was no longer following me. A few folks have noticed and refollowed. Any likes or reposts of my posts before that date were also undone (removed).Ryan (@snarfed.org) has been really good about giving folks a heads-up, and apologizing, and quickly doing what he can to fix things.Bugs happen, yes even in production code, so please do not post/send any hate.I’d rather be one of the folks helping with improving BridgyFed, and temporary setbacks like this are part of being an early / eager #IndieWeb adopter.This bug has also revealed some potential weaknesses in other ActivityPub implementations. E.g. deleting an “actor” should be undoable, and undoing a delete should reconnect everything, from follows to likes & reposts collections, to reply-contexts. Perhaps the ActivityPub specification could be updated with such guidance (if it hasn’t been already, I need to double-check).To be clear, I’m still a big supporter of #BridgyFed, #ActivityPub, #Webmention, and everyone who chooses to implement these and other #IndieWeb related and adjacent protocols as best fits their products and services. All of these are a part of our broader open #socialWeb, and making all these #openStandards work well together (including handling edge-cases and mistakes!) is essential for providing #socialMedia alternatives that put users first.References:¹ https://en.wikipedia.org/wiki/Hanlon%27s_razor² https://github.com/snarfed/bridgy-fed/issues/1379³ https://github.com/snarfed/bridgy-fed/commit/4df76d0db7b87cabbd714039546c05b3221169be⁴ https://chat.indieweb.org/dev/2024-09-22#t1727028174623700This is post 26 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2024/285/t1/io-domain-suggested-steps→ 🔮
's status on Sunday, 13-Oct-2024 16:37:00 EDT
No I did not block you on the #fediverse / #Mastodon / #Misskey etc. If you were following me @tantek.com on your client/server/instance of choice but noticed you were no longer doing so, that was due to a recent software bug in my fediverse provider which accidentally caused everyone’s #ActivityPub servers to unfollow me (bug details below). No it’s absolutely not your fault, you did nothing wrong. We need a variant of Hanlon’s Razor¹ like: “Never attribute to malice that which is adequately explained by a software bug.” Take another look at my posts if you want (directly on @tantek.com or try searching for that on your instance) and if you like what you see or find them otherwise informative and useful, feel free to refollow. If not, no worries! Also no worries if you ever unfollow/refollow for any reason. I mean that. I always assume people know best how to manage their online reader/reading experiences, everyone’s priorities and likes/dislikes change over time, and encourage everyone to make choices that are best for their mental health and overall joy online. Bug details: This was due to a #BridgyFed bug² that deleted my profile (“ActivityPub actor”) from (nearly?) all instances, making everyone’s accounts automatically unfollow me, as well as remove any of my posts from your likes and reposts (boosts) collections. It also removed my posts from any of your replies to my posts, leaving your replies dangling without reply-contexts. Apologies! The bug was introduced accidentally as part of another fix about a month ago³, and was triggered within the following week⁴. Anyone following me before ~2024-09-22 was no longer following me. A few folks have noticed and refollowed. Any likes or reposts of my posts before that date were also undone (removed). Ryan (@snarfed.org) has been really good about giving folks a heads-up, and apologizing, and quickly doing what he can to fix things. Bugs happen, yes even in production code, so please do not post/send any hate. I’d rather be one of the folks helping with improving BridgyFed, and temporary setbacks like this are part of being an early / eager #IndieWeb adopter. This bug has also revealed some potential weaknesses in other ActivityPub implementations. E.g. deleting an “actor” should be undoable, and undoing a delete should reconnect everything, from follows to likes & reposts collections, to reply-contexts. Perhaps the ActivityPub specification could be updated with such guidance (if it hasn’t been already, I need to double-check). To be clear, I’m still a big supporter of #BridgyFed, #ActivityPub, #Webmention, and everyone who chooses to implement these and other #IndieWeb related and adjacent protocols as best fits their products and services. All of these are a part of our broader open #socialWeb, and making all these #openStandards work well together (including handling edge-cases and mistakes!) is essential for providing #socialMedia alternatives that put users first. References: ¹ https://en.wikipedia.org/wiki/Hanlon%27s_razor ² https://github.com/snarfed/bridgy-fed/issues/1379 ³ https://github.com/snarfed/bridgy-fed/commit/4df76d0db7b87cabbd714039546c05b3221169be ⁴ https://chat.indieweb.org/dev/2024-09-22#t1727028174623700 This is post 26 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2024/285/t1/io-domain-suggested-steps → 🔮
: Tip: use the W3C Link Checker and fix any errors before federating with Bridgy Fed.https://validator.w3.org/checklinkIf 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#t1725421768496000More bug details here:* https://github.com/snarfed/bridgy-fed/issues/884#issuecomment-2327861883#IndieWeb #federate #fediverse #interoperabilityThis is post 22 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2024/246/t1/adventures-indieweb-activitypub-bridgy-fed→ 🔮
's status on Wednesday, 04-Sep-2024 02:11:00 EDT
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 → 🔮
: Adventures in IndieWeb / ActivityPub (AP) bridging:While in general my posts are being successfully federated by https://fed.brid.gy/ (#BridgyFed), my most recent three posts, and two more earlier this year, were delivered successfully to multiple #Mastodon instances AP inboxes (returned 202), however the posts do not show up if you look-up my profile on those instances (and thus followers never saw them).These most recent posts:* https://tantek.com/2024/245/t1/read-write-suggest-edit-web* https://tantek.com/2024/242/t1/indiewebcamp-portland* https://tantek.com/2024/238/t3/indiewebcamp-auto-linkingand these earlier this year:* https://tantek.com/2024/173/t1/years-posse-microformats-adoption* https://tantek.com/2024/044/t1/twenty-years-microformatswere all delivered to over 300 instances, which returned "202" codes, however none of them show up in profile views on those instances, e.g.* https://indieweb.social/@tantek.com@tantek.com* https://mastodon.social/@tantek.com@tantek.com* https://social.coop/@tantek.com@tantek.com* https://w3c.social/@tantek.com@tantek.com(My most recent post on all of these is the same 2024-08-25 post starting with “All setup here at IndieWebCamp Portland!”)Why would a Mastodon instance respond with a 202 to an AP inbox delivery and then not show that post on the local profile view?GitHub tracking bug in case you can help narrow/track this down or have * https://github.com/snarfed/bridgy-fed/issues/884Let’s see if this post makes it to your Mastodon (or other #fediverse) reader/client.#indieweb #ActivityPub This is post 21 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2024/245/t1/read-write-suggest-edit-web→ 🔮
's status on Tuesday, 03-Sep-2024 01:32:00 EDT
Adventures in IndieWeb / ActivityPub (AP) bridging: While in general my posts are being successfully federated by https://fed.brid.gy/ (#BridgyFed), my most recent three posts, and two more earlier this year, were delivered successfully to multiple #Mastodon instances AP inboxes (returned 202), however the posts do not show up if you look-up my profile on those instances (and thus followers never saw them). These most recent posts: * https://tantek.com/2024/245/t1/read-write-suggest-edit-web * https://tantek.com/2024/242/t1/indiewebcamp-portland * https://tantek.com/2024/238/t3/indiewebcamp-auto-linking and these earlier this year: * https://tantek.com/2024/173/t1/years-posse-microformats-adoption * https://tantek.com/2024/044/t1/twenty-years-microformats were all delivered to over 300 instances, which returned "202" codes, however none of them show up in profile views on those instances, e.g. * https://indieweb.social/@tantek.com@tantek.com * https://mastodon.social/@tantek.com@tantek.com * https://social.coop/@tantek.com@tantek.com * https://w3c.social/@tantek.com@tantek.com (My most recent post on all of these is the same 2024-08-25 post starting with “All setup here at IndieWebCamp Portland!”) Why would a Mastodon instance respond with a 202 to an AP inbox delivery and then not show that post on the local profile view? GitHub tracking bug in case you can help narrow/track this down or have * https://github.com/snarfed/bridgy-fed/issues/884 Let’s see if this post makes it to your Mastodon (or other #fediverse) reader/client. #indieweb #ActivityPub This is post 21 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2024/245/t1/read-write-suggest-edit-web → 🔮
: All setup here at IndieWebCamp Portland!https://events.indieweb.org/2024/08/indiewebcamp-portland-2024-8bucXDlLqR0kGood crowd of participants from #XOXO #XOXOConf (@xoxofest.com @xoxo@xoxo.zone @xoxo) here to work on their personal website(s), domains, or other independent social media setups!As encouraged by Andy Baio (@waxy.org @andybaio@xoxo.zone @waxpancake)“Every one of you should have a home on the web not controlled by a billionaire.”If you’re in #Portland and want help, encouragement, or camaraderie in getting setup or doing more with your personal site, come on by! We’ll be having a mix of discussion sessions and create/hack sessions. Personal site and hack demos at 16:00 PDT!#indieweb #fediverse #ActivityPub #decentralized #socialMediaThis is post 17 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2024/237/t1/people-over-protocols-platforms→ 🔮
's status on Sunday, 25-Aug-2024 13:18:00 EDT
All setup here at IndieWebCamp Portland! https://events.indieweb.org/2024/08/indiewebcamp-portland-2024-8bucXDlLqR0k Good crowd of participants from #XOXO #XOXOConf (@xoxofest.com @xoxo@xoxo.zone @xoxo) here to work on their personal website(s), domains, or other independent social media setups! As encouraged by Andy Baio (@waxy.org @andybaio@xoxo.zone @waxpancake) “Every one of you should have a home on the web not controlled by a billionaire.” If you’re in #Portland and want help, encouragement, or camaraderie in getting setup or doing more with your personal site, come on by! We’ll be having a mix of discussion sessions and create/hack sessions. Personal site and hack demos at 16:00 PDT! #indieweb #fediverse #ActivityPub #decentralized #socialMedia This is post 17 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2024/237/t1/people-over-protocols-platforms → 🔮
: People over protocols over platforms.inspired by today’s #indieweb #fediverse #ActivityPub #decentralized #socialMedia lunch meetup at #XOXO #XOXOConf (@xoxo@xoxo.zone)This is post 16 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2024/173/t1/years-posse-microformats-adoption→ 🔮
's status on Saturday, 24-Aug-2024 19:56:00 EDT
People over protocols over platforms. inspired by today’s #indieweb #fediverse #ActivityPub #decentralized #socialMedia lunch meetup at #XOXO #XOXOConf (@xoxo@xoxo.zone) This is post 16 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2024/173/t1/years-posse-microformats-adoption → 🔮
: https://www.threads.net/@0xjessel/post/Cvu7-42PVpCPreviously: https://tantek.com/2023/234/t1/threads-supports-indieweb-rel-me#microformats #relme #fediverse #Threads
's status on Saturday, 23-Mar-2024 19:05:00 EDT
https://www.threads.net/@0xjessel/post/Cvu7-42PVpC Previously: https://tantek.com/2023/234/t1/threads-supports-indieweb-rel-me #microformats #relme #fediverse #Threads
: What I created while remotely participating at #IndieWebCamp Brighton 2024: wiki-gardened day 1’s BarCamp sessions notes pages, and documented my @-mention @-@-mention autolinking coding improvements I built the Sunday before.Day 2 of IndieWebCamps is Create Day, where everyone is encouraged to create, make, or build something for their personal website, or the IndieWeb community, or both.At the start of day 2, everyone is encourage to pick things to make¹. What to make at an IndieWebCamp² can be anything from setting up your personal website, to writing a blog post, redesigning your styling, building new features, helping other participants, or contributing to shared IndieWeb community resources, whether code or content. Everyone is encouraged to at least pick something they consider easy, that they can do in less than an hour, then a more bold goal, and then perhaps a stretch goal, something challenging that may require collaboration, asking for help, or breaking into smaller steps.For my "easy" task, I built on what another remote participant, @gregorlove.com completed the night before. gRegor had archived all the IndieWebCamp Brighton Sessions Etherpads onto the wiki, linked from the Schedule page³. gRegor had noted that he didn’t have time to clean-up the pages, e.g. convert and fix Markdown links.I went through the 13 Session Notes archives and did the following:* converted Markdown links to MediaWiki links* converted indieweb.org (and some services) links to local wiki page links* fixed (some) typosWith some help from @alexsirac.com (@alexture@todo.eu), I figured out how to create a MediaWiki Contributions summary link of my edits:* https://indieweb.org/wiki/index.php?title=Special:Contributions&target=Tantek.com&namespace=all&start=2024-03-10&end=2024-03-10&offset=20240310143900&limit=25I point this out to provide an example of an IndieWeb Create Day project that is:* incremental on top of someone else’s work* community contribution rather a personal-focused project* editing and wiki-gardening as valid contributions, not just creating new contentI point this out to illustrate some of the IndieWeb community's recognitions & values in contrast to typical corporate cultures and incentive systems which often only reward:* new innovations (not incremental improvements)* solo (or maybe jointly in a small team) inventions, designs, specs, or implementations* something large, a new service or a big feature, not numerous small edits & fixesIn this regard, the IndieWeb community shares more in common with Wikipedia and similar collaborative communities (despite the #Indie in #IndieWeb), than any corporation.For my "more bold" goal, I wrote a medium-sized post about the auto-linking improvements I made the Sunday before the IndieWebCamp to my personal website with examples and brief descriptions of the coding changes & improvements.* https://tantek.com/2024/070/t1/updated-auto-linking-mention-use-casesMy stretch goal was to write up a more complete auto-linking specification, based on the research I have done into @-mention @-@-mention user practices (on #Mastodon, other #ActivityPub or #fediverse implementations, and even across #socialMedia silos), as well as how implementations link URLs, domains, and paths.That stretch goal remains a goal, however I did collect a handful of prior posts on @-mentions which I plan to source for specifying auto-linking and @-mentioning:* https://tantek.com/2023/011/t1/indieweb-evolving-at-mention* https://tantek.com/2023/014/t4/domain-first-federated-atmention* https://tantek.com/2023/018/t1/elevate-indieweb-above-silo* https://tantek.com/2023/019/t5/reply-domain-above-address-and-silo* https://tantek.com/2023/109/t2/years-ago-first-federated-indieweb-thread#autoLink #atDomain #atPath #atMention #atMentions #atat #atAtMentionI was one of a few remote participants in addition to ~18 in-person participants, the overwhelming majority of overall attendees, who demonstrated something at the end of IndieWebCamp Brighton 2024 day 2. See what everyone else made & demonstrated on Create Day:* https://indieweb.org/2024/Brighton/DemosThis is post 13 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2024/070/t1/updated-auto-linking-mention-use-cases→ 🔮Glossary:Create Day https://indieweb.org/Create_DayIndieWebCamp Brighton 2024 https://indieweb.org/2024/BrightonReferences:¹ https://indieweb.org/IndieWebCamps/Attending#Day_Two² https://indieweb.org/what_to_make_at_IndieWebCamp³ https://indieweb.org/2024/Brighton/Schedule#Saturday
's status on Tuesday, 12-Mar-2024 22:19:00 EDT
What I created while remotely participating at #IndieWebCamp Brighton 2024: wiki-gardened day 1’s BarCamp sessions notes pages, and documented my @-mention @-@-mention autolinking coding improvements I built the Sunday before. Day 2 of IndieWebCamps is Create Day, where everyone is encouraged to create, make, or build something for their personal website, or the IndieWeb community, or both. At the start of day 2, everyone is encourage to pick things to make¹. What to make at an IndieWebCamp² can be anything from setting up your personal website, to writing a blog post, redesigning your styling, building new features, helping other participants, or contributing to shared IndieWeb community resources, whether code or content. Everyone is encouraged to at least pick something they consider easy, that they can do in less than an hour, then a more bold goal, and then perhaps a stretch goal, something challenging that may require collaboration, asking for help, or breaking into smaller steps. For my "easy" task, I built on what another remote participant, @gregorlove.com completed the night before. gRegor had archived all the IndieWebCamp Brighton Sessions Etherpads onto the wiki, linked from the Schedule page³. gRegor had noted that he didn’t have time to clean-up the pages, e.g. convert and fix Markdown links. I went through the 13 Session Notes archives and did the following: * converted Markdown links to MediaWiki links * converted indieweb.org (and some services) links to local wiki page links * fixed (some) typos With some help from @alexsirac.com (@alexture@todo.eu), I figured out how to create a MediaWiki Contributions summary link of my edits: * https://indieweb.org/wiki/index.php?title=Special:Contributions&target=Tantek.com&namespace=all&start=2024-03-10&end=2024-03-10&offset=20240310143900&limit=25 I point this out to provide an example of an IndieWeb Create Day project that is: * incremental on top of someone else’s work * community contribution rather a personal-focused project * editing and wiki-gardening as valid contributions, not just creating new content I point this out to illustrate some of the IndieWeb community's recognitions & values in contrast to typical corporate cultures and incentive systems which often only reward: * new innovations (not incremental improvements) * solo (or maybe jointly in a small team) inventions, designs, specs, or implementations * something large, a new service or a big feature, not numerous small edits & fixes In this regard, the IndieWeb community shares more in common with Wikipedia and similar collaborative communities (despite the #Indie in #IndieWeb), than any corporation. For my "more bold" goal, I wrote a medium-sized post about the auto-linking improvements I made the Sunday before the IndieWebCamp to my personal website with examples and brief descriptions of the coding changes & improvements. * https://tantek.com/2024/070/t1/updated-auto-linking-mention-use-cases My stretch goal was to write up a more complete auto-linking specification, based on the research I have done into @-mention @-@-mention user practices (on #Mastodon, other #ActivityPub or #fediverse implementations, and even across #socialMedia silos), as well as how implementations link URLs, domains, and paths. That stretch goal remains a goal, however I did collect a handful of prior posts on @-mentions which I plan to source for specifying auto-linking and @-mentioning: * https://tantek.com/2023/011/t1/indieweb-evolving-at-mention * https://tantek.com/2023/014/t4/domain-first-federated-atmention * https://tantek.com/2023/018/t1/elevate-indieweb-above-silo * https://tantek.com/2023/019/t5/reply-domain-above-address-and-silo * https://tantek.com/2023/109/t2/years-ago-first-federated-indieweb-thread #autoLink #atDomain #atPath #atMention #atMentions #atat #atAtMention I was one of a few remote participants in addition to ~18 in-person participants, the overwhelming majority of overall attendees, who demonstrated something at the end of IndieWebCamp Brighton 2024 day 2. See what everyone else made & demonstrated on Create Day: * https://indieweb.org/2024/Brighton/Demos This is post 13 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2024/070/t1/updated-auto-linking-mention-use-cases → 🔮 Glossary: Create Day https://indieweb.org/Create_Day IndieWebCamp Brighton 2024 https://indieweb.org/2024/Brighton References: ¹ https://indieweb.org/IndieWebCamps/Attending#Day_Two ² https://indieweb.org/what_to_make_at_IndieWebCamp ³ https://indieweb.org/2024/Brighton/Schedule#Saturday
: A couple of days ago in an informal discussion in the #indieweb chat channel about how different people view #Mastodon, the #fediverse, or #Bluesky, and services like #Bridgy & #BridgyFed quite differently, I noted¹ that one big unspoken difference was how things on the web last over time, from the traditional persistent web, vs the newer and growing ephemeral web.There is the publicly viewable #OpenWeb that many of us take for granted, meaning the web that is persistent, that lasts over time, and thanks to being #curlable, that the Internet Archive archives, and that a plurality of search engines see and index (robots.txt allowing). The HTML + CSS + media files declarative web.Then there are the https APIs that return JSON "web", the thing that I’ve started calling the ephemeral web, the set of things that are here today, briefly, gone tomorrow. I’ve previously used the more provocative phrase js;dr (JavaScript required, Didn’t Read) for this #ephemeralWeb, yet like many things, it turns out there is a spectrum from ephemeral to persistent.One popular example on that spectrum that’s closer to the ephemeral edge is anything on a Mastodon server running v4 (or later as of this writing) of the software. (I’m not bothering to discuss the examples of walled garden social media silos because I expect we will continue to see their demise² over time.)For example, the Internet Archive version of the shutdown notice for the queer(.)af Mastodon server, is visibly blank:https://web.archive.org/web/20240112165635/https://queer.af/@postmaster/111733741786950083Note: only a single Internet Archive snapshot was made of that post.However if you View Source, you can find the entirety of that #queerAF post duplicated across a couple of invisible-to-the-user meta tags inside the raw HTML: "**TL;DR: Queer[.]AF will close on 2024-04-12** …" [.] added to avoid linking to a dead domain.Note: such meta tags in js;dr pages were part of the motivation to specify metaformats.To be clear, the shutdown of queer(.)af was a tragedy and not the fault of the creators, administrators etc., but rather one of the unfortunate outcomes of using some ccTLDs, country-code top level domains, that risk sudden draconian rules, domain renewal price hikes, or other unpredictable risks due to the politics, turmoil, regime changes etc. of the countries that administrate such domains.Nearly the entirety of every Mastodon server, every post, every reply, is ephemeral.When a Mastodon server shuts down, all its posts disappear from the surface of the web, forever.Perhaps internet archeologists of the future will discover such dead permalinks, check the Internet Archive, find apparent desolation, and a few of them will be curious enough to use View Source tools to unearth parts of those posts, unintentionally preserved inside ceremonial meta tags next to dead scripts disconnected from databases and an empty shell of a body. All reply-contexts of and replies to such posts and conversations lost, like threads unraveled from an ancient tapestry, scattered to the winds.If you’re reading this post in your Mastodon reader, on either the website of your Mastodon account, or in a proprietary native client application, you should be able to click through, perhaps on the date-time stamp displayed to you, to view the original post on my website, where it is served in relatively simple declarative HTML + CSS with a bit of progressive enhancement script.Because I serve declarative content, my posts are both findable across a variety of services & search engines, and archived by the Internet Archive. Even if my site goes down, snapshots or archives will be viewable elsewhere, with nearly the same fidelity of viewing them directly on my site.This design for longevity is both deliberate, and the default for which the web was designed. It’s also one of the explicit principles in the IndieWeb community.If that resonates with you, if creating, writing, & building things that last matter to you, choose web tools, services, and software that support the persistence & longevity of your work.#persistentWeb #longWeb #LongNowThis is post 10 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2024/035/t2/indiewebcamp-brighton-tickets-available→ 🔮Post glossary:API (Application Programming Interface) https://indieweb.org/APIBluesky https://indieweb.org/BlueskyBridgy https://brid.gy/Bridgy Fed https://fed.brid.gy/ccTLD (country-code top level domain) https://indieweb.org/ccTLDcurlable https://indieweb.org/curlabledeclarative web https://www.mozilla.org/en-US/about/webvision/full/#thedeclarativewebInternet Archive https://archive.org/js;dr (JavaScript required; Didn’t Read) https://tantek.com/2015/069/t1/js-dr-javascript-required-deadJSON https://indieweb.org/JSONlongevity https://indieweb.org/longevityMastodon https://indieweb.org/Mastodonmetaformats https://microformats.org/wiki/metaformatspermalink https://indieweb.org/permalinkprinciples in the IndieWeb community https://indieweb.org/principlesprogressive enhancement https://indieweb.org/progressive_enhancementreply https://indieweb.org/replyreply-context https://indieweb.org/reply-contextrobots.txt https://indieweb.org/robots_txtsocial media https://indieweb.org/social_mediasilo https://indieweb.org/siloView Source https://firefox-source-docs.mozilla.org/devtools-user/view_source/index.html¹ https://chat.indieweb.org/2024-02-13#t1707845454695700² https://indieweb.org/site-deaths
's status on Thursday, 15-Feb-2024 16:18:00 EST
A couple of days ago in an informal discussion in the #indieweb chat channel about how different people view #Mastodon, the #fediverse, or #Bluesky, and services like #Bridgy & #BridgyFed quite differently, I noted¹ that one big unspoken difference was how things on the web last over time, from the traditional persistent web, vs the newer and growing ephemeral web. There is the publicly viewable #OpenWeb that many of us take for granted, meaning the web that is persistent, that lasts over time, and thanks to being #curlable, that the Internet Archive archives, and that a plurality of search engines see and index (robots.txt allowing). The HTML + CSS + media files declarative web. Then there are the https APIs that return JSON "web", the thing that I’ve started calling the ephemeral web, the set of things that are here today, briefly, gone tomorrow. I’ve previously used the more provocative phrase js;dr (JavaScript required, Didn’t Read) for this #ephemeralWeb, yet like many things, it turns out there is a spectrum from ephemeral to persistent. One popular example on that spectrum that’s closer to the ephemeral edge is anything on a Mastodon server running v4 (or later as of this writing) of the software. (I’m not bothering to discuss the examples of walled garden social media silos because I expect we will continue to see their demise² over time.) For example, the Internet Archive version of the shutdown notice for the queer(.)af Mastodon server, is visibly blank: https://web.archive.org/web/20240112165635/https://queer.af/@postmaster/111733741786950083 Note: only a single Internet Archive snapshot was made of that post. However if you View Source, you can find the entirety of that #queerAF post duplicated across a couple of invisible-to-the-user meta tags inside the raw HTML: "**TL;DR: Queer[.]AF will close on 2024-04-12** …" [.] added to avoid linking to a dead domain. Note: such meta tags in js;dr pages were part of the motivation to specify metaformats. To be clear, the shutdown of queer(.)af was a tragedy and not the fault of the creators, administrators etc., but rather one of the unfortunate outcomes of using some ccTLDs, country-code top level domains, that risk sudden draconian rules, domain renewal price hikes, or other unpredictable risks due to the politics, turmoil, regime changes etc. of the countries that administrate such domains. Nearly the entirety of every Mastodon server, every post, every reply, is ephemeral. When a Mastodon server shuts down, all its posts disappear from the surface of the web, forever. Perhaps internet archeologists of the future will discover such dead permalinks, check the Internet Archive, find apparent desolation, and a few of them will be curious enough to use View Source tools to unearth parts of those posts, unintentionally preserved inside ceremonial meta tags next to dead scripts disconnected from databases and an empty shell of a body. All reply-contexts of and replies to such posts and conversations lost, like threads unraveled from an ancient tapestry, scattered to the winds. If you’re reading this post in your Mastodon reader, on either the website of your Mastodon account, or in a proprietary native client application, you should be able to click through, perhaps on the date-time stamp displayed to you, to view the original post on my website, where it is served in relatively simple declarative HTML + CSS with a bit of progressive enhancement script. Because I serve declarative content, my posts are both findable across a variety of services & search engines, and archived by the Internet Archive. Even if my site goes down, snapshots or archives will be viewable elsewhere, with nearly the same fidelity of viewing them directly on my site. This design for longevity is both deliberate, and the default for which the web was designed. It’s also one of the explicit principles in the IndieWeb community. If that resonates with you, if creating, writing, & building things that last matter to you, choose web tools, services, and software that support the persistence & longevity of your work. #persistentWeb #longWeb #LongNow This is post 10 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2024/035/t2/indiewebcamp-brighton-tickets-available → 🔮 Post glossary: API (Application Programming Interface) https://indieweb.org/API Bluesky https://indieweb.org/Bluesky Bridgy https://brid.gy/ Bridgy Fed https://fed.brid.gy/ ccTLD (country-code top level domain) https://indieweb.org/ccTLD curlable https://indieweb.org/curlable declarative web https://www.mozilla.org/en-US/about/webvision/full/#thedeclarativeweb Internet Archive https://archive.org/ js;dr (JavaScript required; Didn’t Read) https://tantek.com/2015/069/t1/js-dr-javascript-required-dead JSON https://indieweb.org/JSON longevity https://indieweb.org/longevity Mastodon https://indieweb.org/Mastodon metaformats https://microformats.org/wiki/metaformats permalink https://indieweb.org/permalink principles in the IndieWeb community https://indieweb.org/principles progressive enhancement https://indieweb.org/progressive_enhancement reply https://indieweb.org/reply reply-context https://indieweb.org/reply-context robots.txt https://indieweb.org/robots_txt social media https://indieweb.org/social_media silo https://indieweb.org/silo View Source https://firefox-source-docs.mozilla.org/devtools-user/view_source/index.html ¹ https://chat.indieweb.org/2024-02-13#t1707845454695700 ² https://indieweb.org/site-deaths
: Twenty years and two days ago, @KevinMarks.com (@KevinMarks@xoxo.zone @KevinMarks) and I introduced #microformats in a conference presentation.I wrote a long retrospective last year: https://tantek.com/2023/047/t1/nineteen-years-microformatsSince that post nearly a year ago, here are the top three updates & interesting developments in microformats:1. Growing rel=me adoption for distributed verification (✅ in Mastodon etc.) * Wikipedia: https://tantek.com/2023/139/t1/wikipedia-supports-indieweb-rel-me * Threads: https://tantek.com/2023/234/t1/threads-supports-indieweb-rel-me * omg.lol profile links by default: https://home.omg.lol/info/profile-items2. A proposal to merge h-review into h-entry, since reviews are in practice always entries with a bit more information: * https://github.com/microformats/h-entry/issues/32 3. #metaformats adoptions, implementations, and iteration * There was growing practical interest in metaformats, so I updated the spec accordingly * A half dozen implementations shipped: https://indieweb.org/metaformats#IndieWeb_Examples * Active discussion for evolving metaformats to support more real world use-cases: https://github.com/microformats/metaformats/issuesHard to believe it’s been 20 years of iterating and evolving microformats, to #microformats2, growing adoption as #IndieWeb building blocks, distributed verification (those green checkmarks) in #Mastodon and across the #fediverse, and implementing metaformats parsing to standardize parsing various meta tags for link previews into equivalent microformats2.From last year’s activity, it’s clear there’s more use-cases, implementer interest, and community activity than ever. Looking forward to seeing what we can build in 2024.Post Glossaryh-entry https://microformats.org/wiki/h-entryh-review https://microformats.org/wiki/h-reviewlink-preview https://indieweb.org/link-previewmetaformats https://microformats.org/wiki/metaformatsmicroformats https://microformats.org/wiki/microformats2 https://microformats.org/wiki/microformats2rel-me https://microformats.org/wiki/rel-me
's status on Wednesday, 14-Feb-2024 01:03:00 EST
Twenty years and two days ago, @KevinMarks.com (@KevinMarks@xoxo.zone @KevinMarks) and I introduced #microformats in a conference presentation. I wrote a long retrospective last year: https://tantek.com/2023/047/t1/nineteen-years-microformats Since that post nearly a year ago, here are the top three updates & interesting developments in microformats: 1. Growing rel=me adoption for distributed verification (✅ in Mastodon etc.) * Wikipedia: https://tantek.com/2023/139/t1/wikipedia-supports-indieweb-rel-me * Threads: https://tantek.com/2023/234/t1/threads-supports-indieweb-rel-me * omg.lol profile links by default: https://home.omg.lol/info/profile-items 2. A proposal to merge h-review into h-entry, since reviews are in practice always entries with a bit more information: * https://github.com/microformats/h-entry/issues/32 3. #metaformats adoptions, implementations, and iteration * There was growing practical interest in metaformats, so I updated the spec accordingly * A half dozen implementations shipped: https://indieweb.org/metaformats#IndieWeb_Examples * Active discussion for evolving metaformats to support more real world use-cases: https://github.com/microformats/metaformats/issues Hard to believe it’s been 20 years of iterating and evolving microformats, to #microformats2, growing adoption as #IndieWeb building blocks, distributed verification (those green checkmarks) in #Mastodon and across the #fediverse, and implementing metaformats parsing to standardize parsing various meta tags for link previews into equivalent microformats2. From last year’s activity, it’s clear there’s more use-cases, implementer interest, and community activity than ever. Looking forward to seeing what we can build in 2024. Post Glossary h-entry https://microformats.org/wiki/h-entry h-review https://microformats.org/wiki/h-review link-preview https://indieweb.org/link-preview metaformats https://microformats.org/wiki/metaformats microformats https://microformats.org/wiki/ microformats2 https://microformats.org/wiki/microformats2 rel-me https://microformats.org/wiki/rel-me
: Twenty years and two days ago, @KevinMarks.com (@KevinMarks@xoxo.zone @KevinMarks) and I introduced #microformats in a conference presentation.I wrote a long retrospective last year: https://tantek.com/2023/047/t1/nineteen-years-microformatsSince that update nearly a year ago, here are the top three interesting developments in microformats:1. Growing rel=me adoption for distributed verification: * Wikipedia: https://tantek.com/2023/139/t1/wikipedia-supports-indieweb-rel-me * Threads: https://tantek.com/2023/234/t1/threads-supports-indieweb-rel-me * omg.lol profile links by default: https://home.omg.lol/info/profile-items2. A proposal to merge h-review into h-entry, since reviews are in practice always entries with a bit more information: * https://github.com/microformats/h-entry/issues/32 3. #metaformats adoptions, implementations, and iteration * There was growing practical interest in metaformats, so I updated the spec accordingly * A half dozen implementations shipped: https://indieweb.org/metaformats#IndieWeb_Examples * Active discussion for evolving metaformats to support more real world use-cases: https://github.com/microformats/metaformats/issuesHard to believe it’s been 20 years of iterating and evolving microformats, to #microformats2, growing adoption as #IndieWeb building blocks, distributed verification (those green checkmarks) in #Mastodon and across the #fediverse, and implementing metaformats parsing to standardize parsing various meta tags for link previews into equivalent microformats2.From last year’s activity, it’s clear there’s more use-cases, implementer interest, and community activity than ever. Looking forward to seeing what we can build in 2024.Post Glossaryh-entry https://microformats.org/wiki/h-entryh-review https://microformats.org/wiki/h-reviewlink-preview https://indieweb.org/link-previewmetaformats https://microformats.org/wiki/metaformatsmicroformats https://microformats.org/wiki/microformats2 https://microformats.org/wiki/microformats2rel-me https://microformats.org/wiki/rel-me
Twenty years and two days ago, @KevinMarks.com (@KevinMarks@xoxo.zone @KevinMarks) and I introduced #microformats in a conference presentation. I wrote a long retrospective last year: https://tantek.com/2023/047/t1/nineteen-years-microformats Since that update nearly a year ago, here are the top three interesting developments in microformats: 1. Growing rel=me adoption for distributed verification: * Wikipedia: https://tantek.com/2023/139/t1/wikipedia-supports-indieweb-rel-me * Threads: https://tantek.com/2023/234/t1/threads-supports-indieweb-rel-me * omg.lol profile links by default: https://home.omg.lol/info/profile-items 2. A proposal to merge h-review into h-entry, since reviews are in practice always entries with a bit more information: * https://github.com/microformats/h-entry/issues/32 3. #metaformats adoptions, implementations, and iteration * There was growing practical interest in metaformats, so I updated the spec accordingly * A half dozen implementations shipped: https://indieweb.org/metaformats#IndieWeb_Examples * Active discussion for evolving metaformats to support more real world use-cases: https://github.com/microformats/metaformats/issues Hard to believe it’s been 20 years of iterating and evolving microformats, to #microformats2, growing adoption as #IndieWeb building blocks, distributed verification (those green checkmarks) in #Mastodon and across the #fediverse, and implementing metaformats parsing to standardize parsing various meta tags for link previews into equivalent microformats2. From last year’s activity, it’s clear there’s more use-cases, implementer interest, and community activity than ever. Looking forward to seeing what we can build in 2024. Post Glossary h-entry https://microformats.org/wiki/h-entry h-review https://microformats.org/wiki/h-review link-preview https://indieweb.org/link-preview metaformats https://microformats.org/wiki/metaformats microformats https://microformats.org/wiki/ microformats2 https://microformats.org/wiki/microformats2 rel-me https://microformats.org/wiki/rel-me
: I felt the #earthquake here in #SanFrancisco. A single quick sharp jolt with rapid decay, duration less than 2s, meaning it was relatively nearby and small in magnitudeI was about to say, perhaps #earthquakes are the last use-case for #Twitter because yes I reflexively checked it and did see posts about it from folks, including a few friends.Then I checked https://indieweb.social/tags/earthquake and it has plenty of recent #fediverse posts about the earthquake, several @sfba.social.Feels like something big has shifted. The #federated #IndieWeb has replaced another #socialMedia silo use-case.This is post 7 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2024/027/t1/indieweb-ideals-systems-swappable→ 🔮Post glossary:silo https://indieweb.org/silosocial media https://indieweb.org/social_mediause-case https://indieweb.org/use_case
's status on Friday, 02-Feb-2024 16:49:00 EST
I felt the #earthquake here in #SanFrancisco. A single quick sharp jolt with rapid decay, duration less than 2s, meaning it was relatively nearby and small in magnitude I was about to say, perhaps #earthquakes are the last use-case for #Twitter because yes I reflexively checked it and did see posts about it from folks, including a few friends. Then I checked https://indieweb.social/tags/earthquake and it has plenty of recent #fediverse posts about the earthquake, several @sfba.social. Feels like something big has shifted. The #federated #IndieWeb has replaced another #socialMedia silo use-case. This is post 7 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2024/027/t1/indieweb-ideals-systems-swappable → 🔮 Post glossary: silo https://indieweb.org/silo social media https://indieweb.org/social_media use-case https://indieweb.org/use_case
: @snarfed.org posted a great overview of thoughtful (and sometimes heated) discussions across blogs and the #fediverse about how freely should “public” posts & comments on the web flow across sites:“Moderate people, not code” (https://snarfed.org/2024-01-21_moderate-people-not-code)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 #contextCollapse to #federation to #moderation 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 #publics 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 #IndieWeb, 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 #Webmention 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 #POSSE & #backfeed 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 #100PostsOfIndieWeb. #100Posts← https://tantek.com/2024/022/t1/indiewebcamp-brighton-planned→ 🔮Post glossary:backfeed https://indieweb.org/backfeedblog https://indieweb.org/blogblogging https://indieweb.org/blogging comments https://indieweb.org/commentscontext collapse https://indieweb.org/context_collapseephemerality https://indieweb.org/ephemeralityjs;dr https://indieweb.org/js;drmoderation https://indieweb.org/moderationPOSSE https://indieweb.org/POSSEposts https://indieweb.org/postspublics https://indieweb.org/publicsreply https://indieweb.org/replyVouch https://indieweb.org/Vouch Webmention https://indieweb.org/Webmention
's status on Tuesday, 23-Jan-2024 20:20:00 EST
@snarfed.org posted a great overview of thoughtful (and sometimes heated) discussions across blogs and the #fediverse about how freely should “public” posts & comments on the web flow across sites: “Moderate people, not code” (https://snarfed.org/2024-01-21_moderate-people-not-code) 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 #contextCollapse to #federation to #moderation 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 #publics 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 #IndieWeb, 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 #Webmention 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 #POSSE & #backfeed 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 #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2024/022/t1/indiewebcamp-brighton-planned → 🔮 Post glossary: backfeed https://indieweb.org/backfeed blog https://indieweb.org/blog blogging https://indieweb.org/blogging comments https://indieweb.org/comments context collapse https://indieweb.org/context_collapse ephemerality https://indieweb.org/ephemerality js;dr https://indieweb.org/js;dr moderation https://indieweb.org/moderation POSSE https://indieweb.org/POSSE posts https://indieweb.org/posts publics https://indieweb.org/publics reply https://indieweb.org/reply Vouch https://indieweb.org/Vouch Webmention https://indieweb.org/Webmention
: Time to begin again: restarting my #100Days of #IndieWeb project for 2024, as a #100Posts of IndieWeb project, and congrats to the IndieWeb community on a fully completed 2023 IndieWeb Gift Calendar!Last year I completed 48 out of a planned 100 posts in my #100DaysOfIndieWeb project, for nearly 48 days (some days had multiple posts). Instead of resetting my goals accordingly, say down to 50, I’m going for 100 again, however, this time for 100 posts rather than 100 days, having learned that some days I find the time for multiple posts, and other days none at all.Looking back to the start of last year’s 100 Days project, it’s been one year since I encouraged everyone to own their own notes¹. Since then many have started, restarted, or expanded their personal sites to do so. Some have switched from a #Twitter account to a #Mastodon (or other #fediverse) account as a stopgap for short-form status posts. A step in the right direction, yet also an opportunity to take the leap this year to fully own their identity and posts on the web.In 2023 Twitter also broke all existing API clients (including my website). I did not feel it was worth my time to re-apply for an API key and rebuild/retest any necessary code for my semi-automatic #POSSE publishing, not knowing when they might break things again (since there was no rational reason for them to have broken things in the first place).I manually POSSEd a few posts after that, yet from the lack of interactions, either Twitter’s feed algorithm² isn’t showing my posts, or people have largely left or stopped using Twitter. Either way, when your friends stop seeing your posts on a silo, there’s no need to spend any time POSSEing to it.On the positive side, the IndieWeb community really came together in 2023, shining brightly even through the darker days of December.We, the IndieWeb community (and some beyond!) provided a gift (or often multiple) to the rest of community for every single day of December 2023³, the first time we successfully filled out the whole month since the 2018 IndieWeb Challenge⁴, and only the second time ever in the seven years of the IndieWeb Challenge-turned-Gift-Calendar.By going through the various gifts (more than 2 per day on average!), there are many interesting numbers and patterns we could surface. That deserves its own post however, as does a summary of the 48 posts⁵ of my 2023 100 Days of IndieWeb attempt, so I’ll end this post here.Happy New Year to all, with an especially well deserved congratulations to the IndieWeb community and everyone who contributed to the 2023 Gift Calendar. Well done! Let’s see what else we can create & share on our personal sites in 2024 and continue setting a higher bar for the independent web by showing instead of telling. #ShowDontTellThis is post 1 of #100PostsOfIndieWeb. #100Posts← ✨→ 🔮Post glossary:API https://indieweb.org/APIPOSSE https://indieweb.org/POSSEsilo https://indieweb.org/silo¹ https://tantek.com/2023/001/t1/own-your-notes² https://indieweb.org/algorithmic_feed³ https://indieweb.org/2023-12-indieweb-gift-calendar⁴ https://indieweb.org/2018-12-indieweb-challenge⁵ https://tantek.com/2023/365/t2/no-large-language-model-llm-used
's status on Monday, 01-Jan-2024 22:30:00 EST
Time to begin again: restarting my #100Days of #IndieWeb project for 2024, as a #100Posts of IndieWeb project, and congrats to the IndieWeb community on a fully completed 2023 IndieWeb Gift Calendar! Last year I completed 48 out of a planned 100 posts in my #100DaysOfIndieWeb project, for nearly 48 days (some days had multiple posts). Instead of resetting my goals accordingly, say down to 50, I’m going for 100 again, however, this time for 100 posts rather than 100 days, having learned that some days I find the time for multiple posts, and other days none at all. Looking back to the start of last year’s 100 Days project, it’s been one year since I encouraged everyone to own their own notes¹. Since then many have started, restarted, or expanded their personal sites to do so. Some have switched from a #Twitter account to a #Mastodon (or other #fediverse) account as a stopgap for short-form status posts. A step in the right direction, yet also an opportunity to take the leap this year to fully own their identity and posts on the web. In 2023 Twitter also broke all existing API clients (including my website). I did not feel it was worth my time to re-apply for an API key and rebuild/retest any necessary code for my semi-automatic #POSSE publishing, not knowing when they might break things again (since there was no rational reason for them to have broken things in the first place). I manually POSSEd a few posts after that, yet from the lack of interactions, either Twitter’s feed algorithm² isn’t showing my posts, or people have largely left or stopped using Twitter. Either way, when your friends stop seeing your posts on a silo, there’s no need to spend any time POSSEing to it. On the positive side, the IndieWeb community really came together in 2023, shining brightly even through the darker days of December. We, the IndieWeb community (and some beyond!) provided a gift (or often multiple) to the rest of community for every single day of December 2023³, the first time we successfully filled out the whole month since the 2018 IndieWeb Challenge⁴, and only the second time ever in the seven years of the IndieWeb Challenge-turned-Gift-Calendar. By going through the various gifts (more than 2 per day on average!), there are many interesting numbers and patterns we could surface. That deserves its own post however, as does a summary of the 48 posts⁵ of my 2023 100 Days of IndieWeb attempt, so I’ll end this post here. Happy New Year to all, with an especially well deserved congratulations to the IndieWeb community and everyone who contributed to the 2023 Gift Calendar. Well done! Let’s see what else we can create & share on our personal sites in 2024 and continue setting a higher bar for the independent web by showing instead of telling. #ShowDontTell This is post 1 of #100PostsOfIndieWeb. #100Posts ← ✨ → 🔮 Post glossary: API https://indieweb.org/API POSSE https://indieweb.org/POSSE silo https://indieweb.org/silo ¹ https://tantek.com/2023/001/t1/own-your-notes ² https://indieweb.org/algorithmic_feed ³ https://indieweb.org/2023-12-indieweb-gift-calendar ⁴ https://indieweb.org/2018-12-indieweb-challenge ⁵ https://tantek.com/2023/365/t2/no-large-language-model-llm-used
: Writing about writing: capture first, edit & publish later.Braindump timely thoughts & experiences into as many draft notes as it takes, while ideas & memories are fresh.Collecting higher fidelity memories seems more important than editing past writings or finishing/polishing a post for publishing, which can be done at a later time.Sometimes the passage of time helps provide insights and broader understandings that can help with writing more effective posts, from better summaries to narratives that help sense-making.Bits of even this minor post sat for weeks, and only today did I add a summary and related thoughts.Similarly, it makes sense to edit and publish small notes on a subject, without feeling compelled to turn them into a larger blog post, or a longer list of points.This is a key advantage to publishing on your own #indieweb site, you decide on the granularity of your posts, small, medium or large, instead of being constrained, burdened, or pressured by any particular #socialMedia user interface, character count limitation, or audience expectation. Like Twitter before it, even the default #Mastodon user interface has limitations, and the #fediverse itself as a whole has audience/cultural expectations (certainly quite a few articles have been written about that).On your own site you decide if you want to publish a post to make one point, or mention a related point or two, or collect things into a list or longer article, or eventually all of the above.On your own site you feel more free to prioritize and share what is on your mind, instead of feeling compelled to first respond to whatever topics are trending, or to whatever you happen to read in your algorithmic feed.#writingAboutWritingThis is day 47 of #100DaysOfIndieWeb. #100Days← Day 46: https://tantek.com/2023/289/t1/bridgyfed-webmention-like-fediverse→ Day 48: https://tantek.com/2023/365/t2/no-large-language-model-llm-usedRelated: * “More Thoughtful Reading & Writing on the Web” (https://tantek.com/2023/277/b1/thoughtful-reading-writing-web)Post glossary:algorithmic feed https://indieweb.org/algorithmic_feedarticle https://indieweb.org/articlenote https://indieweb.org/notepost https://indieweb.org/postsense-making https://en.wikipedia.org/wiki/Sensemaking_(information_science)social media https://indieweb.org/social_media
's status on Sunday, 31-Dec-2023 17:04:00 EST
Writing about writing: capture first, edit & publish later. Braindump timely thoughts & experiences into as many draft notes as it takes, while ideas & memories are fresh. Collecting higher fidelity memories seems more important than editing past writings or finishing/polishing a post for publishing, which can be done at a later time. Sometimes the passage of time helps provide insights and broader understandings that can help with writing more effective posts, from better summaries to narratives that help sense-making. Bits of even this minor post sat for weeks, and only today did I add a summary and related thoughts. Similarly, it makes sense to edit and publish small notes on a subject, without feeling compelled to turn them into a larger blog post, or a longer list of points. This is a key advantage to publishing on your own #indieweb site, you decide on the granularity of your posts, small, medium or large, instead of being constrained, burdened, or pressured by any particular #socialMedia user interface, character count limitation, or audience expectation. Like Twitter before it, even the default #Mastodon user interface has limitations, and the #fediverse itself as a whole has audience/cultural expectations (certainly quite a few articles have been written about that). On your own site you decide if you want to publish a post to make one point, or mention a related point or two, or collect things into a list or longer article, or eventually all of the above. On your own site you feel more free to prioritize and share what is on your mind, instead of feeling compelled to first respond to whatever topics are trending, or to whatever you happen to read in your algorithmic feed. #writingAboutWriting This is day 47 of #100DaysOfIndieWeb. #100Days ← Day 46: https://tantek.com/2023/289/t1/bridgyfed-webmention-like-fediverse → Day 48: https://tantek.com/2023/365/t2/no-large-language-model-llm-used Related: * “More Thoughtful Reading & Writing on the Web” (https://tantek.com/2023/277/b1/thoughtful-reading-writing-web) Post glossary: algorithmic feed https://indieweb.org/algorithmic_feed article https://indieweb.org/article note https://indieweb.org/note post https://indieweb.org/post sense-making https://en.wikipedia.org/wiki/Sensemaking_(information_science) social media https://indieweb.org/social_media
: at a fascinating #Threads meetup hosted by Meta in San Francisco, with a handful of great #dataportability #fediverse #indieweb #openweb folks, learning about and providing feedback to Threads folks about their #federation #ActivityPub and other #openStandards support plans.Chatham House rule¹ means we can quote and talk about what’s being discussed (I’m taking notes), however no attribution, which I’m extending to not saying (or @-@-mentioning) who else is here.If you’re also here, feel free to reply to this post or use one of the below hashtags. And since I’m publishing this, feel free to @-me as well.#DataDialogue #Threadiverse (unofficial hashtag suggestion from a participant)¹ https://en.wikipedia.org/wiki/Chatham_House_rule
's status on Thursday, 07-Dec-2023 20:09:00 EST
at a fascinating #Threads meetup hosted by Meta in San Francisco, with a handful of great #dataportability #fediverse #indieweb #openweb folks, learning about and providing feedback to Threads folks about their #federation #ActivityPub and other #openStandards support plans. Chatham House rule¹ means we can quote and talk about what’s being discussed (I’m taking notes), however no attribution, which I’m extending to not saying (or @-@-mentioning) who else is here. If you’re also here, feel free to reply to this post or use one of the below hashtags. And since I’m publishing this, feel free to @-me as well. #DataDialogue #Threadiverse (unofficial hashtag suggestion from a participant) ¹ https://en.wikipedia.org/wiki/Chatham_House_rule
: Inspiring mix of perspective expanding and personal talks at border:none (https://border-none.net/ @border_none) the past two days. Thanks speakers, volunteers, and especially organizers @marcthiele.com (@marcthiele@mastodon.social @marcthiele) and @jkphl.is (@jkphl@mastodon.social @jkphl).Looking forward to the next two days at #IndieWebCamp Nürnberg @tollwerk.de (@tollwerk@mastodon.social @tollwerk) of personal site demos, brainstorming sessions, and making, creating, & hacking things from UX to protocols to improve & interconnect our websites, with each other ( #Webmention ), #fediverse ( #BridgyFed & #ActivityPub ), and others ( #POSSE #backfeed ).Still a few spots if you’re in town or can hop on a train and join us Saturday & Sunday!🎟 Tickets: https://ti.to/beyondtellerrand/bordernone-2023/with/kqyaidtq92k🗓 Event: https://events.indieweb.org/2023/10/indiewebcamp-nuremberg-2023-DmXe4dYdfagcℹ️ More info: https://indieweb.org/2023/Nuremberg#bordernone #bono23 #IndieWeb
's status on Friday, 27-Oct-2023 19:23:00 EDT
Inspiring mix of perspective expanding and personal talks at border:none (https://border-none.net/ @border_none) the past two days. Thanks speakers, volunteers, and especially organizers @marcthiele.com (@marcthiele@mastodon.social @marcthiele) and @jkphl.is (@jkphl@mastodon.social @jkphl). Looking forward to the next two days at #IndieWebCamp Nürnberg @tollwerk.de (@tollwerk@mastodon.social @tollwerk) of personal site demos, brainstorming sessions, and making, creating, & hacking things from UX to protocols to improve & interconnect our websites, with each other ( #Webmention ), #fediverse ( #BridgyFed & #ActivityPub ), and others ( #POSSE #backfeed ). Still a few spots if you’re in town or can hop on a train and join us Saturday & Sunday! 🎟 Tickets: https://ti.to/beyondtellerrand/bordernone-2023/with/kqyaidtq92k 🗓 Event: https://events.indieweb.org/2023/10/indiewebcamp-nuremberg-2023-DmXe4dYdfagc ℹ️ More info: https://indieweb.org/2023/Nuremberg #bordernone #bono23 #IndieWeb
: 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-mastodonSeveral 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: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/backfeedBackfeed 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/backfeedBridgy https://brid.gy/make what you need https://indieweb.org/make_what_you_needmanual (until it hurts) https://indieweb.org/manual_until_it_hurtsoriginal post link https://indieweb.org/original_post_linkown your data https://indieweb.org/own_your_dataown your replies https://indieweb.org/own_your_repliespermalink https://indieweb.org/permalinkpermashortlink https://indieweb.org/permashortlinkPOSSE https://indieweb.org/POSSEsilo https://indieweb.org/silosocial media https://indieweb.org/social_mediastatic site https://indieweb.org/static_sitestart https://indieweb.org/startWebmention 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
's status on Monday, 23-Oct-2023 20:30:00 EDT
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: 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
: 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/favouritesEvery 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
's status on Monday, 16-Oct-2023 21:16:00 EDT
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
: Bridgy Fed (#BridgyFed) recently added support for federating @-@-mentions to #Mastodon: https://fed.brid.gy/docs#mentionSo here’s a test:Happy birthday @evanp.me (@evan@cosocial.ca @evanpro)!!!Let’s see if Evan receives one or more notifications of these mentions, especially on cosocial, directly from my blog to his Mastodon account.Previous related posts on how to @-mention across the #IndieWeb, #fediverse, and silos:* https://tantek.com/2023/014/t4/domain-first-federated-atmention* https://tantek.com/2023/017/t1/socialweb-blogs-reply-comment-post* https://tantek.com/2023/018/t1/elevate-indieweb-above-silo* https://tantek.com/2023/019/t5/reply-domain-above-address-and-silowhich is enough material on the subject to be worth a broader overall blog post on at-mentions, @-mentions, @-@-mentions, how to write them, how to send #Webmentions or #federate them, and perhaps how to recognize & send notifications for them.
's status on Saturday, 14-Oct-2023 22:37:00 EDT
Bridgy Fed (#BridgyFed) recently added support for federating @-@-mentions to #Mastodon: https://fed.brid.gy/docs#mention So here’s a test: Happy birthday @evanp.me (@evan@cosocial.ca @evanpro)!!! Let’s see if Evan receives one or more notifications of these mentions, especially on cosocial, directly from my blog to his Mastodon account. Previous related posts on how to @-mention across the #IndieWeb, #fediverse, and silos: * https://tantek.com/2023/014/t4/domain-first-federated-atmention * https://tantek.com/2023/017/t1/socialweb-blogs-reply-comment-post * https://tantek.com/2023/018/t1/elevate-indieweb-above-silo * https://tantek.com/2023/019/t5/reply-domain-above-address-and-silo which is enough material on the subject to be worth a broader overall blog post on at-mentions, @-mentions, @-@-mentions, how to write them, how to send #Webmentions or #federate them, and perhaps how to recognize & send notifications for them.
: I recently wrote a high level summary blog post:W3C Technical Plenary and Advisory Committee (TPAC) Meetings 2023https://tantek.com/2023/262/b1/w3c-technical-plenary-tpacof my time at the #W3C (@W3.org, @w3c@w3c.social, @W3C) #TPAC the week before.Posting this note to explicitly #hashtag that article with topics mentioned therein:#Sevilla #Seville #Spain #WICG #SocialCG #SWICG #Fediverse #SocialWeb #sustainability #IndieWeb #ActivityPubbecause I forgot to put explicit categories (p-category markup) in the article post.Adding that markup after publishing, and then sending an ActivityPub update (via #BridgyFed) is apparently not enough for #Mastodon to notice that the Update has new tags to display and aggregate on tag pages. In my next #w3cTPAC article post I’ll be sure to include category markup before publishing and see if that works.Post glossary:article post https://indieweb.org/articlenote post https://indieweb.org/notep-category https://indieweb.org/p-categorytags https://indieweb.org/tags
's status on Sunday, 24-Sep-2023 21:33:00 EDT
I recently wrote a high level summary blog post: W3C Technical Plenary and Advisory Committee (TPAC) Meetings 2023 https://tantek.com/2023/262/b1/w3c-technical-plenary-tpac of my time at the #W3C (@W3.org, @w3c@w3c.social, @W3C) #TPAC the week before. Posting this note to explicitly #hashtag that article with topics mentioned therein: #Sevilla #Seville #Spain #WICG #SocialCG #SWICG #Fediverse #SocialWeb #sustainability #IndieWeb #ActivityPub because I forgot to put explicit categories (p-category markup) in the article post. Adding that markup after publishing, and then sending an ActivityPub update (via #BridgyFed) is apparently not enough for #Mastodon to notice that the Update has new tags to display and aggregate on tag pages. In my next #w3cTPAC article post I’ll be sure to include category markup before publishing and see if that works. Post glossary: article post https://indieweb.org/article note post https://indieweb.org/note p-category https://indieweb.org/p-category tags https://indieweb.org/tags
: going to the #SocialWeb CG meeting @W3C #w3cTPAC tomorrow (2023-09-12) at 09:30 CEST.Looking forward to seeing @evanp.me (@evan@cosocial.ca @evanpro) and many others!So many advances in #ActivityPub, #Webmention, Micropub, #IndieAuth etc. that it may be time to restart the #SocialWebWG to officially update all our active specifications.We can & should also reach out to #Bluesky & #Nostr communities to work together on shared semantics and bridging protocols to continue growing a heterogenous #fediverse built on the #OpenWeb.We know it is possible. We worked hard in the Social Web working group to align a lot of semantics across #ActivityStreams and #microformats2. The fruitful results of that are services like http://fed.brid.gy/ which I myself use to send a Webmention when I make a new post (like this one) and have #BridgyFed automatically federate it via ActivityPub using my personal site identity to #Mastodon followers and others.@snarfed.org wrote up a recent comparison of top #decentralized #socialProtocols that can help inform a lot of this discussion: https://snarfed.org/2023-09-04_50856
's status on Monday, 11-Sep-2023 19:06:00 EDT
going to the #SocialWeb CG meeting @W3C #w3cTPAC tomorrow (2023-09-12) at 09:30 CEST. Looking forward to seeing @evanp.me (@evan@cosocial.ca @evanpro) and many others! So many advances in #ActivityPub, #Webmention, Micropub, #IndieAuth etc. that it may be time to restart the #SocialWebWG to officially update all our active specifications. We can & should also reach out to #Bluesky & #Nostr communities to work together on shared semantics and bridging protocols to continue growing a heterogenous #fediverse built on the #OpenWeb. We know it is possible. We worked hard in the Social Web working group to align a lot of semantics across #ActivityStreams and #microformats2. The fruitful results of that are services like http://fed.brid.gy/ which I myself use to send a Webmention when I make a new post (like this one) and have #BridgyFed automatically federate it via ActivityPub using my personal site identity to #Mastodon followers and others. @snarfed.org wrote up a recent comparison of top #decentralized #socialProtocols that can help inform a lot of this discussion: https://snarfed.org/2023-09-04_50856
: Threads.net now supports the #indieWeb #microformats #openStandard rel-me for distributed ✅ verification!¹ (supported since 2023-08-09)My Threads profile already had my domain since it was created from my Instagram profile.View source on https://www.threads.net/@tantek and you can see the #relMe on a link tag: Instructions to add yours:* Add your domain to your Threads profile "Link" field. That’s it.Longer explicit steps: https://indieweb.org/rel-me#ThreadsThanks especially to @timothychambers.net (@tchambers@indieweb.social, @timothyjchambers@threads.net) for requesting rel-me support² which one Threads engineer “decided to hack it together” one night!³You can view Tim’s profile @tchambers@indieweb.social for a real world example of a Mastodon profile showing a green text ✅ verified link to a Threads profile.Tim made several good points in his request:“… a small, but disproportionately helpful addition would be to support this "rel=me" feature in your profiles. That could launch well before full ActivityPub, & show the first real integration to open social web standards”Microformats (and IndieWeb) standards in general are deliberately designed as small, incremental building blocks which are disproportionately helpful as Tim says.These small building blocks which directly enable user features are usually something a web developer can code at least some (often complete!) support for in one day/night which makes them particularly appealing as a way to rapidly support open #socialWeb standards used by the #fediverse and beyond.Incrementally implementing microformats & IndieWeb standards⁴ also demonstrates good will and good intentions for supporting the #openWeb.This is day 44 of #100DaysOfIndieWeb. #100Days← Day 43: https://tantek.com/2023/171/t1/anniversaries-microformats-posse→ 🔮Previously:* 2023-02-01 Wikipedia.org supports multiple rel=me links: https://tantek.com/2023/139/t1/wikipedia-supports-indieweb-rel-me¹ https://www.threads.net/@mosseri/post/Cvu2eXurRbB² https://www.threads.net/@timothyjchambers/post/CupCvChAxI8³ https://www.threads.net/@0xjessel/post/Cvu7-A4viZu⁴ https://spec.indieweb.org/
's status on Tuesday, 22-Aug-2023 15:43:00 EDT
Threads.net now supports the #indieWeb #microformats #openStandard rel-me for distributed ✅ verification!¹ (supported since 2023-08-09) My Threads profile already had my domain since it was created from my Instagram profile. View source on https://www.threads.net/@tantek and you can see the #relMe on a link tag: Instructions to add yours: * Add your domain to your Threads profile "Link" field. That’s it. Longer explicit steps: https://indieweb.org/rel-me#Threads Thanks especially to @timothychambers.net (@tchambers@indieweb.social, @timothyjchambers@threads.net) for requesting rel-me support² which one Threads engineer “decided to hack it together” one night!³ You can view Tim’s profile @tchambers@indieweb.social for a real world example of a Mastodon profile showing a green text ✅ verified link to a Threads profile. Tim made several good points in his request: “… a small, but disproportionately helpful addition would be to support this "rel=me" feature in your profiles. That could launch well before full ActivityPub, & show the first real integration to open social web standards” Microformats (and IndieWeb) standards in general are deliberately designed as small, incremental building blocks which are disproportionately helpful as Tim says. These small building blocks which directly enable user features are usually something a web developer can code at least some (often complete!) support for in one day/night which makes them particularly appealing as a way to rapidly support open #socialWeb standards used by the #fediverse and beyond. Incrementally implementing microformats & IndieWeb standards⁴ also demonstrates good will and good intentions for supporting the #openWeb. This is day 44 of #100DaysOfIndieWeb. #100Days ← Day 43: https://tantek.com/2023/171/t1/anniversaries-microformats-posse → 🔮 Previously: * 2023-02-01 Wikipedia.org supports multiple rel=me links: https://tantek.com/2023/139/t1/wikipedia-supports-indieweb-rel-me ¹ https://www.threads.net/@mosseri/post/Cvu2eXurRbB ² https://www.threads.net/@timothyjchambers/post/CupCvChAxI8 ³ https://www.threads.net/@0xjessel/post/Cvu7-A4viZu ⁴ https://spec.indieweb.org/
: 10 years ago today the first #federated #IndieWeb comment thread was published and collected peer-to-peer IndieWeb replies across websites without any intermediary, silo or otherwise¹.2013-04-19 @eschnou.com posted a brief note on his personal site with #atMentions of a few domains (putting an '@' sign immediately before a domain name to indicate an explicit cross-web @-mention), which itself was also a first² "Testing #indieweb federation with @waterpigs.co.uk, @aaronparecki.com and @indiewebcamp.com !"When @aaronpk.com was notified and replied from his site within minutes³, it became the first peer-to-peer federated IndieWeb comment thread, at the time using h-entry and Pingback. I blogged about it a few days later⁴.Earlier this year I blogged more observations of all the user interactions that happened on that day and shortly thereafter to make this all work: https://tantek.com/2023/014/t4/domain-first-federated-atmentionUnfortunately Laurent Eschnou’s original post is no longer up, and we only have the Internet Archive copy. However most of the IndieWeb reply posts are still up including Barnaby’s: https://waterpigs.co.uk/notes/1334/The oldest still working federated post and comment thread was second overall, unsurprisingly from @aaronparecki.com⁵, a whole 40 days after Laurent’s first.This is day 37 of #100DaysOfIndieWeb. #100Days #OpenWeb #federation #fediverse← Day 36: https://tantek.com/2023/100/t1/auto-linked-hashtags-federated→ 🔮Glossaryfederation https://indieweb.org/federationh-entry https://microformats.org/wiki/h-entryPingback https://indieweb.org/Pingbackreply post https://indieweb.org/replyReferences¹ https://web.archive.org/web/20130427010301/http://eschnou.com/entry/testing-indieweb-federation-with-waterpigscouk-aaronpareckicom-and--62-24908.html² https://tantek.com/2023/014/t4/domain-first-federated-atmention³ https://aaronparecki.com/2013/04/19/3/indieweb⁴ https://tantek.com/2013/113/b1/first-federated-indieweb-comment-thread⁵ https://aaronparecki.com/2013/05/21/4/xkcd
's status on Wednesday, 19-Apr-2023 20:48:00 EDT
10 years ago today the first #federated #IndieWeb comment thread was published and collected peer-to-peer IndieWeb replies across websites without any intermediary, silo or otherwise¹. 2013-04-19 @eschnou.com posted a brief note on his personal site with #atMentions of a few domains (putting an '@' sign immediately before a domain name to indicate an explicit cross-web @-mention), which itself was also a first² "Testing #indieweb federation with @waterpigs.co.uk, @aaronparecki.com and @indiewebcamp.com !" When @aaronpk.com was notified and replied from his site within minutes³, it became the first peer-to-peer federated IndieWeb comment thread, at the time using h-entry and Pingback. I blogged about it a few days later⁴. Earlier this year I blogged more observations of all the user interactions that happened on that day and shortly thereafter to make this all work: https://tantek.com/2023/014/t4/domain-first-federated-atmention Unfortunately Laurent Eschnou’s original post is no longer up, and we only have the Internet Archive copy. However most of the IndieWeb reply posts are still up including Barnaby’s: https://waterpigs.co.uk/notes/1334/ The oldest still working federated post and comment thread was second overall, unsurprisingly from @aaronparecki.com⁵, a whole 40 days after Laurent’s first. This is day 37 of #100DaysOfIndieWeb. #100Days #OpenWeb #federation #fediverse ← Day 36: https://tantek.com/2023/100/t1/auto-linked-hashtags-federated → 🔮 Glossary federation https://indieweb.org/federation h-entry https://microformats.org/wiki/h-entry Pingback https://indieweb.org/Pingback reply post https://indieweb.org/reply References ¹ https://web.archive.org/web/20130427010301/http://eschnou.com/entry/testing-indieweb-federation-with-waterpigscouk-aaronpareckicom-and--62-24908.html ² https://tantek.com/2023/014/t4/domain-first-federated-atmention ³ https://aaronparecki.com/2013/04/19/3/indieweb ⁴ https://tantek.com/2013/113/b1/first-federated-indieweb-comment-thread ⁵ https://aaronparecki.com/2013/05/21/4/xkcd
: @fredrocha.net (@john_fisherman@mastodon.social) saw your post (https://mastodon.social/@john_fisherman/110224246899618915) from the #IndieWeb stream. Beautiful photos on your site! #btconf was great wasn’t it?My personal URL is https://tantek.com/ and my #fediverse @ is @tantek.com. My Atom feed file is auto-discoverable by feed readers from my home page.Feeding (so to speak) two discovery birds with one stonefruit¹.Your personal website can be your fediverse address², each providing seamless discovery for the other.As web developers we should be building & developing our personal sites to exemplify the latest & greatest of such practices, including using Mastodon/ActivityPub as yet another distribution mechanism (ala POSSE) for your existing personal websites rather than a separate profile/stream.Discussed this with @nebu@mastodon.social and @kadirtopal@mastodon.social just after the last talk @beyondtellerrand.com (@btconf@mastodon.social @btconf) yesterday, fitting conference closing thoughts complementing the heartfelt opening talk by @localghost.dev (https://sophie.omg.lol/ @sophie@social.lol)³.GlossaryActivityPub https://indieweb.org/ActivityPubfeed file https://indieweb.org/feed_filePOSSE https://indieweb.org/POSSEReferences¹ https://tantek.com/2020/147/t2/replace-violent-metaphors² https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indieweb³ https://tantek.com/2023/107/t1/beyond-tellerand-talk-love-personal-website
's status on Wednesday, 19-Apr-2023 04:22:00 EDT
@fredrocha.net (@john_fisherman@mastodon.social) saw your post (https://mastodon.social/@john_fisherman/110224246899618915) from the #IndieWeb stream. Beautiful photos on your site! #btconf was great wasn’t it? My personal URL is https://tantek.com/ and my #fediverse @ is @tantek.com. My Atom feed file is auto-discoverable by feed readers from my home page. Feeding (so to speak) two discovery birds with one stonefruit¹. Your personal website can be your fediverse address², each providing seamless discovery for the other. As web developers we should be building & developing our personal sites to exemplify the latest & greatest of such practices, including using Mastodon/ActivityPub as yet another distribution mechanism (ala POSSE) for your existing personal websites rather than a separate profile/stream. Discussed this with @nebu@mastodon.social and @kadirtopal@mastodon.social just after the last talk @beyondtellerrand.com (@btconf@mastodon.social @btconf) yesterday, fitting conference closing thoughts complementing the heartfelt opening talk by @localghost.dev (https://sophie.omg.lol/ @sophie@social.lol)³. Glossary ActivityPub https://indieweb.org/ActivityPub feed file https://indieweb.org/feed_file POSSE https://indieweb.org/POSSE References ¹ https://tantek.com/2020/147/t2/replace-violent-metaphors ² https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indieweb ³ https://tantek.com/2023/107/t1/beyond-tellerand-talk-love-personal-website
: Watching #MozFest session Dialogues & Debates: Making the Fediverse¹ and panelist @stevetex@mozilla.social (@stevetex) just announced that we (#Mozilla) are standing up a #Mastodon instance², starting with limited sign-ups.I’m excited that Mozilla is experimenting with #socialWeb alternatives to centralized #socialMedia silos.There are many #Mozillians with #fediverse addresses you can follow:* https://wiki.mozilla.org/MastodonSeveral of these folks also have their own #IndieWeb sites. It’s interesting seeing how people are individually choosing to use a fediverse address on someone else’s server, vs their own server like with a subdomain, vs just using their existing site.One trend I have seen is people using someone else’s Mastodon server as a stepping stone, a learning experience, before migrating to either self-hosting Mastodon (or an easier to run alternative like microblog.pub³, not to be confused with micro.blog⁴), or ideally directly using their own site, blog etc. to connect to the fediverse⁵.Do you have an @-@ address and want to use your own site instead?If you’re a #webdev, you can totally do this by connecting your existing personal site with https://fed.brid.gy/ and own your presence on the web, social web, fediverse all at one place.Got questions? Drop by the IndieWeb chat! https://chat.indieweb.org/devThis is day 35 of #100DaysOfIndieWeb #100Days← Day 34: https://tantek.com/2023/072/t1/blog-as-if-ai-trained-posts→ 🔮¹ https://schedule.mozillafestival.org/session/UEEGYL-1² https://mozilla.social/³ https://indieweb.org/microblog.pub⁴ https://indieweb.org/micro.blog⁵ https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indieweb
's status on Wednesday, 22-Mar-2023 11:14:00 EDT
Watching #MozFest session Dialogues & Debates: Making the Fediverse¹ and panelist @stevetex@mozilla.social (@stevetex) just announced that we (#Mozilla) are standing up a #Mastodon instance², starting with limited sign-ups. I’m excited that Mozilla is experimenting with #socialWeb alternatives to centralized #socialMedia silos. There are many #Mozillians with #fediverse addresses you can follow: * https://wiki.mozilla.org/Mastodon Several of these folks also have their own #IndieWeb sites. It’s interesting seeing how people are individually choosing to use a fediverse address on someone else’s server, vs their own server like with a subdomain, vs just using their existing site. One trend I have seen is people using someone else’s Mastodon server as a stepping stone, a learning experience, before migrating to either self-hosting Mastodon (or an easier to run alternative like microblog.pub³, not to be confused with micro.blog⁴), or ideally directly using their own site, blog etc. to connect to the fediverse⁵. Do you have an @-@ address and want to use your own site instead? If you’re a #webdev, you can totally do this by connecting your existing personal site with https://fed.brid.gy/ and own your presence on the web, social web, fediverse all at one place. Got questions? Drop by the IndieWeb chat! https://chat.indieweb.org/dev This is day 35 of #100DaysOfIndieWeb #100Days ← Day 34: https://tantek.com/2023/072/t1/blog-as-if-ai-trained-posts → 🔮 ¹ https://schedule.mozillafestival.org/session/UEEGYL-1 ² https://mozilla.social/ ³ https://indieweb.org/microblog.pub ⁴ https://indieweb.org/micro.blog ⁵ https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indieweb
: Watching #MozFest session Dialogues & Debates: Making the Fediverse¹ and panelist @stevetex@mozilla.social (@stevetex) just announced that we (#Mozilla) are standing up a #Mastodon instance², starting with limited sign-ups.I’m excited that Mozilla is experimenting with #socialWeb alternatives to centralized #socialMedia silos.There are many #Mozillians with #fediverse addresses you can follow:* https://wiki.mozilla.org/MastodonSeveral of these folks also have their own #IndieWeb sites. It’s interesting seeing how people are individually choosing to use a fediverse address on someone else’s server, vs their own server like with a subdomain, vs just using their existing site.One trend I have seen is people using someone else’s Mastodon server as a stepping stone, a learning experience, before moving to either self-hosting Mastodon (or an easier to run alternative like microblog.pub³, not to be confused with micro.blog⁴), or ideally, directly using their existing site, blog etc. to connect to the fediverse⁵.Do you have an @-@ address and want to use your own site instead?If you’re a #webdev, you can totally do this by connecting your existing personal site with https://fed.brid.gy/ and own your presence on the web, social web, fediverse all at one place.Got questions? Drop by the IndieWeb chat! https://chat.indieweb.org/dev¹ https://schedule.mozillafestival.org/session/UEEGYL-1² https://mozilla.social/³ https://indieweb.org/microblog.pub⁴ https://indieweb.org/micro.blog⁵ https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indieweb
Watching #MozFest session Dialogues & Debates: Making the Fediverse¹ and panelist @stevetex@mozilla.social (@stevetex) just announced that we (#Mozilla) are standing up a #Mastodon instance², starting with limited sign-ups. I’m excited that Mozilla is experimenting with #socialWeb alternatives to centralized #socialMedia silos. There are many #Mozillians with #fediverse addresses you can follow: * https://wiki.mozilla.org/Mastodon Several of these folks also have their own #IndieWeb sites. It’s interesting seeing how people are individually choosing to use a fediverse address on someone else’s server, vs their own server like with a subdomain, vs just using their existing site. One trend I have seen is people using someone else’s Mastodon server as a stepping stone, a learning experience, before moving to either self-hosting Mastodon (or an easier to run alternative like microblog.pub³, not to be confused with micro.blog⁴), or ideally, directly using their existing site, blog etc. to connect to the fediverse⁵. Do you have an @-@ address and want to use your own site instead? If you’re a #webdev, you can totally do this by connecting your existing personal site with https://fed.brid.gy/ and own your presence on the web, social web, fediverse all at one place. Got questions? Drop by the IndieWeb chat! https://chat.indieweb.org/dev ¹ https://schedule.mozillafestival.org/session/UEEGYL-1 ² https://mozilla.social/ ³ https://indieweb.org/microblog.pub ⁴ https://indieweb.org/micro.blog ⁵ https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indieweb
: Five years ago last Monday, the @W3C Social Web Working Group officially closed¹.Operating for less than four years, it standardized several foundations of the #fediverse & #IndieWeb:#Webmention#Micropub#ActivityStreams2#ActivityPubEach of these has numerous interoperable implementations which are in active use by anywhere from thousands to millions of users.Two additional specifications also had several implementations as of the time of their publication as a W3C Recommendations (which you can find from the Implementation Report linked near the top of each spec). However today they’re both fairly invisible "plumbing" (as most specs should be) or they haven’t picked up widespread use like the others:#LinkedDataNotifications (LDN)#WebSubTo be fair, LDN was only one building block in what eventually became SoLiD², the basis of Tim Berners–Lee’s startup Inrupt.However, in the post Elon-acquisition of Twitter and subsequent Twexodus, as Anil Dash noted³, “nobody ran to the ’web3’ platforms”, and nobody ran to SoLiD either.The other spec, WebSub, was roughly interoperably implemented as PubSubHubbub before it was brought to the Social Web Working Group. Yet despite that implementation experience, a more rigorous specification that fixed a lot of bugs, and a test suite⁴, WebSub’s adoption hasn’t really noticeably grown since. Existing implementations & services are still functioning though. My own blog supports WebSub notifications for example, for anyone that wants to receive/read my posts in real time.One of the biggest challenges the Social Web Working Group faced was with so many approaches being brought to the group, which approach should we choose?As one of the co-chairs of the group, with the other co-chairs, and our staff contacts over time, we realized that if we as chairs & facilitators tried to pick any one approach, we would almost certainly alienate and lose more than half of the working group who had already built or were actively interested in developing other approaches.We (as chairs) decided to do something which very few standards groups do, and for that matter, have ever done successfully.From 15+ different approaches, or projects, or efforts that were brought⁵ to the working group, we narrowed them down to about 2.5 which I can summarize as:1. #IndieWeb building blocks, many of which were already implemented, deployed, and showing rough interoperability across numerous independent websites2. ActivityStreams based approaches, which also demonstrated implementability, interoperability, and real user value as part of the OStatus suite, implemented in StatusNet, Identica, etc.2.5 "something with Linked Data (LD)" — expressed as a 0.5 because there wasn’t anything user-visible “social web” with LD working at the start of the Working Group, however there was a very passionate set of participants insisting that everything be done with RDF/LD, despite the fact that it was less of a proven social web approach than the other two.As chairs we figured out that if we were able to help facilitate the development of these 2.5 approaches in parallel, nearly everyone who was active in the Working Group would have something they would feel like they could direct their positive energy into, instead of spending time fighting or tearing down someone else’s approach.It was a very difficult social-technical balance to maintain, and we hit more than a few bumps along the way. However we also had many moments of alignment, where two (or all) of the various approaches found common problems, and either identical or at least compatible solutions.I saw many examples where the discoveries of one approach helped inform and improve another approach. Developing more than one approach in the same working group was not only possible, it actually worked.I also saw examples of different problems being solved by different approaches, and I found that aspect particularly fascinating and hopeful. Multiple approaches were able to choose & priortize different subsets of social web use-cases and problems to solve from the larger space of decentralized social web challenges. By doing so, different approaches often explored and mapped out different areas of the larger social web space.I’m still a bit amazed we were able to complete all of those Recommendations in less than four years, and everyone who participated in the working group should be proud of that accomplishment, beyond any one specification they may have worked on.With hindsight, we can see the positive practical benefits from allowing & facilitating multiple approaches to move forward. Today there is both a very healthy & growing set of folks who want simple personal sites to do with as they please (#IndieWeb), and we also have a growing network of Mastodon instances and other software & services that interoperate with them, like Bridgy Fed⁶. Millions of users are posting & interacting with each other daily, without depending on any large central corporate site or service, whether on their own personal domain & site they fully control, or with an account on a trusted community server, using different software & services.Choosing to go from 15+ down to 2.5, but not down to 1 approach turned out to be the right answer, to both allow a wide variety⁷ of decentralized social web efforts to grow, interoperate via bridges, and frankly, socially to provide something positive for everyone to contribute to, instead of wasting weeks, possibly months in heated debates about which one approach was the one true way.There’s lots more to be written about the history of the Social Web Working Group, which perhaps I will do some day.For now, if you’re curious for more, I strongly recommend diving into the group’s wiki https://www.w3.org/wiki/Socialwg and its subpages for more historical details. All the minutes of our meetings are there. All the research we conducted is there.If you’re interested in contributing to the specifications we developed, find the place where that work is being done, the people actively implementing those specs, and even better, actively using their own implementations⁸.You can find the various IndieWeb building blocks living specifications here:* https://spec.indieweb.org/And discussions thereof in the development chat channel:* https://chat.indieweb.org/devIf you’re not sure, pop by the indieweb-dev chat and ask anyway!The IndieWeb community has grown only larger and more diverse in approaches & implementations in the past five years, and we regularly have discussions about most of the specifications that were developed in the Social Web Working Group.This is day 33 of #100DaysOfIndieWeb #100Days← Day 32: https://tantek.com/2023/047/t1/nineteen-years-microformats→ 🔮Post Glossary:ActivityPub https://www.w3.org/TR/activitypub/ ActivityStreams2 https://www.w3.org/TR/activitystreams-core/ https://www.w3.org/TR/activitystreams-vocabulary/Linked Data Notifications https://www.w3.org/TR/ldn/Micropub https://micropub.spec.indieweb.org/Webmention https://webmention.net/draft/WebSub https://www.w3.org/TR/websub/References:¹ https://www.w3.org/wiki/Socialwg² https://www.w3.org/wiki/Socialwg/2015-03-18-minutes#solid³ https://mastodon.cloud/@anildash/109299991009836007⁴ https://websub.rocks/⁵ https://indieweb.org/Social_Web_Working_Group#History⁶ https://tantek.com/2023/008/t7/bridgy-indieweb-posse-backfeed⁷ https://indieweb.org/plurality⁸ https://indieweb.org/use_what_you_make
's status on Monday, 20-Feb-2023 22:16:00 EST
Five years ago last Monday, the @W3C Social Web Working Group officially closed¹. Operating for less than four years, it standardized several foundations of the #fediverse & #IndieWeb: #Webmention #Micropub #ActivityStreams2 #ActivityPub Each of these has numerous interoperable implementations which are in active use by anywhere from thousands to millions of users. Two additional specifications also had several implementations as of the time of their publication as a W3C Recommendations (which you can find from the Implementation Report linked near the top of each spec). However today they’re both fairly invisible "plumbing" (as most specs should be) or they haven’t picked up widespread use like the others: #LinkedDataNotifications (LDN) #WebSub To be fair, LDN was only one building block in what eventually became SoLiD², the basis of Tim Berners–Lee’s startup Inrupt. However, in the post Elon-acquisition of Twitter and subsequent Twexodus, as Anil Dash noted³, “nobody ran to the ’web3’ platforms”, and nobody ran to SoLiD either. The other spec, WebSub, was roughly interoperably implemented as PubSubHubbub before it was brought to the Social Web Working Group. Yet despite that implementation experience, a more rigorous specification that fixed a lot of bugs, and a test suite⁴, WebSub’s adoption hasn’t really noticeably grown since. Existing implementations & services are still functioning though. My own blog supports WebSub notifications for example, for anyone that wants to receive/read my posts in real time. One of the biggest challenges the Social Web Working Group faced was with so many approaches being brought to the group, which approach should we choose? As one of the co-chairs of the group, with the other co-chairs, and our staff contacts over time, we realized that if we as chairs & facilitators tried to pick any one approach, we would almost certainly alienate and lose more than half of the working group who had already built or were actively interested in developing other approaches. We (as chairs) decided to do something which very few standards groups do, and for that matter, have ever done successfully. From 15+ different approaches, or projects, or efforts that were brought⁵ to the working group, we narrowed them down to about 2.5 which I can summarize as: 1. #IndieWeb building blocks, many of which were already implemented, deployed, and showing rough interoperability across numerous independent websites 2. ActivityStreams based approaches, which also demonstrated implementability, interoperability, and real user value as part of the OStatus suite, implemented in StatusNet, Identica, etc. 2.5 "something with Linked Data (LD)" — expressed as a 0.5 because there wasn’t anything user-visible “social web” with LD working at the start of the Working Group, however there was a very passionate set of participants insisting that everything be done with RDF/LD, despite the fact that it was less of a proven social web approach than the other two. As chairs we figured out that if we were able to help facilitate the development of these 2.5 approaches in parallel, nearly everyone who was active in the Working Group would have something they would feel like they could direct their positive energy into, instead of spending time fighting or tearing down someone else’s approach. It was a very difficult social-technical balance to maintain, and we hit more than a few bumps along the way. However we also had many moments of alignment, where two (or all) of the various approaches found common problems, and either identical or at least compatible solutions. I saw many examples where the discoveries of one approach helped inform and improve another approach. Developing more than one approach in the same working group was not only possible, it actually worked. I also saw examples of different problems being solved by different approaches, and I found that aspect particularly fascinating and hopeful. Multiple approaches were able to choose & priortize different subsets of social web use-cases and problems to solve from the larger space of decentralized social web challenges. By doing so, different approaches often explored and mapped out different areas of the larger social web space. I’m still a bit amazed we were able to complete all of those Recommendations in less than four years, and everyone who participated in the working group should be proud of that accomplishment, beyond any one specification they may have worked on. With hindsight, we can see the positive practical benefits from allowing & facilitating multiple approaches to move forward. Today there is both a very healthy & growing set of folks who want simple personal sites to do with as they please (#IndieWeb), and we also have a growing network of Mastodon instances and other software & services that interoperate with them, like Bridgy Fed⁶. Millions of users are posting & interacting with each other daily, without depending on any large central corporate site or service, whether on their own personal domain & site they fully control, or with an account on a trusted community server, using different software & services. Choosing to go from 15+ down to 2.5, but not down to 1 approach turned out to be the right answer, to both allow a wide variety⁷ of decentralized social web efforts to grow, interoperate via bridges, and frankly, socially to provide something positive for everyone to contribute to, instead of wasting weeks, possibly months in heated debates about which one approach was the one true way. There’s lots more to be written about the history of the Social Web Working Group, which perhaps I will do some day. For now, if you’re curious for more, I strongly recommend diving into the group’s wiki https://www.w3.org/wiki/Socialwg and its subpages for more historical details. All the minutes of our meetings are there. All the research we conducted is there. If you’re interested in contributing to the specifications we developed, find the place where that work is being done, the people actively implementing those specs, and even better, actively using their own implementations⁸. You can find the various IndieWeb building blocks living specifications here: * https://spec.indieweb.org/ And discussions thereof in the development chat channel: * https://chat.indieweb.org/dev If you’re not sure, pop by the indieweb-dev chat and ask anyway! The IndieWeb community has grown only larger and more diverse in approaches & implementations in the past five years, and we regularly have discussions about most of the specifications that were developed in the Social Web Working Group. This is day 33 of #100DaysOfIndieWeb #100Days ← Day 32: https://tantek.com/2023/047/t1/nineteen-years-microformats → 🔮 Post Glossary: ActivityPub https://www.w3.org/TR/activitypub/ ActivityStreams2 https://www.w3.org/TR/activitystreams-core/ https://www.w3.org/TR/activitystreams-vocabulary/ Linked Data Notifications https://www.w3.org/TR/ldn/ Micropub https://micropub.spec.indieweb.org/ Webmention https://webmention.net/draft/ WebSub https://www.w3.org/TR/websub/ References: ¹ https://www.w3.org/wiki/Socialwg ² https://www.w3.org/wiki/Socialwg/2015-03-18-minutes#solid ³ https://mastodon.cloud/@anildash/109299991009836007 ⁴ https://websub.rocks/ ⁵ https://indieweb.org/Social_Web_Working_Group#History ⁶ https://tantek.com/2023/008/t7/bridgy-indieweb-posse-backfeed ⁷ https://indieweb.org/plurality ⁸ https://indieweb.org/use_what_you_make
: Instead of posting on a personal #IndieWeb site (& POSSE copies), some post primarily to a #fediverse instance and syndicate to Twitter, or vice-versa. How to reply^1 to such posts, e.g.:Reply to a toot (& POSSE tweet): https://tantek.com/2023/019/t4* @-@ (Twitter @-name)This is a variant of case (2) in https://tantek.com/2023/018/t1/elevate-indieweb-above-silo.We can update the directive and two questions & answers in that prior post accordingly:* Elevate #IndieWeb domains above @-@ addresses, and those above any silo identities1. Do they have an #IndieWeb domain? Then @-domain mention them^2, like you are speaking to them at their domain identity. This will notify them there, or at least reinforce their domain’s importance.2. Was their post only published on a #fediverse instance (and/or silo), or was it POSSEd to a fediverse instance (and/or silo) and do you plan to federate (and/or POSSE) your reply^3?Then use their @-@ address or silo @-name, or @-@ (silo @-name) for both, or (@-@, silo @-name) parenthetically following their @-domain if (1). This will notify them on that instance (or silo), and may help thread your POSSE reply.When posting a reply, you (or your CMS automatically) should explicitly link with u-in-reply-to markup^4 to the post your are replying to, and any of its syndicated copy permalinks on destinations you plan to POSSE your reply (see also multi-reply^5). This is day 18 of #100DaysOfIndieWeb #100Days, written the day after.← Day 17: https://tantek.com/2023/018/t1/elevate-indieweb-above-silo→ 🔮^1 https://tantek.com/2023/017/t1/socialweb-blogs-reply-comment-post^2 https://tantek.com/2023/011/t1/indieweb-evolving-at-mention^3 https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute^4 https://indieweb.org/in-reply-to^5 https://indieweb.org/multiple-reply
's status on Thursday, 19-Jan-2023 21:05:00 EST
Instead of posting on a personal #IndieWeb site (& POSSE copies), some post primarily to a #fediverse instance and syndicate to Twitter, or vice-versa. How to reply^1 to such posts, e.g.: Reply to a toot (& POSSE tweet): https://tantek.com/2023/019/t4 * @-@ (Twitter @-name) This is a variant of case (2) in https://tantek.com/2023/018/t1/elevate-indieweb-above-silo. We can update the directive and two questions & answers in that prior post accordingly: * Elevate #IndieWeb domains above @-@ addresses, and those above any silo identities 1. Do they have an #IndieWeb domain? Then @-domain mention them^2, like you are speaking to them at their domain identity. This will notify them there, or at least reinforce their domain’s importance. 2. Was their post only published on a #fediverse instance (and/or silo), or was it POSSEd to a fediverse instance (and/or silo) and do you plan to federate (and/or POSSE) your reply^3? Then use their @-@ address or silo @-name, or @-@ (silo @-name) for both, or (@-@, silo @-name) parenthetically following their @-domain if (1). This will notify them on that instance (or silo), and may help thread your POSSE reply. When posting a reply, you (or your CMS automatically) should explicitly link with u-in-reply-to markup^4 to the post your are replying to, and any of its syndicated copy permalinks on destinations you plan to POSSE your reply (see also multi-reply^5). This is day 18 of #100DaysOfIndieWeb #100Days, written the day after. ← Day 17: https://tantek.com/2023/018/t1/elevate-indieweb-above-silo → 🔮 ^1 https://tantek.com/2023/017/t1/socialweb-blogs-reply-comment-post ^2 https://tantek.com/2023/011/t1/indieweb-evolving-at-mention ^3 https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute ^4 https://indieweb.org/in-reply-to ^5 https://indieweb.org/multiple-reply
: The answer to “How should you @-mention someone you are replying to?”^1 can depend on many factors or a few. Context matters somewhat, sometimes.We can simplify it to 2 questions, based on 1 directive:* Elevate #IndieWeb domains, above any silo or @-@ identitiesTwo questions and answers: 1. Do they have an #IndieWeb domain? Then @-domain mention them^2, like you are speaking to them at their domain identity. This will notify them there, or at least reinforce their domain’s importance.2. Was their post only published on a silo (or #fediverse instance), or was it POSSEd to a silo (or fediverse instance) and you plan to POSSE (or federate) your reply^3? Then @-mention their silo @-name (or @-@ address), in parentheses if (1). This will notify them on that silo (or instance), and may help thread your POSSE reply.Examples:If the author has their own domain:Reply to an IndieWeb post (& POSSE toot): https://tantek.com/2023/008/t1/* @-domain (@-@)Reply to an IndieWeb post (& POSSE tweet): https://tantek.com/2023/016/t1/* @-domain [that matches their Twitter @-name]Reply to a toot: https://tantek.com/2023/008/t4/* @-domain (@-@)Reply to a tweet: https://tantek.com/2023/002/t2/* @-domain (Twitter @-name)If the author does not have their own domain:Reply to a toot: https://tantek.com/2023/002/t4/* @-@Reply to a tweet: none since this series, though it would be of the form:* Twitter @-nameThis is day 17 of #100DaysOfIndieWeb #100Days, again finished the next day.← Day 16: https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute→ 🔮^1 https://tantek.com/2023/017/t1/socialweb-blogs-reply-comment-post^2 https://tantek.com/2023/011/t1/indieweb-evolving-at-mention^3 https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute
's status on Thursday, 19-Jan-2023 02:11:00 EST
The answer to “How should you @-mention someone you are replying to?”^1 can depend on many factors or a few. Context matters somewhat, sometimes. We can simplify it to 2 questions, based on 1 directive: * Elevate #IndieWeb domains, above any silo or @-@ identities Two questions and answers: 1. Do they have an #IndieWeb domain? Then @-domain mention them^2, like you are speaking to them at their domain identity. This will notify them there, or at least reinforce their domain’s importance. 2. Was their post only published on a silo (or #fediverse instance), or was it POSSEd to a silo (or fediverse instance) and you plan to POSSE (or federate) your reply^3? Then @-mention their silo @-name (or @-@ address), in parentheses if (1). This will notify them on that silo (or instance), and may help thread your POSSE reply. Examples: If the author has their own domain: Reply to an IndieWeb post (& POSSE toot): https://tantek.com/2023/008/t1/ * @-domain (@-@) Reply to an IndieWeb post (& POSSE tweet): https://tantek.com/2023/016/t1/ * @-domain [that matches their Twitter @-name] Reply to a toot: https://tantek.com/2023/008/t4/ * @-domain (@-@) Reply to a tweet: https://tantek.com/2023/002/t2/ * @-domain (Twitter @-name) If the author does not have their own domain: Reply to a toot: https://tantek.com/2023/002/t4/ * @-@ Reply to a tweet: none since this series, though it would be of the form: * Twitter @-name This is day 17 of #100DaysOfIndieWeb #100Days, again finished the next day. ← Day 16: https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute → 🔮 ^1 https://tantek.com/2023/017/t1/socialweb-blogs-reply-comment-post ^2 https://tantek.com/2023/011/t1/indieweb-evolving-at-mention ^3 https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute
lnxw48a1: https://500ish.com/mastodon-brought-a-protocol-to-a-product-fight-ba9fda767c6a #Medium link; don't be surprised if it does weird things before showing you the article. "Mastodon brought a protocol to a product fight" > Yes, yes, the network is under immense strain as people flee the Elon strain infecting Twitter. But come on, there are folks who really believe this is going to replace, or even stand alongside Twitter, as a massively scaled social network? I call bullshit. While it’s impressive that millions of users have apparently given Mastodon a try, the product is far too slapdash and clunky to keep folks engaged. A lump of coal. No, it isn't meant to be a #Twitter replacement. Keep your Twitter account until you no longer want it--or the company closes and the site shuts down--you can use Mastodon alongside Twitter. And the #Fediverse networks are much more than just #Mastodon. Don't think you have experienced the network and all it has to offer if all you've done is briefly tried to use Mastodon, because you haven't experienced it. > I’ve somehow avoided signing up for the service up until now. Largely because signing up was and is so comically obtuse — pick your server everyone, hope you choose wisely! Have you not used e-mail? It works the same way. You pick a server, such as Gmail or Outlook dot com, and sign up. Please tell me you realize that the people you communicate with are not all on the same e-mail service that you use. > But, but, it’s not a product, it’s a protocol. Yeah, that’s a nice thing to say. And to believe in. But I truly believe the ship has sadly sailed for such idealism in this space. Jack Dorsey can talk about how this should have been what Twitter was from the get go until he’s bluesky in the face. It’s just not going to happen. And he’s more to blame for that than most everyone else. As is he for the Elon element of this current equation. But that’s a different story. Okay, so how about this story: Twitter has only been profitable two or three years of its entire history. Since it started, it has existed by burning through investors' funds. Eventually, with or without Elon Musk's ownership, that runs out. Without such funding, their corporate-centralized ( #corpocentric ) model cannot exist very long. And same for their centralized competitors, such as Post.news, Gab, Parler, and so on. What is left is either #federated or #peer-to-peer approaches, where no single entity is responsible for funding and managing the entire network. So whether it is the #Fediverse ( with #ActivityPub and #OStatus and their successors ) & the Federation ( with #Diaspora ) or #Bluesky, or #Twister, or #NOSTR, the eventual future of #socnets is #decentralized, if not entirely peer-to-peer unless a national government takes over Facebook and Twitter in order to provide effectively unlimited resources. It is the protocol that makes it possible for thousands or millions of instances to displace and replace one big centralized instance. 1/2
lnxw48a1's status on Wednesday, 28-Dec-2022 21:20:57 EST
https://500ish.com/mastodon-brought-a-protocol-to-a-product-fight-ba9fda767c6a #Medium link; don't be surprised if it does weird things before showing you the article. "Mastodon brought a protocol to a product fight" > Yes, yes, the network is under immense strain as people flee the Elon strain infecting Twitter. But come on, there are folks who really believe this is going to replace, or even stand alongside Twitter, as a massively scaled social network? I call bullshit. While it’s impressive that millions of users have apparently given Mastodon a try, the product is far too slapdash and clunky to keep folks engaged. A lump of coal. No, it isn't meant to be a #Twitter replacement. Keep your Twitter account until you no longer want it--or the company closes and the site shuts down--you can use Mastodon alongside Twitter. And the #Fediverse networks are much more than just #Mastodon. Don't think you have experienced the network and all it has to offer if all you've done is briefly tried to use Mastodon, because you haven't experienced it. > I’ve somehow avoided signing up for the service up until now. Largely because signing up was and is so comically obtuse — pick your server everyone, hope you choose wisely! Have you not used e-mail? It works the same way. You pick a server, such as Gmail or Outlook dot com, and sign up. Please tell me you realize that the people you communicate with are not all on the same e-mail service that you use. > But, but, it’s not a product, it’s a protocol. Yeah, that’s a nice thing to say. And to believe in. But I truly believe the ship has sadly sailed for such idealism in this space. Jack Dorsey can talk about how this should have been what Twitter was from the get go until he’s bluesky in the face. It’s just not going to happen. And he’s more to blame for that than most everyone else. As is he for the Elon element of this current equation. But that’s a different story. Okay, so how about this story: Twitter has only been profitable two or three years of its entire history. Since it started, it has existed by burning through investors' funds. Eventually, with or without Elon Musk's ownership, that runs out. Without such funding, their corporate-centralized ( #corpocentric ) model cannot exist very long. And same for their centralized competitors, such as Post.news, Gab, Parler, and so on. What is left is either #federated or #peer-to-peer approaches, where no single entity is responsible for funding and managing the entire network. So whether it is the #Fediverse ( with #ActivityPub and #OStatus and their successors ) & the Federation ( with #Diaspora ) or #Bluesky, or #Twister, or #NOSTR, the eventual future of #socnets is #decentralized, if not entirely peer-to-peer unless a national government takes over Facebook and Twitter in order to provide effectively unlimited resources. It is the protocol that makes it possible for thousands or millions of instances to displace and replace one big centralized instance. 1/2
lnxw48a1: https://prodromou.pub/@evan/109498060348615260 @evan@prodromou.pub @evan@identi.ca ( and formerly @evan@e14n.com ) has said this a few times, but here it is again. "Every time you post on Twitter, you produce value for the advertisers. You tell everyone in your network there that it's OK to stay. That you're all helpless to leave. You tell the people who've lost their jobs, the people who are being hounded and harassed, that they are not important to you. You know you're going to be ashamed of it later. Just stop posting. Do it here, not there. Connect here, not there. Don't reply, don't like, don't retweet. Stop feeding your life into the machine." This was true before Elon #Musk bought #Twitter, but I guess it wasn't as important before. I don't fully agree, simply because there may be some advantages to many people who continue to use Twitter instead of moving to the #Fediverse (e.g., #GNU_Social, #Mastodon, #Pleroma, #Misskey, #PixelFed, #Lenny / #Lemmy, etc) or they would have moved over already. Also, because unless one self-hosts one's own presence, an angry instance admin is all it takes to lose all posts and connections and have to start over. Or, if one has contacts on a different instance, then irate instance admins participating in #blockwars (including #fediblock) can separate the person from some portion of their contacts. So remember, everything that Twitter is or can do to you, your Fediverse instance can also do. Most instances will never do most of those things, but pretending that one is safe here could result in disappointment in the future.
lnxw48a1's status on Sunday, 11-Dec-2022 20:58:05 EST
https://prodromou.pub/@evan/109498060348615260 @evan@prodromou.pub @evan@identi.ca ( and formerly @evan@e14n.com ) has said this a few times, but here it is again. "Every time you post on Twitter, you produce value for the advertisers. You tell everyone in your network there that it's OK to stay. That you're all helpless to leave. You tell the people who've lost their jobs, the people who are being hounded and harassed, that they are not important to you. You know you're going to be ashamed of it later. Just stop posting. Do it here, not there. Connect here, not there. Don't reply, don't like, don't retweet. Stop feeding your life into the machine." This was true before Elon #Musk bought #Twitter, but I guess it wasn't as important before. I don't fully agree, simply because there may be some advantages to many people who continue to use Twitter instead of moving to the #Fediverse (e.g., #GNU_Social, #Mastodon, #Pleroma, #Misskey, #PixelFed, #Lenny / #Lemmy, etc) or they would have moved over already. Also, because unless one self-hosts one's own presence, an angry instance admin is all it takes to lose all posts and connections and have to start over. Or, if one has contacts on a different instance, then irate instance admins participating in #blockwars (including #fediblock) can separate the person from some portion of their contacts. So remember, everything that Twitter is or can do to you, your Fediverse instance can also do. Most instances will never do most of those things, but pretending that one is safe here could result in disappointment in the future.
: Two days ago my #BridgyFed followers crossed 8-bits:https://fed.brid.gy/user/tantek.comSigns of #TwitterMigration: my prev post had ~2x more #fediverse responses than Twitter, a ~500:1 difference per follower (having ~250x more Twitter followers).Many possible factors. Mastodon users see more from their followings. Twitter accounts could be mostly bots or abandoned. Recent posts are technical, maybe Mastodon users are more technical. Tech friends migrated first. Or hashtagging #fediverse.
's status on Tuesday, 06-Dec-2022 16:48:00 EST
Two days ago my #BridgyFed followers crossed 8-bits: https://fed.brid.gy/user/tantek.com Signs of #TwitterMigration: my prev post had ~2x more #fediverse responses than Twitter, a ~500:1 difference per follower (having ~250x more Twitter followers). Many possible factors. Mastodon users see more from their followings. Twitter accounts could be mostly bots or abandoned. Recent posts are technical, maybe Mastodon users are more technical. Tech friends migrated first. Or hashtagging #fediverse.
: #indieweb 🤝 #fediverse✨ https://werd.io/2022/the-fediverse-and-the-indieweb (@benwerd)✨ https://catgirlin.space/posts/moving-to-the-fediverse-and-indieweb/✨ https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indiewebPreviously: https://twitter.com/t/status/1586264352453427201, https://twitter.com/t/status/956436348361158658 #TwitterMigration #ActivityPub #SocialWeb #OpenStandards #OpenWeb
's status on Friday, 02-Dec-2022 15:01:00 EST
#indieweb 🤝 #fediverse ✨ https://werd.io/2022/the-fediverse-and-the-indieweb (@benwerd) ✨ https://catgirlin.space/posts/moving-to-the-fediverse-and-indieweb/ ✨ https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indieweb Previously: https://twitter.com/t/status/1586264352453427201, https://twitter.com/t/status/956436348361158658 #TwitterMigration #ActivityPub #SocialWeb #OpenStandards #OpenWeb
apollo: Mastodon & SeizeMeans.comSince the middle of last year I've had a Mastodon instance at SeizeMeans.com. I didn't feel I should make it open to anyone else until I put together a Code of Conduct, but today I finally pieced one together. SeizeMeans.com is a Mastodon instance open to communists, socialists, anarchists and fellow travelers.https://apollolemmon.com/2019/09/12/mastodon-seizemeans-com/#anarchism #Communism #fediverse #Mastodon #socialism
apollo's status on Thursday, 12-Sep-2019 13:24:55 EDT
Mastodon & SeizeMeans.com Since the middle of last year I've had a Mastodon instance at SeizeMeans.com. I didn't feel I should make it open to anyone else until I put together a Code of Conduct, but today I finally pieced one together. SeizeMeans.com is a Mastodon instance open to communists, socialists, anarchists and fellow travelers. https://apollolemmon.com/2019/09/12/mastodon-seizemeans-com/ #anarchism #Communism #fediverse #Mastodon #socialism
douginamug: TODAY (28th) activist itinerary for #35c3 ✊ 🌍 🔥 - 13:00, #ExtinctionRebellion meetup @ Lect. rm. M1- 14:00, #YunoHost workshop @ Lect. rm. M1- 14:00, #Fediverse meetup @ Lect. rm. M3- 17:00, #Briar 'party' @ Curry Club Augsburg Assembly- 19:30, Intro to #Anarchy @ Lect. rm. M3Maybe see you there 🙂
douginamug's status on Friday, 28-Dec-2018 05:50:15 EST
TODAY (28th) activist itinerary for #35c3 ✊ 🌍 🔥 - 13:00, #ExtinctionRebellion meetup @ Lect. rm. M1 - 14:00, #YunoHost workshop @ Lect. rm. M1 - 14:00, #Fediverse meetup @ Lect. rm. M3 - 17:00, #Briar 'party' @ Curry Club Augsburg Assembly - 19:30, Intro to #Anarchy @ Lect. rm. M3 Maybe see you there 🙂
sebastians: I'm considering running a scholar/academic/research/education oriented #peertube instance, wondering how much interest there is in it on this bit of the #fediverse?It seems very doable, but bit steep in investment cost (hardware). I think it should be doable with a running cost of ca 100-150,- per month for hosting and hardware. Assuming sponsored/donated admin-time.
sebastians's status on Friday, 14-Dec-2018 05:34:31 EST
I'm considering running a scholar/academic/research/education oriented #peertube instance, wondering how much interest there is in it on this bit of the #fediverse? It seems very doable, but bit steep in investment cost (hardware). I think it should be doable with a running cost of ca 100-150,- per month for hosting and hardware. Assuming sponsored/donated admin-time.
slackz: Hey all, I wanna open up this invite again. I really want to grow organizing.social. This instance is a space for community organizers and we welcome folks trying to bring that work into a proper social media space.The #fediverse is vast and has been amazing, but #OrgSoc is way too small :PHere's an invite link:https://organizing.social/invite/tnBbPe2XWe wanna encourage a diversity of voices and joining this instance will mean you are a part of deciding how it operates.#DirectDemocracy#ComradesWelcome
slackz's status on Wednesday, 14-Nov-2018 11:27:27 EST
Hey all, I wanna open up this invite again. I really want to grow organizing.social. This instance is a space for community organizers and we welcome folks trying to bring that work into a proper social media space. The #fediverse is vast and has been amazing, but #OrgSoc is way too small :P Here's an invite link: https://organizing.social/invite/tnBbPe2X We wanna encourage a diversity of voices and joining this instance will mean you are a part of deciding how it operates. #DirectDemocracy #ComradesWelcome
bobjonkman: OK, that's definitely the best thing I've seen in the #Fediverse yet! Listening to the @hardmous archive, and just letting the images autoscroll in a full-screen browser... https://anonradio.net/archive/201811032200_hardmous.mp3
bobjonkman's status on Sunday, 04-Nov-2018 00:26:26 EDT
OK, that's definitely the best thing I've seen in the #Fediverse yet! Listening to the @hardmous archive, and just letting the images autoscroll in a full-screen browser... https://anonradio.net/archive/201811032200_hardmous.mp3
liamerven: Hey #Fediverse. When you post pictures, please please please with puppies on top fill in that description box for the visually impaired. You will be helping us out tremendously. We want to enjoy your pictures as much as others do. You don't have to write a novel, but just fill in some details.Thanks with much love:A Blind Dude
liamerven's status on Tuesday, 14-Aug-2018 13:30:11 EDT
Hey #Fediverse. When you post pictures, please please please with puppies on top fill in that description box for the visually impaired. You will be helping us out tremendously. We want to enjoy your pictures as much as others do. You don't have to write a novel, but just fill in some details. Thanks with much love: A Blind Dude
kosinus: You can now challenge someone to game of #chess over toots! https://castling.club/ 💪It's actually a standalone server in the #fediverse, implementing #activitypub all by itself. 😃
kosinus's status on Saturday, 04-Aug-2018 14:13:42 EDT
You can now challenge someone to game of #chess over toots! https://castling.club/ 💪 It's actually a standalone server in the #fediverse, implementing #activitypub all by itself. 😃
fuuko: Good afternoon #sdf, #tildeverse and #fediverse! Watching Trix play Dark Souls 3! Come get in here: https://www.twitch.tv/bagotrixhttps://www.twitch.tv/bagotrix
fuuko's status on Friday, 27-Jul-2018 13:15:12 EDT
Good afternoon #sdf, #tildeverse and #fediverse! Watching Trix play Dark Souls 3! Come get in here: https://www.twitch.tv/bagotrixhttps://www.twitch.tv/bagotrix
fuuko: Good afternoon #sdf, #tildeverse and #fediverse! Today I wonder about how we can make self-hosting easy for the average person. Something they could learn in 5 min with a cheat sheet. Of course, it depends on what you want to self-host, and it also opens a can of security worms. Maybe peer-to-peer solutions are the way to go for now? Stuff like RetroShare, ZeroNet, I2P and the like are good examples I guess, but are there other good applications out there not listed on wikipedia?
fuuko's status on Thursday, 26-Jul-2018 14:35:07 EDT
Good afternoon #sdf, #tildeverse and #fediverse! Today I wonder about how we can make self-hosting easy for the average person. Something they could learn in 5 min with a cheat sheet. Of course, it depends on what you want to self-host, and it also opens a can of security worms. Maybe peer-to-peer solutions are the way to go for now? Stuff like RetroShare, ZeroNet, I2P and the like are good examples I guess, but are there other good applications out there not listed on wikipedia?