Updates tagged with mastodon 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 → 🔮
: Twenty years ago this past February, Kevin Marks and I introduced #microformats in a conference presentation.Full post: https://tantek.com/2024/044/t1/twenty-years-microformatsAside: This is an even shorter summary of that post from ~200 days ago, which #Mastodon readers never got due to a Mastodon #federation bug (details in https://tantek.com/t5Yo1).Since early 2023, here are the top three updates & interesting developments in microformats:1. Growing rel=me adoption for distributed verification (✅ in Mastodon etc.) * Wikipedia, Threads, omg.lol2. Proposal to merge #microformats2 h-review into h-entry, since in practice (e.g. on #indieweb) reviews are just entries with a bit more.3. #metaformats adoptions, implementations, iteration
's status on Tuesday, 03-Sep-2024 21:47:00 EDT
Twenty years ago this past February, Kevin Marks and I introduced #microformats in a conference presentation. Full post: https://tantek.com/2024/044/t1/twenty-years-microformats Aside: This is an even shorter summary of that post from ~200 days ago, which #Mastodon readers never got due to a Mastodon #federation bug (details in https://tantek.com/t5Yo1). Since early 2023, here are the top three updates & interesting developments in microformats: 1. Growing rel=me adoption for distributed verification (✅ in Mastodon etc.) * Wikipedia, Threads, omg.lol 2. Proposal to merge #microformats2 h-review into h-entry, since in practice (e.g. on #indieweb) reviews are just entries with a bit more. 3. #metaformats adoptions, implementations, iteration
: Twenty years ago this past February, @KevinMarks.com (@KevinMarks@xoxo.zone) and I introduced #microformats in a conference presentation.Full post: https://tantek.com/2024/044/t1/twenty-years-microformatsAside: This is a summary of a longer post from ~200 days ago¹, which #Mastodon readers never got due to a Mastodon #federation bug (instances returned 202 for post inbox delivery, but did not show post to followers or on local profiles, details in https://tantek.com/t5Yo1).I wrote a retrospective last year: https://tantek.com/2023/047/t1/nineteen-years-microformatsSince then, here are the top three updates & interesting developments in microformats:1. Growing rel=me adoption for distributed verification (✅ in Mastodon etc.) * Wikipedia, Threads, omg.lol support2. A proposal to merge #microformats2 h-review into h-entry, since reviews are in practice (e.g. on the #indieweb) always entries with a bit more information.3. #metaformats adoptions, implementations, and iterationMore details: ¹ https://tantek.com/2024/044/t1/twenty-years-microformats
's status on Tuesday, 03-Sep-2024 17:02:00 EDT
Twenty years ago this past February, @KevinMarks.com (@KevinMarks@xoxo.zone) and I introduced #microformats in a conference presentation. Full post: https://tantek.com/2024/044/t1/twenty-years-microformats Aside: This is a summary of a longer post from ~200 days ago¹, which #Mastodon readers never got due to a Mastodon #federation bug (instances returned 202 for post inbox delivery, but did not show post to followers or on local profiles, details in https://tantek.com/t5Yo1). I wrote a retrospective last year: https://tantek.com/2023/047/t1/nineteen-years-microformats Since then, here are the top three updates & interesting developments in microformats: 1. Growing rel=me adoption for distributed verification (✅ in Mastodon etc.) * Wikipedia, Threads, omg.lol support 2. A proposal to merge #microformats2 h-review into h-entry, since reviews are in practice (e.g. on the #indieweb) always entries with a bit more information. 3. #metaformats adoptions, implementations, and iteration More details: ¹ https://tantek.com/2024/044/t1/twenty-years-microformats
: 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 → 🔮
: ✏️ I want the Read Write Suggest-Edit Accept-Edit Update Web.The consumer Infinite Scroll Web leaves us feeling empty.Too few of us participate in the Read Write Web, whether with personal sites or Wikipedia.A week ago when we wrapped up #IndieWebCamp Portland and I was reading Kevin Marks (@kevinmarks@indieweb.social) live-tooting of the demos¹, I noticed a few errors, typos or miscaptures, and pointed them out in-person.Kevin was able to quickly edit his toots and update them for anyone reading, thanks to #Mastodon’s post editing feature and its support of #ActivityPub Updates. But this shouldn’t require being in the same room, whether IRL or chat.We should be able to suggest edits to each other’s posts, as easily as we can reply and add a comment.13 years ago I wrote²: “The Read Write Web is no longer sufficient. I want the Read Fork Write Merge Web.”Now I want the Read Write Suggest-Edit Accept-Edit Update Web.The ↪ Reply button is fairly ubiquitous in modern post user interfaces (UIs).Why not also a ✏️ Suggest Edit button, to craft a fix for a typo, grammar, or other minor error, and send the author for their review, and acceptance or rejection? Perhaps viewable only by the suggester and the author, to avoid "performative" suggested edits.If the author’s posts provide revision histories, when a suggested edit is accepted, a post’s history could show the contributor of the edit.Instead of asking Kevin in-person, what if I could have posted special "Suggested Edit" responses in reply to his toots, for which he would receive special notifications, and could choose to one-click accept and update (or further edit) his toots?To enable such UIs and interactions across servers and implementations, we may need a new type of response³, perhaps with a special property (or more) to convey the edits being suggested.There is documentation of this and similar use-cases, prior art / UIs, as well as some brainstorming on the #IndieWeb wiki:* https://indieweb.org/editOur interaction after IndieWebCamp has inspired me to take another look at how can we design and prototype solutions to this problem.For now, if you host your blog and posts as static files on GitHub (or equivalent), you could add a button like this to your posts alongside Like, Reply, Repost buttons:✏️ Suggest Editand link it to an edit URL for the static file for the post.I don’t use GitHub static files myself for posts, but here’s an example of such an edit link for one of my projects:https://tantek.com/github/cassis/edit/main/README.mdThis will start the process of creating a “pull request”, GitHub’s jargon⁴ for a “suggested edit”.After completing GitHub’s ceremony of entering multiple text fields (summary & description), and multiple clicks to create said “pull request”, it’ll be sent to the author to review. Presuming the author likes the suggested edit, they can perform the other half of GitHub’s jargon-filled ceremonies to “Merge” or “Squash & Merge”, “Delete fork”, etc. to accept the edit.It’s an awkward interaction⁵, however useful for at least prototyping a ✏️ Suggest Edit button on sites that store their posts as files in GitHub. Certainly worthy of experimenting with and gathering experience to design and build even better interactions.We can start with the shortest path to getting something working, then learn, iterate, improve, repeat.#readWriteWeb #editableWeb #suggestEdit #acceptEditReferences:¹ https://indieweb.social/@kevinmarks/113025295600067213² https://tantek.com/2011/174/t1/read-fork-write-merge-web-osb11³ https://indieweb.org/responses⁴ The phrase “pull request” was derived from the git command: “git request-pull” according to https://www.reddit.com/r/git/comments/nvahcp/comment/h12hzj7/⁵ “edits” in GitHub require taking far more steps, and navigating far more jargon, then say, Wikipedia pages, which come down to “Edit” and “Save”. We should aspire to Wikipedia’s simplicity, not GitHub’s ceremonies.This is post 20 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2024/242/t1/indiewebcamp-portland→ https://tantek.com/2024/246/t1/adventures-indieweb-activitypub-bridgy-fed
's status on Sunday, 01-Sep-2024 17:51:00 EDT
✏️ I want the Read Write Suggest-Edit Accept-Edit Update Web. The consumer Infinite Scroll Web leaves us feeling empty. Too few of us participate in the Read Write Web, whether with personal sites or Wikipedia. A week ago when we wrapped up #IndieWebCamp Portland and I was reading Kevin Marks (@kevinmarks@indieweb.social) live-tooting of the demos¹, I noticed a few errors, typos or miscaptures, and pointed them out in-person. Kevin was able to quickly edit his toots and update them for anyone reading, thanks to #Mastodon’s post editing feature and its support of #ActivityPub Updates. But this shouldn’t require being in the same room, whether IRL or chat. We should be able to suggest edits to each other’s posts, as easily as we can reply and add a comment. 13 years ago I wrote²: “The Read Write Web is no longer sufficient. I want the Read Fork Write Merge Web.” Now I want the Read Write Suggest-Edit Accept-Edit Update Web. The ↪ Reply button is fairly ubiquitous in modern post user interfaces (UIs). Why not also a ✏️ Suggest Edit button, to craft a fix for a typo, grammar, or other minor error, and send the author for their review, and acceptance or rejection? Perhaps viewable only by the suggester and the author, to avoid "performative" suggested edits. If the author’s posts provide revision histories, when a suggested edit is accepted, a post’s history could show the contributor of the edit. Instead of asking Kevin in-person, what if I could have posted special "Suggested Edit" responses in reply to his toots, for which he would receive special notifications, and could choose to one-click accept and update (or further edit) his toots? To enable such UIs and interactions across servers and implementations, we may need a new type of response³, perhaps with a special property (or more) to convey the edits being suggested. There is documentation of this and similar use-cases, prior art / UIs, as well as some brainstorming on the #IndieWeb wiki: * https://indieweb.org/edit Our interaction after IndieWebCamp has inspired me to take another look at how can we design and prototype solutions to this problem. For now, if you host your blog and posts as static files on GitHub (or equivalent), you could add a button like this to your posts alongside Like, Reply, Repost buttons: ✏️ Suggest Edit and link it to an edit URL for the static file for the post. I don’t use GitHub static files myself for posts, but here’s an example of such an edit link for one of my projects: https://tantek.com/github/cassis/edit/main/README.md This will start the process of creating a “pull request”, GitHub’s jargon⁴ for a “suggested edit”. After completing GitHub’s ceremony of entering multiple text fields (summary & description), and multiple clicks to create said “pull request”, it’ll be sent to the author to review. Presuming the author likes the suggested edit, they can perform the other half of GitHub’s jargon-filled ceremonies to “Merge” or “Squash & Merge”, “Delete fork”, etc. to accept the edit. It’s an awkward interaction⁵, however useful for at least prototyping a ✏️ Suggest Edit button on sites that store their posts as files in GitHub. Certainly worthy of experimenting with and gathering experience to design and build even better interactions. We can start with the shortest path to getting something working, then learn, iterate, improve, repeat. #readWriteWeb #editableWeb #suggestEdit #acceptEdit References: ¹ https://indieweb.social/@kevinmarks/113025295600067213 ² https://tantek.com/2011/174/t1/read-fork-write-merge-web-osb11 ³ https://indieweb.org/responses ⁴ The phrase “pull request” was derived from the git command: “git request-pull” according to https://www.reddit.com/r/git/comments/nvahcp/comment/h12hzj7/ ⁵ “edits” in GitHub require taking far more steps, and navigating far more jargon, then say, Wikipedia pages, which come down to “Edit” and “Save”. We should aspire to Wikipedia’s simplicity, not GitHub’s ceremonies. This is post 20 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2024/242/t1/indiewebcamp-portland → https://tantek.com/2024/246/t1/adventures-indieweb-activitypub-bridgy-fed
: ✏️ I want the Read Write Suggest-Edit Accept-Edit Update Web.The consumer Infinite Scroll Web leaves us feeling empty.Too few of us participate in the Read Write Web, whether with personal sites or Wikipedia.A week ago when we wrapped up #IndieWebCamp Portland and I was reading @KevinMarks.com (@kevinmarks@indieweb.social @kevinmarks@xoxo.zone @kevinmarks) live-tooting of the demos¹, I noticed a few errors, typos or miscaptures, and pointed them out in-person.Kevin was able to quickly edit his toots and update them for anyone reading, thanks to #Mastodon’s post editing feature and its support of #ActivityPub Updates. But this shouldn’t require being in the same room, IRL or chat.We should be able to suggest edits to each other’s posts, as easily as we can reply and add a comment.13 years ago I wrote²: “The Read Write Web is no longer sufficient. I want the Read Fork Write Merge Web.”Now I want the Read Write Suggest-Edit Accept-Edit Update Web.The ↪ Reply button is fairly ubiquitous in modern post user interfaces (UIs).Why not also a ✏️ Suggest Edit button, to craft a fix for a typo, grammar, or other minor error, and send the author for their review, and acceptance or rejection? Perhaps viewable only by the suggester and the author, to avoid "performative" suggested edits.If the author’s posts provide revision histories, when a suggested edit is accepted, a post’s history could show the contributor of the edit.Instead of asking Kevin in-person, what if I could have posted special "Suggested Edit" responses in reply to his toots, for which he would receive special notifications, and could choose to one-click accept and update (or further edit) his toots?To enable such UIs and interactions across servers and implementations, we may need a new type of response³, perhaps with a special property (or more) to convey the edits being suggested.There is documentation of this and similar use-cases, prior art / UIs, as well as some brainstorming on the #IndieWeb wiki:* https://indieweb.org/editOur interaction after IndieWebCamp has inspired me to take another look at how can we design and prototype solutions to this problem.For now, if you host your blog and posts as static files on GitHub (or equivalent), you could add a button like this to your posts alongside Like, Reply, Repost buttons:✏️ Suggest Editand link it to an edit URL for the static file for the post.I don’t use GitHub static files myself for posts, but here’s an example of such an edit link for one of my projects:https://tantek.com/github/cassis/edit/main/README.mdThis will start the process of creating a “pull request”, GitHub’s jargon⁴ for a “suggested edit”.After completing GitHub’s ceremony of entering multiple text fields (summary & description), and multiple clicks to create said “pull request”, it’ll be sent to the author to review. Presuming the author likes the suggested edit, they can perform the other half of GitHub’s jargon-filled ceremonies to “Merge” or “Squash & Merge”, “Delete fork”, etc. to accept the edit.It’s an awkward interaction⁵, however useful for at least prototyping a ✏️ Suggest Edit button on sites that store their posts as files in GitHub. Certainly worthy of experimenting with and gathering experience to design and build even better interactions.We can start with the shortest path to getting something working, then learn, iterate, improve, repeat.#readWriteWeb #editableWeb #suggestEdit #acceptEditReferences:¹ https://indieweb.social/@kevinmarks/113025295600067213² https://tantek.com/2011/174/t1/read-fork-write-merge-web-osb11³ https://indieweb.org/responses⁴ The phrase “pull request” was derived from the git command: “git request-pull” according to https://www.reddit.com/r/git/comments/nvahcp/comment/h12hzj7/⁵ “edits” in GitHub require taking far more steps, and navigating far more jargon, then say, Wikipedia pages, which come down to “Edit” and “Save”. We should aspire to Wikipedia’s simplicity, not GitHub’s ceremonies.This is post 20 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2024/242/t1/indiewebcamp-portland→ 🔮
✏️ I want the Read Write Suggest-Edit Accept-Edit Update Web. The consumer Infinite Scroll Web leaves us feeling empty. Too few of us participate in the Read Write Web, whether with personal sites or Wikipedia. A week ago when we wrapped up #IndieWebCamp Portland and I was reading @KevinMarks.com (@kevinmarks@indieweb.social @kevinmarks@xoxo.zone @kevinmarks) live-tooting of the demos¹, I noticed a few errors, typos or miscaptures, and pointed them out in-person. Kevin was able to quickly edit his toots and update them for anyone reading, thanks to #Mastodon’s post editing feature and its support of #ActivityPub Updates. But this shouldn’t require being in the same room, IRL or chat. We should be able to suggest edits to each other’s posts, as easily as we can reply and add a comment. 13 years ago I wrote²: “The Read Write Web is no longer sufficient. I want the Read Fork Write Merge Web.” Now I want the Read Write Suggest-Edit Accept-Edit Update Web. The ↪ Reply button is fairly ubiquitous in modern post user interfaces (UIs). Why not also a ✏️ Suggest Edit button, to craft a fix for a typo, grammar, or other minor error, and send the author for their review, and acceptance or rejection? Perhaps viewable only by the suggester and the author, to avoid "performative" suggested edits. If the author’s posts provide revision histories, when a suggested edit is accepted, a post’s history could show the contributor of the edit. Instead of asking Kevin in-person, what if I could have posted special "Suggested Edit" responses in reply to his toots, for which he would receive special notifications, and could choose to one-click accept and update (or further edit) his toots? To enable such UIs and interactions across servers and implementations, we may need a new type of response³, perhaps with a special property (or more) to convey the edits being suggested. There is documentation of this and similar use-cases, prior art / UIs, as well as some brainstorming on the #IndieWeb wiki: * https://indieweb.org/edit Our interaction after IndieWebCamp has inspired me to take another look at how can we design and prototype solutions to this problem. For now, if you host your blog and posts as static files on GitHub (or equivalent), you could add a button like this to your posts alongside Like, Reply, Repost buttons: ✏️ Suggest Edit and link it to an edit URL for the static file for the post. I don’t use GitHub static files myself for posts, but here’s an example of such an edit link for one of my projects: https://tantek.com/github/cassis/edit/main/README.md This will start the process of creating a “pull request”, GitHub’s jargon⁴ for a “suggested edit”. After completing GitHub’s ceremony of entering multiple text fields (summary & description), and multiple clicks to create said “pull request”, it’ll be sent to the author to review. Presuming the author likes the suggested edit, they can perform the other half of GitHub’s jargon-filled ceremonies to “Merge” or “Squash & Merge”, “Delete fork”, etc. to accept the edit. It’s an awkward interaction⁵, however useful for at least prototyping a ✏️ Suggest Edit button on sites that store their posts as files in GitHub. Certainly worthy of experimenting with and gathering experience to design and build even better interactions. We can start with the shortest path to getting something working, then learn, iterate, improve, repeat. #readWriteWeb #editableWeb #suggestEdit #acceptEdit References: ¹ https://indieweb.social/@kevinmarks/113025295600067213 ² https://tantek.com/2011/174/t1/read-fork-write-merge-web-osb11 ³ https://indieweb.org/responses ⁴ The phrase “pull request” was derived from the git command: “git request-pull” according to https://www.reddit.com/r/git/comments/nvahcp/comment/h12hzj7/ ⁵ “edits” in GitHub require taking far more steps, and navigating far more jargon, then say, Wikipedia pages, which come down to “Edit” and “Save”. We should aspire to Wikipedia’s simplicity, not GitHub’s ceremonies. This is post 20 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2024/242/t1/indiewebcamp-portland → 🔮
: 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
: 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
: 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
: If you added a #Mastodon / #ActivityPub follow form to your #IndieWeb site based on Bridgy Fed (e.g. using code/instructions I previously posted¹), you need to update it to add another invisible input element for the "protocol", e.g.: Otherwise people trying to use your form to follow you may see an error from #BridgyFed like:> Bad Request > Missing required parameter protocolHere is the complete example that I posted previously with the new invisible input: 🐘 Follow @tantek.com@tantek.com: enter your @-@ fediverse address: Follow I also updated that previous post¹ with the new input in case people find that instead.This is day 42 of #100DaysOfIndieWeb. #100Days← Day 41: https://tantek.com/2023/139/t1/wikipedia-supports-indieweb-rel-me→ 🔮¹ https://tantek.com/2023/020/t2/bridgy-fed-follow-form
's status on Friday, 09-Jun-2023 22:14:00 EDT
If you added a #Mastodon / #ActivityPub follow form to your #IndieWeb site based on Bridgy Fed (e.g. using code/instructions I previously posted¹), you need to update it to add another invisible input element for the "protocol", e.g.: Otherwise people trying to use your form to follow you may see an error from #BridgyFed like: > Bad Request > Missing required parameter protocol Here is the complete example that I posted previously with the new invisible input: 🐘 Follow @tantek.com@tantek.com: enter your @-@ fediverse address: Follow I also updated that previous post¹ with the new input in case people find that instead. This is day 42 of #100DaysOfIndieWeb. #100Days ← Day 41: https://tantek.com/2023/139/t1/wikipedia-supports-indieweb-rel-me → 🔮 ¹ https://tantek.com/2023/020/t2/bridgy-fed-follow-form
: One of the pretty neat innovations from #Mastodon has been actual, functional, and fairly reliable (from all accounts I’ve seen) distributed system account migration, with the notable exception of post migration, which has additional challenges worth exploring.To be clear, as far as I know, no other blogging (or chat) software, system, or even protocol comes close to achieving the level of functionality described in Mastodon’s documentation:https://docs.joinmastodon.org/user/moving/#migrationIn short, moving:* all your profile information* moving all your followers & followings, transparently * redirecting your old account to your new oneMore at that link. From the docs, it’s clear that quite a bit of thought & consideration went into the design & implementation.Once I had setup #BridgyFed to #federate posts from my own site¹, I myself made use of the this Mastodon feature to migrate from my try-it-out @t@xoxo.zone account to my #IndieWeb @tantek.com (move destination handled by BridgyFed).For me the migration experience was 100%, because I had not posted anything @t@xoxo.zone.The challenge of post migration is not unique to Mastodon, though I believe it goes beyond “simple” export & import support, which is still a good place to start.Mastodon has two forms of posts “export” currently:* RSS feeds, which will get you some number of recent posts, by adding ".rss" to the end of any Mastodon profile URL, e.g. https://indieweb.social/@tchambers.rss* Activity Streams 2.0 JSON, per https://docs.joinmastodon.org/user/moving/#export (note: it currently says “ActivityPub JSON format”, but there is no such thing, #ActivityPub uses the #ActivityStreams 2.0 JSON format and I’ve filed a PR² to fix this in the docs)Lots of software & services import RSS, e.g. #WordPress.As far as I know, nothing (not even Mastodon itself) actually supports importing Activity Streams 2.0.There is a more complete format (with specification!) for exporting & importing blog content:Blog Archive Format (.bar), first specified here with example file:* https://www.manton.org/2017/11/24/blog-archive-format.htmlMore details and another example file:* https://www.manton.org/2021/12/27/importing-blog-archive.htmlBlog Archive Format has the very nice features of:* portable HTML feed (h-feed) and JSON Feed* photos and other media* locally browsable post archiveNaturally, https://micro.blog/ supports both exporting & importing Blog Archive Format.There’s an interesting opportunity here for an open source converter * from Activity Streams 2.0 * to Blog Archive FormatSuch a library would make an excellent drop-in addition to any #ActivityPub implementation, allowing both export of posts, and also a browsable archive format, so you could visually double check when importing to another service that these were the old posts you were looking for.This would be a good first step, using an open standard, towards Mastodon itself supporting post migration³.Ideally, similar to account migration, the old posts server should also at least:* redirect old permalinks to the new permalinks* redirect any replies being delivered by ActivityPub to the new location* provide #Webmention discovery forwarding from the old URLs to the new URLs (e.g. using HTTP LINK headers)for some amount of time.Want to add support for Blog Archive Format or got questions or feedback?Join in the development conversations: https://chat.indieweb.org/devThis is day 39 of #100DaysOfIndieWeb. #100Days← Day 38: https://tantek.com/2023/110/t2/beyond-mastodon-indieweb-own-domain→ 🔮Glossaryaccount migration https://indieweb.org/account_migrationblog archive format https://indieweb.org/blog_archive_formath-feed https://microformats.org/wiki/h-feedJSON Feed https://www.jsonfeed.org/post migration https://indieweb.org/post_migrationWebmention https://indieweb.org/WebmentionReferences¹ https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indieweb² https://github.com/mastodon/documentation/pull/1202³ https://github.com/mastodon/mastodon/issues/12423
's status on Saturday, 22-Apr-2023 20:40:00 EDT
One of the pretty neat innovations from #Mastodon has been actual, functional, and fairly reliable (from all accounts I’ve seen) distributed system account migration, with the notable exception of post migration, which has additional challenges worth exploring. To be clear, as far as I know, no other blogging (or chat) software, system, or even protocol comes close to achieving the level of functionality described in Mastodon’s documentation: https://docs.joinmastodon.org/user/moving/#migration In short, moving: * all your profile information * moving all your followers & followings, transparently * redirecting your old account to your new one More at that link. From the docs, it’s clear that quite a bit of thought & consideration went into the design & implementation. Once I had setup #BridgyFed to #federate posts from my own site¹, I myself made use of the this Mastodon feature to migrate from my try-it-out @t@xoxo.zone account to my #IndieWeb @tantek.com (move destination handled by BridgyFed). For me the migration experience was 100%, because I had not posted anything @t@xoxo.zone. The challenge of post migration is not unique to Mastodon, though I believe it goes beyond “simple” export & import support, which is still a good place to start. Mastodon has two forms of posts “export” currently: * RSS feeds, which will get you some number of recent posts, by adding ".rss" to the end of any Mastodon profile URL, e.g. https://indieweb.social/@tchambers.rss * Activity Streams 2.0 JSON, per https://docs.joinmastodon.org/user/moving/#export (note: it currently says “ActivityPub JSON format”, but there is no such thing, #ActivityPub uses the #ActivityStreams 2.0 JSON format and I’ve filed a PR² to fix this in the docs) Lots of software & services import RSS, e.g. #WordPress. As far as I know, nothing (not even Mastodon itself) actually supports importing Activity Streams 2.0. There is a more complete format (with specification!) for exporting & importing blog content: Blog Archive Format (.bar), first specified here with example file: * https://www.manton.org/2017/11/24/blog-archive-format.html More details and another example file: * https://www.manton.org/2021/12/27/importing-blog-archive.html Blog Archive Format has the very nice features of: * portable HTML feed (h-feed) and JSON Feed * photos and other media * locally browsable post archive Naturally, https://micro.blog/ supports both exporting & importing Blog Archive Format. There’s an interesting opportunity here for an open source converter * from Activity Streams 2.0 * to Blog Archive Format Such a library would make an excellent drop-in addition to any #ActivityPub implementation, allowing both export of posts, and also a browsable archive format, so you could visually double check when importing to another service that these were the old posts you were looking for. This would be a good first step, using an open standard, towards Mastodon itself supporting post migration³. Ideally, similar to account migration, the old posts server should also at least: * redirect old permalinks to the new permalinks * redirect any replies being delivered by ActivityPub to the new location * provide #Webmention discovery forwarding from the old URLs to the new URLs (e.g. using HTTP LINK headers) for some amount of time. Want to add support for Blog Archive Format or got questions or feedback? Join in the development conversations: https://chat.indieweb.org/dev This is day 39 of #100DaysOfIndieWeb. #100Days ← Day 38: https://tantek.com/2023/110/t2/beyond-mastodon-indieweb-own-domain → 🔮 Glossary account migration https://indieweb.org/account_migration blog archive format https://indieweb.org/blog_archive_format h-feed https://microformats.org/wiki/h-feed JSON Feed https://www.jsonfeed.org/ post migration https://indieweb.org/post_migration Webmention https://indieweb.org/Webmention References ¹ https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indieweb ² https://github.com/mastodon/documentation/pull/1202 ³ https://github.com/mastodon/mastodon/issues/12423
: In https://www.theverge.com/2023/4/20/23689570/activitypub-protocol-standard-social-network, author @pierce@mas.to does an excellent job covering a broad range of #ActivityPub related updates, and goes beyond the usual #Mastodon focus to describe numerous implementations.I was very happy to see that he also clearly communicated several #IndieWeb principles¹, practices, goals, and reasons why². Like this quote: “But the advice you’ll hear from most people in this space is this: own your own domain. Don’t be john@/mastodon.social or anna@/facebook.com. Have a space that is yours, that belongs to you, a username and identity that can’t disappear just because a company goes out of business or sells to a megalomaniac.”and this: “It’s [your own domain is] your YouTube channel name and your TikTok username and your Instagram handle and your phone number and your Twitter @, all in one name.”Great interviews with @stevetex@mozilla.social, @mike@flipboard.social, @dustycloud.org (@cwebber@octodon.social), @evanp.me (@evan@cosocial.ca), @anildash.com (@anildash@me.dm), @coachtony@me.dm, and @manton.org.As Manton said in the article: “If you solve identity with domain names, it makes things easier because it fits the way the web has been for 20 years,”Pierce also noted: “you might soon be able to turn your personal website into your entire social identity online” Already can.I replied to Pierce’s post³ about his article noting this⁴, from #federating directly from my website for the past ~6 months⁵, to over a decade of using it as my social identity with the POSSE method⁶ with various #socialMedia silos.It’s important enough that I’ll repeat part of Pierce’s quote at the top: “own your own domain. Don’t be john@/mastodon.social or anna@/facebook.com. Have a space that is yours” He gets it. Don’t be someone at someone else’s server. Big Chad or Little Chad’s garages⁷ are social media stepping stones towards owning your own domain and IndieWeb presence.We’re here when you’re ready to take that next step: https://chat.indieweb.org/This is day 38 of #100DaysOfIndieWeb. #100Days← Day 37: https://tantek.com/2023/109/t2/years-ago-first-federated-indieweb-thread→ 🔮¹ https://indieweb.org/principles² https://indieweb.org/why³ https://mas.to/@pierce/110231624819547202⁴ https://tantek.com/2023/110/t1/⁵ https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indieweb⁶ https://indieweb.org/POSSE⁷ https://tantek.com/2023/001/t1/own-your-notes
's status on Thursday, 20-Apr-2023 20:57:00 EDT
In https://www.theverge.com/2023/4/20/23689570/activitypub-protocol-standard-social-network, author @pierce@mas.to does an excellent job covering a broad range of #ActivityPub related updates, and goes beyond the usual #Mastodon focus to describe numerous implementations. I was very happy to see that he also clearly communicated several #IndieWeb principles¹, practices, goals, and reasons why². Like this quote: “But the advice you’ll hear from most people in this space is this: own your own domain. Don’t be john@/mastodon.social or anna@/facebook.com. Have a space that is yours, that belongs to you, a username and identity that can’t disappear just because a company goes out of business or sells to a megalomaniac.” and this: “It’s [your own domain is] your YouTube channel name and your TikTok username and your Instagram handle and your phone number and your Twitter @, all in one name.” Great interviews with @stevetex@mozilla.social, @mike@flipboard.social, @dustycloud.org (@cwebber@octodon.social), @evanp.me (@evan@cosocial.ca), @anildash.com (@anildash@me.dm), @coachtony@me.dm, and @manton.org. As Manton said in the article: “If you solve identity with domain names, it makes things easier because it fits the way the web has been for 20 years,” Pierce also noted: “you might soon be able to turn your personal website into your entire social identity online” Already can. I replied to Pierce’s post³ about his article noting this⁴, from #federating directly from my website for the past ~6 months⁵, to over a decade of using it as my social identity with the POSSE method⁶ with various #socialMedia silos. It’s important enough that I’ll repeat part of Pierce’s quote at the top: “own your own domain. Don’t be john@/mastodon.social or anna@/facebook.com. Have a space that is yours” He gets it. Don’t be someone at someone else’s server. Big Chad or Little Chad’s garages⁷ are social media stepping stones towards owning your own domain and IndieWeb presence. We’re here when you’re ready to take that next step: https://chat.indieweb.org/ This is day 38 of #100DaysOfIndieWeb. #100Days ← Day 37: https://tantek.com/2023/109/t2/years-ago-first-federated-indieweb-thread → 🔮 ¹ https://indieweb.org/principles ² https://indieweb.org/why ³ https://mas.to/@pierce/110231624819547202 ⁴ https://tantek.com/2023/110/t1/ ⁵ https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indieweb ⁶ https://indieweb.org/POSSE ⁷ https://tantek.com/2023/001/t1/own-your-notes
: 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
: 3 weeks since the 1st, since asking you to own your notes^1Still tweeting in Big Chad’s garage or tooting in little Chad’s garage next door?^2 What's the delay?Choosing a domain name?^3Or a service or other path?^4Or #TwitterMigration to #Mastodon?Two #IndieWeb alternatives to owning your notes (https://micro.blog/ or https://fed.brid.gy/, either with your own domain) both support migrating your followers from Mastodon.For example, I migrated my experimental @t@xoxo.zone Mastodon account to my own site^5, @tantek.com, thanks to the migration support in Bridgy Fed.If you’re not sure where you’d like to migrate, you can try https://micro.blog/ for 30 days to see if it works for you.If you’re a #webDev or otherwise like to tinker, it’s well worth the time to setup your own website with an SSG or CMS^6 or your own code, and grow it incrementally as you post and have time to do so.Either way, drop by https://chat.indieweb.org/ and ask any questions you have. There’s a whole community that wants you to succeed, that wants to help you own your notes.This is day 21 of #100DaysOfIndieWeb #100Days, written the night after. ← Day 20: https://tantek.com/2023/022/t1/indieweb-eat-what-you-cook→ 🔮^1 https://tantek.com/2023/001/t1/own-your-notes^2 https://xkcd.com/1150/^3 https://tantek.com/2023/004/t1/choosing-domain-name-indieweb^4 https://tantek.com/2023/003/t1/indieweb-path-chosen-why^5 https://tantek.com/2022/358/t3/^6 https://indieweb.org/CMS
's status on Monday, 23-Jan-2023 02:49:00 EST
3 weeks since the 1st, since asking you to own your notes^1 Still tweeting in Big Chad’s garage or tooting in little Chad’s garage next door?^2 What's the delay? Choosing a domain name?^3 Or a service or other path?^4 Or #TwitterMigration to #Mastodon? Two #IndieWeb alternatives to owning your notes (https://micro.blog/ or https://fed.brid.gy/, either with your own domain) both support migrating your followers from Mastodon. For example, I migrated my experimental @t@xoxo.zone Mastodon account to my own site^5, @tantek.com, thanks to the migration support in Bridgy Fed. If you’re not sure where you’d like to migrate, you can try https://micro.blog/ for 30 days to see if it works for you. If you’re a #webDev or otherwise like to tinker, it’s well worth the time to setup your own website with an SSG or CMS^6 or your own code, and grow it incrementally as you post and have time to do so. Either way, drop by https://chat.indieweb.org/ and ask any questions you have. There’s a whole community that wants you to succeed, that wants to help you own your notes. This is day 21 of #100DaysOfIndieWeb #100Days, written the night after. ← Day 20: https://tantek.com/2023/022/t1/indieweb-eat-what-you-cook → 🔮 ^1 https://tantek.com/2023/001/t1/own-your-notes ^2 https://xkcd.com/1150/ ^3 https://tantek.com/2023/004/t1/choosing-domain-name-indieweb ^4 https://tantek.com/2023/003/t1/indieweb-path-chosen-why ^5 https://tantek.com/2022/358/t3/ ^6 https://indieweb.org/CMS
: Sometimes it’s the little things, like editing a post. Edit a reply, see a comment update on another post.From day 5 (https://tantek.com/2023/005/t3/indieweb-simpler-approach)* Can I edit my post after publishing?Whether a tweet or Instagram photo, the answer is no.^1Blogs and websites have had editing capabilities since the start.However, no site is an island, it's a *web* site. Interlinked.We expect edits on one site to show up when embedded or syndicated on other sites.#Webmention provides the ability for cross-site comments, and unlike the "one-off" prior protocols of Trackbacks & Pingbacks^2, when you update a cross-site comment, by resending a Webmention, the other post updates its copy of your reply: https://www.w3.org/TR/webmention/#sending-webmentions-for-updated-postsIf you delete a reply, by resending a Webmention, the other post can delete its copy (or mark it as deleted) https://www.w3.org/TR/webmention/#sending-webmentions-for-deleted-postsSimilarly, the #ActivityPub protocol specifies update & delete capabilities, as implemented by #Mastodon and others.#BridgyFed (https://fed.brid.gy) bridges (as the name says) these two protocols, which enables the following interactions.#IndieWeb post -(Webmention)-> BridgyFed -(ActivtyPub)-> Mastodon displays postand then this:IndieWeb updated post -(Webmention)-> BridgyFed -(ActivtyPub)-> Mastodon displays updated postThis works for replies to toots as well:IndieWeb reply to toot -(Webmention)-> BridgyFed -(ActivtyPub)-> toot displays replyand subsequently:IndieWeb updated reply -(Webmention)-> BridgyFed -(ActivtyPub)-> toot updates display of replyThanks to these update protocols in Webmention & ActivityPub, and BridgyFed connecting them, after adding “forward-in-time” links (https://tantek.com/2023/006/t1/forward-in-time-links) I was able to resend webmentions for my previous #100DaysOfIndieWeb posts, and have those forward links show up wherever my posts were already displayed on Mastodon.Posts interlinked with replies interlinked with protocols interlinked.This is day 9 of #100DaysOfIndieWeb #100Days.← Day 8: https://tantek.com/2023/008/t7/bridgy-indieweb-posse-backfeed→ 🔮^1 The ability to edit tweets has literally been the most requested feature on Twitter since perhaps its launch. Last year, paid Twitter “Blue” accounts finally got the ability to edit tweets, sort of: five times within 30 minutes of posting. Too little, too late.* https://techcrunch.com/2022/10/03/twitters-edit-button-is-rolling-out-to-blue-subscribers-in-canada-australia-and-new-zealand/* https://blog.hootsuite.com/can-you-edit-a-tweet/* https://www.pcmag.com/news/twitters-edit-button-is-coming-soon-for-paid-users* https://www.macrumors.com/2022/10/06/twitter-edit-tweet-option-united-states/* https://9to5mac.com/2022/10/06/twitter-rolling-out-edit-button/^2 Pingbacks were originally (and for many years) only implemented as one-off cross-blog interactions. One-time, uneditable. Pingbacks (and Trackbacks before them) were notoriously ugly when they showed up on blogs, listed & displayed as a separate thing (never tie presentation to the name of a protocol) with cryptically elided summaries: https://indieweb.org/pingback#Poor_display. It took over 10 years since being specified (2002) for the IndieWeb community to re-use pingbacks for actual comments across sites: https://tantek.com/2013/113/b1/first-federated-indieweb-comment-thread separating presentation & UI from the protocol. This separation of concerns approach evolved into the Webmention specification, separating the protocol from the display of comments, likes, reposts, and other social web https://indieweb.org/responses.
's status on Tuesday, 10-Jan-2023 01:44:00 EST
Sometimes it’s the little things, like editing a post. Edit a reply, see a comment update on another post. From day 5 (https://tantek.com/2023/005/t3/indieweb-simpler-approach) * Can I edit my post after publishing? Whether a tweet or Instagram photo, the answer is no.^1 Blogs and websites have had editing capabilities since the start. However, no site is an island, it's a *web* site. Interlinked. We expect edits on one site to show up when embedded or syndicated on other sites. #Webmention provides the ability for cross-site comments, and unlike the "one-off" prior protocols of Trackbacks & Pingbacks^2, when you update a cross-site comment, by resending a Webmention, the other post updates its copy of your reply: https://www.w3.org/TR/webmention/#sending-webmentions-for-updated-posts If you delete a reply, by resending a Webmention, the other post can delete its copy (or mark it as deleted) https://www.w3.org/TR/webmention/#sending-webmentions-for-deleted-posts Similarly, the #ActivityPub protocol specifies update & delete capabilities, as implemented by #Mastodon and others. #BridgyFed (https://fed.brid.gy) bridges (as the name says) these two protocols, which enables the following interactions. #IndieWeb post -(Webmention)-> BridgyFed -(ActivtyPub)-> Mastodon displays post and then this: IndieWeb updated post -(Webmention)-> BridgyFed -(ActivtyPub)-> Mastodon displays updated post This works for replies to toots as well: IndieWeb reply to toot -(Webmention)-> BridgyFed -(ActivtyPub)-> toot displays reply and subsequently: IndieWeb updated reply -(Webmention)-> BridgyFed -(ActivtyPub)-> toot updates display of reply Thanks to these update protocols in Webmention & ActivityPub, and BridgyFed connecting them, after adding “forward-in-time” links (https://tantek.com/2023/006/t1/forward-in-time-links) I was able to resend webmentions for my previous #100DaysOfIndieWeb posts, and have those forward links show up wherever my posts were already displayed on Mastodon. Posts interlinked with replies interlinked with protocols interlinked. This is day 9 of #100DaysOfIndieWeb #100Days. ← Day 8: https://tantek.com/2023/008/t7/bridgy-indieweb-posse-backfeed → 🔮 ^1 The ability to edit tweets has literally been the most requested feature on Twitter since perhaps its launch. Last year, paid Twitter “Blue” accounts finally got the ability to edit tweets, sort of: five times within 30 minutes of posting. Too little, too late. * https://techcrunch.com/2022/10/03/twitters-edit-button-is-rolling-out-to-blue-subscribers-in-canada-australia-and-new-zealand/ * https://blog.hootsuite.com/can-you-edit-a-tweet/ * https://www.pcmag.com/news/twitters-edit-button-is-coming-soon-for-paid-users * https://www.macrumors.com/2022/10/06/twitter-edit-tweet-option-united-states/ * https://9to5mac.com/2022/10/06/twitter-rolling-out-edit-button/ ^2 Pingbacks were originally (and for many years) only implemented as one-off cross-blog interactions. One-time, uneditable. Pingbacks (and Trackbacks before them) were notoriously ugly when they showed up on blogs, listed & displayed as a separate thing (never tie presentation to the name of a protocol) with cryptically elided summaries: https://indieweb.org/pingback#Poor_display. It took over 10 years since being specified (2002) for the IndieWeb community to re-use pingbacks for actual comments across sites: https://tantek.com/2013/113/b1/first-federated-indieweb-comment-thread separating presentation & UI from the protocol. This separation of concerns approach evolved into the Webmention specification, separating the protocol from the display of comments, likes, reposts, and other social web https://indieweb.org/responses.
: Is it hard to setup & use your own #IndieWeb site?Depends on the path chosen, and why.1 turnkey: get a https://micro.blog/ - easier than #Mastodon, works with2 #webdev: install a https://indieweb.org/CMS - needs tech knowhow3 builder: assemble https://indieweb.org/building_blocks as desired, experiment, iterate, and explore how deep the rabbit hole goesAll paths share perhaps the hardest part:Picking a domain name. Next, tips for choosing one.This is day 3 of #100DaysOfIndieWeb #100DaysDay 2: https://tantek.com/2023/002/t6/key-owning-notes-domain-name
's status on Wednesday, 04-Jan-2023 02:36:00 EST
Is it hard to setup & use your own #IndieWeb site? Depends on the path chosen, and why. 1 turnkey: get a https://micro.blog/ - easier than #Mastodon, works with 2 #webdev: install a https://indieweb.org/CMS - needs tech knowhow 3 builder: assemble https://indieweb.org/building_blocks as desired, experiment, iterate, and explore how deep the rabbit hole goes All paths share perhaps the hardest part: Picking a domain name. Next, tips for choosing one. This is day 3 of #100DaysOfIndieWeb #100Days Day 2: https://tantek.com/2023/002/t6/key-owning-notes-domain-name
: Is it hard to setup & use your own #IndieWeb site?Depends on the path choosen, and why1 turnkey: get a https://micro.blog/ - easier than #Mastodon, works with2 #webdev: install a https://indieweb.org/CMS - needs tech knowhow3 builder: assemble https://indieweb.org/building_blocks as desired, experiment, iterate, and explore how deep the rabbit hole goesAll paths share perhaps the hardest part:Picking a domain name. Next, tips for choosing one.This is day 3 of #100DaysOfIndieWeb #100DaysDay 2: https://tantek.com/2023/002/t6/key-owning-notes-domain-name
Is it hard to setup & use your own #IndieWeb site? Depends on the path choosen, and why 1 turnkey: get a https://micro.blog/ - easier than #Mastodon, works with 2 #webdev: install a https://indieweb.org/CMS - needs tech knowhow 3 builder: assemble https://indieweb.org/building_blocks as desired, experiment, iterate, and explore how deep the rabbit hole goes All paths share perhaps the hardest part: Picking a domain name. Next, tips for choosing one. This is day 3 of #100DaysOfIndieWeb #100Days Day 2: https://tantek.com/2023/002/t6/key-owning-notes-domain-name
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.
lnxw48a1: Oh, look! Evan has his own #Mastodon server now. https://prodromou.pub/@evan
lnxw48a1's status on Friday, 11-Nov-2022 23:27:04 EST
Oh, look! Evan has his own #Mastodon server now. https://prodromou.pub/@evan
: #TwitterMigration, first time?Have posted notes at https://tantek.com/ since 2010, syndicated tweets & an #AtomFeed.Added one .htaccess line, thanks to #BridgyFed, if you use #Mastodon, you can follow my #IndieWeb site:@tantek.com@tantek.comWhich demonstrates both the redundancy & awkwardness (it’s not a clickable URL) of such @-@ (AT-AT) usernames.Like why make me type or show “@tantek.com” twice like that?Why can’t Mastodon follow a username of “@tantek.com”? Or just “tantek.com”?And either way expanding it internally if need be to the AT-AT syntax.Why this regression from what we had with classic feed readers where a domain was enough to discover & follow a feed?Also, why does following show a blank result?Contrast that with classic feed readers which immediately show you the most recent items in a feed you subscribed to.Lastly (for now), I asked around and no one knew of a simple public way to “preview” or “validate” that @tantek.com@tantek.com actually “worked”. You have to be *logged-in* to a Mastodon instance and search for a username to check to see if it works.Contrast that with https://validator.w3.org/feed/ which you can use without any log-in to validate that your classic feed file works.Why these regressions from the days of feed readers?
's status on Saturday, 29-Oct-2022 01:01:00 EDT
#TwitterMigration, first time? Have posted notes at https://tantek.com/ since 2010, syndicated tweets & an #AtomFeed. Added one .htaccess line, thanks to #BridgyFed, if you use #Mastodon, you can follow my #IndieWeb site: @tantek.com@tantek.com Which demonstrates both the redundancy & awkwardness (it’s not a clickable URL) of such @-@ (AT-AT) usernames. Like why make me type or show “@tantek.com” twice like that? Why can’t Mastodon follow a username of “@tantek.com”? Or just “tantek.com”? And either way expanding it internally if need be to the AT-AT syntax. Why this regression from what we had with classic feed readers where a domain was enough to discover & follow a feed? Also, why does following show a blank result? Contrast that with classic feed readers which immediately show you the most recent items in a feed you subscribed to. Lastly (for now), I asked around and no one knew of a simple public way to “preview” or “validate” that @tantek.com@tantek.com actually “worked”. You have to be *logged-in* to a Mastodon instance and search for a username to check to see if it works. Contrast that with https://validator.w3.org/feed/ which you can use without any log-in to validate that your classic feed file works. Why these regressions from the days of feed readers?
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
bobjonkman: Making !GNUsocial work with #ActivityPub is the right thing to do, but I'm not sure that removing OStatus is. Does #Mastodon allow transport protocols to be added as plugins?
bobjonkman's status on Sunday, 30-Dec-2018 20:26:33 EST
Making !GNUsocial work with #ActivityPub is the right thing to do, but I'm not sure that removing OStatus is. Does #Mastodon allow transport protocols to be added as plugins?
douginamug: #ExtinctionRebellion session @ #35c3 is FULL! One third of the people sitting on the floor 😂 Amazing to see a room full of hackers excited to join the cause. There's enthusiasm to help non-techy people switch to #signal, #mastodon & #nextcloud ⚡ 💻 🌐
douginamug's status on Friday, 28-Dec-2018 07:46:43 EST
#ExtinctionRebellion session @ #35c3 is FULL! One third of the people sitting on the floor 😂 Amazing to see a room full of hackers excited to join the cause. There's enthusiasm to help non-techy people switch to #signal, #mastodon & #nextcloud ⚡ 💻 🌐
morganth: I should probably explain that hashtag, #foak. Back in the Usenet days (I know, I’m old), we used “FOAK” in subject lines to designate a fact-based question we were looking for an answer to. The idea was that Usenet contained so many knowledgeable people that we were collectively the Font Of All Knowledge. I’d love it if that caught on as a hashtag here; I’d really enjoy following the tag and seeing if I could answer any of the questions. #meta #mastodon
morganth's status on Thursday, 20-Sep-2018 20:37:18 EDT
I should probably explain that hashtag, #foak. Back in the Usenet days (I know, I’m old), we used “FOAK” in subject lines to designate a fact-based question we were looking for an answer to. The idea was that Usenet contained so many knowledgeable people that we were collectively the Font Of All Knowledge. I’d love it if that caught on as a hashtag here; I’d really enjoy following the tag and seeing if I could answer any of the questions. #meta #mastodon
switchingsocial: TIL if you want to subscribe to a #Mastodon account via #RSS or #Atom, just add .rss or .atom to the end of their profile page's address.For example:Profile page:https://mastodon.at/@switchingsocialRSS feed:https://mastodon.at/@switchingsocial.rssAtom feed:https://mastodon.at/@switchingsocial.atom#News #Feeds #NewsFeeds #FeedReaders #NewsAggregation #Aggregation #ReallySimpleSyndication
switchingsocial's status on Friday, 13-Jul-2018 12:55:04 EDT
TIL if you want to subscribe to a #Mastodon account via #RSS or #Atom, just add .rss or .atom to the end of their profile page's address. For example: Profile page: https://mastodon.at/@switchingsocial RSS feed: https://mastodon.at/@switchingsocial.rss Atom feed: https://mastodon.at/@switchingsocial.atom #News #Feeds #NewsFeeds #FeedReaders #NewsAggregation #Aggregation #ReallySimpleSyndication
mmn: Holy crap there's a bunch of commercial crap pouring from #Mastodon. What do people think this is, a market place?! Person-to-person sales are capitalism too, remember.
mmn's status on Sunday, 26-Nov-2017 05:11:37 EST
Holy crap there's a bunch of commercial crap pouring from #Mastodon. What do people think this is, a market place?! Person-to-person sales are capitalism too, remember.
tdemin: Looks like I'm abandoning on my #Mastodon account. I've migrated back to #Twitter since it introduced the #280characters limit. And yes, there are better clients than Mastodon now has. #TweetDeck is not as good as Mastodon's web client, but in general it's OK.Maybe I'll be back at some point.https://twitter.com/timur_demin
tdemin's status on Saturday, 11-Nov-2017 07:33:30 EST
Looks like I'm abandoning on my #Mastodon account. I've migrated back to #Twitter since it introduced the #280characters limit. And yes, there are better clients than Mastodon now has. #TweetDeck is not as good as Mastodon's web client, but in general it's OK. Maybe I'll be back at some point. https://twitter.com/timur_demin
mmn: It is also thanks to Evan that !ostatus hade a platform in #identica to strive on, which turned into StatusNet which is today !GNUsocial and was the network which #Mastodon could bootstrap off and to this day federates with.
mmn's status on Sunday, 22-Oct-2017 10:37:36 EDT
It is also thanks to Evan that !ostatus hade a platform in #identica to strive on, which turned into StatusNet which is today !GNUsocial and was the network which #Mastodon could bootstrap off and to this day federates with.
mmn: @oxenfree @cybermeow @elizafox @cyberpotato @cajun @thatbrickster @lain @heluecht Hi, I'm @mmn, maintainer of GNUsocial. I reacted when it was written that "many people on gnusocial are angry" and wish to say that !GNUsocial has only love and appreciation for #Mastodon and #ActivityPub. I believe cooperation is important for libre software and the federated social web. I believe our plural and diverse community should embrace and encourage contributors and development. Any progress we want to make - regardless of anyone's preferred technology - is impeded by hostility and empowered by friendship. So I want to say thank @cwebber @gargron et al. for all the hard work you actively put into ActivityPub. It's awesome that so many users get in touch with !fs via open protocols.
mmn's status on Monday, 11-Sep-2017 04:50:08 EDT
@oxenfree @cybermeow @elizafox @cyberpotato @cajun @thatbrickster @lain @heluecht Hi, I'm @mmn, maintainer of GNUsocial. I reacted when it was written that "many people on gnusocial are angry" and wish to say that !GNUsocial has only love and appreciation for #Mastodon and #ActivityPub. I believe cooperation is important for libre software and the federated social web. I believe our plural and diverse community should embrace and encourage contributors and development. Any progress we want to make - regardless of anyone's preferred technology - is impeded by hostility and empowered by friendship. So I want to say thank @cwebber @gargron et al. for all the hard work you actively put into ActivityPub. It's awesome that so many users get in touch with !fs via open protocols.
mmn: @cwebber The only reason !GNUsocial doesn't have #ActivityPub yet is because I have a fulltime job and noone else has been up for the task .] Though I'm pretty sure it'd still just be the 100% public parts of AP that would be used/promoted, as I'm pretty much convinced there's no such thing as privacy in the social sphere anyway and anyone using "private" communication in an environment like !GNUsocial or #Mastodon is fooled either by the platform, the administrator or other users. (anything accessible via a web browser isn't made for privacy)
mmn's status on Tuesday, 05-Sep-2017 18:37:58 EDT
@cwebber The only reason !GNUsocial doesn't have #ActivityPub yet is because I have a fulltime job and noone else has been up for the task .] Though I'm pretty sure it'd still just be the 100% public parts of AP that would be used/promoted, as I'm pretty much convinced there's no such thing as privacy in the social sphere anyway and anyone using "private" communication in an environment like !GNUsocial or #Mastodon is fooled either by the platform, the administrator or other users. (anything accessible via a web browser isn't made for privacy)
mmn: @patrickme !GNUsocial is another piece of software entirely that has some features that #Mastodon lacks and vice versa.
mmn's status on Sunday, 13-Aug-2017 12:13:00 EDT
@patrickme !GNUsocial is another piece of software entirely that has some features that #Mastodon lacks and vice versa.
gargron: #Mastodon v1.5.1 is a really small patch release that fixes a rather important regression in 1.5.0 that (to my knowledge) affected primarily GNU social accounts https://github.com/tootsuite/mastodon/releases/tag/v1.5.1
gargron's status on Sunday, 06-Aug-2017 18:04:34 EDT
#Mastodon v1.5.1 is a really small patch release that fixes a rather important regression in 1.5.0 that (to my knowledge) affected primarily GNU social accounts https://github.com/tootsuite/mastodon/releases/tag/v1.5.1
mmn: PS, that server is (at least to search engine caches) a #Mastodon instance ,)
mmn's status on Monday, 10-Jul-2017 15:01:30 EDT
PS, that server is (at least to search engine caches) a #Mastodon instance ,)