status.blaise.ca
type: Site
name: stadeus
space of: mastodon

mastodon
type: Container
type: channel
description: Updates tagged with mastodon on stadeus!
licence: http://creativecommons.org/licenses/by/3.0/
items: microformats-20-years
items: three-steps-indieweb-cybersecurity
items: micro-one-onramp-open-social-web
items: indiewebcamp-berlin-2024-day-1
items: fediverse-unfollow-bridgyfed-bug
items: w3c-link-checker-before-federating
items: twenty-years-microformats-shorter2
items: twenty-years-microformats-summary
items: adventures-indieweb-activitypub-bridgy-fed
items: read-write-suggest-edit-update-web
items: read-write-suggest-edit-web
items: created-at-indiewebcamp-brighton
items: the-ephemeral-web
items: twenty-years-microformats-updates
items: twenty-years-microformats
items: restarting-100days-indieweb-gift-calendar
items: capture-first-edit-publish-later
items: posse-syndicate-link-reply
items: bridgyfed-webmention-like-fediverse
items: federating-mentions
items: summary-w3c-tpac-2023
items: socialweb-cg-w3ctpac
items: mastodon-activitypub-follow-form-bridgy-fed
items: account-migration-post-blog-archive-format
items: beyond-mastodon-indieweb-own-domain
items: mozfest-making-fediverse-socialweb
items: mozfest-making-fediverse
items: own-your-notes-domain-migration
items: edit-reply-comment-update
items: indieweb-path-chosen-why
items: indieweb-path-you-choose
items: objectType=note
items: lnxw48a1: Oh, look! Evan has his own #Mastodon server now. https://prodromou.pub/@evan
items: twittermigration-bridgyfed-mastodon-indieweb
items: https://seizemeans.com/users/apollo/statuses/102780704884365882
items: 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?
items: https://mastodon.xyz/users/douginamug/statuses/101318734890999447
items: https://social.tchncs.de/users/morganth/statuses/100760960238403533
items: https://mastodon.at/users/switchingsocial/statuses/100368443255001645
items: 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.
items: https://mstdn.jp/users/tdemin/statuses/98985810982125853
items: mmn: @patrickme !GNUsocial is another piece of software entirely that has some features that #Mastodon lacks and vice versa.
items: objectType=Status
items: mmn: PS, that server is (at least to search engine caches) a #Mastodon instance ,)

microformats-20-years
type: item
type: MicroblogPost
title: : 🎂 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, previous…
link: https://status.blaise.ca/notice/116274
description: 's status on Friday, 20-Jun-2025 20:48:00 EDT
encoded: 🎂 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 Pr…
date: 2025-06-20T20:48:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110341
enclosure: anniversaries-microformats-posse
links to: anniversaries-microformats-posse
enclosure: faux
links to: faux
enclosure: 114705990062730513That
links to: 114705990062730513That
enclosure: html3*
links to: html3*
enclosure: svg*
links to: svg*
enclosure: wmlLiterally
links to: wmlLiterally
enclosure: )*
links to: )*
enclosure: its-the-th-anniversary-of.html)*
links to: its-the-th-anniversary-of.html)*
enclosure: years-posse-microformats-beyond
links to: years-posse-microformats-beyond
enclosure: happy-14th-microformats-org
links to: happy-14th-microformats-org
tagged: concept

anniversaries-microformats-posse
date: 2023-08-22T19:29:07-04:00
type: text/html; charset=UTF-8

faux
date: 2025-06-20T21:51:27-04:00
type: text/html; charset=UTF-8

114705990062730513That
date: 2025-06-20T21:51:27-04:00
length: 23695
type: text/html; charset=utf-8

html3*
date: 2025-06-20T21:51:29-04:00
type: text/html; charset=UTF-8

svg*
date: 2025-06-20T21:51:29-04:00
type: text/html; charset=UTF-8

wmlLiterally
date: 2025-06-20T21:51:30-04:00
type: text/html; charset=UTF-8

)*
date: 2025-06-20T21:51:31-04:00
type: text/html; charset=UTF-8

its-the-th-anniversary-of.html)*
date: 2025-06-20T21:51:31-04:00
length: 9
type: text/html;charset=utf-8

years-posse-microformats-beyond
date: 2025-06-20T21:51:32-04:00
type: text/html; charset=UTF-8

happy-14th-microformats-org
date: 2025-06-20T21:51:32-04:00
type: text/html; charset=UTF-8

concept
type: Tag
label: federate

concept
type: Tag
label: fediverse

concept
type: Tag
label: indieweb

concept
type: Tag
label: looselyjoinedpreviously

concept
type: Tag
label: mastodon

concept
type: Tag
label: microformats

concept
type: Tag
label: microformats20

concept
type: Tag
label: microformats20even

concept
type: Tag
label: smallpieces

three-steps-indieweb-cybersecurity
type: item
type: MicroblogPost
title: : 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 …
link: https://status.blaise.ca/notice/116261
description: 's status on Monday, 24-Feb-2025 19:10:00 EST
encoded: 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…
date: 2025-02-24T19:10:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110328
enclosure: tantek.com
links to: tantek.com
enclosure: web hosting
links to: web hosting
enclosure: multi-factor authentication
links to: multi-factor authentication
enclosure: steps-indieweb-cybersecurity
links to: steps-indieweb-cybersecurity
enclosure: If
links to: If
enclosure: seek-2024-year-in-review
links to: seek-2024-year-in-review
enclosure: articleAtom
links to: articleAtom
enclosure: Atomcontent
links to: Atomcontent
enclosure: content delivery networkcybersecurity
links to: content delivery networkcybersecurity
enclosure: CybersecurityDNS
links to: CybersecurityDNS
enclosure: DNSdomain
links to: DNSdomain
enclosure: domain registrarentropy
links to: domain registrarentropy
enclosure: Entropy (information theory)feed
links to: Entropy (information theory)feed
enclosure: feed readerh-feed
links to: feed readerh-feed
enclosure: h-feedMFA
links to: h-feedMFA
enclosure: Criticismnote
links to: Criticismnote
enclosure: notesocial
links to: notesocial
enclosure: social readerweb
links to: social readerweb
tagged: concept

tantek.com
date: 2022-10-29T03:01:39-04:00
type: text/html; charset=UTF-8

web hosting
date: 2023-01-11T09:44:05-05:00
type: text/html; charset=UTF-8

multi-factor authentication
date: 2025-02-21T20:06:02-05:00
type: text/html; charset=UTF-8

steps-indieweb-cybersecurity
date: 2025-02-24T20:09:38-05:00
type: text/html; charset=UTF-8

If
date: 2025-02-24T20:09:38-05:00
type: text/html; charset=utf-8

seek-2024-year-in-review
date: 2025-02-24T20:09:39-05:00
type: text/html; charset=UTF-8

articleAtom
date: 2025-02-24T20:09:39-05:00
type: text/html; charset=UTF-8

Atomcontent
date: 2025-02-24T20:09:40-05:00
type: text/html; charset=UTF-8

content delivery networkcybersecurity
date: 2025-02-24T20:09:41-05:00
type: text/html; charset=UTF-8

CybersecurityDNS
date: 2025-02-24T20:09:42-05:00
type: text/html; charset=UTF-8

DNSdomain
date: 2025-02-24T20:09:43-05:00
type: text/html; charset=UTF-8

domain registrarentropy
date: 2025-02-24T20:09:44-05:00
type: text/html; charset=UTF-8

Entropy (information theory)feed
date: 2025-02-24T20:09:45-05:00
type: text/html; charset=UTF-8

feed readerh-feed
date: 2025-02-24T20:09:46-05:00
type: text/html; charset=UTF-8

h-feedMFA
date: 2025-02-24T20:09:47-05:00
type: text/html; charset=UTF-8

