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

fediverse
type: Container
type: channel
description: Updates tagged with fediverse 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: adventures-indieweb-activitypub-bridgy-fed
items: indiewebcamp-portland
items: people-over-protocols-platforms
items: : https://www.threads.net/@0xjessel/post/Cvu7-42PVpCPreviously: https://tantek.com/2023/234/t1/threads-supports-indieweb-rel-me#microformats #relme #fediverse #Threads
items: created-at-indiewebcamp-brighton
items: the-ephemeral-web
items: twenty-years-microformats-updates
items: twenty-years-microformats
items: earthquake-sanfrancisco-shifted
items: should-public-posts-flow-across-sites
items: restarting-100days-indieweb-gift-calendar
items: capture-first-edit-publish-later
items: threads-meetup-meta-fediverse-indieweb
items: border-none-indiewebcamp-nurnberg
items: posse-syndicate-link-reply
items: bridgyfed-webmention-like-fediverse
items: federating-mentions
items: summary-w3c-tpac-2023
items: socialweb-cg-w3ctpac
items: threads-supports-indieweb-rel-me
items: years-ago-first-federated-indieweb-thread
items: btconf-personal-url-fediverse-feed
items: t1
items: mozfest-making-fediverse-socialweb
items: mozfest-making-fediverse
items: five-years-ago-w3c-social-web
items: reply-domain-above-address-and-silo
items: elevate-indieweb-above-silo
items: objectType=note
items: bridgyfed-followers-fediverse-responses
items: indieweb-fediverse
items: indieweb-gift-calendar
items: https://seizemeans.com/users/apollo/statuses/102780704884365882
items: https://mastodon.xyz/users/douginamug/statuses/101318276905189251
items: https://scholar.social/users/SebastianS/statuses/101238942703054131
items: https://organizing.social/users/slackz/statuses/101070461185622767
items: https://mastodon.social/users/LiamErven/statuses/100549775260499384
items: kosinus: You can now challenge someone to game of #chess over toots! https://castling.club/ 💪It's actually a standalone server in the #fediverse, implementing #activitypub all by itself. 😃
items: fuuko: Good afternoon #sdf, #tildeverse and #fediverse! Watching Trix play Dark Souls 3! Come get in here: https://www.twitch.tv/bagotrixhttps://www.twitch.tv/bagotrix
items: https://mastodon.sdf.org/users/fuuko/statuses/100442446688913495

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

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
tagged: concept

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

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

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
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

indiewebcamp-portland
type: item
type: MicroblogPost
title: : All setup here at IndieWebCamp Portland!https://events.indieweb.org/2024/08/indiewebcamp-portland-2024-8bucXDlLqR0kGood crowd of participants from #XOXO #XOXOConf (@xoxofest.com @xoxo@xoxo.zone @xoxo) here to work on their personal website(s), domains, or other independent social media setups!As encouraged by Andy Baio (@waxy.org @andybaio@xoxo.zone @waxpancake)“Every one of you should have a home on the web not controlled by a billionaire.”If you’re in #Portland and want help, encouragement, or camaraderie in getting setup or doing more with your personal site, come on by! We’ll be having a mix of discussion sessions and create/hack sessions. Personal site and hack demos at 16:00 PDT!#indieweb #fediverse #ActivityPub #decentralized #socialMediaThis is post 17 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2024/237/t1/people-over-protocols-platforms→ 🔮
link: https://status.blaise.ca/notice/116211
description: 's status on Sunday, 25-Aug-2024 13:18:00 EDT
encoded: All setup here at IndieWebCamp Portland! https://events.indieweb.org/2024/08/indiewebcamp-portland-2024-8bucXDlLqR0k Good crowd of participants from #XOXO #XOXOConf (@xoxofest.com @xoxo@xoxo.zone @xoxo) here to work on their personal website(s), domains, or other independent social media setups! As encouraged by Andy Baio (@waxy.org @andybaio@xoxo.zone @waxpancake) “Every one of you should have a home on the web not controlled by a billionaire.” If you’re in #Portland and want help, encouragement, or camaraderie in getting setup or doing more with your personal site, come on by! We’ll be having a mix of discussion sessions and create/hack sessions. Personal site and hack demos at 16:00 PDT! #indieweb #fediverse #ActivityPub #decentralized #socialMedia This is post 17 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2024/237/t1/people-over-protocols-platforms → 🔮
date: 2024-08-25T13:18:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110280
tagged: concept

concept
type: Tag
label: decentralized

concept
type: Tag
label: portland

concept
type: Tag
label: socialmediathis

concept
type: Tag
label: xoxo

concept
type: Tag
label: xoxoconf

people-over-protocols-platforms
type: item
type: MicroblogPost
title: : People over protocols over platforms.inspired by today’s #indieweb #fediverse #ActivityPub #decentralized #socialMedia lunch meetup at #XOXO #XOXOConf (@xoxo@xoxo.zone)This is post 16 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2024/173/t1/years-posse-microformats-adoption→ 🔮
link: https://status.blaise.ca/notice/116210
description: 's status on Saturday, 24-Aug-2024 19:56:00 EDT
encoded: People over protocols over platforms. inspired by today’s #indieweb #fediverse #ActivityPub #decentralized #socialMedia lunch meetup at #XOXO #XOXOConf (@xoxo@xoxo.zone) This is post 16 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2024/173/t1/years-posse-microformats-adoption → 🔮
date: 2024-08-24T19:56:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110279
tagged: concept

: https://www.threads.net/@0xjessel/post/Cvu7-42PVpCPreviously: https://tantek.com/2023/234/t1/threads-supports-indieweb-rel-me#microformats #relme #fediverse #Threads
type: item
type: MicroblogPost
link: https://status.blaise.ca/notice/116193
description: 's status on Saturday, 23-Mar-2024 19:05:00 EDT
encoded: https://www.threads.net/@0xjessel/post/Cvu7-42PVpC Previously: https://tantek.com/2023/234/t1/threads-supports-indieweb-rel-me #microformats #relme #fediverse #Threads
date: 2024-03-23T19:05:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110262
tagged: concept

concept
type: Tag
label: relme

concept
type: Tag
label: threads

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
type: item
type: MicroblogPost
title: : The answer to “How should you @-mention someone you are replying to?”^1 can depend on many factors or a few. Context matters somewhat, sometimes.We can simplify it to 2 questions, based on 1 directive:* Elevate #IndieWeb domains, above any silo or @-@ identitiesTwo questions and answers: 1. Do they have an #IndieWeb domain? Then @-domain mention them^2, like you are speaking to them at their domain identity. This will notify them there, or at least reinforce their domain’s importance.2. Was their post only published on a silo (or #fediverse instance), or was it POSSEd to a silo (or fediverse instance) and you plan to POSSE (or federate) your reply^3? Then @-mention their silo @-name (or @-@ address), in parentheses if (1). This will notify them on that silo (or instance), and may help thread your POSSE reply.Examples:If the author has their own domain:Reply to an IndieWeb post (& POSSE toot): https://tantek.com/2023/008/t1/* @-domain (@-@)Reply to an IndieWeb post (& POSSE tweet): https://tantek.com/2023/016/t1/* @-domain [that matches their Twitter @-name]Reply to a toot: https://tantek.com/2023/008/t4/* @-domain (@-@)Reply to a tweet: https://tantek.com/2023/002/t2/* @-domain (Twitter @-name)If the author does not have their own domain:Reply to a toot: https://tantek.com/2023/002/t4/* @-@Reply to a tweet: none since this series, though it would be of the form:* Twitter @-nameThis is day 17 of #100DaysOfIndieWeb #100Days, again finished the next day.← Day 16: https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute→ 🔮^1 https://tantek.com/2023/017/t1/socialweb-blogs-reply-comment-post^2 https://tantek.com/2023/011/t1/indieweb-evolving-at-mention^3 https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute
link: https://status.blaise.ca/notice/116002
description: 's status on Thursday, 19-Jan-2023 02:11:00 EST
encoded: The answer to “How should you @-mention someone you are replying to?”^1 can depend on many factors or a few. Context matters somewhat, sometimes. We can simplify it to 2 questions, based on 1 directive: * Elevate #IndieWeb domains, above any silo or @-@ identities Two questions and answers: 1. Do they have an #IndieWeb domain? Then @-domain mention them^2, like you are speaking to them at their domain identity. This will notify them there, or at least reinforce their domain’s importance. 2. Was their post only published on a silo (or #fediverse instance), or was it POSSEd to a silo (or fediverse instance) and you plan to POSSE (or federate) your reply^3? Then @-mention their silo @-name (or @-@ address), in parentheses if (1). This will notify them on that silo (or instance), and may help thread your POSSE reply. Examples: If the author has their own domain: Reply to an IndieWeb post (& POSSE toot): https://tantek.com/2023/008/t1/ * @-domain (@-@) Reply to an IndieWeb post (& POSSE tweet): https://tantek.com/2023/016/t1/ * @-domain [that matches their Twitter @-name] Reply to a toot: https://tantek.com/2023/008/t4/ * @-domain (@-@) Reply to a tweet: https://tantek.com/2023/002/t2/ * @-domain (Twitter @-name) If the author does not have their own domain: Reply to a toot: https://tantek.com/2023/002/t4/ * @-@ Reply to a tweet: none since this series, though it would be of the form: * Twitter @-name This is day 17 of #100DaysOfIndieWeb #100Days, again finished the next day. ← Day 16: https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute → 🔮 ^1 https://tantek.com/2023/017/t1/socialweb-blogs-reply-comment-post ^2 https://tantek.com/2023/011/t1/indieweb-evolving-at-mention ^3 https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute
date: 2023-01-19T02:11:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110125
tagged: concept