Criticismnote
date: 2025-02-24T20:09:48-05:00
type: text/html; charset=UTF-8

notesocial
date: 2025-02-24T20:09:49-05:00
type: text/html; charset=UTF-8

social readerweb
date: 2025-02-24T20:09:49-05:00
type: text/html; charset=UTF-8

concept
type: Tag
label: 100posts

concept
type: Tag
label: 100postsofindieweb

concept
type: Tag
label: cyber

concept
type: Tag
label: cybersecurity

concept
type: Tag
label: security

concept
type: Tag
label: socialmedia

micro-one-onramp-open-social-web
type: item
type: MicroblogPost
title: : 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
link: https://status.blaise.ca/notice/116253
description: 's status on Saturday, 04-Jan-2025 23:48:00 EST
encoded: 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-m…
date: 2025-01-04T23:48:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110320
enclosure: own-your-notes-domain-migration
links to: own-your-notes-domain-migration
enclosure: Webmention¹
links to: Webmention¹
enclosure: 15-years-notes-my-site-first
links to: 15-years-notes-my-site-first
enclosure: micro.one
links to: micro.one
enclosure: pricingAnd
links to: pricingAnd
enclosure: indiewebDid
links to: indiewebDid
enclosure: 39Well
links to: 39Well
enclosure: lastfm-year-in-review-playback24
links to: lastfm-year-in-review-playback24
enclosure: IndieAuthmicroformats
links to: IndieAuthmicroformats
enclosure: microformatsMicropub
links to: microformatsMicropub
enclosure: MicropubMicrosub
links to: MicropubMicrosub
enclosure: MicrosubWebmention
links to: MicrosubWebmention
enclosure: microone-was-effectively-a-softlaunch.html²
links to: microone-was-effectively-a-softlaunch.html²
tagged: concept

own-your-notes-domain-migration
date: 2023-01-27T05:09:58-05:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : 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
link: https://status.blaise.ca/notice/116006
description: 's status on Monday, 23-Jan-2023 02:49:00 EST
encoded: 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
date: 2023-01-23T02:49:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110129
enclosure: bottom
links to: bottom
enclosure: https://xkcd.com/1150/
links to: https://xkcd.com/1150/
enclosure: micro.blog
links to: micro.blog
enclosure: CMS
links to: CMS
enclosure: own-your-notes
links to: own-your-notes
enclosure: indieweb-path-chosen-why
links to: indieweb-path-chosen-why
enclosure: choosing-domain-name-indieweb
links to: choosing-domain-name-indieweb
enclosure: fed.brid.gy
links to: fed.brid.gy
enclosure: indieweb-eat-what-you-cook
links to: indieweb-eat-what-you-cook
enclosure: t3
links to: t3
tagged: concept

Webmention¹
date: 2023-10-23T22:05:53-04:00
type: text/html; charset=UTF-8

15-years-notes-my-site-first
date: 2025-01-01T20:01:47-05:00
type: text/html; charset=UTF-8

micro.one
date: 2025-01-05T00:52:09-05:00
length: 5630
type: text/html;charset=utf-8

pricingAnd
date: 2025-01-05T00:52:09-05:00
length: 14
type: text/html;charset=utf-8

indiewebDid
date: 2025-01-05T00:52:10-05:00
length: 14
type: text/html;charset=utf-8

39Well
date: 2025-01-05T00:52:10-05:00
type: text/html; charset=utf-8

lastfm-year-in-review-playback24
date: 2025-01-05T00:52:11-05:00
type: text/html; charset=UTF-8

IndieAuthmicroformats
date: 2025-01-05T00:52:11-05:00
type: text/html; charset=UTF-8

microformatsMicropub
date: 2025-01-05T00:52:12-05:00
type: text/html; charset=UTF-8

MicropubMicrosub
date: 2025-01-05T00:52:13-05:00
type: text/html; charset=UTF-8

MicrosubWebmention
date: 2025-01-05T00:52:14-05:00
type: text/html; charset=UTF-8

microone-was-effectively-a-softlaunch.html²
date: 2025-01-05T00:52:15-05:00
length: 9
type: text/html;charset=utf-8

concept
type: Tag
label: activitypub

concept
type: Tag
label: indieauth

concept
type: Tag
label: micropub

concept
type: Tag
label: microsub

concept
type: Tag
label: opensocialweb

concept
type: Tag
label: ownyourdata

concept
type: Tag
label: ownyouridentity

concept
type: Tag
label: socialweb

concept
type: Tag
label: webmention

indiewebcamp-berlin-2024-day-1
type: item
type: MicroblogPost
title: : 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→ 🔮
link: https://status.blaise.ca/notice/116236
description: 's status on Saturday, 09-Nov-2024 08:31:00 EST
encoded: 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 → 🔮
date: 2024-11-09T08:31:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110305
enclosure: 2024²
links to: 2024²
enclosure: Intros³
links to: Intros³
enclosure: SaturdayThis
links to: SaturdayThis
enclosure: simple-embeds
links to: simple-embeds
tagged: concept

2024²
date: 2024-11-10T12:02:30-05:00
type: text/html; charset=UTF-8

Intros³
date: 2024-11-10T12:02:31-05:00
type: text/html; charset=UTF-8

SaturdayThis
date: 2024-11-10T12:02:32-05:00
type: text/html; charset=UTF-8

simple-embeds
date: 2024-11-10T12:02:34-05:00
type: text/html; charset=UTF-8

concept
type: Tag
label: algorithms

concept
type: Tag
label: berlin

concept
type: Tag
label: collab

concept
type: Tag
label: death

concept
type: Tag
label: designfordummies

concept
type: Tag
label: federation

concept
type: Tag
label: imagewriting

concept
type: Tag
label: inclusion

concept
type: Tag
label: indiewebcamp

concept
type: Tag
label: longevity

concept
type: Tag
label: places

concept
type: Tag
label: posse

concept
type: Tag
label: privacy

concept
type: Tag
label: queer

concept
type: Tag
label: ssr

concept
type: Tag
label: syndication

concept
type: Tag
label: textux

concept
type: Tag
label: threatmodeling

concept
type: Tag
label: timelinesetherpad

concept
type: Tag
label: writing

fediverse-unfollow-bridgyfed-bug
type: item
type: MicroblogPost
title: : 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…
link: https://status.blaise.ca/notice/116232
description: 's status on Sunday, 13-Oct-2024 16:37:00 EDT
encoded: 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 ra…
date: 2024-10-13T16:37:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110301
enclosure: Hanlon's razor²
links to: Hanlon's razor²
links to: 1379³
links to: 4df76d0db7b87cabbd714039546c05b3221169be⁴
enclosure: t1727028174623700This
links to: t1727028174623700This
enclosure: io-domain-suggested-steps
links to: io-domain-suggested-steps
tagged: concept

Hanlon's razor²
date: 2024-10-13T23:50:41-04:00
type: text/html; charset=UTF-8

t1727028174623700This
date: 2024-10-13T23:50:41-04:00
type: text/html; charset=utf-8

io-domain-suggested-steps
date: 2024-10-13T23:50:42-04:00
type: text/html; charset=UTF-8

concept
type: Tag
label: bridgyfed

concept
type: Tag
label: misskey

concept
type: Tag
label: openstandards

w3c-link-checker-before-federating
type: item
type: MicroblogPost
title: : 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→ 🔮
link: https://status.blaise.ca/notice/116218
description: 's status on Wednesday, 04-Sep-2024 02:11:00 EDT
encoded: 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 → 🔮
date: 2024-09-04T02:11:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110287
enclosure: t1725421768496000More
links to: t1725421768496000More
enclosure: IndieWeb
links to: IndieWeb
enclosure: adventures-indieweb-activitypub-bridgy-fed
links to: adventures-indieweb-activitypub-bridgy-fed
tagged: concept