reply-domain-above-address-and-silo
date: 2023-01-21T04:12:23-05:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : Instead of posting on a personal #IndieWeb site (& POSSE copies), some post primarily to a #fediverse instance and syndicate to Twitter, or vice-versa. How to reply^1 to such posts, e.g.:Reply to a toot (& POSSE tweet): https://tantek.com/2023/019/t4* @-@ (Twitter @-name)This is a variant of case (2) in https://tantek.com/2023/018/t1/elevate-indieweb-above-silo.We can update the directive and two questions & answers in that prior post accordingly:* Elevate #IndieWeb domains above @-@ addresses, and those above any silo identities1. Do they have an #IndieWeb domain? Then @-domain mention them^2, like you are speaking to them at their domain identity. This will notify them there, or at least reinforce their domain’s importance.2. Was their post only published on a #fediverse instance (and/or silo), or was it POSSEd to a fediverse instance (and/or silo) and do you plan to federate (and/or POSSE) your reply^3?Then use their @-@ address or silo @-name, or @-@ (silo @-name) for both, or (@-@, silo @-name) parenthetically following their @-domain if (1). This will notify them on that instance (or silo), and may help thread your POSSE reply.When posting a reply, you (or your CMS automatically) should explicitly link with u-in-reply-to markup^4 to the post your are replying to, and any of its syndicated copy permalinks on destinations you plan to POSSE your reply (see also multi-reply^5). This is day 18 of #100DaysOfIndieWeb #100Days, written the day after.← Day 17: https://tantek.com/2023/018/t1/elevate-indieweb-above-silo→ 🔮^1 https://tantek.com/2023/017/t1/socialweb-blogs-reply-comment-post^2 https://tantek.com/2023/011/t1/indieweb-evolving-at-mention^3 https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute^4 https://indieweb.org/in-reply-to^5 https://indieweb.org/multiple-reply
link: https://status.blaise.ca/notice/116003
description: 's status on Thursday, 19-Jan-2023 21:05:00 EST
encoded: Instead of posting on a personal #IndieWeb site (& POSSE copies), some post primarily to a #fediverse instance and syndicate to Twitter, or vice-versa. How to reply^1 to such posts, e.g.: Reply to a toot (& POSSE tweet): https://tantek.com/2023/019/t4 * @-@ (Twitter @-name) This is a variant of case (2) in https://tantek.com/2023/018/t1/elevate-indieweb-above-silo. We can update the directive and two questions & answers in that prior post accordingly: * Elevate #IndieWeb domains above @-@ addresses, and those above any silo identities 1. Do they have an #IndieWeb domain? Then @-domain mention them^2, like you are speaking to them at their domain identity. This will notify them there, or at least reinforce their domain’s importance. 2. Was their post only published on a #fediverse instance (and/or silo), or was it POSSEd to a fediverse instance (and/or silo) and do you plan to federate (and/or POSSE) your reply^3? Then use their @-@ address or silo @-name, or @-@ (silo @-name) for both, or (@-@, silo @-name) parenthetically following their @-domain if (1). This will notify them on that instance (or silo), and may help thread your POSSE reply. When posting a reply, you (or your CMS automatically) should explicitly link with u-in-reply-to markup^4 to the post your are replying to, and any of its syndicated copy permalinks on destinations you plan to POSSE your reply (see also multi-reply^5). This is day 18 of #100DaysOfIndieWeb #100Days, written the day after. ← Day 17: https://tantek.com/2023/018/t1/elevate-indieweb-above-silo → 🔮 ^1 https://tantek.com/2023/017/t1/socialweb-blogs-reply-comment-post ^2 https://tantek.com/2023/011/t1/indieweb-evolving-at-mention ^3 https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute ^4 https://indieweb.org/in-reply-to ^5 https://indieweb.org/multiple-reply
date: 2023-01-19T21:05:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110126
enclosure: indieweb-evolving-at-mention
links to: indieweb-evolving-at-mention
enclosure: publish-indieweb-decide-distribute
links to: publish-indieweb-decide-distribute
enclosure: socialweb-blogs-reply-comment-post
links to: socialweb-blogs-reply-comment-post
enclosure: t4*
links to: t4*
enclosure: elevate-indieweb-above-silo
links to: elevate-indieweb-above-silo
enclosure: in-reply-to
links to: in-reply-to
enclosure: multiple-reply
links to: multiple-reply
tagged: concept

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
enclosure: js-dr-javascript-required-dead
links to: js-dr-javascript-required-dead
enclosure: site-deaths
links to: site-deaths
enclosure: indiewebcamp-brighton-tickets-available
links to: indiewebcamp-brighton-tickets-available
enclosure: APIBluesky
links to: APIBluesky
enclosure: BlueskyBridgy
links to: BlueskyBridgy
enclosure: Bridgy
links to: Bridgy
enclosure: ccTLD
links to: ccTLD
enclosure: ccTLDcurlable
links to: ccTLDcurlable
enclosure: curlabledeclarative
links to: curlabledeclarative
enclosure: thedeclarativewebInternet
links to: thedeclarativewebInternet
enclosure: https://archive.org/js
links to: https://archive.org/js
enclosure: JSONlongevity
links to: JSONlongevity
enclosure: longevityMastodon
links to: longevityMastodon
enclosure: Mastodonmetaformats
links to: Mastodonmetaformats
enclosure: metaformatspermalink
links to: metaformatspermalink
enclosure: permalinkprinciples
links to: permalinkprinciples
enclosure: principlesprogressive
links to: principlesprogressive
enclosure: progressive enhancementreply
links to: progressive enhancementreply
enclosure: replyreply-context
links to: replyreply-context
enclosure: reply-contextrobots.txt
links to: reply-contextrobots.txt
enclosure: robots txtsocial
links to: robots txtsocial
enclosure: social mediasilo
links to: social mediasilo
enclosure: siloView
links to: siloView
links to: index.html¹
enclosure: t1707845454695700²
links to: t1707845454695700²
tagged: concept

js-dr-javascript-required-dead
date: 2021-01-17T17:12:07-05:00
type: text/html; charset=UTF-8

site-deaths
date: 2023-01-17T19:26:41-05:00
type: text/html; charset=UTF-8

indiewebcamp-brighton-tickets-available
date: 2024-02-15T19:54:52-05:00
type: text/html; charset=UTF-8

APIBluesky
date: 2024-02-15T19:54:53-05:00
type: text/html; charset=UTF-8

BlueskyBridgy
date: 2024-02-15T19:54:54-05:00
type: text/html; charset=UTF-8

Bridgy
date: 2024-02-15T19:54:55-05:00
length: 207
type: text/html; charset=utf-8

ccTLD
date: 2024-02-15T19:54:55-05:00
length: 207
type: text/html; charset=utf-8

ccTLDcurlable
date: 2024-02-15T19:54:56-05:00
type: text/html; charset=UTF-8

curlabledeclarative
date: 2024-02-15T19:54:57-05:00
type: text/html; charset=UTF-8

thedeclarativewebInternet
date: 2024-02-15T19:54:58-05:00
length: 135958
type: text/html; charset=utf-8

https://archive.org/js
date: 2024-02-15T19:54:59-05:00
length: 4847
type: text/html; charset=utf-8

JSONlongevity
date: 2024-02-15T19:55:01-05:00
type: text/html; charset=UTF-8

longevityMastodon
date: 2024-02-15T19:55:02-05:00
type: text/html; charset=UTF-8

Mastodonmetaformats
date: 2024-02-15T19:55:03-05:00
type: text/html; charset=UTF-8

metaformatspermalink
date: 2024-02-15T19:55:04-05:00
type: text/html; charset=UTF-8

permalinkprinciples
date: 2024-02-15T19:55:05-05:00
type: text/html; charset=UTF-8

principlesprogressive
date: 2024-02-15T19:55:06-05:00
type: text/html; charset=UTF-8

progressive enhancementreply
date: 2024-02-15T19:55:07-05:00
type: text/html; charset=UTF-8

replyreply-context
date: 2024-02-15T19:55:08-05:00
type: text/html; charset=UTF-8

reply-contextrobots.txt
date: 2024-02-15T19:55:09-05:00
type: text/html; charset=UTF-8

robots txtsocial
date: 2024-02-15T19:55:10-05:00
type: text/html; charset=UTF-8

social mediasilo
date: 2024-02-15T19:55:11-05:00
type: text/html; charset=UTF-8

siloView
date: 2024-02-15T19:55:12-05:00
type: text/html; charset=UTF-8