t1725421768496000More
date: 2024-09-04T03:08:31-04:00
type: text/html; charset=utf-8

IndieWeb
date: 2024-09-04T03:08:32-04:00
type: text/html; charset=utf-8

adventures-indieweb-activitypub-bridgy-fed
date: 2024-09-04T03:08:33-04:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : 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→ 🔮
link: https://status.blaise.ca/notice/116215
description: 's status on Tuesday, 03-Sep-2024 01:32:00 EDT
encoded: 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 → 🔮
date: 2024-09-03T01:32:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110284
enclosure: fed.brid.gy
links to: fed.brid.gy
enclosure: years-posse-microformats-adoption
links to: years-posse-microformats-adoption
enclosure: indiewebcamp-auto-linking
links to: indiewebcamp-auto-linking
enclosure: indiewebcamp-portland
links to: indiewebcamp-portland
enclosure: read-write-suggest-edit-web
links to: read-write-suggest-edit-web
enclosure: twenty-years-microformats
links to: twenty-years-microformats
enclosure: @tantek.com@tantek.com*
links to: @tantek.com@tantek.com*
enclosure: @tantek.com@tantek.com(My
links to: @tantek.com@tantek.com(My
enclosure: 884Let
links to: 884Let
tagged: concept

concept
type: Tag
label: interoperabilitythis

twenty-years-microformats-shorter2
type: item
type: MicroblogPost
title: : 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
link: https://status.blaise.ca/notice/116216
description: 's status on Tuesday, 03-Sep-2024 21:47:00 EDT
encoded: 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
date: 2024-09-03T21:47:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110285
enclosure: twenty-years-microformats
links to: twenty-years-microformats
enclosure: t5Yo1).Since
links to: t5Yo1).Since
tagged: concept

twenty-years-microformats
date: 2024-09-03T02:52:25-04:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : 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/microform…
link: https://status.blaise.ca/notice/116168
description: 's status on Wednesday, 14-Feb-2024 01:03:00 EST
encoded: 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/wik…
date: 2024-02-14T01:03:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110241
enclosure: nineteen-years-microformats
links to: nineteen-years-microformats
enclosure: h-entryh-review
links to: h-entryh-review
enclosure: wikipedia-supports-indieweb-rel-me
links to: wikipedia-supports-indieweb-rel-me
enclosure: rel-me
links to: rel-me
enclosure: threads-supports-indieweb-rel-me
links to: threads-supports-indieweb-rel-me
enclosure: profile-items2
links to: profile-items2
enclosure: https://github.com/microformats/h-entry/issues/32
links to: https://github.com/microformats/h-entry/issues/32
enclosure: IndieWeb Examples
links to: IndieWeb Examples
enclosure: issuesHard
links to: issuesHard
enclosure: h-reviewlink-preview
links to: h-reviewlink-preview
enclosure: link-previewmetaformats
links to: link-previewmetaformats
enclosure: metaformatsmicroformats
links to: metaformatsmicroformats
enclosure: microformats2
links to: microformats2
enclosure: microformats2rel-me
links to: microformats2rel-me
tagged: concept

t5Yo1).Since
date: 2024-09-03T23:30:06-04:00
type: text/html; charset=iso-8859-1

concept
type: Tag
label: metaformats

concept
type: Tag
label: microformats2

twenty-years-microformats-summary
type: item
type: MicroblogPost
title: : 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
link: https://status.blaise.ca/notice/116217
description: 's status on Tuesday, 03-Sep-2024 17:02:00 EDT
encoded: 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
date: 2024-09-03T17:02:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110286
enclosure: nineteen-years-microformats
links to: nineteen-years-microformats
enclosure: twenty-years-microformats
links to: twenty-years-microformats
enclosure: t5Yo1).I
links to: t5Yo1).I
tagged: concept

nineteen-years-microformats
date: 2023-02-21T04:41:06-05:00
type: text/html; charset=UTF-8

t5Yo1).I
date: 2024-09-03T23:30:06-04:00
type: text/html; charset=iso-8859-1

fed.brid.gy
date: 2023-01-09T00:56:28-05:00
length: 4243
type: text/html; charset=utf-8

years-posse-microformats-adoption
date: 2024-08-24T21:52:59-04:00
type: text/html; charset=UTF-8

indiewebcamp-auto-linking
date: 2024-08-30T01:23:31-04:00
type: text/html; charset=UTF-8

indiewebcamp-portland
date: 2024-09-02T21:41:18-04:00
type: text/html; charset=UTF-8

read-write-suggest-edit-web
date: 2024-09-03T02:52:22-04:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : ✏️ 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:* http…
link: https://status.blaise.ca/notice/116214
description: 's status on Sunday, 01-Sep-2024 17:51:00 EDT
encoded: ✏️ 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 …
date: 2024-09-01T17:51:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110283
enclosure: editOur
links to: editOur
enclosure: 113025295600067213²
links to: 113025295600067213²
enclosure: read-fork-write-merge-web-osb11
links to: read-fork-write-merge-web-osb11
enclosure: responses⁴
links to: responses⁴
enclosure: https://www.reddit.com/r/git/comments/nvahcp/comment/h12hzj7/⁵
links to: https://www.reddit.com/r/git/comments/nvahcp/comment/h12hzj7/⁵
enclosure: indiewebcamp-portland
links to: indiewebcamp-portland
tagged: concept

@tantek.com@tantek.com*
date: 2024-09-03T02:52:26-04:00
type: text/html; charset=utf-8

@tantek.com@tantek.com*
date: 2024-09-03T02:52:27-04:00
length: 23497
type: text/html; charset=utf-8

@tantek.com@tantek.com*
date: 2024-09-03T02:52:28-04:00
type: text/html; charset=utf-8