t1707845454695700²
date: 2024-02-15T19:55:14-05:00
type: text/html; charset=utf-8

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

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

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
type: item
type: MicroblogPost
title: : Threads.net now supports the #indieWeb #microformats #openStandard rel-me for distributed ✅ verification!¹ (supported since 2023-08-09)My Threads profile already had my domain since it was created from my Instagram profile.View source on https://www.threads.net/@tantek and you can see the #relMe on a link tag: Instructions to add yours:* Add your domain to your Threads profile "Link" field. That’s it.Longer explicit steps: https://indieweb.org/rel-me#ThreadsThanks especially to @timothychambers.net (@tchambers@indieweb.social, @timothyjchambers@threads.net) for requesting rel-me support² which one Threads engineer “decided to hack it together” one night!³You can view Tim’s profile @tchambers@indieweb.social for a real world example of a Mastodon profile showing a green text ✅ verified link to a Threads profile.Tim made several good points in his request:“… a small, but disproportionately helpful addition would be to support this "rel=me" feature in your profiles. That could launch well before full ActivityPub, & show the first real integration to open social web standards”Microformats (and IndieWeb) standards in general are deliberately designed as small, incremental building blocks which are disproportionately helpful as Tim says.These small building blocks which directly enable user features are usually something a web developer can code at least some (often complete!) support for in one day/night which makes them particularly appealing as a way to rapidly support open #socialWeb standards used by the #fediverse and beyond.Incrementally implementing microformats & IndieWeb standards⁴ also demonstrates good will and good intentions for supporting the #openWeb.This is day 44 of #100DaysOfIndieWeb. #100Days← Day 43: https://tantek.com/2023/171/t1/anniversaries-microformats-posse→ 🔮Previously:* 2023-02-01 Wikipedia.org supports multiple rel=me links: https://tantek.com/2023/139/t1/wikipedia-supports-indieweb-rel-me¹ https://www.threads.net/@mosseri/post/Cvu2eXurRbB²…
link: https://status.blaise.ca/notice/116129
description: 's status on Tuesday, 22-Aug-2023 15:43:00 EDT
encoded: Threads.net now supports the #indieWeb #microformats #openStandard rel-me for distributed ✅ verification!¹ (supported since 2023-08-09) My Threads profile already had my domain since it was created from my Instagram profile. View source on https://www.threads.net/@tantek and you can see the #relMe on a link tag: Instructions to add yours: * Add your domain to your Threads profile "Link" field. That’s it. Longer explicit steps: https://indieweb.org/rel-me#Threads Thanks especially to @timothychambers.net (@tchambers@indieweb.social, @timothyjchambers@threads.net) for requesting rel-me support² which one Threads engineer “decided to hack it together” one night!³ You can view Tim’s profile @tchambers@indieweb.social for a real world example of a Mastodon profile showing a green text ✅ verified link to a Threads profile. Tim made several good points in his request: “… a small, but disproportionately helpful addition would be to support this "rel=me" feature in your profiles. That could launch well before full ActivityPub, & show the first real integration to open social web standards” Microformats (and IndieWeb) standards in general are deliberately designed as small, incremental building blocks which are disproportionately helpful as Tim says. These small building blocks which directly enable user features are usually something a web developer can code at least some (often complete!) support for in one day/night which makes them particularly appealing as a way to rapidly support open #socialWeb standards used by the #fediverse and beyond. Incrementally implementing microformats & IndieWeb standards⁴ also demonstrates good will and good intentions for supporting the #openWeb. This is day 44 of #100DaysOfIndieWeb. #100Days ← Day 43: https://tantek.com/2023/171/t1/anniversaries-microformats-posse → 🔮 Previously: * 2023-02-01 Wikipedia.org supports multiple rel=me links: https://tantek.com/2023/139/t1/wikipedia-supports-indieweb-rel-me ¹ https://www.threads.net/@mosseri/po…
date: 2023-08-22T15:43:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110207
enclosure: tantek.com
links to: tantek.com
enclosure: spec.indieweb.org
links to: spec.indieweb.org
enclosure: wikipedia-supports-indieweb-rel-me
links to: wikipedia-supports-indieweb-rel-me
enclosure: @tantek
links to: @tantek
enclosure: ThreadsThanks
links to: ThreadsThanks
enclosure: anniversaries-microformats-posse
links to: anniversaries-microformats-posse
links to: Cvu2eXurRbB²
links to: CupCvChAxI8³
links to: Cvu7-A4viZu⁴
tagged: concept

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

concept
type: Tag
label: metaformats

concept
type: Tag
label: microformats2

earthquake-sanfrancisco-shifted
type: item
type: MicroblogPost
title: : I felt the #earthquake here in #SanFrancisco. A single quick sharp jolt with rapid decay, duration less than 2s, meaning it was relatively nearby and small in magnitudeI was about to say, perhaps #earthquakes are the last use-case for #Twitter because yes I reflexively checked it and did see posts about it from folks, including a few friends.Then I checked https://indieweb.social/tags/earthquake and it has plenty of recent #fediverse posts about the earthquake, several @sfba.social.Feels like something big has shifted. The #federated #IndieWeb has replaced another #socialMedia silo use-case.This is post 7 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2024/027/t1/indieweb-ideals-systems-swappable→ 🔮Post glossary:silo https://indieweb.org/silosocial media https://indieweb.org/social_mediause-case https://indieweb.org/use_case
link: https://status.blaise.ca/notice/116163
description: 's status on Friday, 02-Feb-2024 16:49:00 EST
encoded: I felt the #earthquake here in #SanFrancisco. A single quick sharp jolt with rapid decay, duration less than 2s, meaning it was relatively nearby and small in magnitude I was about to say, perhaps #earthquakes are the last use-case for #Twitter because yes I reflexively checked it and did see posts about it from folks, including a few friends. Then I checked https://indieweb.social/tags/earthquake and it has plenty of recent #fediverse posts about the earthquake, several @sfba.social. Feels like something big has shifted. The #federated #IndieWeb has replaced another #socialMedia silo use-case. This is post 7 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2024/027/t1/indieweb-ideals-systems-swappable → 🔮 Post glossary: silo https://indieweb.org/silo social media https://indieweb.org/social_media use-case https://indieweb.org/use_case
date: 2024-02-02T16:49:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110236
enclosure: silosocial
links to: silosocial
enclosure: earthquake
links to: earthquake
enclosure: indieweb-ideals-systems-swappable
links to: indieweb-ideals-systems-swappable
enclosure: social mediause-case
links to: social mediause-case
enclosure: use case
links to: use case
tagged: concept

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

earthquake
date: 2024-02-02T17:58:24-05:00
type: text/html; charset=utf-8

indieweb-ideals-systems-swappable
date: 2024-02-02T17:58:25-05:00
type: text/html; charset=UTF-8

social mediause-case
date: 2024-02-02T17:58:26-05:00
type: text/html; charset=UTF-8

use case
date: 2024-02-02T17:58:27-05:00
type: text/html; charset=UTF-8

concept
type: Tag
label: earthquake

concept
type: Tag
label: earthquakes

concept
type: Tag
label: federated

concept
type: Tag
label: sanfrancisco

concept
type: Tag
label: twitter

should-public-posts-flow-across-sites
type: item
type: MicroblogPost
title: : @snarfed.org posted a great overview of thoughtful (and sometimes heated) discussions across blogs and the #fediverse about how freely should “public” posts & comments on the web flow across sites:“Moderate people, not code” (https://snarfed.org/2024-01-21_moderate-people-not-code)If you are designing or creating any kind of publishing or social features on the web, this post is for you.It touches on topics ranging from #contextCollapse to #federation to #moderation and everything in between.Does your choice of publishing tool set expectations about where your content might propagate, or whether it will be indexed by search engines? Should it?Do the limitations of your server (e.g. js;dr) imply limitations of where your posts go, or whether they can be searched or archived? Should they?When you post something publicly, are you truly posting it for a global audience for all time, or only for one or a few more limited #publics for an ephemerality?When you reply to a post, do you expect your reply to only be visible in the context you posted it, or do you expect it to travel alongside that post to anywhere it might propagate to?On the #IndieWeb, especially for public posts, some of these questions have easier and more obvious answers, because the intent of nearly all public IndieWeb posts is to interact across the web with other posts and sites, typically via the #Webmention protocol. However there are still questions.Are the expectations for a blog and blogging different from a social media site, whether a silo or an instance on a network?Is a personal website with posts still just a blog, or does it become something new when you start posting responses from your site, or receiving (e.g. via Webmention) and displaying responses from across the web to your posts on your site? Or is it now a “social website”?If you have a social website, what is your responsibility for keeping it, well, social? Do you moderate Webmentions by default? Do you use the Vouch extension for…
link: https://status.blaise.ca/notice/116160
description: 's status on Tuesday, 23-Jan-2024 20:20:00 EST
encoded: @snarfed.org posted a great overview of thoughtful (and sometimes heated) discussions across blogs and the #fediverse about how freely should “public” posts & comments on the web flow across sites: “Moderate people, not code” (https://snarfed.org/2024-01-21_moderate-people-not-code) If you are designing or creating any kind of publishing or social features on the web, this post is for you. It touches on topics ranging from #contextCollapse to #federation to #moderation and everything in between. Does your choice of publishing tool set expectations about where your content might propagate, or whether it will be indexed by search engines? Should it? Do the limitations of your server (e.g. js;dr) imply limitations of where your posts go, or whether they can be searched or archived? Should they? When you post something publicly, are you truly posting it for a global audience for all time, or only for one or a few more limited #publics for an ephemerality? When you reply to a post, do you expect your reply to only be visible in the context you posted it, or do you expect it to travel alongside that post to anywhere it might propagate to? On the #IndieWeb, especially for public posts, some of these questions have easier and more obvious answers, because the intent of nearly all public IndieWeb posts is to interact across the web with other posts and sites, typically via the #Webmention protocol. However there are still questions. Are the expectations for a blog and blogging different from a social media site, whether a silo or an instance on a network? Is a personal website with posts still just a blog, or does it become something new when you start posting responses from your site, or receiving (e.g. via Webmention) and displaying responses from across the web to your posts on your site? Or is it now a “social website”? If you have a social website, what is your responsibility for keeping it, well, social? Do you moderate Webmentions by default? Do you use the Vouch exte…
date: 2024-01-23T20:20:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110233
enclosure: Webmention
links to: Webmention
enclosure: Vouch
links to: Vouch
enclosure: 2024-01-21 moderate-people-not-code)If
links to: 2024-01-21 moderate-people-not-code)If
enclosure: indiewebcamp-brighton-planned
links to: indiewebcamp-brighton-planned
enclosure: backfeedblog
links to: backfeedblog
enclosure: blogblogging
links to: blogblogging
enclosure: blogging
links to: blogging
enclosure: commentscontext
links to: commentscontext
enclosure: context collapseephemerality
links to: context collapseephemerality
enclosure: https://indieweb.org/ephemeralityjs
links to: https://indieweb.org/ephemeralityjs
enclosure: https://indieweb.org/js
links to: https://indieweb.org/js
enclosure: moderationPOSSE
links to: moderationPOSSE
enclosure: POSSEposts
links to: POSSEposts
enclosure: postspublics
links to: postspublics
enclosure: publicsreply
links to: publicsreply
enclosure: replyVouch
links to: replyVouch
tagged: concept