@tantek.com@tantek.com(My
date: 2024-09-03T02:52:29-04:00
length: 23052
type: text/html; charset=utf-8

884Let
date: 2024-09-03T02:52:30-04:00
type: text/html; charset=utf-8

read-write-suggest-edit-update-web
type: item
type: MicroblogPost
title: : ✏️ 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 inter…
link: https://status.blaise.ca/notice/116219
description: 's status on Sunday, 01-Sep-2024 17:51:00 EDT
encoded: ✏️ 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/e…
date: 2024-09-01T17:51:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110288
enclosure: editOur
links to: editOur
enclosure: 113025295600067213²
links to: 113025295600067213²
enclosure: read-fork-write-merge-web-osb11
links to: read-fork-write-merge-web-osb11
enclosure: responses⁴
links to: responses⁴
enclosure: https://www.reddit.com/r/git/comments/nvahcp/comment/h12hzj7/⁵
links to: https://www.reddit.com/r/git/comments/nvahcp/comment/h12hzj7/⁵
enclosure: indiewebcamp-portland
links to: indiewebcamp-portland
enclosure: adventures-indieweb-activitypub-bridgy-fed
links to: adventures-indieweb-activitypub-bridgy-fed
tagged: concept

editOur
date: 2024-09-02T21:41:12-04:00
type: text/html; charset=UTF-8

113025295600067213²
date: 2024-09-02T21:41:14-04:00
type: text/html; charset=utf-8

read-fork-write-merge-web-osb11
date: 2024-09-02T21:41:16-04:00
type: text/html; charset=UTF-8

responses⁴
date: 2024-09-02T21:41:17-04:00
type: text/html; charset=UTF-8

https://www.reddit.com/r/git/comments/nvahcp/comment/h12hzj7/⁵
date: 2024-09-02T21:41:18-04:00
length: 190240
type: text/html

concept
type: Tag
label: accepteditreferences

concept
type: Tag
label: editableweb

concept
type: Tag
label: suggestedit

created-at-indiewebcamp-brighton
type: item
type: MicroblogPost
title: : 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-focus…
link: https://status.blaise.ca/notice/116190
description: 's status on Tuesday, 12-Mar-2024 22:19:00 EDT
encoded: 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 pers…
date: 2024-03-12T22:19:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110259
enclosure: indieweb-evolving-at-mention
links to: indieweb-evolving-at-mention
enclosure: domain-first-federated-atmention
links to: domain-first-federated-atmention
enclosure: elevate-indieweb-above-silo
links to: elevate-indieweb-above-silo
enclosure: reply-domain-above-address-and-silo
links to: reply-domain-above-address-and-silo
enclosure: https://indieweb.org/wiki/index.php
links to: https://indieweb.org/wiki/index.php
enclosure: updated-auto-linking-mention-use-cases
links to: updated-auto-linking-mention-use-cases
enclosure: autoLink
links to: autoLink
enclosure: DemosThis
links to: DemosThis
enclosure: Create DayIndieWebCamp
links to: Create DayIndieWebCamp
enclosure: BrightonReferences:¹
links to: BrightonReferences:¹
enclosure: Day Two²
links to: Day Two²
enclosure: what to make at IndieWebCamp³
links to: what to make at IndieWebCamp³
enclosure: Saturday
links to: Saturday
tagged: concept

indieweb-evolving-at-mention
date: 2023-01-13T06:37:52-05:00
type: text/html; charset=UTF-8

domain-first-federated-atmention
date: 2023-01-16T07:31:35-05:00
type: text/html; charset=UTF-8

elevate-indieweb-above-silo
date: 2023-01-19T21:40:10-05:00
type: text/html; charset=UTF-8

reply-domain-above-address-and-silo
date: 2023-01-21T04:12:23-05:00
type: text/html; charset=UTF-8

https://indieweb.org/wiki/index.php
date: 2024-03-13T00:20:13-04:00
type: text/html; charset=UTF-8

updated-auto-linking-mention-use-cases
date: 2024-03-13T00:20:15-04:00
type: text/html; charset=UTF-8

autoLink
date: 2024-03-13T00:20:17-04:00
type: text/html; charset=UTF-8

DemosThis
date: 2024-03-13T00:20:18-04:00
type: text/html; charset=UTF-8

Create DayIndieWebCamp
date: 2024-03-13T00:20:19-04:00
type: text/html; charset=UTF-8

BrightonReferences:¹
date: 2024-03-13T00:20:20-04:00
type: text/html; charset=UTF-8

Day Two²
date: 2024-03-13T00:20:21-04:00
type: text/html; charset=UTF-8

what to make at IndieWebCamp³
date: 2024-03-13T00:20:23-04:00
type: text/html; charset=UTF-8

Saturday
date: 2024-03-13T00:20:24-04:00
type: text/html; charset=UTF-8

concept
type: Tag
label: atat

concept
type: Tag
label: atatmentioni

concept
type: Tag
label: atdomain

concept
type: Tag
label: atmention

concept
type: Tag
label: atmentions

concept
type: Tag
label: atpath

concept
type: Tag
label: indie

the-ephemeral-web
type: item
type: MicroblogPost
title: : 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, th…
link: https://status.blaise.ca/notice/116170
description: 's status on Thursday, 15-Feb-2024 16:18:00 EST
encoded: 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 cl…
date: 2024-02-15T16:18:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110243
tagged: concept

concept
type: Tag
label: bluesky

concept
type: Tag
label: bridgy

concept
type: Tag
label: curlable

concept
type: Tag
label: ephemeralweb

concept
type: Tag
label: longnowthis

concept
type: Tag
label: longweb

concept
type: Tag
label: openweb

concept
type: Tag
label: queeraf

twenty-years-microformats-updates
type: item
type: MicroblogPost
title: : 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://mic…
link: https://status.blaise.ca/notice/116169
description: 's status on Wednesday, 14-Feb-2024 01:03:00 EST
encoded: 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 …
date: 2024-02-14T01:03:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110242
enclosure: nineteen-years-microformats
links to: nineteen-years-microformats
enclosure: h-entryh-review
links to: h-entryh-review
enclosure: wikipedia-supports-indieweb-rel-me
links to: wikipedia-supports-indieweb-rel-me
enclosure: rel-me
links to: rel-me
enclosure: threads-supports-indieweb-rel-me
links to: threads-supports-indieweb-rel-me
enclosure: profile-items2
links to: profile-items2
enclosure: https://github.com/microformats/h-entry/issues/32
links to: https://github.com/microformats/h-entry/issues/32
enclosure: IndieWeb Examples
links to: IndieWeb Examples
enclosure: issuesHard
links to: issuesHard
enclosure: h-reviewlink-preview
links to: h-reviewlink-preview
enclosure: link-previewmetaformats
links to: link-previewmetaformats
enclosure: metaformatsmicroformats
links to: metaformatsmicroformats
enclosure: microformats2
links to: microformats2
enclosure: microformats2rel-me
links to: microformats2rel-me
tagged: concept

h-entryh-review
date: 2023-04-24T19:02:32-04:00
type: text/html; charset=UTF-8

wikipedia-supports-indieweb-rel-me
date: 2023-06-10T00:12:54-04:00
type: text/html; charset=UTF-8

rel-me
date: 2023-06-21T04:00:17-04:00
type: text/html; charset=UTF-8

threads-supports-indieweb-rel-me
date: 2023-10-17T00:09:45-04:00
type: text/html; charset=UTF-8

profile-items2
date: 2024-02-14T04:22:31-05:00
type: text/html; charset=UTF-8

https://github.com/microformats/h-entry/issues/32
date: 2024-02-14T04:22:32-05:00
type: text/html; charset=utf-8

IndieWeb Examples
date: 2024-02-14T04:22:32-05:00
type: text/html; charset=UTF-8

issuesHard
date: 2024-02-14T04:22:34-05:00
type: text/html; charset=utf-8

h-reviewlink-preview
date: 2024-02-14T04:22:35-05:00
type: text/html; charset=UTF-8

link-previewmetaformats
date: 2024-02-14T04:22:36-05:00
type: text/html; charset=UTF-8

metaformatsmicroformats
date: 2024-02-14T04:22:37-05:00
type: text/html; charset=UTF-8

microformats2
date: 2024-02-14T04:22:37-05:00
type: text/html; charset=UTF-8

microformats2rel-me
date: 2024-02-14T04:22:38-05:00
type: text/html; charset=UTF-8

restarting-100days-indieweb-gift-calendar
type: item
type: MicroblogPost
title: : 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 suc…
link: https://status.blaise.ca/notice/116150
description: 's status on Monday, 01-Jan-2024 22:30:00 EST
encoded: 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…
date: 2024-01-01T22:30:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110227
tagged: concept

concept
type: Tag
label: 100days

concept
type: Tag
label: 100daysofindieweb

concept
type: Tag
label: showdonttellthis

concept
type: Tag
label: twitter

capture-first-edit-publish-later
type: item
type: MicroblogPost
title: : 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/202…
link: https://status.blaise.ca/notice/116148
description: 's status on Sunday, 31-Dec-2023 17:04:00 EST
encoded: 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://tan…
date: 2023-12-31T17:04:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110225
enclosure: articlenote
links to: articlenote
enclosure: bridgyfed-webmention-like-fediverse
links to: bridgyfed-webmention-like-fediverse
enclosure: no-large-language-model-llm-used
links to: no-large-language-model-llm-used
enclosure: thoughtful-reading-writing-web
links to: thoughtful-reading-writing-web
enclosure: algorithmic feedarticle
links to: algorithmic feedarticle
enclosure: notepost
links to: notepost
enclosure: postsense-making
links to: postsense-making
enclosure: Sensemaking (information science)social
links to: Sensemaking (information science)social
enclosure: social media
links to: social media
tagged: concept

articlenote
date: 2023-09-24T23:16:24-04:00
type: text/html; charset=UTF-8

bridgyfed-webmention-like-fediverse
date: 2023-10-23T22:05:42-04:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : 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
link: https://status.blaise.ca/notice/116139
description: 's status on Monday, 16-Oct-2023 21:16:00 EDT
encoded: 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
date: 2023-10-16T21:16:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110216
enclosure: threads-supports-indieweb-rel-me
links to: threads-supports-indieweb-rel-me
enclosure: 111237962392745000²
links to: 111237962392745000²
enclosure: federating-mentions
links to: federating-mentions
enclosure: f1
links to: f1
tagged: concept

no-large-language-model-llm-used
date: 2023-12-31T19:22:23-05:00
type: text/html; charset=UTF-8

thoughtful-reading-writing-web
date: 2023-12-31T19:22:24-05:00
type: text/html; charset=UTF-8

algorithmic feedarticle
date: 2023-12-31T19:22:25-05:00
type: text/html; charset=UTF-8

notepost
date: 2023-12-31T19:22:26-05:00
type: text/html; charset=UTF-8

postsense-making
date: 2023-12-31T19:22:27-05:00
type: text/html; charset=UTF-8

Sensemaking (information science)social
date: 2023-12-31T19:22:28-05:00
type: text/html; charset=UTF-8

social media
date: 2023-12-31T19:22:28-05:00
type: text/html; charset=UTF-8

posse-syndicate-link-reply
type: item
type: MicroblogPost
title: : 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 rep…
link: https://status.blaise.ca/notice/116140
description: 's status on Monday, 23-Oct-2023 20:30:00 EDT
encoded: 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 …
date: 2023-10-23T20:30:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110217
enclosure: bottom
links to: bottom
enclosure: brid.gy
links to: brid.gy
enclosure: own-your-notes
links to: own-your-notes
enclosure: fed.brid.gy
links to: fed.brid.gy
enclosure: discuss
links to: discuss
enclosure: POSSEsilo
links to: POSSEsilo
enclosure: backfeedBackfeed
links to: backfeedBackfeed
enclosure: bridgyfed-webmention-like-fediverse
links to: bridgyfed-webmention-like-fediverse
enclosure: backfeedBridgy
links to: backfeedBridgy
enclosure: make
links to: make
enclosure: make what you needmanual
links to: make what you needmanual
enclosure: manual until it hurtsoriginal
links to: manual until it hurtsoriginal
enclosure: original post linkown
links to: original post linkown
enclosure: own your dataown
links to: own your dataown
enclosure: own your repliespermalink
links to: own your repliespermalink
enclosure: permalinkpermashortlink
links to: permalinkpermashortlink
enclosure: permashortlinkPOSSE
links to: permashortlinkPOSSE
enclosure: silosocial
links to: silosocial
enclosure: social mediastatic
links to: social mediastatic
enclosure: static sitestart
links to: static sitestart
enclosure: startWebmention
links to: startWebmention
enclosure: Webmention¹
links to: Webmention¹
enclosure: t2
links to: t2
enclosure: diso-2-personal-domains-shortener-hatom-push-relmeauth
links to: diso-2-personal-domains-shortener-hatom-push-relmeauth
tagged: concept

bottom
date: 2020-01-02T00:13:25-05:00
type: text/html; charset=utf-8

brid.gy
date: 2022-01-06T03:52:41-05:00
type: text/html; charset=utf-8

own-your-notes
date: 2023-01-03T03:32:20-05:00
type: text/html; charset=UTF-8

discuss
date: 2023-01-28T08:19:05-05:00
type: text/html; charset=UTF-8

POSSEsilo
date: 2023-06-21T04:00:22-04:00
type: text/html; charset=UTF-8

backfeedBackfeed
date: 2023-10-23T22:05:41-04:00
type: text/html; charset=UTF-8

backfeedBridgy
date: 2023-10-23T22:05:43-04:00
type: text/html; charset=UTF-8

make
date: 2023-10-23T22:05:44-04:00
length: 207
type: text/html; charset=utf-8

make what you needmanual
date: 2023-10-23T22:05:44-04:00
type: text/html; charset=UTF-8

manual until it hurtsoriginal
date: 2023-10-23T22:05:45-04:00
type: text/html; charset=UTF-8

original post linkown
date: 2023-10-23T22:05:46-04:00
type: text/html; charset=UTF-8

own your dataown
date: 2023-10-23T22:05:47-04:00
type: text/html; charset=UTF-8

own your repliespermalink
date: 2023-10-23T22:05:47-04:00
type: text/html; charset=UTF-8

permalinkpermashortlink
date: 2023-10-23T22:05:48-04:00
type: text/html; charset=UTF-8

permashortlinkPOSSE
date: 2023-10-23T22:05:49-04:00
type: text/html; charset=UTF-8

silosocial
date: 2023-10-23T22:05:50-04:00
type: text/html; charset=UTF-8

social mediastatic
date: 2023-10-23T22:05:51-04:00
type: text/html; charset=UTF-8

static sitestart
date: 2023-10-23T22:05:51-04:00
type: text/html; charset=UTF-8

startWebmention
date: 2023-10-23T22:05:52-04:00
type: text/html; charset=UTF-8

t2
date: 2023-10-23T22:05:54-04:00
type: text/html; charset=UTF-8

diso-2-personal-domains-shortener-hatom-push-relmeauth
date: 2023-10-23T22:05:56-04:00
type: text/html; charset=UTF-8

concept
type: Tag
label: backfeed

concept
type: Tag
label: federated

111237962392745000²
date: 2023-10-17T00:09:46-04:00
length: 22930
type: text/html; charset=utf-8

federating-mentions
date: 2023-10-17T00:09:47-04:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : 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.
link: https://status.blaise.ca/notice/116137
description: 's status on Saturday, 14-Oct-2023 22:37:00 EDT
encoded: 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.
date: 2023-10-14T22:37:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110214
enclosure: domain-first-federated-atmention
links to: domain-first-federated-atmention
enclosure: socialweb-blogs-reply-comment-post
links to: socialweb-blogs-reply-comment-post
enclosure: elevate-indieweb-above-silo
links to: elevate-indieweb-above-silo
enclosure: reply-domain-above-address-and-silo
links to: reply-domain-above-address-and-silo
enclosure: mentionSo
links to: mentionSo
tagged: concept

f1
date: 2023-10-17T00:09:47-04:00
type: text/html; charset=UTF-8

concept
type: Tag
label: favorite

concept
type: Tag
label: favourite

concept
type: Tag
label: favourites

concept
type: Tag
label: like

concept
type: Tag
label: likes

socialweb-blogs-reply-comment-post
date: 2023-01-19T04:34:11-05:00
type: text/html; charset=UTF-8

mentionSo
date: 2023-10-14T23:52:41-04:00
length: 69941
type: text/html; charset=utf-8

concept
type: Tag
label: webmentions

summary-w3c-tpac-2023
type: item
type: MicroblogPost
title: : 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
link: https://status.blaise.ca/notice/116135
description: 's status on Sunday, 24-Sep-2023 21:33:00 EDT
encoded: 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
date: 2023-09-24T21:33:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110212
enclosure: articlenote
links to: articlenote
enclosure: notep-category
links to: notep-category
enclosure: p-categorytags
links to: p-categorytags
enclosure: tags
links to: tags
tagged: concept

notep-category
date: 2023-09-24T23:16:25-04:00
type: text/html; charset=UTF-8

p-categorytags
date: 2023-09-24T23:16:27-04:00
type: text/html; charset=UTF-8

tags
date: 2023-09-24T23:16:28-04:00
type: text/html; charset=UTF-8

concept
type: Tag
label: activitypubbecause

concept
type: Tag
label: hashtag

concept
type: Tag
label: seville

concept
type: Tag
label: socialcg

concept
type: Tag
label: spain

concept
type: Tag
label: sustainability

concept
type: Tag
label: swicg

concept
type: Tag
label: tpac

concept
type: Tag
label: w3c

concept
type: Tag
label: w3ctpac

concept
type: Tag
label: wicg

socialweb-cg-w3ctpac
type: item
type: MicroblogPost
title: : 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
link: https://status.blaise.ca/notice/116133
description: 's status on Monday, 11-Sep-2023 19:06:00 EDT
encoded: 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
date: 2023-09-11T19:06:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110210
enclosure: fed.brid.gy
links to: fed.brid.gy
enclosure: 2023-09-04 50856
links to: 2023-09-04 50856
tagged: concept

2023-09-04 50856
date: 2023-09-11T19:23:26-04:00
type: text/html; charset=UTF-8

concept
type: Tag
label: activitystreams

concept
type: Tag
label: decentralized

concept
type: Tag
label: nostr

concept
type: Tag
label: openwebwe

concept
type: Tag
label: socialprotocols

concept
type: Tag
label: socialwebwg

mastodon-activitypub-follow-form-bridgy-fed
type: item
type: MicroblogPost
title: : 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
link: https://status.blaise.ca/notice/116116
description: 's status on Friday, 09-Jun-2023 22:14:00 EDT
encoded: 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: <input id="follow-address" name="address" type="text" required="required" placeholder="@you@instance.social" alt="fediverse address" value="" /> 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
date: 2023-06-09T22:14:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110201
enclosure: remote-follow
links to: remote-follow
enclosure: bridgy-fed-follow-form
links to: bridgy-fed-follow-form
enclosure: wikipedia-supports-indieweb-rel-me
links to: wikipedia-supports-indieweb-rel-me
tagged: concept

remote-follow
date: 2023-01-21T04:12:21-05:00
length: 153
type: text/html; charset=utf-8

bridgy-fed-follow-form
date: 2023-01-22T19:43:20-05:00
type: text/html; charset=UTF-8

account-migration-post-blog-archive-format
type: item
type: MicroblogPost
title: : 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 For…
link: https://status.blaise.ca/notice/116064
description: 's status on Saturday, 22-Apr-2023 20:40:00 EDT
encoded: 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: Bl…
date: 2023-04-22T20:40:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110170
enclosure: twittermigration-bridgyfed-mastodon-indieweb
links to: twittermigration-bridgyfed-mastodon-indieweb
enclosure: micro.blog
links to: micro.blog
enclosure: devThis
links to: devThis
enclosure: @tchambers.rss*
links to: @tchambers.rss*
enclosure: export
links to: export
enclosure: blog-archive-format.htmlMore
links to: blog-archive-format.htmlMore
enclosure: importing-blog-archive.htmlBlog
links to: importing-blog-archive.htmlBlog
enclosure: beyond-mastodon-indieweb-own-domain
links to: beyond-mastodon-indieweb-own-domain
enclosure: account migrationblog
links to: account migrationblog
enclosure: blog archive formath-feed
links to: blog archive formath-feed
enclosure: h-feedJSON
links to: h-feedJSON
enclosure: post
links to: post
enclosure: post migrationWebmention
links to: post migrationWebmention
enclosure: WebmentionReferences¹
links to: WebmentionReferences¹
links to: 1202³
enclosure: https://github.com/mastodon/mastodon/issues/12423
links to: https://github.com/mastodon/mastodon/issues/12423
tagged: concept

twittermigration-bridgyfed-mastodon-indieweb
date: 2022-12-02T15:58:37-05:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : #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?
link: https://status.blaise.ca/notice/115928
description: 's status on Saturday, 29-Oct-2022 01:01:00 EDT
encoded: #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?
date: 2022-10-29T01:01:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110073
tagged: concept

micro.blog
date: 2023-01-02T02:36:49-05:00
length: 7960
type: text/html;charset=utf-8

devThis
date: 2023-01-27T23:33:59-05:00
length: 169
type: text/html

@tchambers.rss*
date: 2023-04-22T21:09:40-04:00
type: text/html; charset=utf-8

export
date: 2023-04-22T21:09:41-04:00
length: 23133
type: text/html; charset=utf-8

blog-archive-format.htmlMore
date: 2023-04-22T21:09:42-04:00
length: 9
type: text/html;charset=utf-8

importing-blog-archive.htmlBlog
date: 2023-04-22T21:09:42-04:00
length: 9
type: text/html;charset=utf-8

beyond-mastodon-indieweb-own-domain
date: 2023-04-22T21:09:43-04:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : 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 re…
link: https://status.blaise.ca/notice/116063
description: 's status on Thursday, 20-Apr-2023 20:57:00 EDT
encoded: 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…
date: 2023-04-20T20:57:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110169
enclosure: twittermigration-bridgyfed-mastodon-indieweb
links to: twittermigration-bridgyfed-mastodon-indieweb
enclosure: own-your-notes
links to: own-your-notes
enclosure: activitypub-protocol-standard-social-network
links to: activitypub-protocol-standard-social-network
enclosure: This
links to: This
enclosure: years-ago-first-federated-indieweb-thread
links to: years-ago-first-federated-indieweb-thread
enclosure: principles²
links to: principles²
enclosure: why³
links to: why³
enclosure: 110231624819547202⁴
links to: 110231624819547202⁴
enclosure: t1
links to: t1
enclosure: POSSE⁷
links to: POSSE⁷
tagged: concept

account migrationblog
date: 2023-04-22T21:09:44-04:00
type: text/html; charset=UTF-8

blog archive formath-feed
date: 2023-04-22T21:09:45-04:00
type: text/html; charset=UTF-8

h-feedJSON
date: 2023-04-22T21:09:46-04:00
type: text/html; charset=UTF-8

post
date: 2023-04-22T21:09:47-04:00
length: 9
type: text/html;charset=utf-8

post migrationWebmention
date: 2023-04-22T21:09:48-04:00
type: text/html; charset=UTF-8

WebmentionReferences¹
date: 2023-04-22T21:09:49-04:00
type: text/html; charset=UTF-8

https://github.com/mastodon/mastodon/issues/12423
date: 2023-04-22T21:09:51-04:00
type: text/html; charset=utf-8

concept
type: Tag
label: wordpressas

activitypub-protocol-standard-social-network
date: 2023-04-20T23:31:24-04:00
length: 274524
type: text/html; charset=utf-8

This
date: 2023-04-20T23:31:24-04:00
length: 169
type: text/html

years-ago-first-federated-indieweb-thread
date: 2023-04-20T23:31:25-04:00
type: text/html; charset=UTF-8

principles²
date: 2023-04-20T23:31:26-04:00
type: text/html; charset=UTF-8

why³
date: 2023-04-20T23:31:27-04:00
type: text/html; charset=UTF-8

110231624819547202⁴
date: 2023-04-20T23:31:27-04:00
type: text/html; charset=utf-8

t1
date: 2023-04-20T23:31:29-04:00
type: text/html; charset=UTF-8

POSSE⁷
date: 2023-04-20T23:31:30-04:00
type: text/html; charset=UTF-8

concept
type: Tag
label: federating

mozfest-making-fediverse-socialweb
type: item
type: MicroblogPost
title: : 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
link: https://status.blaise.ca/notice/116045
description: 's status on Wednesday, 22-Mar-2023 11:14:00 EDT
encoded: 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
date: 2023-03-22T11:14:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110156
enclosure: twittermigration-bridgyfed-mastodon-indieweb
links to: twittermigration-bridgyfed-mastodon-indieweb
enclosure: fed.brid.gy
links to: fed.brid.gy
enclosure: devThis
links to: devThis
enclosure: MastodonSeveral
links to: MastodonSeveral
enclosure: UEEGYL-1²
links to: UEEGYL-1²
enclosure: https://mozilla.social/³
links to: https://mozilla.social/³
enclosure: microblog.pub⁴
links to: microblog.pub⁴
enclosure: micro.blog⁵
links to: micro.blog⁵
enclosure: blog-as-if-ai-trained-posts
links to: blog-as-if-ai-trained-posts
tagged: concept

MastodonSeveral
date: 2023-03-22T11:42:06-04:00
length: 118
type: text/html

UEEGYL-1²
date: 2023-03-22T11:42:07-04:00
length: 1268
type: text/html

https://mozilla.social/³
date: 2023-03-22T11:42:09-04:00
type: text/html; charset=utf-8

microblog.pub⁴
date: 2023-03-22T11:42:09-04:00
type: text/html; charset=UTF-8

micro.blog⁵
date: 2023-03-22T11:42:10-04:00
type: text/html; charset=UTF-8

blog-as-if-ai-trained-posts
date: 2023-03-22T11:47:48-04:00
type: text/html; charset=UTF-8

concept
type: Tag
label: mozfest

concept
type: Tag
label: mozillians

concept
type: Tag
label: webdev

mozfest-making-fediverse
type: item
type: MicroblogPost
title: : 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
link: https://status.blaise.ca/notice/116044
description: 's status on Wednesday, 22-Mar-2023 11:14:00 EDT
encoded: 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
date: 2023-03-22T11:14:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110155
tagged: concept

https://xkcd.com/1150/
date: 2023-01-02T02:36:49-05:00
length: 8725
type: text/html; charset=UTF-8

CMS
date: 2023-01-02T02:36:50-05:00
type: text/html; charset=UTF-8

indieweb-path-chosen-why
date: 2023-01-05T04:06:24-05:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : 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
link: https://status.blaise.ca/notice/115976
description: 's status on Wednesday, 04-Jan-2023 02:36:00 EST
encoded: 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
date: 2023-01-04T02:36:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110105
enclosure: micro.blog
links to: micro.blog
enclosure: CMS
links to: CMS
enclosure: building blocks
links to: building blocks
enclosure: key-owning-notes-domain-name
links to: key-owning-notes-domain-name
tagged: concept

choosing-domain-name-indieweb
date: 2023-01-06T07:17:04-05:00
type: text/html; charset=UTF-8

indieweb-eat-what-you-cook
date: 2023-01-23T05:45:22-05:00
type: text/html; charset=UTF-8

t3
date: 2023-01-23T05:45:22-05:00
type: text/html; charset=UTF-8

concept
type: Tag
label: twittermigration

edit-reply-comment-update
type: item
type: MicroblogPost
title: : 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 wi…
link: https://status.blaise.ca/notice/115988
description: 's status on Tuesday, 10-Jan-2023 01:44:00 EST
encoded: 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. Pos…
date: 2023-01-10T01:44:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110114
enclosure: indieweb-simpler-approach
links to: indieweb-simpler-approach
enclosure: forward-in-time-links
links to: forward-in-time-links
enclosure: fed.brid.gy
links to: fed.brid.gy
enclosure: sending-webmentions-for-updated-postsIf
links to: sending-webmentions-for-updated-postsIf
enclosure: sending-webmentions-for-deleted-postsSimilarly
links to: sending-webmentions-for-deleted-postsSimilarly
enclosure: bridgy-indieweb-posse-backfeed
links to: bridgy-indieweb-posse-backfeed
enclosure: https://techcrunch.com/2022/10/03/twitters-edit-button-is-rolling-out-to-blue-subscribers-in-canada-australia-and-new-zealand/*
links to: https://techcrunch.com/2022/10/03/twitters-edit-button-is-rolling-out-to-blue-subscribers-in-canada-australia-and-new-zealand/*
enclosure: https://blog.hootsuite.com/can-you-edit-a-tweet/*
links to: https://blog.hootsuite.com/can-you-edit-a-tweet/*
enclosure: twitters-edit-button-is-coming-soon-for-paid-users*
links to: twitters-edit-button-is-coming-soon-for-paid-users*
enclosure: https://www.macrumors.com/2022/10/06/twitter-edit-tweet-option-united-states/*/
links to: https://www.macrumors.com/2022/10/06/twitter-edit-tweet-option-united-states/*/
enclosure: twitter-rolling-out-edit-button
links to: twitter-rolling-out-edit-button
enclosure: Poor display
links to: Poor display
enclosure: first-federated-indieweb-comment-thread
links to: first-federated-indieweb-comment-thread
enclosure: responses
links to: responses
tagged: concept

indieweb-simpler-approach
date: 2023-01-07T08:30:40-05:00
type: text/html; charset=UTF-8

forward-in-time-links
date: 2023-01-08T05:17:05-05:00
type: text/html; charset=UTF-8

sending-webmentions-for-updated-postsIf
date: 2023-01-10T07:07:31-05:00
type: text/html; charset=utf-8

sending-webmentions-for-deleted-postsSimilarly
date: 2023-01-10T07:07:31-05:00
type: text/html; charset=utf-8

bridgy-indieweb-posse-backfeed
date: 2023-01-10T07:07:32-05:00
type: text/html; charset=UTF-8

https://techcrunch.com/2022/10/03/twitters-edit-button-is-rolling-out-to-blue-subscribers-in-canada-australia-and-new-zealand/*
date: 2023-01-10T07:07:33-05:00
type: text/html; charset=UTF-8

https://blog.hootsuite.com/can-you-edit-a-tweet/*
date: 2023-01-10T07:07:34-05:00
type: text/html; charset=UTF-8

twitters-edit-button-is-coming-soon-for-paid-users*
date: 2023-01-10T07:07:36-05:00
type: text/html; charset=UTF-8

https://www.macrumors.com/2022/10/06/twitter-edit-tweet-option-united-states/*/
date: 2023-01-10T07:07:36-05:00
type: text/html; charset=UTF-8

twitter-rolling-out-edit-button
date: 2023-01-10T07:07:37-05:00
type: text/html; charset=UTF-8

Poor display
date: 2023-01-10T07:07:37-05:00
type: text/html; charset=UTF-8

first-federated-indieweb-comment-thread
date: 2023-01-10T07:07:39-05:00
type: text/html; charset=UTF-8

responses
date: 2023-01-10T07:07:40-05:00
type: text/html; charset=UTF-8

building blocks
date: 2023-01-04T03:18:31-05:00
type: text/html; charset=UTF-8

key-owning-notes-domain-name
date: 2023-01-04T03:18:32-05:00
type: text/html; charset=UTF-8

concept
type: Tag
label: 100daysday

indieweb-path-you-choose
type: item
type: MicroblogPost
title: : 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
link: https://status.blaise.ca/notice/115975
description: 's status on Wednesday, 04-Jan-2023 02:36:00 EST
encoded: 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
date: 2023-01-04T02:36:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110104
enclosure: micro.blog
links to: micro.blog
enclosure: CMS
links to: CMS
enclosure: building blocks
links to: building blocks
enclosure: key-owning-notes-domain-name
links to: key-owning-notes-domain-name
tagged: concept

objectType=note
type: item
type: MicroblogPost
title: 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 pro…
link: https://status.blaise.ca/notice/115980
description: lnxw48a1's status on Wednesday, 28-Dec-2022 21:20:57 EST
encoded: 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 tw…
date: 2022-12-28T21:20:57-05:00
creator: LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864}
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110107
enclosure: mastodon-brought-a-protocol-to-a-product-fight-ba9fda767c6a
links to: mastodon-brought-a-protocol-to-a-product-fight-ba9fda767c6a
tagged: concept

mastodon-brought-a-protocol-to-a-product-fight-ba9fda767c6a
date: 2023-01-05T15:42:27-05:00
length: 165080
type: text/html; charset=utf-8

concept
type: Tag
label: corpocentric

concept
type: Tag
label: diaspora

concept
type: Tag
label: medium

concept
type: Tag
label: ostatus

concept
type: Tag
label: peertopeer

concept
type: Tag
label: socnets

concept
type: Tag
label: twister

objectType=note
type: item
type: MicroblogPost
title: 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.
link: https://status.blaise.ca/notice/115961
description: lnxw48a1's status on Sunday, 11-Dec-2022 20:58:05 EST
encoded: 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.
date: 2022-12-11T20:58:05-05:00
creator: LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864}
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110096
enclosure: https://prodromou.pub/@evan/109498060348615260
links to: https://prodromou.pub/@evan/109498060348615260
tagged: concept

https://prodromou.pub/@evan/109498060348615260
date: 2022-12-14T06:33:11-05:00
type: text/html; charset=utf-8

concept
type: Tag
label: blockwars

concept
type: Tag
label: fediblock

concept
type: Tag
label: gnusocial

concept
type: Tag
label: lemmy

concept
type: Tag
label: lenny

concept
type: Tag
label: musk

concept
type: Tag
label: pixelfed