Webmention
date: 2017-01-12T13:47:24-05:00
type: text/html; charset=UTF-8

Vouch
date: 2022-02-02T02:23:22-05:00
type: text/html; charset=UTF-8

2024-01-21 moderate-people-not-code)If
date: 2024-01-23T21:32:45-05:00
type: text/html; charset=UTF-8

indiewebcamp-brighton-planned
date: 2024-01-23T21:32:47-05:00
type: text/html; charset=UTF-8

backfeedblog
date: 2024-01-23T21:32:48-05:00
type: text/html; charset=UTF-8

blogblogging
date: 2024-01-23T21:32:49-05:00
type: text/html; charset=UTF-8

blogging
date: 2024-01-23T21:32:50-05:00
type: text/html; charset=UTF-8

commentscontext
date: 2024-01-23T21:32:51-05:00
type: text/html; charset=UTF-8

context collapseephemerality
date: 2024-01-23T21:32:52-05:00
type: text/html; charset=UTF-8

https://indieweb.org/ephemeralityjs
date: 2024-01-23T21:32:53-05:00
type: text/html; charset=UTF-8

https://indieweb.org/js
date: 2024-01-23T21:32:54-05:00
type: text/html; charset=UTF-8

moderationPOSSE
date: 2024-01-23T21:32:55-05:00
type: text/html; charset=UTF-8

POSSEposts
date: 2024-01-23T21:32:56-05:00
type: text/html; charset=UTF-8

postspublics
date: 2024-01-23T21:32:57-05:00
type: text/html; charset=UTF-8

publicsreply
date: 2024-01-23T21:32:58-05:00
type: text/html; charset=UTF-8

replyVouch
date: 2024-01-23T21:32:58-05:00
type: text/html; charset=UTF-8

concept
type: Tag
label: backfeed

concept
type: Tag
label: contextcollapse

concept
type: Tag
label: moderation

concept
type: Tag
label: publics

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
enclosure: own-your-notes
links to: own-your-notes
enclosure: POSSEsilo
links to: POSSEsilo
enclosure: no-large-language-model-llm-used
links to: no-large-language-model-llm-used
enclosure: APIPOSSE
links to: APIPOSSE
enclosure: silo¹
links to: silo¹
enclosure: algorithmic feed³
links to: algorithmic feed³
enclosure: 2023-12-indieweb-gift-calendar⁴
links to: 2023-12-indieweb-gift-calendar⁴
enclosure: 2018-12-indieweb-challenge⁵
links to: 2018-12-indieweb-challenge⁵
tagged: concept

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

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

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

APIPOSSE
date: 2024-01-02T00:45:28-05:00
type: text/html; charset=UTF-8

silo¹
date: 2024-01-02T00:45:29-05:00
type: text/html; charset=UTF-8

algorithmic feed³
date: 2024-01-02T00:45:31-05:00
type: text/html; charset=UTF-8

2023-12-indieweb-gift-calendar⁴
date: 2024-01-02T00:45:32-05:00
type: text/html; charset=UTF-8

2018-12-indieweb-challenge⁵
date: 2024-01-02T00:45:33-05:00
type: text/html; charset=UTF-8

concept
type: Tag
label: 100days

concept
type: Tag
label: 100daysofindieweb

concept
type: Tag
label: showdonttellthis

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

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

threads-meetup-meta-fediverse-indieweb
type: item
type: MicroblogPost
title: : at a fascinating #Threads meetup hosted by Meta in San Francisco, with a handful of great #dataportability #fediverse #indieweb #openweb folks, learning about and providing feedback to Threads folks about their #federation #ActivityPub and other #openStandards support plans.Chatham House rule¹ means we can quote and talk about what’s being discussed (I’m taking notes), however no attribution, which I’m extending to not saying (or @-@-mentioning) who else is here.If you’re also here, feel free to reply to this post or use one of the below hashtags. And since I’m publishing this, feel free to @-me as well.#DataDialogue #Threadiverse (unofficial hashtag suggestion from a participant)¹ https://en.wikipedia.org/wiki/Chatham_House_rule
link: https://status.blaise.ca/notice/116145
description: 's status on Thursday, 07-Dec-2023 20:09:00 EST
encoded: at a fascinating #Threads meetup hosted by Meta in San Francisco, with a handful of great #dataportability #fediverse #indieweb #openweb folks, learning about and providing feedback to Threads folks about their #federation #ActivityPub and other #openStandards support plans. Chatham House rule¹ means we can quote and talk about what’s being discussed (I’m taking notes), however no attribution, which I’m extending to not saying (or @-@-mentioning) who else is here. If you’re also here, feel free to reply to this post or use one of the below hashtags. And since I’m publishing this, feel free to @-me as well. #DataDialogue #Threadiverse (unofficial hashtag suggestion from a participant) ¹ https://en.wikipedia.org/wiki/Chatham_House_rule
date: 2023-12-07T20:09:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110222
tagged: concept

concept
type: Tag
label: dataportability

concept
type: Tag
label: threadiverse