concept
type: Tag
label: pleroma

lnxw48a1: Oh, look! Evan has his own #Mastodon server now. https://prodromou.pub/@evan
type: item
type: MicroblogPost
link: https://status.blaise.ca/notice/115933
description: lnxw48a1's status on Friday, 11-Nov-2022 23:27:04 EST
encoded: Oh, look! Evan has his own #Mastodon server now. https://prodromou.pub/@evan
date: 2022-11-11T23:27:04-05:00
creator: LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864}
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110077
tagged: concept

concept
type: Tag
label: atomfeedadded

https://seizemeans.com/users/apollo/statuses/102780704884365882
type: item
type: MicroblogPost
title: 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
link: https://status.blaise.ca/notice/113583
description: apollo's status on Thursday, 12-Sep-2019 13:24:55 EDT
encoded: 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
date: 2019-09-12T13:24:55-04:00
creator: Apollo Lemmon
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/108080
tagged: concept

7491a1e60ba3917a.png
date: 2019-09-13T14:08:24-04:00
length: 114872
type: image/png

concept
type: Tag
label: anarchism

concept
type: Tag
label: communism

concept
type: Tag
label: 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?
type: item
type: MicroblogPost
link: https://status.blaise.ca/notice/111189
description: bobjonkman's status on Sunday, 30-Dec-2018 20:26:33 EST
encoded: 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?
date: 2018-12-30T20:26:33-05:00
creator: Bob Jonkman
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
reply of: https://status.blaise.ca/notice/111171
has discussion: https://status.blaise.ca/conversation/106118
tagged: concept

https://mastodon.xyz/users/douginamug/statuses/101318734890999447
type: item
type: MicroblogPost
title: 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 ⚡ 💻 🌐
link: https://status.blaise.ca/notice/114806
description: douginamug's status on Friday, 28-Dec-2018 07:46:43 EST
encoded: #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 ⚡ 💻 🌐
date: 2018-12-28T07:46:43-05:00
creator: Doug Webb
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/109172
tagged: concept

concept
type: Tag
label: 35c3

concept
type: Tag
label: extinctionrebellion

concept
type: Tag
label: nextcloud

concept
type: Tag
label: signal

https://social.tchncs.de/users/morganth/statuses/100760960238403533
type: item
type: MicroblogPost
title: 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
link: https://status.blaise.ca/notice/113715
description: morganth's status on Thursday, 20-Sep-2018 20:37:18 EDT
encoded: 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
date: 2018-09-20T20:37:18-04:00
creator: morganth
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/108207
tagged: concept

concept
type: Tag
label: foak

concept
type: Tag
label: meta

https://mastodon.at/users/switchingsocial/statuses/100368443255001645
type: item
type: MicroblogPost
title: 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
link: https://status.blaise.ca/notice/109481
description: switchingsocial's status on Friday, 13-Jul-2018 12:55:04 EDT
encoded: 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
date: 2018-07-13T12:55:04-04:00
creator: switching.social
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/104875
tagged: concept