border-none-indiewebcamp-nurnberg
type: item
type: MicroblogPost
title: : Inspiring mix of perspective expanding and personal talks at border:none (https://border-none.net/ @border_none) the past two days. Thanks speakers, volunteers, and especially organizers @marcthiele.com (@marcthiele@mastodon.social @marcthiele) and @jkphl.is (@jkphl@mastodon.social @jkphl).Looking forward to the next two days at #IndieWebCamp Nürnberg @tollwerk.de (@tollwerk@mastodon.social @tollwerk) of personal site demos, brainstorming sessions, and making, creating, & hacking things from UX to protocols to improve & interconnect our websites, with each other ( #Webmention ), #fediverse ( #BridgyFed & #ActivityPub ), and others ( #POSSE #backfeed ).Still a few spots if you’re in town or can hop on a train and join us Saturday & Sunday!🎟 Tickets: https://ti.to/beyondtellerrand/bordernone-2023/with/kqyaidtq92k🗓 Event: https://events.indieweb.org/2023/10/indiewebcamp-nuremberg-2023-DmXe4dYdfagcℹ️ More info: https://indieweb.org/2023/Nuremberg#bordernone #bono23 #IndieWeb
link: https://status.blaise.ca/notice/116142
description: 's status on Friday, 27-Oct-2023 19:23:00 EDT
encoded: Inspiring mix of perspective expanding and personal talks at border:none (https://border-none.net/ @border_none) the past two days. Thanks speakers, volunteers, and especially organizers @marcthiele.com (@marcthiele@mastodon.social @marcthiele) and @jkphl.is (@jkphl@mastodon.social @jkphl). Looking forward to the next two days at #IndieWebCamp Nürnberg @tollwerk.de (@tollwerk@mastodon.social @tollwerk) of personal site demos, brainstorming sessions, and making, creating, & hacking things from UX to protocols to improve & interconnect our websites, with each other ( #Webmention ), #fediverse ( #BridgyFed & #ActivityPub ), and others ( #POSSE #backfeed ). Still a few spots if you’re in town or can hop on a train and join us Saturday & Sunday! 🎟 Tickets: https://ti.to/beyondtellerrand/bordernone-2023/with/kqyaidtq92k 🗓 Event: https://events.indieweb.org/2023/10/indiewebcamp-nuremberg-2023-DmXe4dYdfagc ℹ️ More info: https://indieweb.org/2023/Nuremberg #bordernone #bono23 #IndieWeb
date: 2023-10-27T19:23:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110219
enclosure: https://border-none.net/2023/
links to: https://border-none.net/2023/
enclosure: kqyaidtq92k
links to: kqyaidtq92k
enclosure: indiewebcamp-nuremberg-2023-DmXe4dYdfagcℹ
links to: indiewebcamp-nuremberg-2023-DmXe4dYdfagcℹ
enclosure: bordernone
links to: bordernone
tagged: concept

https://border-none.net/2023/
date: 2023-10-27T20:58:17-04:00
length: 263310
type: text/html

kqyaidtq92k
date: 2023-10-27T20:58:20-04:00
type: text/html; charset=utf-8

indiewebcamp-nuremberg-2023-DmXe4dYdfagcℹ
date: 2023-10-27T20:58:21-04:00
type: text/html; charset=UTF-8

bordernone
date: 2023-10-27T20:58:21-04:00
type: text/html; charset=UTF-8

concept
type: Tag
label: bono23

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

discuss
date: 2023-01-28T08:19:05-05: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

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

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
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

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: nostr

concept
type: Tag
label: openwebwe

concept
type: Tag
label: socialprotocols

concept
type: Tag
label: socialwebwg

spec.indieweb.org
date: 2023-01-11T09:44:12-05:00
length: 35487
type: text/html

@tantek
date: 2023-08-22T19:29:05-04:00
type: text/html; charset="utf-8"

ThreadsThanks
date: 2023-08-22T19:29:06-04:00
type: text/html; charset=UTF-8

concept
type: Tag
label: openstandard

concept
type: Tag
label: openwebthis

years-ago-first-federated-indieweb-thread
type: item
type: MicroblogPost
title: : 10 years ago today the first #federated #IndieWeb comment thread was published and collected peer-to-peer IndieWeb replies across websites without any intermediary, silo or otherwise¹.2013-04-19 @eschnou.com posted a brief note on his personal site with #atMentions of a few domains (putting an '@' sign immediately before a domain name to indicate an explicit cross-web @-mention), which itself was also a first² "Testing #indieweb federation with @waterpigs.co.uk, @aaronparecki.com and @indiewebcamp.com !"When @aaronpk.com was notified and replied from his site within minutes³, it became the first peer-to-peer federated IndieWeb comment thread, at the time using h-entry and Pingback. I blogged about it a few days later⁴.Earlier this year I blogged more observations of all the user interactions that happened on that day and shortly thereafter to make this all work: https://tantek.com/2023/014/t4/domain-first-federated-atmentionUnfortunately Laurent Eschnou’s original post is no longer up, and we only have the Internet Archive copy. However most of the IndieWeb reply posts are still up including Barnaby’s: https://waterpigs.co.uk/notes/1334/The oldest still working federated post and comment thread was second overall, unsurprisingly from @aaronparecki.com⁵, a whole 40 days after Laurent’s first.This is day 37 of #100DaysOfIndieWeb. #100Days #OpenWeb #federation #fediverse← Day 36: https://tantek.com/2023/100/t1/auto-linked-hashtags-federated→ 🔮Glossaryfederation https://indieweb.org/federationh-entry https://microformats.org/wiki/h-entryPingback https://indieweb.org/Pingbackreply post https://indieweb.org/replyReferences¹ https://web.archive.org/web/20130427010301/http://eschnou.com/entry/testing-indieweb-federation-with-waterpigscouk-aaronpareckicom-and--62-24908.html² https://tantek.com/2023/014/t4/domain-first-federated-atmention³ https://aaronparecki.com/2013/04/19/3/indieweb⁴ https://tantek.com/2013/113/b1/first-federated-indieweb-comment-thread⁵ https://aaronpar…
link: https://status.blaise.ca/notice/116061
description: 's status on Wednesday, 19-Apr-2023 20:48:00 EDT
encoded: 10 years ago today the first #federated #IndieWeb comment thread was published and collected peer-to-peer IndieWeb replies across websites without any intermediary, silo or otherwise¹. 2013-04-19 @eschnou.com posted a brief note on his personal site with #atMentions of a few domains (putting an '@' sign immediately before a domain name to indicate an explicit cross-web @-mention), which itself was also a first² "Testing #indieweb federation with @waterpigs.co.uk, @aaronparecki.com and @indiewebcamp.com !" When @aaronpk.com was notified and replied from his site within minutes³, it became the first peer-to-peer federated IndieWeb comment thread, at the time using h-entry and Pingback. I blogged about it a few days later⁴. Earlier this year I blogged more observations of all the user interactions that happened on that day and shortly thereafter to make this all work: https://tantek.com/2023/014/t4/domain-first-federated-atmention Unfortunately Laurent Eschnou’s original post is no longer up, and we only have the Internet Archive copy. However most of the IndieWeb reply posts are still up including Barnaby’s: https://waterpigs.co.uk/notes/1334/ The oldest still working federated post and comment thread was second overall, unsurprisingly from @aaronparecki.com⁵, a whole 40 days after Laurent’s first. This is day 37 of #100DaysOfIndieWeb. #100Days #OpenWeb #federation #fediverse ← Day 36: https://tantek.com/2023/100/t1/auto-linked-hashtags-federated → 🔮 Glossary federation https://indieweb.org/federation h-entry https://microformats.org/wiki/h-entry Pingback https://indieweb.org/Pingback reply post https://indieweb.org/reply References ¹ https://web.archive.org/web/20130427010301/http://eschnou.com/entry/testing-indieweb-federation-with-waterpigscouk-aaronpareckicom-and--62-24908.html ² https://tantek.com/2023/014/t4/domain-first-federated-atmention ³ https://aaronparecki.com/2013/04/19/3/indieweb ⁴ https://tantek.com/2013/113/b1/first-federated-indieweb-comment-thread ⁵…
date: 2023-04-19T20:48:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110167
enclosure: first-federated-indieweb-comment-thread
links to: first-federated-indieweb-comment-thread
enclosure: domain-first-federated-atmention
links to: domain-first-federated-atmention
enclosure: The
links to: The
enclosure: auto-linked-hashtags-federated
links to: auto-linked-hashtags-federated
enclosure: federationh-entry
links to: federationh-entry
enclosure: h-entryPingback
links to: h-entryPingback
enclosure: Pingbackreply
links to: Pingbackreply
enclosure: replyReferences¹
links to: replyReferences¹
links to: testing-indieweb-federation-with-waterpigscouk-aaronpareckicom-and--62-24908.html²
enclosure: indieweb
links to: indieweb
enclosure: xkcd
links to: xkcd
tagged: concept

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

The
date: 2023-04-19T22:24:37-04:00
type: text/html; charset=UTF-8

auto-linked-hashtags-federated
date: 2023-04-19T22:24:38-04:00
type: text/html; charset=UTF-8

federationh-entry
date: 2023-04-19T22:24:39-04:00
type: text/html; charset=UTF-8

h-entryPingback
date: 2023-04-19T22:24:40-04:00
type: text/html; charset=UTF-8

Pingbackreply
date: 2023-04-19T22:24:40-04:00
type: text/html; charset=UTF-8

replyReferences¹
date: 2023-04-19T22:24:41-04:00
type: text/html; charset=UTF-8

indieweb
date: 2023-04-19T22:24:45-04:00
type: text/html; charset=UTF-8

xkcd
date: 2023-04-19T22:24:48-04:00
type: text/html; charset=UTF-8

btconf-personal-url-fediverse-feed
type: item
type: MicroblogPost
title: : @fredrocha.net (@john_fisherman@mastodon.social) saw your post (https://mastodon.social/@john_fisherman/110224246899618915) from the #IndieWeb stream. Beautiful photos on your site! #btconf was great wasn’t it?My personal URL is https://tantek.com/ and my #fediverse @ is @tantek.com. My Atom feed file is auto-discoverable by feed readers from my home page.Feeding (so to speak) two discovery birds with one stonefruit¹.Your personal website can be your fediverse address², each providing seamless discovery for the other.As web developers we should be building & developing our personal sites to exemplify the latest & greatest of such practices, including using Mastodon/ActivityPub as yet another distribution mechanism (ala POSSE) for your existing personal websites rather than a separate profile/stream.Discussed this with @nebu@mastodon.social and @kadirtopal@mastodon.social just after the last talk @beyondtellerrand.com (@btconf@mastodon.social @btconf) yesterday, fitting conference closing thoughts complementing the heartfelt opening talk by @localghost.dev (https://sophie.omg.lol/ @sophie@social.lol)³.GlossaryActivityPub https://indieweb.org/ActivityPubfeed file https://indieweb.org/feed_filePOSSE https://indieweb.org/POSSEReferences¹ https://tantek.com/2020/147/t2/replace-violent-metaphors² https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indieweb³ https://tantek.com/2023/107/t1/beyond-tellerand-talk-love-personal-website
link: https://status.blaise.ca/notice/116062
description: 's status on Wednesday, 19-Apr-2023 04:22:00 EDT
encoded: @fredrocha.net (@john_fisherman@mastodon.social) saw your post (https://mastodon.social/@john_fisherman/110224246899618915) from the #IndieWeb stream. Beautiful photos on your site! #btconf was great wasn’t it? My personal URL is https://tantek.com/ and my #fediverse @ is @tantek.com. My Atom feed file is auto-discoverable by feed readers from my home page. Feeding (so to speak) two discovery birds with one stonefruit¹. Your personal website can be your fediverse address², each providing seamless discovery for the other. As web developers we should be building & developing our personal sites to exemplify the latest & greatest of such practices, including using Mastodon/ActivityPub as yet another distribution mechanism (ala POSSE) for your existing personal websites rather than a separate profile/stream. Discussed this with @nebu@mastodon.social and @kadirtopal@mastodon.social just after the last talk @beyondtellerrand.com (@btconf@mastodon.social @btconf) yesterday, fitting conference closing thoughts complementing the heartfelt opening talk by @localghost.dev (https://sophie.omg.lol/ @sophie@social.lol)³. Glossary ActivityPub https://indieweb.org/ActivityPub feed file https://indieweb.org/feed_file POSSE https://indieweb.org/POSSE References ¹ https://tantek.com/2020/147/t2/replace-violent-metaphors ² https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indieweb ³ https://tantek.com/2023/107/t1/beyond-tellerand-talk-love-personal-website
date: 2023-04-19T04:22:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110168
enclosure: tantek.com
links to: tantek.com
enclosure: twittermigration-bridgyfed-mastodon-indieweb
links to: twittermigration-bridgyfed-mastodon-indieweb
enclosure: sophie.omg.lol
links to: sophie.omg.lol
enclosure: https://mastodon.social/@john_fisherman/110224246899618915
links to: https://mastodon.social/@john_fisherman/110224246899618915
enclosure: ActivityPubfeed
links to: ActivityPubfeed
enclosure: feed filePOSSE
links to: feed filePOSSE
enclosure: POSSEReferences¹
links to: POSSEReferences¹
enclosure: replace-violent-metaphors
links to: replace-violent-metaphors
enclosure: beyond-tellerand-talk-love-personal-website
links to: beyond-tellerand-talk-love-personal-website
tagged: concept

twittermigration-bridgyfed-mastodon-indieweb
date: 2022-12-02T15:58:37-05:00
type: text/html; charset=UTF-8

sophie.omg.lol
date: 2023-04-17T06:49:48-04:00
type: text/html; charset=UTF-8

https://mastodon.social/@john_fisherman/110224246899618915
date: 2023-04-19T10:23:51-04:00
type: text/html; charset=utf-8

ActivityPubfeed
date: 2023-04-19T10:23:52-04:00
type: text/html; charset=UTF-8

feed filePOSSE
date: 2023-04-19T10:23:53-04:00
type: text/html; charset=UTF-8

POSSEReferences¹
date: 2023-04-19T10:23:53-04:00
type: text/html; charset=UTF-8

replace-violent-metaphors
date: 2023-04-19T10:23:55-04:00
type: text/html; charset=UTF-8

beyond-tellerand-talk-love-personal-website
date: 2023-04-19T10:23:56-04:00
type: text/html; charset=UTF-8

concept
type: Tag
label: btconf

t1
type: item
type: MicroblogPost
title: : @fredrocha.net (@john_fisherman@mastodon.social) saw your post (https://mastodon.social/@john_fisherman/110224246899618915) from the #IndieWeb stream. Beautiful photos on your site! #btconf was great wasn’t it?My personal URL is https://tantek.com/ and my #fediverse @ is @tantek.com. My Atom feed file is auto-discoverable by feed readers from my home page.Feeding (so to speak) two discovery birds with one stonefruit¹.Your personal website can be your fediverse address², each providing seamless discovery for the other.As web developers we should be building & developing our personal sites to exemplify the latest & greatest of such practices, including using Mastodon/ActivityPub as yet another distribution mechanism (ala POSSE) for your existing personal websites rather than a separate profile/stream.Discussed this with @nebu@mastodon.social and @kadirtopal@mastodon.social just after the last talk @beyondtellerrand.com (@btconf@mastodon.social @btconf) yesterday, fitting conference closing thoughts complementing the heartfelt opening talk by @localghost.dev (https://sophie.omg.lol/ @sophie@social.lol)³.GlossaryActivityPub https://indieweb.org/ActivityPubfeed file https://indieweb.org/feed_filePOSSE https://indieweb.org/POSSEReferences¹ https://tantek.com/2020/147/t2/replace-violent-metaphors² https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indieweb³ https://tantek.com/2023/107/t1/beyond-tellerand-talk-love-personal-website
link: https://status.blaise.ca/notice/116060
description: 's status on Wednesday, 19-Apr-2023 04:22:00 EDT
encoded: @fredrocha.net (@john_fisherman@mastodon.social) saw your post (https://mastodon.social/@john_fisherman/110224246899618915) from the #IndieWeb stream. Beautiful photos on your site! #btconf was great wasn’t it? My personal URL is https://tantek.com/ and my #fediverse @ is @tantek.com. My Atom feed file is auto-discoverable by feed readers from my home page. Feeding (so to speak) two discovery birds with one stonefruit¹. Your personal website can be your fediverse address², each providing seamless discovery for the other. As web developers we should be building & developing our personal sites to exemplify the latest & greatest of such practices, including using Mastodon/ActivityPub as yet another distribution mechanism (ala POSSE) for your existing personal websites rather than a separate profile/stream. Discussed this with @nebu@mastodon.social and @kadirtopal@mastodon.social just after the last talk @beyondtellerrand.com (@btconf@mastodon.social @btconf) yesterday, fitting conference closing thoughts complementing the heartfelt opening talk by @localghost.dev (https://sophie.omg.lol/ @sophie@social.lol)³. Glossary ActivityPub https://indieweb.org/ActivityPub feed file https://indieweb.org/feed_file POSSE https://indieweb.org/POSSE References ¹ https://tantek.com/2020/147/t2/replace-violent-metaphors ² https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indieweb ³ https://tantek.com/2023/107/t1/beyond-tellerand-talk-love-personal-website
date: 2023-04-19T04:22:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110166
enclosure: tantek.com
links to: tantek.com
enclosure: twittermigration-bridgyfed-mastodon-indieweb
links to: twittermigration-bridgyfed-mastodon-indieweb
enclosure: sophie.omg.lol
links to: sophie.omg.lol
enclosure: https://mastodon.social/@john_fisherman/110224246899618915
links to: https://mastodon.social/@john_fisherman/110224246899618915
enclosure: ActivityPubfeed
links to: ActivityPubfeed
enclosure: feed filePOSSE
links to: feed filePOSSE
enclosure: POSSEReferences¹
links to: POSSEReferences¹
enclosure: replace-violent-metaphors
links to: replace-violent-metaphors
enclosure: beyond-tellerand-talk-love-personal-website
links to: beyond-tellerand-talk-love-personal-website
tagged: concept

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

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

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
enclosure: twittermigration-bridgyfed-mastodon-indieweb
links to: twittermigration-bridgyfed-mastodon-indieweb
enclosure: fed.brid.gy
links to: fed.brid.gy
enclosure: MastodonSeveral
links to: MastodonSeveral
enclosure: dev¹
links to: dev¹
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⁵
tagged: concept

dev¹
date: 2023-03-22T11:42:07-04:00
length: 169
type: text/html

five-years-ago-w3c-social-web
type: item
type: MicroblogPost
title: : Five years ago last Monday, the @W3C Social Web Working Group officially closed¹.Operating for less than four years, it standardized several foundations of the #fediverse & #IndieWeb:#Webmention#Micropub#ActivityStreams2#ActivityPubEach of these has numerous interoperable implementations which are in active use by anywhere from thousands to millions of users.Two additional specifications also had several implementations as of the time of their publication as a W3C Recommendations (which you can find from the Implementation Report linked near the top of each spec). However today they’re both fairly invisible "plumbing" (as most specs should be) or they haven’t picked up widespread use like the others:#LinkedDataNotifications (LDN)#WebSubTo be fair, LDN was only one building block in what eventually became SoLiD², the basis of Tim Berners–Lee’s startup Inrupt.However, in the post Elon-acquisition of Twitter and subsequent Twexodus, as Anil Dash noted³, “nobody ran to the ’web3’ platforms”, and nobody ran to SoLiD either.The other spec, WebSub, was roughly interoperably implemented as PubSubHubbub before it was brought to the Social Web Working Group. Yet despite that implementation experience, a more rigorous specification that fixed a lot of bugs, and a test suite⁴, WebSub’s adoption hasn’t really noticeably grown since. Existing implementations & services are still functioning though. My own blog supports WebSub notifications for example, for anyone that wants to receive/read my posts in real time.One of the biggest challenges the Social Web Working Group faced was with so many approaches being brought to the group, which approach should we choose?As one of the co-chairs of the group, with the other co-chairs, and our staff contacts over time, we realized that if we as chairs & facilitators tried to pick any one approach, we would almost certainly alienate and lose more than half of the working group who had already built or were actively interested in developing …
link: https://status.blaise.ca/notice/116020
description: 's status on Monday, 20-Feb-2023 22:16:00 EST
encoded: Five years ago last Monday, the @W3C Social Web Working Group officially closed¹. Operating for less than four years, it standardized several foundations of the #fediverse & #IndieWeb: #Webmention #Micropub #ActivityStreams2 #ActivityPub Each of these has numerous interoperable implementations which are in active use by anywhere from thousands to millions of users. Two additional specifications also had several implementations as of the time of their publication as a W3C Recommendations (which you can find from the Implementation Report linked near the top of each spec). However today they’re both fairly invisible "plumbing" (as most specs should be) or they haven’t picked up widespread use like the others: #LinkedDataNotifications (LDN) #WebSub To be fair, LDN was only one building block in what eventually became SoLiD², the basis of Tim Berners–Lee’s startup Inrupt. However, in the post Elon-acquisition of Twitter and subsequent Twexodus, as Anil Dash noted³, “nobody ran to the ’web3’ platforms”, and nobody ran to SoLiD either. The other spec, WebSub, was roughly interoperably implemented as PubSubHubbub before it was brought to the Social Web Working Group. Yet despite that implementation experience, a more rigorous specification that fixed a lot of bugs, and a test suite⁴, WebSub’s adoption hasn’t really noticeably grown since. Existing implementations & services are still functioning though. My own blog supports WebSub notifications for example, for anyone that wants to receive/read my posts in real time. One of the biggest challenges the Social Web Working Group faced was with so many approaches being brought to the group, which approach should we choose? As one of the co-chairs of the group, with the other co-chairs, and our staff contacts over time, we realized that if we as chairs & facilitators tried to pick any one approach, we would almost certainly alienate and lose more than half of the working group who had already built or were actively interested in…
date: 2023-02-20T22:16:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110143
enclosure: activitypub
links to: activitypub
enclosure: bridgy-indieweb-posse-backfeed
links to: bridgy-indieweb-posse-backfeed
enclosure: use what you make
links to: use what you make
enclosure: devIf
links to: devIf
enclosure: Socialwg
links to: Socialwg
enclosure: And
links to: And
enclosure: nineteen-years-microformats
links to: nineteen-years-microformats
enclosure: activitystreams-core
links to: activitystreams-core
enclosure: Linked
links to: Linked
enclosure: Micropub
links to: Micropub
enclosure: Webmention
links to: Webmention
enclosure: WebSub
links to: WebSub
enclosure: References:¹
links to: References:¹
enclosure: Socialwg²
links to: Socialwg²
enclosure: solid³
links to: solid³
enclosure: 109299991009836007⁴
links to: 109299991009836007⁴
enclosure: https://websub.rocks/⁵
links to: https://websub.rocks/⁵
enclosure: History⁶
links to: History⁶
enclosure: plurality⁸
links to: plurality⁸
tagged: concept

activitypub
date: 2017-04-14T08:55:31-04:00
length: 171119
type: text/html; charset=utf-8

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

use what you make
date: 2023-01-22T19:43:21-05:00
type: text/html; charset=UTF-8

devIf
date: 2023-02-16T20:15:28-05:00
length: 169
type: text/html

Socialwg
date: 2023-02-21T04:41:05-05:00
type: text/html; charset=UTF-8

And
date: 2023-02-21T04:41:05-05:00
length: 169
type: text/html

activitystreams-core
date: 2023-02-21T04:41:07-05:00
type: text/html; charset=utf-8

Linked
date: 2023-02-21T04:41:07-05:00
length: 6831
type: text/html;charset=utf-8

Micropub
date: 2023-02-21T04:41:08-05:00
length: 6831
type: text/html;charset=utf-8

Webmention
date: 2023-02-21T04:41:08-05:00
length: 169
type: text/html

WebSub
date: 2023-02-21T04:41:09-05:00
type: text/html; charset=UTF-8

References:¹
date: 2023-02-21T04:41:09-05:00
length: 6831
type: text/html;charset=utf-8

Socialwg²
date: 2023-02-21T04:41:09-05:00
type: text/html; charset=UTF-8

solid³
date: 2023-02-21T04:41:10-05:00
type: text/html; charset=UTF-8

109299991009836007⁴
date: 2023-02-21T04:41:11-05:00
type: text/html; charset=utf-8

https://websub.rocks/⁵
date: 2023-02-21T04:41:16-05:00
type: text/html; charset=UTF-8

History⁶
date: 2023-02-21T04:41:17-05:00
type: text/html; charset=UTF-8

plurality⁸
date: 2023-02-21T04:41:19-05:00
type: text/html; charset=UTF-8

publish-indieweb-decide-distribute
date: 2023-01-17T19:26:37-05:00
type: text/html; charset=UTF-8

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

t4*
date: 2023-01-19T21:39:51-05:00
type: text/html; charset=UTF-8

in-reply-to
date: 2023-01-19T21:40:12-05:00
type: text/html; charset=UTF-8

multiple-reply
date: 2023-01-19T21:40:13-05:00
type: text/html; charset=UTF-8

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
tagged: concept

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

bridgyfed-followers-fediverse-responses
type: item
type: MicroblogPost
title: : Two days ago my #BridgyFed followers crossed 8-bits:https://fed.brid.gy/user/tantek.comSigns of #TwitterMigration: my prev post had ~2x more #fediverse responses than Twitter, a ~500:1 difference per follower (having ~250x more Twitter followers).Many possible factors. Mastodon users see more from their followings. Twitter accounts could be mostly bots or abandoned. Recent posts are technical, maybe Mastodon users are more technical. Tech friends migrated first. Or hashtagging #fediverse.
link: https://status.blaise.ca/notice/115956
description: 's status on Tuesday, 06-Dec-2022 16:48:00 EST
encoded: Two days ago my #BridgyFed followers crossed 8-bits: https://fed.brid.gy/user/tantek.com Signs of #TwitterMigration: my prev post had ~2x more #fediverse responses than Twitter, a ~500:1 difference per follower (having ~250x more Twitter followers). Many possible factors. Mastodon users see more from their followings. Twitter accounts could be mostly bots or abandoned. Recent posts are technical, maybe Mastodon users are more technical. Tech friends migrated first. Or hashtagging #fediverse.
date: 2022-12-06T16:48:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110094
tagged: concept

concept
type: Tag
label: twittermigration

indieweb-fediverse
type: item
type: MicroblogPost
title: : #indieweb 🤝 #fediverse✨ https://werd.io/2022/the-fediverse-and-the-indieweb (@benwerd)✨ https://catgirlin.space/posts/moving-to-the-fediverse-and-indieweb/✨ https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indiewebPreviously: https://twitter.com/t/status/1586264352453427201, https://twitter.com/t/status/956436348361158658 #TwitterMigration #ActivityPub #SocialWeb #OpenStandards #OpenWeb
link: https://status.blaise.ca/notice/115953
description: 's status on Friday, 02-Dec-2022 15:01:00 EST
encoded: #indieweb 🤝 #fediverse ✨ https://werd.io/2022/the-fediverse-and-the-indieweb (@benwerd) ✨ https://catgirlin.space/posts/moving-to-the-fediverse-and-indieweb/ ✨ https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indieweb Previously: https://twitter.com/t/status/1586264352453427201, https://twitter.com/t/status/956436348361158658 #TwitterMigration #ActivityPub #SocialWeb #OpenStandards #OpenWeb
date: 2022-12-02T15:01:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110092
tagged: concept

indieweb-gift-calendar
type: item
type: MicroblogPost
title: : #indieweb 🤝 #fediverse✨ https://werd.io/2022/the-fediverse-and-the-indieweb (@benwerd)✨ https://catgirlin.space/posts/moving-to-the-fediverse-and-indieweb/✨ https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indiewebPreviously: https://twitter.com/t/status/1586264352453427201, https://twitter.com/t/status/956436348361158658 #TwitterMigration #ActivityPub #SocialWeb #OpenStandards #OpenWeb
link: https://status.blaise.ca/notice/115950
description: 's status on Friday, 02-Dec-2022 15:01:00 EST
encoded: #indieweb 🤝 #fediverse ✨ https://werd.io/2022/the-fediverse-and-the-indieweb (@benwerd) ✨ https://catgirlin.space/posts/moving-to-the-fediverse-and-indieweb/ ✨ https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indieweb Previously: https://twitter.com/t/status/1586264352453427201, https://twitter.com/t/status/956436348361158658 #TwitterMigration #ActivityPub #SocialWeb #OpenStandards #OpenWeb
date: 2022-12-02T15:01:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110089
enclosure: the-fediverse-and-the-indieweb
links to: the-fediverse-and-the-indieweb
enclosure: moving-to-the-fediverse-and-indieweb
links to: moving-to-the-fediverse-and-indieweb
enclosure: twittermigration-bridgyfed-mastodon-indieweb
links to: twittermigration-bridgyfed-mastodon-indieweb
enclosure: https://twitter.com/t/status/1586264352453427201
links to: https://twitter.com/t/status/1586264352453427201
enclosure: https://twitter.com/t/status/956436348361158658
links to: https://twitter.com/t/status/956436348361158658
tagged: concept

the-fediverse-and-the-indieweb
date: 2022-12-02T15:58:36-05:00
type: text/html;charset=UTF-8

moving-to-the-fediverse-and-indieweb
date: 2022-12-02T15:58:36-05:00
length: 11719
type: text/html; charset=UTF-8

https://twitter.com/t/status/1586264352453427201
date: 2022-12-02T15:58:38-05:00
type: text/html; charset=utf-8

https://twitter.com/t/status/956436348361158658
date: 2022-12-02T15:58:40-05:00
type: text/html; charset=utf-8

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

https://mastodon.xyz/users/douginamug/statuses/101318276905189251
type: item
type: MicroblogPost
title: douginamug: TODAY (28th) activist itinerary for #35c3 ✊ 🌍 🔥 - 13:00, #ExtinctionRebellion meetup @ Lect. rm. M1- 14:00, #YunoHost workshop @ Lect. rm. M1- 14:00, #Fediverse meetup @ Lect. rm. M3- 17:00, #Briar 'party' @ Curry Club Augsburg Assembly- 19:30, Intro to #Anarchy @ Lect. rm. M3Maybe see you there 🙂
link: https://status.blaise.ca/notice/111139
description: douginamug's status on Friday, 28-Dec-2018 05:50:15 EST
encoded: TODAY (28th) activist itinerary for #35c3 ✊ 🌍 🔥 - 13:00, #ExtinctionRebellion meetup @ Lect. rm. M1 - 14:00, #YunoHost workshop @ Lect. rm. M1 - 14:00, #Fediverse meetup @ Lect. rm. M3 - 17:00, #Briar 'party' @ Curry Club Augsburg Assembly - 19:30, Intro to #Anarchy @ Lect. rm. M3 Maybe see you there 🙂
date: 2018-12-28T05:50:15-05:00
creator: Doug Webb
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/106102
tagged: concept

concept
type: Tag
label: 35c3

concept
type: Tag
label: anarchy

concept
type: Tag
label: briar

concept
type: Tag
label: extinctionrebellion

concept
type: Tag
label: yunohost

https://scholar.social/users/SebastianS/statuses/101238942703054131
type: item
type: MicroblogPost
title: sebastians: I'm considering running a scholar/academic/research/education oriented #peertube instance, wondering how much interest there is in it on this bit of the #fediverse?It seems very doable, but bit steep in investment cost (hardware). I think it should be doable with a running cost of ca 100-150,- per month for hosting and hardware. Assuming sponsored/donated admin-time.
link: https://status.blaise.ca/notice/111023
description: sebastians's status on Friday, 14-Dec-2018 05:34:31 EST
encoded: I'm considering running a scholar/academic/research/education oriented #peertube instance, wondering how much interest there is in it on this bit of the #fediverse? It seems very doable, but bit steep in investment cost (hardware). I think it should be doable with a running cost of ca 100-150,- per month for hosting and hardware. Assuming sponsored/donated admin-time.
date: 2018-12-14T05:34:31-05:00
creator: Sebastian
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/106019
tagged: concept

concept
type: Tag
label: peertube

https://organizing.social/users/slackz/statuses/101070461185622767
type: item
type: MicroblogPost
title: slackz: Hey all, I wanna open up this invite again. I really want to grow organizing.social. This instance is a space for community organizers and we welcome folks trying to bring that work into a proper social media space.The #fediverse is vast and has been amazing, but #OrgSoc is way too small :PHere's an invite link:https://organizing.social/invite/tnBbPe2XWe wanna encourage a diversity of voices and joining this instance will mean you are a part of deciding how it operates.#DirectDemocracy#ComradesWelcome
link: https://status.blaise.ca/notice/111526
description: slackz's status on Wednesday, 14-Nov-2018 11:27:27 EST
encoded: Hey all, I wanna open up this invite again. I really want to grow organizing.social. This instance is a space for community organizers and we welcome folks trying to bring that work into a proper social media space. The #fediverse is vast and has been amazing, but #OrgSoc is way too small :P Here's an invite link: https://organizing.social/invite/tnBbPe2X We wanna encourage a diversity of voices and joining this instance will mean you are a part of deciding how it operates. #DirectDemocracy #ComradesWelcome
date: 2018-11-14T11:27:27-05:00
creator: slackz
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/106369
tagged: concept

concept
type: Tag
label: comradeswelcome

concept
type: Tag
label: directdemocracy

concept
type: Tag
label: orgsoc

objectType=note
type: item
type: MicroblogPost
title: bobjonkman: OK, that's definitely the best thing I've seen in the #Fediverse yet! Listening to the @hardmous archive, and just letting the images autoscroll in a full-screen browser... https://anonradio.net/archive/201811032200_hardmous.mp3
link: https://status.blaise.ca/notice/110676
description: bobjonkman's status on Sunday, 04-Nov-2018 00:26:26 EDT
encoded: OK, that's definitely the best thing I've seen in the #Fediverse yet! Listening to the @hardmous archive, and just letting the images autoscroll in a full-screen browser... https://anonradio.net/archive/201811032200_hardmous.mp3
date: 2018-11-04T00:26:26-04:00
creator: Bob Jonkman
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
reply of: https://status.blaise.ca/notice/110675
has discussion: https://status.blaise.ca/conversation/105785
tagged: concept

201811032200 hardmous.mp3
date: 2018-11-04T01:00:41-04:00
length: 175556307
type: audio/mpeg

https://mastodon.social/users/LiamErven/statuses/100549775260499384
type: item
type: MicroblogPost
title: liamerven: Hey #Fediverse. When you post pictures, please please please with puppies on top fill in that description box for the visually impaired. You will be helping us out tremendously. We want to enjoy your pictures as much as others do. You don't have to write a novel, but just fill in some details.Thanks with much love:A Blind Dude
link: https://status.blaise.ca/notice/109966
description: liamerven's status on Tuesday, 14-Aug-2018 13:30:11 EDT
encoded: Hey #Fediverse. When you post pictures, please please please with puppies on top fill in that description box for the visually impaired. You will be helping us out tremendously. We want to enjoy your pictures as much as others do. You don't have to write a novel, but just fill in some details. Thanks with much love: A Blind Dude
date: 2018-08-14T13:30:11-04:00
creator: Liam Erven
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/105266
tagged: concept

kosinus: You can now challenge someone to game of #chess over toots! https://castling.club/ 💪It's actually a standalone server in the #fediverse, implementing #activitypub all by itself. 😃
type: item
type: MicroblogPost
link: https://status.blaise.ca/notice/109850
description: kosinus's status on Saturday, 04-Aug-2018 14:13:42 EDT
encoded: You can now challenge someone to game of #chess over toots! https://castling.club/ 💪 It's actually a standalone server in the #fediverse, implementing #activitypub all by itself. 😃
date: 2018-08-04T14:13:42-04:00
creator: Stéphan Kochen
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/105182
tagged: concept

9c37ea59ccc5dc24.png
date: 2018-08-05T20:38:47-04:00
length: 154251
type: image/png

concept
type: Tag
label: chess

fuuko: Good afternoon #sdf, #tildeverse and #fediverse! Watching Trix play Dark Souls 3! Come get in here: https://www.twitch.tv/bagotrixhttps://www.twitch.tv/bagotrix
type: item
type: MicroblogPost
link: https://status.blaise.ca/notice/109732
description: fuuko's status on Friday, 27-Jul-2018 13:15:12 EDT
encoded: Good afternoon #sdf, #tildeverse and #fediverse! Watching Trix play Dark Souls 3! Come get in here: https://www.twitch.tv/bagotrixhttps://www.twitch.tv/bagotrix
date: 2018-07-27T13:15:12-04:00
creator: Zed Ex Fuuma
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/105074
enclosure: bagotrix
links to: bagotrix
tagged: concept

bagotrix
date: 2018-07-27T13:14:30-04:00
length: 33388
type: text/html

concept
type: Tag
label: sdf

concept
type: Tag
label: tildeverse

https://mastodon.sdf.org/users/fuuko/statuses/100442446688913495
type: item
type: MicroblogPost
title: fuuko: Good afternoon #sdf, #tildeverse and #fediverse! Today I wonder about how we can make self-hosting easy for the average person. Something they could learn in 5 min with a cheat sheet. Of course, it depends on what you want to self-host, and it also opens a can of security worms. Maybe peer-to-peer solutions are the way to go for now? Stuff like RetroShare, ZeroNet, I2P and the like are good examples I guess, but are there other good applications out there not listed on wikipedia?
link: https://status.blaise.ca/notice/109709
description: fuuko's status on Thursday, 26-Jul-2018 14:35:07 EDT
encoded: Good afternoon #sdf, #tildeverse and #fediverse! Today I wonder about how we can make self-hosting easy for the average person. Something they could learn in 5 min with a cheat sheet. Of course, it depends on what you want to self-host, and it also opens a can of security worms. Maybe peer-to-peer solutions are the way to go for now? Stuff like RetroShare, ZeroNet, I2P and the like are good examples I guess, but are there other good applications out there not listed on wikipedia?
date: 2018-07-26T14:35:07-04:00
creator: Zed Ex Fuuma
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/105060
tagged: concept

Zed Ex Fuuma
type: Agent
nick: fuuko
holds account: acct