concept
type: Tag
label: aggregation

concept
type: Tag
label: atom

concept
type: Tag
label: feedreaders

concept
type: Tag
label: feeds

concept
type: Tag
label: news

concept
type: Tag
label: newsaggregation

concept
type: Tag
label: newsfeeds

concept
type: Tag
label: reallysimplesyndication

concept
type: Tag
label: rss

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.
type: item
type: MicroblogPost
link: https://status.blaise.ca/notice/105349
description: mmn's status on Sunday, 26-Nov-2017 05:11:37 EST
encoded: 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.
date: 2017-11-26T05:11:37-05:00
creator: MMN-o ✅⃠
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/101752
tagged: concept

https://mstdn.jp/users/tdemin/statuses/98985810982125853
type: item
type: MicroblogPost
title: 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
link: https://status.blaise.ca/notice/105135
description: tdemin's status on Saturday, 11-Nov-2017 07:33:30 EST
encoded: 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
date: 2017-11-11T07:33:30-05:00
creator: Timur Demin
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/101595
tagged: concept

concept
type: Tag
label: 280characters

concept
type: Tag
label: tweetdeck

objectType=note
type: item
type: MicroblogPost
title: 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.
link: https://status.blaise.ca/notice/104786
description: mmn's status on Sunday, 22-Oct-2017 10:37:36 EDT
encoded: 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.
date: 2017-10-22T10:37:36-04:00
creator: MMN-o ✅⃠
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/101315
tagged: concept

concept
type: Tag
label: identica

objectType=note
type: item
type: MicroblogPost
title: 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.
link: https://status.blaise.ca/notice/104127
description: mmn's status on Monday, 11-Sep-2017 04:50:08 EDT
encoded: @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.
date: 2017-09-11T04:50:08-04:00
creator: MMN-o ✅⃠
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/100802
tagged: concept

objectType=note
type: item
type: MicroblogPost
title: 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)
link: https://status.blaise.ca/notice/103987
description: mmn's status on Tuesday, 05-Sep-2017 18:37:58 EDT
encoded: @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)
date: 2017-09-05T18:37:58-04:00
creator: MMN-o ✅⃠
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/100710
tagged: concept

mmn: @patrickme !GNUsocial is another piece of software entirely that has some features that #Mastodon lacks and vice versa.
type: item
type: MicroblogPost
link: https://status.blaise.ca/notice/103365
description: mmn's status on Sunday, 13-Aug-2017 12:13:00 EDT
encoded: @patrickme !GNUsocial is another piece of software entirely that has some features that #Mastodon lacks and vice versa.
date: 2017-08-13T12:13:00-04:00
creator: MMN-o ✅⃠
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/100315
tagged: concept

objectType=Status
type: item
type: MicroblogPost
title: 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
link: https://status.blaise.ca/notice/103154
description: gargron's status on Sunday, 06-Aug-2017 18:04:34 EDT
encoded: #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
date: 2017-08-06T18:04:34-04:00
creator: Eugen
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/100197
enclosure: v1.5.1
links to: v1.5.1
tagged: concept

v1.5.1
date: 2017-08-06T18:23:32-04:00
type: text/html; charset=utf-8

mmn: PS, that server is (at least to search engine caches) a #Mastodon instance ,)
type: item
type: MicroblogPost
link: https://status.blaise.ca/notice/102431
description: mmn's status on Monday, 10-Jul-2017 15:01:30 EDT
encoded: PS, that server is (at least to search engine caches) a #Mastodon instance ,)
date: 2017-07-10T15:01:30-04:00
creator: MMN-o ✅⃠
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/99762
tagged: concept

MMN-o ✅⃠
type: Agent
nick: mmn
holds account: acct