status.blaise.ca
type: Site
name: stadeus
space of: 100posts

100posts
type: Container
type: channel
description: Updates tagged with 100posts on stadeus!
licence: http://creativecommons.org/licenses/by/3.0/
items: night-before-indiewebcamp-berlin
items: october-blogging-challenges
items: movie-club-tomorrowland-submissions
items: indieweb-movie-club-tomorrowland
items: what-are-words-for-blogging
items: three-steps-indieweb-cybersecurity
items: seek-2024-year-in-review
items: eight-years-webmention
items: micro-one-onramp-open-social-web
items: lastfm-year-in-review-playback24
items: indieweb-third-place-community
items: strava-year-in-sport-how-to-get-info-save
items: first-new-year-review-prior
items: 15-years-notes-my-site-first
items: why-what-how-to-post
items: indiewebcamp-berlin-2024-day-1
items: simple-embeds
items: fediverse-unfollow-bridgyfed-bug
items: metaphors-constructive-cooperative-joyful
items: october-blogtober-indieweb
items: w3c-link-checker-before-federating
items: adventures-indieweb-activitypub-bridgy-fed
items: read-write-suggest-edit-update-web
items: read-write-suggest-edit-web
items: indiewebcamp-portland-10
items: indiewebcamp-portland
items: indiewebcamp-auto-link
items: indiewebcamp-auto-linking
items: people-over-protocols-platforms
items: years-posse-microformats-adoption
items: minimum-interesting-service-worker
items: created-at-indiewebcamp-brighton
items: updated-auto-linking-mention-use-cases
items: indieweb-major-update-design
items: the-ephemeral-web
items: indiewebcamp-brighton-tickets-available
items: greshams-law-developers-users-jargon
items: gresham-law-developers-users-jargon
items: earthquake-sanfrancisco-shifted
items: indieweb-ideals-systems-swappable
items: indieweb-for-everyone-internet-of-people
items: should-public-posts-flow-across-sites
items: indiewebcamp-brighton-planned
items: 2023-indieweb-gift-calendar-numbers
items: restarting-100days-indieweb-gift-calendar

night-before-indiewebcamp-berlin
type: item
type: MicroblogPost
title: : 🎃 Night before IndieWebCamp Berlin! Participants are (hopefully, mostly) all tucked into their beds, dreaming of what wonderful things they can brainstorm for their personal sites Saturday, and #HackTheirPlanet on Sunday.Want to keep up with #IndieWebCamp #Berlin participants?Follow their feeds and a Bluesky starter pack (happy to include more for any other formats, protocols, or platforms)* https://indieweb.org/2025/Berlin#Feeds_Lists_Starter_Packs_Oh_MyWe’ll add more as folks sign-in at the camp!This is post 14 of #100PostsOfIndieWeb. #100Posts #IndieWeb #Blogtober #IndieWebMovieClub #HackThePlanet 📟← https://tantek.com/2025/303/t1/october-blogging-challenges→ 🔮
link: https://status.blaise.ca/notice/116287
description: 's status on Friday, 31-Oct-2025 18:14:00 EDT
encoded: 🎃 Night before IndieWebCamp Berlin! Participants are (hopefully, mostly) all tucked into their beds, dreaming of what wonderful things they can brainstorm for their personal sites Saturday, and #HackTheirPlanet on Sunday. Want to keep up with #IndieWebCamp #Berlin participants? Follow their feeds and a Bluesky starter pack (happy to include more for any other formats, protocols, or platforms) * https://indieweb.org/2025/Berlin#Feeds_Lists_Starter_Packs_Oh_My We’ll add more as folks sign-in at the camp! This is post 14 of #100PostsOfIndieWeb. #100Posts #IndieWeb #Blogtober #IndieWebMovieClub #HackThePlanet 📟 ← https://tantek.com/2025/303/t1/october-blogging-challenges → 🔮
date: 2025-10-31T18:14:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110353
enclosure: Feeds Lists Starter Packs Oh MyWe
links to: Feeds Lists Starter Packs Oh MyWe
enclosure: october-blogging-challenges
links to: october-blogging-challenges
tagged: concept

Feeds Lists Starter Packs Oh MyWe
date: 2025-10-31T19:11:55-04:00
type: text/html; charset=UTF-8

october-blogging-challenges
date: 2025-10-31T19:11:57-04:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : October is almost over! For all us procrastinators, still time to write a post or two to participate in #October blogging challenges like:#Blogtober#IndieWebMovieClub on #Hackers#Inktober#Mathober#WeirdWebOctober+ coding challenges:#Hacktoberfest — https://blog.holopin.io/posts/hacktoberfest-2025Many more at:* https://indieweb.org/October* https://indieweb.org/blog_carnival🎃 And tomorrow is #Halloween so consider a holiday theme for your site as well! See #IndieWeb examples for inspiration:* https://indieweb.org/HalloweenLast but not least, perhaps we’ll see some of you at #IndieWebCamp Berlin this weekend!* https://indieweb.org/2025/BerlinThis is post 13 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2025/182/t1/movie-club-tomorrowland-submissions→ 🔮
link: https://status.blaise.ca/notice/116286
description: 's status on Thursday, 30-Oct-2025 19:27:00 EDT
encoded: October is almost over! For all us procrastinators, still time to write a post or two to participate in #October blogging challenges like: #Blogtober #IndieWebMovieClub on #Hackers #Inktober #Mathober #WeirdWebOctober + coding challenges: #Hacktoberfest — https://blog.holopin.io/posts/hacktoberfest-2025 Many more at: * https://indieweb.org/October * https://indieweb.org/blog_carnival 🎃 And tomorrow is #Halloween so consider a holiday theme for your site as well! See #IndieWeb examples for inspiration: * https://indieweb.org/Halloween Last but not least, perhaps we’ll see some of you at #IndieWebCamp Berlin this weekend! * https://indieweb.org/2025/Berlin This is post 13 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2025/182/t1/movie-club-tomorrowland-submissions → 🔮
date: 2025-10-30T19:27:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110352
enclosure: hacktoberfest-2025Many
links to: hacktoberfest-2025Many
enclosure: October*
links to: October*
enclosure: blog carnival
links to: blog carnival
enclosure: HalloweenLast
links to: HalloweenLast
enclosure: BerlinThis
links to: BerlinThis
enclosure: movie-club-tomorrowland-submissions
links to: movie-club-tomorrowland-submissions
tagged: concept

concept
type: Tag
label: 100posts

concept
type: Tag
label: 100postsofindieweb

concept
type: Tag
label: berlin

concept
type: Tag
label: blogtober

concept
type: Tag
label: hacktheirplanet

concept
type: Tag
label: hacktheplanet

concept
type: Tag
label: indieweb

concept
type: Tag
label: indiewebcamp

concept
type: Tag
label: indiewebmovieclub

hacktoberfest-2025Many
date: 2025-10-30T22:42:52-04:00
length: 2656
type: text/html; charset=utf-8

October*
date: 2025-10-30T22:42:53-04:00
type: text/html; charset=UTF-8

blog carnival
date: 2025-10-30T22:42:54-04:00
type: text/html; charset=UTF-8

HalloweenLast
date: 2025-10-30T22:42:54-04:00
type: text/html; charset=UTF-8

BerlinThis
date: 2025-10-30T22:42:55-04:00
type: text/html; charset=UTF-8

movie-club-tomorrowland-submissions
date: 2025-10-30T22:42:56-04:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : I really enjoyed the IndieWeb Movie Club May 2025 submissions about the film “Tomorrowland”. Ordered from earliest to most recent:* Paolo Feadin: https://www.feadin.eu/en/posts/tomorrowland* Thomas Vander Wal: https://vanderwal.net/random/entrysel.php?blog=2119* gRegor Morrill: https://gregorlove.com/2025/05/tomorrowland/* Benji: https://www.benji.dog/watched/1748757918-tomorrowland-2015/* James: https://jamesg.blog/2025/07/01/tomorrowland-indieweb-movie-clubAs promised in my welcome post, here are my past posts regarding or related to Tomorrowland the film, Before Tomorrowland the book, and the themes and messages therein:* https://tantek.com/2016/042/t1/the-problem-to-solve-negative-news* https://tantek.com/2016/145/b1/tomorrowland-misjudging-by-name-association* https://tantek.com/2016/150/b1/tomorrowland-change-perspective-flight-paris* https://tantek.com/2016/279/t2/finished-reading-before-tomorrowlandI rewatched the film in May, and had a mix of remembering my past impressions as well as forming new impressions in the context of 2025. A lot has changed in the past 10 years. Worth a separate blog post. Previously: https://tantek.com/2025/120/t1/indieweb-movie-club-tomorrowland#TomorrowlandFilm #BeforeTomorrowland #IndieWeb #IndieWebMovieClubThis is post 12 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2025/120/t1/indieweb-movie-club-tomorrowland→ 🔮
link: https://status.blaise.ca/notice/116275
description: 's status on Tuesday, 01-Jul-2025 20:41:00 EDT
encoded: I really enjoyed the IndieWeb Movie Club May 2025 submissions about the film “Tomorrowland”. Ordered from earliest to most recent: * Paolo Feadin: https://www.feadin.eu/en/posts/tomorrowland * Thomas Vander Wal: https://vanderwal.net/random/entrysel.php?blog=2119 * gRegor Morrill: https://gregorlove.com/2025/05/tomorrowland/ * Benji: https://www.benji.dog/watched/1748757918-tomorrowland-2015/ * James: https://jamesg.blog/2025/07/01/tomorrowland-indieweb-movie-club As promised in my welcome post, here are my past posts regarding or related to Tomorrowland the film, Before Tomorrowland the book, and the themes and messages therein: * https://tantek.com/2016/042/t1/the-problem-to-solve-negative-news * https://tantek.com/2016/145/b1/tomorrowland-misjudging-by-name-association * https://tantek.com/2016/150/b1/tomorrowland-change-perspective-flight-paris * https://tantek.com/2016/279/t2/finished-reading-before-tomorrowland I rewatched the film in May, and had a mix of remembering my past impressions as well as forming new impressions in the context of 2025. A lot has changed in the past 10 years. Worth a separate blog post. Previously: https://tantek.com/2025/120/t1/indieweb-movie-club-tomorrowland #TomorrowlandFilm #BeforeTomorrowland #IndieWeb #IndieWebMovieClub This is post 12 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2025/120/t1/indieweb-movie-club-tomorrowland → 🔮
date: 2025-07-01T20:41:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110342
enclosure: tomorrowland*
links to: tomorrowland*
enclosure: https://vanderwal.net/random/entrysel.php
links to: https://vanderwal.net/random/entrysel.php
enclosure: https://gregorlove.com/2025/05/tomorrowland/*
links to: https://gregorlove.com/2025/05/tomorrowland/*
enclosure: https://www.benji.dog/watched/1748757918-tomorrowland-2015/*
links to: https://www.benji.dog/watched/1748757918-tomorrowland-2015/*
enclosure: tomorrowland-indieweb-movie-clubAs
links to: tomorrowland-indieweb-movie-clubAs
enclosure: the-problem-to-solve-negative-news
links to: the-problem-to-solve-negative-news
enclosure: tomorrowland-misjudging-by-name-association
links to: tomorrowland-misjudging-by-name-association
enclosure: tomorrowland-change-perspective-flight-paris
links to: tomorrowland-change-perspective-flight-paris
enclosure: finished-reading-before-tomorrowland
links to: finished-reading-before-tomorrowland
enclosure: TomorrowlandFilm
links to: TomorrowlandFilm
enclosure: indieweb-movie-club-tomorrowland
links to: indieweb-movie-club-tomorrowland
tagged: concept

concept
type: Tag
label: hackers

concept
type: Tag
label: halloween

concept
type: Tag
label: october

tomorrowland*
date: 2025-07-01T23:20:26-04:00
type: text/html; charset=iso-8859-1

https://vanderwal.net/random/entrysel.php
date: 2025-07-01T23:20:27-04:00
type: text/html; charset=UTF-8

https://gregorlove.com/2025/05/tomorrowland/*
date: 2025-07-01T23:20:28-04:00
type: text/html; charset=utf-8

https://www.benji.dog/watched/1748757918-tomorrowland-2015/*
date: 2025-07-01T23:20:29-04:00
type: text/html; charset=utf-8

tomorrowland-indieweb-movie-clubAs
date: 2025-07-01T23:20:30-04:00
length: 24526
type: text/html; charset=utf-8

the-problem-to-solve-negative-news
date: 2025-07-01T23:20:31-04:00
type: text/html; charset=UTF-8

tomorrowland-misjudging-by-name-association
date: 2025-07-01T23:20:32-04:00
type: text/html; charset=UTF-8

tomorrowland-change-perspective-flight-paris
date: 2025-07-01T23:20:33-04:00
type: text/html; charset=UTF-8

finished-reading-before-tomorrowland
date: 2025-07-01T23:20:35-04:00
type: text/html; charset=UTF-8

TomorrowlandFilm
date: 2025-07-01T23:20:35-04:00
type: text/html; charset=UTF-8

indieweb-movie-club-tomorrowland
date: 2025-07-01T23:20:36-04:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : Welcome to the May 2025 edition of IndieWeb Movie Club!As your host for this month¹, I invite you to (re)watch the film “Tomorrowland” (https://movies.disney.com/tomorrowland), with an optional prequel book reading assignment!“Before Tomorrowland” (https://books.disney.com/book/before-tomorrowland/) was released about a month before the film, so it’s fine to read before watching.#Tomorrowland is available in various physical media formats, and via streaming on DisneyPlus². 130 minutes, rated PG.This month is the 10th anniversary of Tomorrowland’s release.The world was quite different in 2015.I had my own impressions of Tomorrowland when I first heard about it and then watched it much later (which I won’t link to yet to avoid spoilers or biasing your opinions). The film made such a strong impression on me that I held a group film viewing and discussion party in 2015!I’m curious how both first time viewers in 2025 and folks watching a second (or more) time think of Tomorrowland.If you would like to participate in this month’s IndieWeb Movie Club:* optional: read the prequel book* watch the film* blog a read³ (for the book), watch⁴, review⁵, or even a simple note⁶ post of your impressions, or some or all the above and link to this postIf you want your post(s) to be included in the May 2025 IndieWeb Movie Club roundup, notify me with a Webmention⁷ from your post, or drop a link in the IndieWeb chat discussion channel⁸ and @-mention me.Since this is an IndieWeb community activity, please both follow the Code of Conduct⁹, and also keep your post within the same rating (PG) as the movie. I may curate the roundup accordingly.Happy reading, watching, and dreaming!#TomorrowlandFilm #BeforeTomorrowland #IndieWeb #IndieWebMovieClubThis is post 11 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2025/077/t1/what-are-words-for-blogging→ 🔮References:¹ https://indieweb.org/IndieWeb_Movie_Club#2025² https://www.disneyplus.com/en-gb/browse/entity-3355a91d-addb-4c66-91a6-136325…
link: https://status.blaise.ca/notice/116268
description: 's status on Wednesday, 30-Apr-2025 21:03:00 EDT
encoded: Welcome to the May 2025 edition of IndieWeb Movie Club! As your host for this month¹, I invite you to (re)watch the film “Tomorrowland” (https://movies.disney.com/tomorrowland), with an optional prequel book reading assignment! “Before Tomorrowland” (https://books.disney.com/book/before-tomorrowland/) was released about a month before the film, so it’s fine to read before watching. #Tomorrowland is available in various physical media formats, and via streaming on DisneyPlus². 130 minutes, rated PG. This month is the 10th anniversary of Tomorrowland’s release. The world was quite different in 2015. I had my own impressions of Tomorrowland when I first heard about it and then watched it much later (which I won’t link to yet to avoid spoilers or biasing your opinions). The film made such a strong impression on me that I held a group film viewing and discussion party in 2015! I’m curious how both first time viewers in 2025 and folks watching a second (or more) time think of Tomorrowland. If you would like to participate in this month’s IndieWeb Movie Club: * optional: read the prequel book * watch the film * blog a read³ (for the book), watch⁴, review⁵, or even a simple note⁶ post of your impressions, or some or all the above and link to this post If you want your post(s) to be included in the May 2025 IndieWeb Movie Club roundup, notify me with a Webmention⁷ from your post, or drop a link in the IndieWeb chat discussion channel⁸ and @-mention me. Since this is an IndieWeb community activity, please both follow the Code of Conduct⁹, and also keep your post within the same rating (PG) as the movie. I may curate the roundup accordingly. Happy reading, watching, and dreaming! #TomorrowlandFilm #BeforeTomorrowland #IndieWeb #IndieWebMovieClub This is post 11 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2025/077/t1/what-are-words-for-blogging → 🔮 References: ¹ https://indieweb.org/IndieWeb_Movie_Club#2025 ² https://www.disneyplus.com/en-gb/browse/entity-3355a91d-ad…
date: 2025-04-30T21:03:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110335
enclosure: code-of-conduct
links to: code-of-conduct
enclosure: tomorrowland
links to: tomorrowland
enclosure: before-tomorrowland
links to: before-tomorrowland
enclosure: what-are-words-for-blogging
links to: what-are-words-for-blogging
enclosure: 2025²
links to: 2025²
links to: entity-3355a91d-addb-4c66-91a6-136325e6ecf7³
enclosure: read⁴
links to: read⁴
enclosure: watch⁵
links to: watch⁵
enclosure: review⁶
links to: review⁶
enclosure: note⁷
links to: note⁷
enclosure: Webmention⁸
links to: Webmention⁸
enclosure: indieweb⁹
links to: indieweb⁹
tagged: concept

concept
type: Tag
label: beforetomorrowland

concept
type: Tag
label: indiewebmovieclubthis

code-of-conduct
date: 2023-01-28T08:19:12-05:00
type: text/html; charset=UTF-8

tomorrowland
date: 2025-05-01T23:48:17-04:00
length: 383
type: text/html

before-tomorrowland
date: 2025-05-01T23:48:18-04:00
length: 282
type: text/html

what-are-words-for-blogging
date: 2025-05-01T23:48:20-04:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : “Tell me, what are words for?” They are for blogging!Earlier today during an informal espresso live stream in the #indieweb cafe, Spotify was playing an auto-generated daylist, something like “romantic 80s tuesday morning”, and the 1982 song “Words”¹ by the band Missing Persons came on.When we heard this lyric:🎶 What are words for when no one listens? 🎶I remarked half-jokingly in response:Words are for blogging, whether anyone is listening, reading, or not.Another participant noted that blogging sometimes feels like screaming into the void.I noted it doesn’t matter if anyone is reading (or listening), it’s fine to blog for an audience of one, yourself, even just to have something to refer to or reference in the future.When I write a post it’s often directed at only a small number of people, who may be part of a larger conversation. The point of publishing it publicly is to assert a level of confidence and credibility by the act of “putting it on the permanent record” (since nearly everything blogged is promptly indexed and archived.) with a permalink.The lyrics have some quite prescient bits, like this:“No one notices, I think I'll dye my hair blue Media overload bombarding you with action It’s getting near impossible to cause distraction”Written and sung more than forty years ago. Long before the web (or #socialWeb) was a thing.Rewriting the lyrics as a parody could be a fun project, e.g.:🎶 What are blogs for when no one reads them? 🎶some existing lyrics barely need any edits, like:“It’s like the feeling at the end of the page When you realize you don't know what you just read”perhaps an exercise for the reader for now.Previously: “Inbox Zero” (parody of The Fixx “Saved by Zero”²)* https://tantek.com/w/InboxZero (2009-01-29 https://twitter.com/t/status/1160324190)This is post 10 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2025/055/t1/three-steps-indieweb-cybersecurity→ 🔮Glossaryblog https://indieweb.org/blogblogging https://indieweb.org/bloggingpermalin…
link: https://status.blaise.ca/notice/116265
description: 's status on Tuesday, 18-Mar-2025 21:25:00 EDT
encoded: “Tell me, what are words for?” They are for blogging! Earlier today during an informal espresso live stream in the #indieweb cafe, Spotify was playing an auto-generated daylist, something like “romantic 80s tuesday morning”, and the 1982 song “Words”¹ by the band Missing Persons came on. When we heard this lyric: 🎶 What are words for when no one listens? 🎶 I remarked half-jokingly in response: Words are for blogging, whether anyone is listening, reading, or not. Another participant noted that blogging sometimes feels like screaming into the void. I noted it doesn’t matter if anyone is reading (or listening), it’s fine to blog for an audience of one, yourself, even just to have something to refer to or reference in the future. When I write a post it’s often directed at only a small number of people, who may be part of a larger conversation. The point of publishing it publicly is to assert a level of confidence and credibility by the act of “putting it on the permanent record” (since nearly everything blogged is promptly indexed and archived.) with a permalink. The lyrics have some quite prescient bits, like this: “No one notices, I think I'll dye my hair blue Media overload bombarding you with action It’s getting near impossible to cause distraction” Written and sung more than forty years ago. Long before the web (or #socialWeb) was a thing. Rewriting the lyrics as a parody could be a fun project, e.g.: 🎶 What are blogs for when no one reads them? 🎶 some existing lyrics barely need any edits, like: “It’s like the feeling at the end of the page When you realize you don't know what you just read” perhaps an exercise for the reader for now. Previously: “Inbox Zero” (parody of The Fixx “Saved by Zero”²) * https://tantek.com/w/InboxZero (2009-01-29 https://twitter.com/t/status/1160324190) This is post 10 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2025/055/t1/three-steps-indieweb-cybersecurity → 🔮 Glossary blog https://indieweb.org/blog blogging https://indiewe…
date: 2025-03-18T21:25:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110332
enclosure: blogblogging
links to: blogblogging
enclosure: InboxZero
links to: InboxZero
links to: 1160324190)This
enclosure: three-steps-indieweb-cybersecurity
links to: three-steps-indieweb-cybersecurity
enclosure: bloggingpermalink
links to: bloggingpermalink
enclosure: permalinkwhy
links to: permalinkwhy
enclosure: why postReferences¹
links to: why postReferences¹
enclosure: Words
links to: Words
enclosure: Saved+by+Zero
links to: Saved+by+Zero
tagged: concept

2025²
date: 2025-05-01T23:48:22-04:00
type: text/html; charset=UTF-8

read⁴
date: 2025-05-01T23:48:25-04:00
type: text/html; charset=UTF-8

watch⁵
date: 2025-05-01T23:48:26-04:00
type: text/html; charset=UTF-8

review⁶
date: 2025-05-01T23:48:27-04:00
type: text/html; charset=UTF-8

note⁷
date: 2025-05-01T23:48:28-04:00
type: text/html; charset=UTF-8

Webmention⁸
date: 2025-05-01T23:48:28-04:00
type: text/html; charset=UTF-8

indieweb⁹
date: 2025-05-01T23:48:29-04:00
type: text/html; charset=UTF-8

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

InboxZero
date: 2025-03-18T22:43:18-04:00
type: text/html; charset=utf-8

three-steps-indieweb-cybersecurity
date: 2025-03-18T22:43:18-04:00
type: text/html; charset=UTF-8
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

bloggingpermalink
date: 2025-03-18T22:43:19-04:00
type: text/html; charset=UTF-8

permalinkwhy
date: 2025-03-18T22:43:20-04:00
type: text/html; charset=UTF-8

why postReferences¹
date: 2025-03-18T22:43:21-04:00
type: text/html; charset=UTF-8

Words
date: 2025-03-18T22:43:24-04:00
type: text/html; charset=utf-8

Saved+by+Zero
date: 2025-03-18T22:43:25-04:00
type: text/html; charset=utf-8

concept
type: Tag
label: socialweb

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
type: item
type: MicroblogPost
title: : My Seek 2024 Year in Review:* 141 new species observed, of those, the top three kinds: * 79 plants * 20 insects * 16 fungi* 56 challenge badges earnedJune was the month I observed the most new species in 2024, followed by March, and then July.Seek also gave me a graph of observations per month, and also a map of where I made my discoveries.Rather than posting screenshots of the Year in Review that Seek provided me in the app, I am posting the relevant content here in a post on my personal site, which I know I’ll be able to search and look up in the future.Seek is a delightful free (like actually free, free of tracking, free of surveillance) native mobile application for identifying species.Made by the iNaturalist folks (https://www.inaturalist.org/pages/seek_app), Seek works without creating an account, and is able to work completely offline to identify species out in the wild (and add them to your local collection).Seek awards you Species Badges when you discover a number of species of a particular grouping, as well as Challenge Badges when you complete one or more of their monthly challenges that they post.In some ways it’s like Pokemon Go, except based on finding and collecting observations of real living things.I have found it quite useful especially when traveling, and wondering is that plant (or animal) the same as one I’ve seen elsewhere, perhaps around home, or is it a slightly different species?I also really like the good example that Seek provides for how an app can be immediately useful without requiring extra labor (like creating an account, or logging on) on behalf of the person using it.Lastly, Seek is an excellent example of a truly offline capable app where nearly all of its functionality works just fine without a network connection.Both of these capabilities (offline first, no login wall) are what we should aspire to when we build #indieweb apps or websites for ourselves and our friends.This is post 8 of #100PostsOfIndieWeb. #100Posts #yearInRevie…
link: https://status.blaise.ca/notice/116258
description: 's status on Monday, 20-Jan-2025 17:04:00 EST
encoded: My Seek 2024 Year in Review: * 141 new species observed, of those, the top three kinds: * 79 plants * 20 insects * 16 fungi * 56 challenge badges earned June was the month I observed the most new species in 2024, followed by March, and then July. Seek also gave me a graph of observations per month, and also a map of where I made my discoveries. Rather than posting screenshots of the Year in Review that Seek provided me in the app, I am posting the relevant content here in a post on my personal site, which I know I’ll be able to search and look up in the future. Seek is a delightful free (like actually free, free of tracking, free of surveillance) native mobile application for identifying species. Made by the iNaturalist folks (https://www.inaturalist.org/pages/seek_app), Seek works without creating an account, and is able to work completely offline to identify species out in the wild (and add them to your local collection). Seek awards you Species Badges when you discover a number of species of a particular grouping, as well as Challenge Badges when you complete one or more of their monthly challenges that they post. In some ways it’s like Pokemon Go, except based on finding and collecting observations of real living things. I have found it quite useful especially when traveling, and wondering is that plant (or animal) the same as one I’ve seen elsewhere, perhaps around home, or is it a slightly different species? I also really like the good example that Seek provides for how an app can be immediately useful without requiring extra labor (like creating an account, or logging on) on behalf of the person using it. Lastly, Seek is an excellent example of a truly offline capable app where nearly all of its functionality works just fine without a network connection. Both of these capabilities (offline first, no login wall) are what we should aspire to when we build #indieweb apps or websites for ourselves and our friends. This is post 8 of #100PostsOfIndieWeb. #100Posts …
date: 2025-01-20T17:04:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110325
enclosure: seek app
links to: seek app
enclosure: eight-years-webmention
links to: eight-years-webmention
enclosure: login walloffline
links to: login walloffline
enclosure: offline first
links to: offline first
tagged: concept

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

concept
type: Tag
label: cybersecurity

concept
type: Tag
label: fediverse

concept
type: Tag
label: mastodon

concept
type: Tag
label: security

concept
type: Tag
label: socialmedia

seek app
date: 2025-01-20T19:19:12-05:00
type: text/html; charset=utf-8

eight-years-webmention
date: 2025-01-20T19:19:13-05:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : 🎉 Eight years ago today, the #IndieWeb Webmention protocol was published as a W3C REC https://www.w3.org/TR/webmention/As a social web building block, #Webmention was designed to work with various other building blocks. Small pieces, loosely joined. Every year developers find new ways to work with Webmention, and new subtleties when combined with other building blocks.The primary uses of Webmention, peer-to-peer comments, likes, and other responses across web sites, has long presented an interesting challenge with the incorporation and display of external content originally from one site (the Webmention sender), on another site (the Webmention receiver).There are multiple considerations to keep in mind when displaying such external content.Two examples of external content are images (e.g. people’s icons or profile images from the author of a comment) and text (e.g. people’s names or the text of their comments).For external images, rather than displaying them in full fidelity, you may want to compress them into a smaller resolution for how your site displays the profile images of comment authors.If you accept Webmentions from arbitrary sources, there’s no telling what might show up in author images. You may want to pixelate images from unknown or novel sources into say 3x3 pixel grids of color (or grayscale) averages to make them uniquely identifiable while blurring any undesirable graphics beyond recognition.For external text, one thing we discovered in recent IndieWeb chat¹ is that someone’s comment (or in this case their name) can contain Unicode directional formatting characters, e.g. for displaying an Arabic or Hebrew name right-to-left. Text with such formatting characters can errantly impact the direction of adjacent text adjacent.Fortunately there is a CSS property, 'unicode-bidi', that can be used to isolate such external text. Thus when you embed text that was parsed from a received Webmention, possibly with formatting characters, you have to wrap it in a…
link: https://status.blaise.ca/notice/116256
description: 's status on Monday, 13-Jan-2025 00:23:00 EST
encoded: 🎉 Eight years ago today, the #IndieWeb Webmention protocol was published as a W3C REC https://www.w3.org/TR/webmention/ As a social web building block, #Webmention was designed to work with various other building blocks. Small pieces, loosely joined. Every year developers find new ways to work with Webmention, and new subtleties when combined with other building blocks. The primary uses of Webmention, peer-to-peer comments, likes, and other responses across web sites, has long presented an interesting challenge with the incorporation and display of external content originally from one site (the Webmention sender), on another site (the Webmention receiver). There are multiple considerations to keep in mind when displaying such external content. Two examples of external content are images (e.g. people’s icons or profile images from the author of a comment) and text (e.g. people’s names or the text of their comments). For external images, rather than displaying them in full fidelity, you may want to compress them into a smaller resolution for how your site displays the profile images of comment authors. If you accept Webmentions from arbitrary sources, there’s no telling what might show up in author images. You may want to pixelate images from unknown or novel sources into say 3x3 pixel grids of color (or grayscale) averages to make them uniquely identifiable while blurring any undesirable graphics beyond recognition. For external text, one thing we discovered in recent IndieWeb chat¹ is that someone’s comment (or in this case their name) can contain Unicode directional formatting characters, e.g. for displaying an Arabic or Hebrew name right-to-left. Text with such formatting characters can errantly impact the direction of adjacent text adjacent. Fortunately there is a CSS property, 'unicode-bidi', that can be used to isolate such external text. Thus when you embed text that was parsed from a received Webmention, possibly with formatting characters, you have to wrap i…
date: 2025-01-13T00:23:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110323
enclosure: why-html-classes-css-class-selectors
links to: why-html-classes-css-class-selectors
enclosure: As
links to: As
enclosure: micro-one-onramp-open-social-web
links to: micro-one-onramp-open-social-web
enclosure: discusspixelate
links to: discusspixelate
enclosure: pixelatedsmall
links to: pixelatedsmall
enclosure: Unicode
links to: Unicode
enclosure: Explicit formattingunicode-bidi
links to: Explicit formattingunicode-bidi
enclosure: unicode-bidi
links to: unicode-bidi
enclosure: t1736092889120900
links to: t1736092889120900
tagged: concept

login walloffline
date: 2025-01-20T19:19:14-05:00
type: text/html; charset=UTF-8

offline first
date: 2025-01-20T19:19:14-05:00
type: text/html; charset=UTF-8

concept
type: Tag
label: inaturalist

concept
type: Tag
label: seekapp

concept
type: Tag
label: yearinreview

why-html-classes-css-class-selectors
date: 2023-02-16T20:15:49-05:00
type: text/html; charset=UTF-8

As
date: 2025-01-13T01:46:35-05:00
type: text/html;charset=utf-8

micro-one-onramp-open-social-web
date: 2025-01-13T01:46:36-05:00
type: text/html; charset=UTF-8
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

discusspixelate
date: 2025-01-13T01:46:37-05:00
type: text/html; charset=UTF-8

pixelatedsmall
date: 2025-01-13T01:46:38-05:00
type: text/html; charset=UTF-8

Unicode
date: 2025-01-13T01:46:39-05:00
type: text/html; charset=iso-8859-1

Explicit formattingunicode-bidi
date: 2025-01-13T01:46:39-05:00
type: text/html; charset=UTF-8

unicode-bidi
date: 2025-01-13T01:46:40-05:00
length: 266694
type: text/html

t1736092889120900
date: 2025-01-13T01:46:40-05:00
type: text/html; charset=utf-8

concept
type: Tag
label: opensocialweb

concept
type: Tag
label: webmention

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
type: item
type: MicroblogPost
title: : Welcome to 2025!15 years ago today I began posting notes on my own #indieweb site first, and only later on #socialMedia: https://tantek.com/2010/001/t1/declaring-independence-building-itYou can too.I am once again encouraging you start the year with:1. Getting a personal domain name2. Posting on your own site first, then syndicating elsewhere: #POSSEIn 2025 there are even more neighborhoods with other people’s garages¹ to post into. Companies, servers, services, disappear all the time, taking all their posts and permalinks with them to graveyard 404².This is your annual reminder to embrace #independent ownership of your online self, your creations, and their #longevity:* Own your domain -> own your online identity* Own your permalinks -> own your postsWant help? Just ask: https://chat.indieweb.org/#ownYourContent #ownYourDataOnce again I am restarting a #100PostsOfIndieWeb #100Posts project for the year.This is post 1.Previously, previously, previously:* https://tantek.com/2024/001/t1/restarting-100days-indieweb-gift-calendar* https://tantek.com/2023/001/t1/own-your-notes* https://tantek.com/2022/001/t1/12-years-notes-my-site* https://tantek.com/2020/001/t1/10-years-notes-my-site* https://tantek.com/2015/002/t1/notes-replies-faves-before-twitter-ownyourdata← ✨→ https://tantek.com/2025/001/t2/first-new-year-review-priorGlossary:IndieWeb https://indieweb.org/longevity https://indieweb.org/longevitypost https://indieweb.org/postpermalink https://indieweb.org/permalinkpersonal domain name https://indieweb.org/personal-domainPOSSE https://indieweb.org/POSSEsyndicate https://indieweb.org/syndicate¹ https://tantek.com/2023/022/t2/own-your-notes-domain-migration² https://indieweb.org/site-deaths
link: https://status.blaise.ca/notice/116249
description: 's status on Wednesday, 01-Jan-2025 19:18:00 EST
encoded: Welcome to 2025! 15 years ago today I began posting notes on my own #indieweb site first, and only later on #socialMedia: https://tantek.com/2010/001/t1/declaring-independence-building-it You can too. I am once again encouraging you start the year with: 1. Getting a personal domain name 2. Posting on your own site first, then syndicating elsewhere: #POSSE In 2025 there are even more neighborhoods with other people’s garages¹ to post into. Companies, servers, services, disappear all the time, taking all their posts and permalinks with them to graveyard 404². This is your annual reminder to embrace #independent ownership of your online self, your creations, and their #longevity: * Own your domain -> own your online identity * Own your permalinks -> own your posts Want help? Just ask: https://chat.indieweb.org/ #ownYourContent #ownYourData Once again I am restarting a #100PostsOfIndieWeb #100Posts project for the year. This is post 1. Previously, previously, previously: * https://tantek.com/2024/001/t1/restarting-100days-indieweb-gift-calendar * https://tantek.com/2023/001/t1/own-your-notes * https://tantek.com/2022/001/t1/12-years-notes-my-site * https://tantek.com/2020/001/t1/10-years-notes-my-site * https://tantek.com/2015/002/t1/notes-replies-faves-before-twitter-ownyourdata ← ✨ → https://tantek.com/2025/001/t2/first-new-year-review-prior Glossary: IndieWeb https://indieweb.org/ longevity https://indieweb.org/longevity post https://indieweb.org/post permalink https://indieweb.org/permalink personal domain name https://indieweb.org/personal-domain POSSE https://indieweb.org/POSSE syndicate https://indieweb.org/syndicate ¹ https://tantek.com/2023/022/t2/own-your-notes-domain-migration ² https://indieweb.org/site-deaths
date: 2025-01-01T19:18:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110316
enclosure: declaring-independence-building-it
links to: declaring-independence-building-it
enclosure: 10-years-notes-my-site
links to: 10-years-notes-my-site
enclosure: 12-years-notes-my-site
links to: 12-years-notes-my-site
enclosure: own-your-notes
links to: own-your-notes
enclosure: site-deaths
links to: site-deaths
enclosure: own-your-notes-domain-migration
links to: own-your-notes-domain-migration
enclosure: restarting-100days-indieweb-gift-calendar
links to: restarting-100days-indieweb-gift-calendar
enclosure: bottom
links to: bottom
enclosure: notes-replies-faves-before-twitter-ownyourdata
links to: notes-replies-faves-before-twitter-ownyourdata
enclosure: first-new-year-review-prior
links to: first-new-year-review-prior
enclosure: longevity
links to: longevity
enclosure: longevitypost
links to: longevitypost
enclosure: postpermalink
links to: postpermalink
enclosure: permalinkpersonal
links to: permalinkpersonal
enclosure: personal-domainPOSSE
links to: personal-domainPOSSE
enclosure: POSSEsyndicate
links to: POSSEsyndicate
enclosure: syndicate¹
links to: syndicate¹
tagged: concept

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
type: item
type: MicroblogPost
title: : Yesterday https://last.fm/ (@lastfm) emailed their year in review reports, which they called #Playback24 and Last.Year.Kudos to them for waiting until the new year to do so, and breaking with the pattern of services prematurely posting year in review summaries.¹They’re also available on the web, without requiring a native mobile app to view.Mine is here: https://www.last.fm/user/tantekc/listening-report/yearYou can find yours (if you’re a last.fm user) by going here:* https://www.last.fm/user/_/listening-report/yearThe page title calls it your #YearInMusic, and the URL your #ListeningReport.It has many interesting elements, from various top listened lists (artist, album, track), to what percent of 2024 listens (which they call scrobbles) were new artists, albums, and tracks.Their “Top Tags” time chart is quite cool. Fascinating to see the differences in music listening over the seasons and the whole year.The report has many interactive features, so it will take me some time to figure out how to save, export, and/or republish my listening report on my personal #indieweb site.For now I used Firefox to save the page as an .html page to my laptop, and was quite impressed with how much of the information was available in that one file. Much more than #Spotify’s #Wrapped. That’s step 1. Step 2 is figuring out a good way to blog at least some of it.This is post 5 of #100PostsOfIndieWeb. #100Posts #LastFM #YearInReview← https://tantek.com/2025/002/t1/indieweb-third-place-community→ 🔮Glossary:scrobble https://indieweb.org/scrobbleyear in review https://indieweb.org/year_in_review¹ https://tantek.com/2025/001/t2/first-new-year-review-prior
link: https://status.blaise.ca/notice/116252
description: 's status on Saturday, 04-Jan-2025 01:00:00 EST
encoded: Yesterday https://last.fm/ (@lastfm) emailed their year in review reports, which they called #Playback24 and Last.Year. Kudos to them for waiting until the new year to do so, and breaking with the pattern of services prematurely posting year in review summaries.¹ They’re also available on the web, without requiring a native mobile app to view. Mine is here: https://www.last.fm/user/tantekc/listening-report/year You can find yours (if you’re a last.fm user) by going here: * https://www.last.fm/user/_/listening-report/year The page title calls it your #YearInMusic, and the URL your #ListeningReport. It has many interesting elements, from various top listened lists (artist, album, track), to what percent of 2024 listens (which they call scrobbles) were new artists, albums, and tracks. Their “Top Tags” time chart is quite cool. Fascinating to see the differences in music listening over the seasons and the whole year. The report has many interactive features, so it will take me some time to figure out how to save, export, and/or republish my listening report on my personal #indieweb site. For now I used Firefox to save the page as an .html page to my laptop, and was quite impressed with how much of the information was available in that one file. Much more than #Spotify’s #Wrapped. That’s step 1. Step 2 is figuring out a good way to blog at least some of it. This is post 5 of #100PostsOfIndieWeb. #100Posts #LastFM #YearInReview ← https://tantek.com/2025/002/t1/indieweb-third-place-community → 🔮 Glossary: scrobble https://indieweb.org/scrobble year in review https://indieweb.org/year_in_review ¹ https://tantek.com/2025/001/t2/first-new-year-review-prior
date: 2025-01-04T01:00:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110319
enclosure: first-new-year-review-prior
links to: first-new-year-review-prior
enclosure: www.last.fm
links to: www.last.fm
enclosure: yearYou
links to: yearYou
links to: yearThe
enclosure: indieweb-third-place-community
links to: indieweb-third-place-community
enclosure: scrobbleyear
links to: scrobbleyear
enclosure: year in review¹
links to: year in review¹
tagged: concept

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

concept
type: Tag
label: micropub

concept
type: Tag
label: microsub

concept
type: Tag
label: ownyourdata

concept
type: Tag
label: ownyouridentity

first-new-year-review-prior
date: 2025-01-01T20:01:55-05:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : The first of a new year seems like a good day to assemble, aggregate, summarize and publish various year in review posts for the prior year.When various online services create a year in review for you many weeks before the end of the year (whether #Spotify #Unwrapped or #Strava #YearInSport), it seems they are short-changing you.No one asks for an 11 months in review (except HR departments, which is a different problem).So why do people accept only an ~11 months summary when services provide such a premature “year” in review?When people say things like “Make every day count” do they not also believe you should “Count every day”?In this case, 2024 had 366 days. You should count every one of them, and every thing from every one of them.Rather than “sharing” a premature year in review, request your “year in review” today on the 1st of the year from various services, extract the data you want, fill in any gaps, and post your year in reviews on your own site¹.#yearInReview #ownYourYearInReviewThis is post 2 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2025/001/t1/15-years-notes-my-site-first→ 🔮Glossary:year in review https://indieweb.org/year_in_review ¹ https://indieweb.org/year_in_review#IndieWeb_Examples
link: https://status.blaise.ca/notice/116248
description: 's status on Wednesday, 01-Jan-2025 19:30:00 EST
encoded: The first of a new year seems like a good day to assemble, aggregate, summarize and publish various year in review posts for the prior year. When various online services create a year in review for you many weeks before the end of the year (whether #Spotify #Unwrapped or #Strava #YearInSport), it seems they are short-changing you. No one asks for an 11 months in review (except HR departments, which is a different problem). So why do people accept only an ~11 months summary when services provide such a premature “year” in review? When people say things like “Make every day count” do they not also believe you should “Count every day”? In this case, 2024 had 366 days. You should count every one of them, and every thing from every one of them. Rather than “sharing” a premature year in review, request your “year in review” today on the 1st of the year from various services, extract the data you want, fill in any gaps, and post your year in reviews on your own site¹. #yearInReview #ownYourYearInReview This is post 2 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2025/001/t1/15-years-notes-my-site-first → 🔮 Glossary: year in review https://indieweb.org/year_in_review ¹ https://indieweb.org/year_in_review#IndieWeb_Examples
date: 2025-01-01T19:30:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110315
enclosure: 15-years-notes-my-site-first
links to: 15-years-notes-my-site-first
enclosure: year in review
links to: year in review
enclosure: IndieWeb Examples
links to: IndieWeb Examples
tagged: concept

www.last.fm
date: 2025-01-04T03:44:22-05:00
length: 116312
type: text/html; charset=utf-8

yearYou
date: 2025-01-04T03:44:23-05:00
length: 107308
type: text/html; charset=utf-8

indieweb-third-place-community
date: 2025-01-04T03:44:23-05:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : The #indieweb is more than #independence. It’s also a web, of both personal sites and “third place” sites like aggregators, bridges, proxies, directories, indexes, and other community sites.Broadly speaking, such “third place” sites include places we collectively contribute to, and which license our contributions for free use by others. While open source projects come to mind, perhaps a more obvious example is Wikipedia.Similarly, the most obvious “third place” in the #IndieWeb community is our community site and wiki https://indieweb.org/ as well as the heterogeneous chat https://chat.indieweb.org/.We also have many services run by individuals (or small teams) in the community, for the benefit of the community, like:* @snarfed.org’s https://brid.gy/ and https://fed.brid.gy/* @aaronparecki.com’s https://webmention.io/ and many others* @martymcgui.re’s https://xn--sr8hvo.ws/ (IndieWeb Webring)* @gregorlove.com’s https://indiebookclub.biz/* @mat.tl’s https://libre.fm/and I’m sure many more I’m forgetting.All these services respect your data and your ownership of it. #ownYourDataAll these services are swappable. Many (most?) are open source and self-hostable in case you want to run your own personal instance or another shared instance.The web part of the indieweb complements, connects, and strengthens the indie part.This is post 4 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2025/001/t3/strava-year-in-sport-how-to-get-info-save→ 🔮
link: https://status.blaise.ca/notice/116251
description: 's status on Friday, 03-Jan-2025 02:54:00 EST
encoded: The #indieweb is more than #independence. It’s also a web, of both personal sites and “third place” sites like aggregators, bridges, proxies, directories, indexes, and other community sites. Broadly speaking, such “third place” sites include places we collectively contribute to, and which license our contributions for free use by others. While open source projects come to mind, perhaps a more obvious example is Wikipedia. Similarly, the most obvious “third place” in the #IndieWeb community is our community site and wiki https://indieweb.org/ as well as the heterogeneous chat https://chat.indieweb.org/. We also have many services run by individuals (or small teams) in the community, for the benefit of the community, like: * @snarfed.org’s https://brid.gy/ and https://fed.brid.gy/ * @aaronparecki.com’s https://webmention.io/ and many others * @martymcgui.re’s https://xn--sr8hvo.ws/ (IndieWeb Webring) * @gregorlove.com’s https://indiebookclub.biz/ * @mat.tl’s https://libre.fm/ and I’m sure many more I’m forgetting. All these services respect your data and your ownership of it. #ownYourData All these services are swappable. Many (most?) are open source and self-hostable in case you want to run your own personal instance or another shared instance. The web part of the indieweb complements, connects, and strengthens the indie part. This is post 4 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2025/001/t3/strava-year-in-sport-how-to-get-info-save → 🔮
date: 2025-01-03T02:54:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110318
enclosure: indieweb.org
links to: indieweb.org
enclosure: brid.gy
links to: brid.gy
enclosure: webmention.io
links to: webmention.io
enclosure: .We
links to: .We
enclosure: https://fed.brid.gy/*
links to: https://fed.brid.gy/*
enclosure: xn--sr8hvo.ws
links to: xn--sr8hvo.ws
enclosure: https://indiebookclub.biz/*
links to: https://indiebookclub.biz/*
enclosure: and
links to: and
enclosure: strava-year-in-sport-how-to-get-info-save
links to: strava-year-in-sport-how-to-get-info-save
tagged: concept

scrobbleyear
date: 2025-01-04T03:44:24-05:00
type: text/html; charset=UTF-8

year in review¹
date: 2025-01-04T03:44:25-05:00
type: text/html; charset=UTF-8

concept
type: Tag
label: lastfm

concept
type: Tag
label: listeningreportit

concept
type: Tag
label: playback24

concept
type: Tag
label: spotify

concept
type: Tag
label: wrapped

concept
type: Tag
label: yearinmusic

indieweb.org
date: 2018-06-11T17:12:37-04:00
type: text/html; charset=UTF-8

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

webmention.io
date: 2023-01-11T09:44:07-05:00
length: 9438
type: text/html;charset=utf-8

.We
date: 2025-01-03T05:29:41-05:00
length: 169
type: text/html

https://fed.brid.gy/*
date: 2025-01-03T05:29:42-05:00
length: 207
type: text/html; charset=utf-8

xn--sr8hvo.ws
date: 2025-01-03T05:29:42-05:00
type: text/html; charset=UTF-8

https://indiebookclub.biz/*
date: 2025-01-03T05:29:42-05:00
length: 1770
type: text/html; charset=UTF-8

and
date: 2025-01-03T05:29:43-05:00
type: text/html; charset=iso-8859-1

strava-year-in-sport-how-to-get-info-save
date: 2025-01-03T05:29:43-05:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : When we say #ownYourData we mean whatever data is important to you, like the data services aggregate about you and present back to you. Owning that data means extracting it into a form you can hang onto regardless of what the service does in the future (or disappears), and publishing whatever aspects of it you wish to, on your personal #indieweb site.Speaking of year in reviews¹ and #Strava Year in Sport in particular, here are my brief notes for how to get the info from it (before it disappears after the 6th!²) and save it locally so you can write and publish your own year in sport.How to find your Strava: Year in Sport 2024 For 2024, the Strava Year in Sport 2024 is only available on the native mobile app (iOS and presumably Android) and not accessible via the website. Prior years which were available on the website e.g. 2018(.)strava(.)com and 2017(.)strava(.)com are long gone.From the mobile app home screen, tap the "📋 You" button in the lower right corner.At the top you should see:"Play back your 2024" heading with an orange button:[ See your Year in Sport ]Tap that button.Saving Seven Summary SegmentsYou should immediately see an animation start playing, with seven "segments" (like Instagram stories) at the top, gradually filling-in as progress indicators one at a time. For each "segment" if you press the screenshot combination of buttons on your mobile (e.g. volume-up + power on iPhone 14), in addition to taking a screenshot it will put you in a "share" screen with one or more videos or still images to share in a carousel format. For each item in the carousel (if there is more than one)* tap the item in the carousel* tap the "[↑] More" button at the bottom.* scroll down the list of options up a bit* tap "Save Video [↓]" or "Save Image [↓]" option to store it locally on your mobile.The seventh "segment" is your overall summary, and shows all your sports combined.Save it (as an image as noted above), then* tap the "✏️ Customize" button* choose an individual s…
link: https://status.blaise.ca/notice/116250
description: 's status on Wednesday, 01-Jan-2025 20:04:00 EST
encoded: When we say #ownYourData we mean whatever data is important to you, like the data services aggregate about you and present back to you. Owning that data means extracting it into a form you can hang onto regardless of what the service does in the future (or disappears), and publishing whatever aspects of it you wish to, on your personal #indieweb site. Speaking of year in reviews¹ and #Strava Year in Sport in particular, here are my brief notes for how to get the info from it (before it disappears after the 6th!²) and save it locally so you can write and publish your own year in sport. How to find your Strava: Year in Sport 2024 For 2024, the Strava Year in Sport 2024 is only available on the native mobile app (iOS and presumably Android) and not accessible via the website. Prior years which were available on the website e.g. 2018(.)strava(.)com and 2017(.)strava(.)com are long gone. From the mobile app home screen, tap the "📋 You" button in the lower right corner. At the top you should see: "Play back your 2024" heading with an orange button: [ See your Year in Sport ] Tap that button. Saving Seven Summary Segments You should immediately see an animation start playing, with seven "segments" (like Instagram stories) at the top, gradually filling-in as progress indicators one at a time. For each "segment" if you press the screenshot combination of buttons on your mobile (e.g. volume-up + power on iPhone 14), in addition to taking a screenshot it will put you in a "share" screen with one or more videos or still images to share in a carousel format. For each item in the carousel (if there is more than one) * tap the item in the carousel * tap the "[↑] More" button at the bottom. * scroll down the list of options up a bit * tap "Save Video [↓]" or "Save Image [↓]" option to store it locally on your mobile. The seventh "segment" is your overall summary, and shows all your sports combined. Save it (as an image as noted above), then * tap the "✏️ Customize" button * choose …
date: 2025-01-01T20:04:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110317
enclosure: year in review
links to: year in review
enclosure: first-new-year-review-prior
links to: first-new-year-review-prior
enclosure: hashtagown
links to: hashtagown
enclosure: own your data¹
links to: own your data¹
enclosure: h 01HH5VW132BPDTEZJZDHBGJ6KM³
links to: h 01HH5VW132BPDTEZJZDHBGJ6KM³
tagged: concept

concept
type: Tag
label: independence

concept
type: Tag
label: ownyourdataall

year in review
date: 2025-01-01T20:01:48-05:00
type: text/html; charset=UTF-8

hashtagown
date: 2025-01-01T23:04:32-05:00
type: text/html; charset=UTF-8

own your data¹
date: 2025-01-01T23:04:33-05:00
type: text/html; charset=UTF-8

h 01HH5VW132BPDTEZJZDHBGJ6KM³
date: 2025-01-01T23:04:35-05:00
type: text/html; charset=UTF-8

concept
type: Tag
label: ownyouryearinreviewthis

concept
type: Tag
label: strava

concept
type: Tag
label: yearinsport

IndieWeb Examples
date: 2025-01-01T20:01:49-05:00
type: text/html; charset=UTF-8

concept
type: Tag
label: unwrapped

declaring-independence-building-it
date: 2020-01-02T00:13:23-05:00
type: text/html; charset=UTF-8

10-years-notes-my-site
date: 2022-01-01T21:30:05-05:00
type: text/html; charset=UTF-8

12-years-notes-my-site
date: 2023-01-02T02:36:53-05:00
type: text/html; charset=UTF-8

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

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

restarting-100days-indieweb-gift-calendar
date: 2024-01-04T06:26:25-05:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : Time to begin again: restarting my #100Days of #IndieWeb project for 2024, as a #100Posts of IndieWeb project, and congrats to the IndieWeb community on a fully completed 2023 IndieWeb Gift Calendar!Last year I completed 48 out of a planned 100 posts in my #100DaysOfIndieWeb project, for nearly 48 days (some days had multiple posts). Instead of resetting my goals accordingly, say down to 50, I’m going for 100 again, however, this time for 100 posts rather than 100 days, having learned that some days I find the time for multiple posts, and other days none at all.Looking back to the start of last year’s 100 Days project, it’s been one year since I encouraged everyone to own their own notes¹. Since then many have started, restarted, or expanded their personal sites to do so. Some have switched from a #Twitter account to a #Mastodon (or other #fediverse) account as a stopgap for short-form status posts. A step in the right direction, yet also an opportunity to take the leap this year to fully own their identity and posts on the web.In 2023 Twitter also broke all existing API clients (including my website). I did not feel it was worth my time to re-apply for an API key and rebuild/retest any necessary code for my semi-automatic #POSSE publishing, not knowing when they might break things again (since there was no rational reason for them to have broken things in the first place).I manually POSSEd a few posts after that, yet from the lack of interactions, either Twitter’s feed algorithm² isn’t showing my posts, or people have largely left or stopped using Twitter. Either way, when your friends stop seeing your posts on a silo, there’s no need to spend any time POSSEing to it.On the positive side, the IndieWeb community really came together in 2023, shining brightly even through the darker days of December.We, the IndieWeb community (and some beyond!) provided a gift (or often multiple) to the rest of community for every single day of December 2023³, the first time we suc…
link: https://status.blaise.ca/notice/116150
description: 's status on Monday, 01-Jan-2024 22:30:00 EST
encoded: Time to begin again: restarting my #100Days of #IndieWeb project for 2024, as a #100Posts of IndieWeb project, and congrats to the IndieWeb community on a fully completed 2023 IndieWeb Gift Calendar! Last year I completed 48 out of a planned 100 posts in my #100DaysOfIndieWeb project, for nearly 48 days (some days had multiple posts). Instead of resetting my goals accordingly, say down to 50, I’m going for 100 again, however, this time for 100 posts rather than 100 days, having learned that some days I find the time for multiple posts, and other days none at all. Looking back to the start of last year’s 100 Days project, it’s been one year since I encouraged everyone to own their own notes¹. Since then many have started, restarted, or expanded their personal sites to do so. Some have switched from a #Twitter account to a #Mastodon (or other #fediverse) account as a stopgap for short-form status posts. A step in the right direction, yet also an opportunity to take the leap this year to fully own their identity and posts on the web. In 2023 Twitter also broke all existing API clients (including my website). I did not feel it was worth my time to re-apply for an API key and rebuild/retest any necessary code for my semi-automatic #POSSE publishing, not knowing when they might break things again (since there was no rational reason for them to have broken things in the first place). I manually POSSEd a few posts after that, yet from the lack of interactions, either Twitter’s feed algorithm² isn’t showing my posts, or people have largely left or stopped using Twitter. Either way, when your friends stop seeing your posts on a silo, there’s no need to spend any time POSSEing to it. On the positive side, the IndieWeb community really came together in 2023, shining brightly even through the darker days of December. We, the IndieWeb community (and some beyond!) provided a gift (or often multiple) to the rest of community for every single day of December 2023³, the first time we…
date: 2024-01-01T22:30:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110227
tagged: concept

bottom
date: 2025-01-01T20:01:51-05:00
type: text/html; charset=utf-8

notes-replies-faves-before-twitter-ownyourdata
date: 2025-01-01T20:01:54-05:00
type: text/html; charset=UTF-8

longevity
date: 2025-01-01T20:01:56-05:00
type: text/html; charset=UTF-8

longevitypost
date: 2025-01-01T20:01:57-05:00
type: text/html; charset=UTF-8

postpermalink
date: 2025-01-01T20:01:58-05:00
type: text/html; charset=UTF-8

permalinkpersonal
date: 2025-01-01T20:01:59-05:00
type: text/html; charset=UTF-8

personal-domainPOSSE
date: 2025-01-01T20:02:00-05:00
type: text/html; charset=UTF-8

POSSEsyndicate
date: 2025-01-01T20:02:01-05:00
type: text/html; charset=UTF-8

syndicate¹
date: 2025-01-01T20:02:02-05:00
type: text/html; charset=UTF-8

concept
type: Tag
label: independent

concept
type: Tag
label: longevity

concept
type: Tag
label: ownyourdataonce

concept
type: Tag
label: possein

why-what-how-to-post
type: item
type: MicroblogPost
title: : I have written several posts with tips for various aspects of blogging. This post curates those posts and bits from the #IndieWeb wiki into a linear progression, from why, to what, and how to post. This post assumes you already have a blog — if you don’t have one and wonder why you should, that’s a different blog post.Why PostThere is a whole wiki page on the topic:* https://indieweb.org/why_post — which could use some gardeningHere is a summary of reasons why to post:1. Wean yourself off social media. Post to your own site instead of social media. If you already post on social media, into someone else’s garage¹, then you already have reason enough to post. So post on your own site first, and optionally syndicate² to that silo, only if you have friends who still use it to read posts.2. What to Post* Post positive things promptly: https://tantek.com/2018/357/t3 * … from that day first: https://tantek.com/2018/364/t1 * … in time order: https://tantek.com/2018/364/t5* Make and share lists. People like listsHow to Post* Use a local text editor* Capture first, edit & publish later: https://tantek.com/2023/365/t1/* Do something positive (in-person), then post about it: https://tantek.com/2018/002/t1* Single topic post* Short and to the point. Edit and remove anything distracting from the main point.* Quotable post title* Summary opening paragraph* Put tangents aside* Quotable sentences and multi-sentence paragraphs* Subheadings help cluster related paragraphs* Use a footer for updates, terminology, previous writings, additional reading, and citations. * Move definitions, citations, etc. to the footer unless including them inline either provides little risk of distraction or significantly helps reading flow. * Use footer subsections: Previously, Post Glossary, References, Additional Reading* Check your referencesEach of these points could be its own blog post.Glossarysilo https://indieweb.org/silosocial media https://indieweb.org/social_mediaReferences¹ https://tantek.co…
link: https://status.blaise.ca/notice/116239
description: 's status on Tuesday, 03-Dec-2024 00:11:00 EST
encoded: I have written several posts with tips for various aspects of blogging. This post curates those posts and bits from the #IndieWeb wiki into a linear progression, from why, to what, and how to post. This post assumes you already have a blog — if you don’t have one and wonder why you should, that’s a different blog post. Why Post There is a whole wiki page on the topic: * https://indieweb.org/why_post — which could use some gardening Here is a summary of reasons why to post: 1. Wean yourself off social media. Post to your own site instead of social media. If you already post on social media, into someone else’s garage¹, then you already have reason enough to post. So post on your own site first, and optionally syndicate² to that silo, only if you have friends who still use it to read posts. 2. What to Post * Post positive things promptly: https://tantek.com/2018/357/t3 * … from that day first: https://tantek.com/2018/364/t1 * … in time order: https://tantek.com/2018/364/t5 * Make and share lists. People like lists How to Post * Use a local text editor * Capture first, edit & publish later: https://tantek.com/2023/365/t1/ * Do something positive (in-person), then post about it: https://tantek.com/2018/002/t1 * Single topic post * Short and to the point. Edit and remove anything distracting from the main point. * Quotable post title * Summary opening paragraph * Put tangents aside * Quotable sentences and multi-sentence paragraphs * Subheadings help cluster related paragraphs * Use a footer for updates, terminology, previous writings, additional reading, and citations. * Move definitions, citations, etc. to the footer unless including them inline either provides little risk of distraction or significantly helps reading flow. * Use footer subsections: Previously, Post Glossary, References, Additional Reading * Check your references Each of these points could be its own blog post. Glossary silo https://indieweb.org/silo social media https://indieweb.org/social_media Refer…
date: 2024-12-03T00:11:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110308
enclosure: own-your-notes
links to: own-your-notes
enclosure: silosocial
links to: silosocial
enclosure: capture-first-edit-publish-later
links to: capture-first-edit-publish-later
enclosure: simple-embeds
links to: simple-embeds
enclosure: why post
links to: why post
enclosure: five-reasons-post-positive-things-promptly
links to: five-reasons-post-positive-things-promptly
enclosure: sixth-reason-post-positive-things-promptly
links to: sixth-reason-post-positive-things-promptly
enclosure: t5*
links to: t5*
enclosure: t1*
links to: t1*
enclosure: social mediaReferences¹
links to: social mediaReferences¹
enclosure: POSSEThis
links to: POSSEThis
tagged: concept

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

capture-first-edit-publish-later
date: 2023-12-31T19:22:17-05:00
type: text/html; charset=UTF-8

simple-embeds
date: 2024-11-10T12:02:34-05:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : Last week at a #HomebrewWebsiteClub session¹ I pointed out that I was working on implementing a “simple” way to support embeds of my notes, that is, make my short notes embeddable, like how people embed tweets or toots.I noted that to keep it as simple as possible while being flexible to implementation changes, I planned to implement three things:1. A separate “embed” version of my post permalinks, with just the entry information (no header, nav, search, sidebar, footer etc.), embeddable via copy/paste or an iframe.2. A way to “Follow Your Nose” discover that separate embed version3. A way to discover the original post from the embedded versionFor (1) a minimal h-entry, with perhaps a little bit of inline CSS would suffice.For (2) I proposed using “rel=embed” which I’ve subsequently written up briefly².For (3) The obvious existing answer is rel=canonical link from the embed version to the canonical post permalink.Soon thereafter, several folks in the #IndieWeb community went ahead and implemented such embeds for their own sites, and even the https://libre.fm/ open scrobbling service!https://indieweb.org/embed#IndieWeb_ExamplesI have yet to implement it myself, and that’s fine. This is one of the things I appreciate about the community, we can share our plans and ideas for improving things on our own sites, and if someone else does it first, that's great! We celebrate it and explore the solution space together.Got other ideas for simple embeds? Want to implement them on your own site?Join us in the #indiewebdev chat: https://chat.indieweb.org/devUPDATE: What about oEmbed? tl;dr: oEmbed requires JS and backend code, more work and unsuitable for embeds from static site hosting (like GitHub pages). A simple HTML method is accessible to many more independent publishers and easier to implement. More: https://tantek.com/2024/306/t2Glossaryembed https://indieweb.org/embedFollow Your Nose https://indieweb.org/follow_your_noseh-entry https://microformats.org/wiki/h-entryoEm…
link: https://status.blaise.ca/notice/116234
description: 's status on Friday, 01-Nov-2024 17:33:00 EDT
encoded: Last week at a #HomebrewWebsiteClub session¹ I pointed out that I was working on implementing a “simple” way to support embeds of my notes, that is, make my short notes embeddable, like how people embed tweets or toots. I noted that to keep it as simple as possible while being flexible to implementation changes, I planned to implement three things: 1. A separate “embed” version of my post permalinks, with just the entry information (no header, nav, search, sidebar, footer etc.), embeddable via copy/paste or an iframe. 2. A way to “Follow Your Nose” discover that separate embed version 3. A way to discover the original post from the embedded version For (1) a minimal h-entry, with perhaps a little bit of inline CSS would suffice. For (2) I proposed using “rel=embed” which I’ve subsequently written up briefly². For (3) The obvious existing answer is rel=canonical link from the embed version to the canonical post permalink. Soon thereafter, several folks in the #IndieWeb community went ahead and implemented such embeds for their own sites, and even the https://libre.fm/ open scrobbling service! https://indieweb.org/embed#IndieWeb_Examples I have yet to implement it myself, and that’s fine. This is one of the things I appreciate about the community, we can share our plans and ideas for improving things on our own sites, and if someone else does it first, that's great! We celebrate it and explore the solution space together. Got other ideas for simple embeds? Want to implement them on your own site? Join us in the #indiewebdev chat: https://chat.indieweb.org/dev UPDATE: What about oEmbed? tl;dr: oEmbed requires JS and backend code, more work and unsuitable for embeds from static site hosting (like GitHub pages). A simple HTML method is accessible to many more independent publishers and easier to implement. More: https://tantek.com/2024/306/t2 Glossary embed https://indieweb.org/embed Follow Your Nose https://indieweb.org/follow_your_nose h-entry https://microformats.org/…
date: 2024-11-01T17:33:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110303
enclosure: libre.fm
links to: libre.fm
enclosure: devUPDATE:
links to: devUPDATE:
enclosure: t2Glossaryembed
links to: t2Glossaryembed
enclosure: embedFollow
links to: embedFollow
enclosure: follow your noseh-entry
links to: follow your noseh-entry
enclosure: h-entryoEmbed
links to: h-entryoEmbed
enclosure: oEmbedrel-canonical
links to: oEmbedrel-canonical
enclosure: rel-canonicalstatic
links to: rel-canonicalstatic
enclosure: static web hostingReferences
links to: static web hostingReferences
enclosure: embedding²
links to: embedding²
enclosure: rel-embedThis
links to: rel-embedThis
enclosure: fediverse-unfollow-bridgyfed-bug
links to: fediverse-unfollow-bridgyfed-bug
tagged: concept

why post
date: 2024-12-03T02:10:56-05:00
type: text/html; charset=UTF-8

five-reasons-post-positive-things-promptly
date: 2024-12-03T02:10:58-05:00
type: text/html; charset=UTF-8

sixth-reason-post-positive-things-promptly
date: 2024-12-03T02:10:59-05:00
type: text/html; charset=UTF-8

t5*
date: 2024-12-03T02:10:59-05:00
type: text/html; charset=UTF-8

t1*
date: 2024-12-03T02:11:00-05:00
type: text/html; charset=UTF-8

social mediaReferences¹
date: 2024-12-03T02:11:01-05:00
type: text/html; charset=UTF-8

POSSEThis
date: 2024-12-03T02:11:02-05:00
type: text/html; charset=UTF-8

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

concept
type: Tag
label: algorithms

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

libre.fm
date: 2024-11-01T20:03:07-04:00
type: text/html; charset=utf-8

devUPDATE:
date: 2024-11-01T20:03:08-04:00
length: 169
type: text/html

t2Glossaryembed
date: 2024-11-01T20:03:08-04:00
type: text/html; charset=UTF-8

embedFollow
date: 2024-11-01T20:03:09-04:00
type: text/html; charset=UTF-8

follow your noseh-entry
date: 2024-11-01T20:03:10-04:00
type: text/html; charset=UTF-8

h-entryoEmbed
date: 2024-11-01T20:03:11-04:00
type: text/html; charset=UTF-8

oEmbedrel-canonical
date: 2024-11-01T20:03:12-04:00
type: text/html; charset=UTF-8

rel-canonicalstatic
date: 2024-11-01T20:03:12-04:00
type: text/html; charset=UTF-8

static web hostingReferences
date: 2024-11-01T20:03:13-04:00
type: text/html; charset=UTF-8

embedding²
date: 2024-11-01T20:03:14-04:00
type: text/html; charset=UTF-8

rel-embedThis
date: 2024-11-01T20:03:16-04:00
type: text/html; charset=UTF-8

fediverse-unfollow-bridgyfed-bug
date: 2024-11-01T20:03:17-04:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : No I did not block you on the #fediverse / #Mastodon / #Misskey etc.If you were following me @tantek.com on your client/server/instance of choice but noticed you were no longer doing so, that was due to a recent software bug in my fediverse provider which accidentally caused everyone’s #ActivityPub servers to unfollow me (bug details below).No it’s absolutely not your fault, you did nothing wrong.We need a variant of Hanlon’s Razor¹ like:“Never attribute to malice that which is adequately explained by a software bug.”Take another look at my posts if you want (directly on @tantek.com or try searching for that on your instance) and if you like what you see or find them otherwise informative and useful, feel free to refollow. If not, no worries!Also no worries if you ever unfollow/refollow for any reason. I mean that. I always assume people know best how to manage their online reader/reading experiences, everyone’s priorities and likes/dislikes change over time, and encourage everyone to make choices that are best for their mental health and overall joy online.Bug details:This was due to a #BridgyFed bug² that deleted my profile (“ActivityPub actor”) from (nearly?) all instances, making everyone’s accounts automatically unfollow me, as well as remove any of my posts from your likes and reposts (boosts) collections. It also removed my posts from any of your replies to my posts, leaving your replies dangling without reply-contexts. Apologies!The bug was introduced accidentally as part of another fix about a month ago³, and was triggered within the following week⁴.Anyone following me before ~2024-09-22 was no longer following me. A few folks have noticed and refollowed. Any likes or reposts of my posts before that date were also undone (removed).Ryan (@snarfed.org) has been really good about giving folks a heads-up, and apologizing, and quickly doing what he can to fix things.Bugs happen, yes even in production code, so please do not post/send any hate.I’d rather be one…
link: https://status.blaise.ca/notice/116232
description: 's status on Sunday, 13-Oct-2024 16:37:00 EDT
encoded: No I did not block you on the #fediverse / #Mastodon / #Misskey etc. If you were following me @tantek.com on your client/server/instance of choice but noticed you were no longer doing so, that was due to a recent software bug in my fediverse provider which accidentally caused everyone’s #ActivityPub servers to unfollow me (bug details below). No it’s absolutely not your fault, you did nothing wrong. We need a variant of Hanlon’s Razor¹ like: “Never attribute to malice that which is adequately explained by a software bug.” Take another look at my posts if you want (directly on @tantek.com or try searching for that on your instance) and if you like what you see or find them otherwise informative and useful, feel free to refollow. If not, no worries! Also no worries if you ever unfollow/refollow for any reason. I mean that. I always assume people know best how to manage their online reader/reading experiences, everyone’s priorities and likes/dislikes change over time, and encourage everyone to make choices that are best for their mental health and overall joy online. Bug details: This was due to a #BridgyFed bug² that deleted my profile (“ActivityPub actor”) from (nearly?) all instances, making everyone’s accounts automatically unfollow me, as well as remove any of my posts from your likes and reposts (boosts) collections. It also removed my posts from any of your replies to my posts, leaving your replies dangling without reply-contexts. Apologies! The bug was introduced accidentally as part of another fix about a month ago³, and was triggered within the following week⁴. Anyone following me before ~2024-09-22 was no longer following me. A few folks have noticed and refollowed. Any likes or reposts of my posts before that date were also undone (removed). Ryan (@snarfed.org) has been really good about giving folks a heads-up, and apologizing, and quickly doing what he can to fix things. Bugs happen, yes even in production code, so please do not post/send any hate. I’d ra…
date: 2024-10-13T16:37:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110301
enclosure: Hanlon's razor²
links to: Hanlon's razor²
links to: 1379³
links to: 4df76d0db7b87cabbd714039546c05b3221169be⁴
enclosure: t1727028174623700This
links to: t1727028174623700This
enclosure: io-domain-suggested-steps
links to: io-domain-suggested-steps
tagged: concept

concept
type: Tag
label: homebrewwebsiteclub

concept
type: Tag
label: indiewebdev

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

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

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

concept
type: Tag
label: bridgyfed

concept
type: Tag
label: misskey

concept
type: Tag
label: openstandards

metaphors-constructive-cooperative-joyful
type: item
type: MicroblogPost
title: : I have put a lot of thought into deliberately shifting¹ metaphors², often in the context of the #indieweb³. One goal is to replace use of violent or divisive metaphors with actively constructive, cooperative, or joyful alternatives, like:* gardening/farming e.g. digital garden⁴* biology/ecology/nature e.g. digital ecosystem⁵* cooking/baking e.g. eat your own cooking⁶* toolmaking, clothing making, other useful crafts e.g. sew what you want⁷* music, dancing, painting, and other expressive crafts e.g. remixing⁸* travel, navigation, maps e.g. information superhighway⁹* games, sports, running, e.g. surfing the net¹⁰Some of these areas are well developed (sports metaphors), others are obvious or emergent from various IndieWeb efforts like our principles¹¹, and others could use brainstorming and experimentation.Thoughts and words, whether spoken or written, influence each other in reinforcement feedback loops. Consciously choosing one can impact the other and vice versa.Especially in messages to others or our even future selves, words and metaphors communicate and reinforce our values and thus merit care in their invention¹² and usage.What are metaphors you have found constructive, cooperative, or joyful?References:¹ https://tantek.com/2023/132/t1/agenda-gardening-metaphors² https://tantek.com/2023/023/t3/³ https://tantek.com/2023/022/t1/indieweb-eat-what-you-cook⁴ https://indieweb.org/digital_garden⁵ https://en.wikipedia.org/wiki/Digital_ecosystem⁶ https://indieweb.org/cook_what_you_want⁷ https://indieweb.org/events/2020-08-19-hwc-west-coast#sewing⁸ https://en.wikipedia.org/wiki/Remix_culture#Analog_era⁹ https://en.wikipedia.org/wiki/Information_superhighway¹⁰ https://en.wikipedia.org/wiki/Internet_metaphors#Functional_metaphors¹¹ https://indieweb.org/principles¹² https://tantek.com/2024/180/b1/responsible-inventingThis is post 24 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2024/277/t2/october-blogtober-indieweb→ 🔮
link: https://status.blaise.ca/notice/116228
description: 's status on Wednesday, 09-Oct-2024 15:06:00 EDT
encoded: I have put a lot of thought into deliberately shifting¹ metaphors², often in the context of the #indieweb³. One goal is to replace use of violent or divisive metaphors with actively constructive, cooperative, or joyful alternatives, like: * gardening/farming e.g. digital garden⁴ * biology/ecology/nature e.g. digital ecosystem⁵ * cooking/baking e.g. eat your own cooking⁶ * toolmaking, clothing making, other useful crafts e.g. sew what you want⁷ * music, dancing, painting, and other expressive crafts e.g. remixing⁸ * travel, navigation, maps e.g. information superhighway⁹ * games, sports, running, e.g. surfing the net¹⁰ Some of these areas are well developed (sports metaphors), others are obvious or emergent from various IndieWeb efforts like our principles¹¹, and others could use brainstorming and experimentation. Thoughts and words, whether spoken or written, influence each other in reinforcement feedback loops. Consciously choosing one can impact the other and vice versa. Especially in messages to others or our even future selves, words and metaphors communicate and reinforce our values and thus merit care in their invention¹² and usage. What are metaphors you have found constructive, cooperative, or joyful? References: ¹ https://tantek.com/2023/132/t1/agenda-gardening-metaphors ² https://tantek.com/2023/023/t3/ ³ https://tantek.com/2023/022/t1/indieweb-eat-what-you-cook ⁴ https://indieweb.org/digital_garden ⁵ https://en.wikipedia.org/wiki/Digital_ecosystem ⁶ https://indieweb.org/cook_what_you_want ⁷ https://indieweb.org/events/2020-08-19-hwc-west-coast#sewing ⁸ https://en.wikipedia.org/wiki/Remix_culture#Analog_era ⁹ https://en.wikipedia.org/wiki/Information_superhighway ¹⁰ https://en.wikipedia.org/wiki/Internet_metaphors#Functional_metaphors ¹¹ https://indieweb.org/principles ¹² https://tantek.com/2024/180/b1/responsible-inventing This is post 24 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2024/277/t2/october-blogtober-indieweb → 🔮
date: 2024-10-09T15:06:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110297
enclosure: indieweb-eat-what-you-cook
links to: indieweb-eat-what-you-cook
enclosure: agenda-gardening-metaphors
links to: agenda-gardening-metaphors
enclosure: t3
links to: t3
enclosure: digital garden⁵
links to: digital garden⁵
enclosure: Digital ecosystem⁶
links to: Digital ecosystem⁶
enclosure: cook what you want⁷
links to: cook what you want⁷
enclosure: sewing⁸
links to: sewing⁸
enclosure: Analog era⁹
links to: Analog era⁹
enclosure: Information superhighway¹⁰
links to: Information superhighway¹⁰
enclosure: Functional metaphors¹¹
links to: Functional metaphors¹¹
enclosure: principles¹²
links to: principles¹²
enclosure: responsible-inventing
links to: responsible-inventing
enclosure: october-blogtober-indieweb
links to: october-blogtober-indieweb
tagged: concept

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

agenda-gardening-metaphors
date: 2024-10-09T17:28:04-04:00
type: text/html; charset=UTF-8

t3
date: 2024-10-09T17:28:05-04:00
type: text/html; charset=UTF-8

digital garden⁵
date: 2024-10-09T17:28:06-04:00
type: text/html; charset=UTF-8

Digital ecosystem⁶
date: 2024-10-09T17:28:07-04:00
type: text/html; charset=UTF-8

cook what you want⁷
date: 2024-10-09T17:28:08-04:00
type: text/html; charset=UTF-8

sewing⁸
date: 2024-10-09T17:28:09-04:00
type: text/html; charset=UTF-8

Analog era⁹
date: 2024-10-09T17:28:11-04:00
length: 285548
type: text/html; charset=UTF-8

Information superhighway¹⁰
date: 2024-10-09T17:28:12-04:00
type: text/html; charset=UTF-8

Functional metaphors¹¹
date: 2024-10-09T17:28:12-04:00
length: 87906
type: text/html; charset=UTF-8

principles¹²
date: 2024-10-09T17:28:13-04:00
type: text/html; charset=UTF-8

responsible-inventing
date: 2024-10-09T17:28:14-04:00
type: text/html; charset=UTF-8

october-blogtober-indieweb
date: 2024-10-09T17:28:15-04:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : Happy October!For some reason this month has a plethora of daily blogging or other creativity prompts. Here’s a list of the ones I found so far:* #Blogtober (consider this post my first for this, retroactively day 1)* Inktober — https://inktober.com/* LOLtober - https://weblog.anniegreens.lol/2024/10/loltober-2024* Looptober — https://looptober.com/* Mathober - https://mathober.com/* Viztober — https://www.instagram.com/evalottchen/p/DAiNm3ZtuTj/Having found so many for the month I created an “October” page on the #IndieWeb wiki to document them all (and in case folks find others to add):* https://indieweb.org/OctoberOctober is also a very popular month for seasonal blog styling:* https://indieweb.org/HalloweenDo you have a custom Halloween theme for your personal site? Add it to the wiki!This is post 23 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2024/247/t4/w3c-link-checker-before-federating→ 🔮
link: https://status.blaise.ca/notice/116226
description: 's status on Thursday, 03-Oct-2024 19:04:00 EDT
encoded: Happy October! For some reason this month has a plethora of daily blogging or other creativity prompts. Here’s a list of the ones I found so far: * #Blogtober (consider this post my first for this, retroactively day 1) * Inktober — https://inktober.com/ * LOLtober - https://weblog.anniegreens.lol/2024/10/loltober-2024 * Looptober — https://looptober.com/ * Mathober - https://mathober.com/ * Viztober — https://www.instagram.com/evalottchen/p/DAiNm3ZtuTj/ Having found so many for the month I created an “October” page on the #IndieWeb wiki to document them all (and in case folks find others to add): * https://indieweb.org/October October is also a very popular month for seasonal blog styling: * https://indieweb.org/Halloween Do you have a custom Halloween theme for your personal site? Add it to the wiki! This is post 23 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2024/247/t4/w3c-link-checker-before-federating → 🔮
date: 2024-10-03T19:04:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110295
enclosure: https://inktober.com/*
links to: https://inktober.com/*
enclosure: loltober-2024*
links to: loltober-2024*
enclosure: https://looptober.com/*
links to: https://looptober.com/*
enclosure: https://mathober.com/*
links to: https://mathober.com/*
enclosure: Having
links to: Having
enclosure: OctoberOctober
links to: OctoberOctober
enclosure: HalloweenDo
links to: HalloweenDo
enclosure: w3c-link-checker-before-federating
links to: w3c-link-checker-before-federating
tagged: concept

concept
type: Tag
label: indieweb³

https://inktober.com/*
date: 2024-10-03T20:36:00-04:00
length: 44898
type: text/html;charset=utf-8

loltober-2024*
date: 2024-10-03T20:36:01-04:00
type: text/html; charset=UTF-8

https://looptober.com/*
date: 2024-10-03T20:36:04-04:00
length: 1054
type: text/html; charset=utf-8

https://mathober.com/*
date: 2024-10-03T20:36:04-04:00
type: text/html; charset=utf-8

Having
date: 2024-10-03T20:36:04-04:00
type: text/html; charset="utf-8"

OctoberOctober
date: 2024-10-03T20:36:05-04:00
type: text/html; charset=UTF-8

HalloweenDo
date: 2024-10-03T20:36:06-04:00
type: text/html; charset=UTF-8

w3c-link-checker-before-federating
date: 2024-10-03T20:36:07-04:00
type: text/html; charset=UTF-8
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: federate

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
type: item
type: MicroblogPost
title: : Happy 12 years of https://indieweb.org/POSSE #POSSE and19 years of https://microformats.org/ #microformats! (as of yesterday, the 20th)A few highlights from the past year:POSSE (Publish on your Own Site, Syndicate Elsewhere) has grown steadily as a common practice in the #IndieWeb community, personal sites, CMSs (like Withknown, which itself reached 10 years in May!), and services (like https://micro.blog) for over a decade.In its 12th year, POSSE broke through to broader technology press and adoption beyond the community. For example:* David Pierce’s (@pierce@mas.to) excellent article @TheVerge.com (@verge@mastodon.social): “The poster’s guide to the internet of the future” (https://www.theverge.com/2023/10/23/23928550/posse-posting-activitypub-standard-twitter-tumblr-mastodon): “Your post appears natively on all of those platforms, typically with some kind of link back to your blog. And your blog becomes the hub for everything, your main home on the internet.Done right, POSSE is the best of all posting worlds.”* David also recorded a 29 minute podcast on POSSE with some great interviews: https://podcasts.apple.com/us/podcast/the-posters-guide-to-the-new-internet/id430333725?i=1000632256014* Cory Doctorow (@craphound.com @doctorow@mamot.fr) declared in his Pluralistic blog (@pluralisticmamot.fr) post: “Vice surrenders” (https://pluralistic.net/2024/02/24/anti-posse/): “This is the moment for POSSE (Post Own Site, Share Everywhere [sic]), a strategy that sees social media as a strategy for bringing readers to channels that you control” * And none other than Molly White (@mollywhite.net @molly0xfff@hachyderm.io) of @web3isgoinggreat.com (@web3isgreat@indieweb.social) built, deployed, and started actively using her own POSSE setup as described in her post titled “POSSE” (https://www.mollywhite.net/micro/entry/202403091817) to: "… write posts in the microblog and automatically crosspost them to Twitter/Mastodon/Bluesky, while keeping the original post on my site." Co…
link: https://status.blaise.ca/notice/116204
description: 's status on Saturday, 22-Jun-2024 01:02:00 EDT
encoded: Happy 12 years of https://indieweb.org/POSSE #POSSE and 19 years of https://microformats.org/ #microformats! (as of yesterday, the 20th) A few highlights from the past year: POSSE (Publish on your Own Site, Syndicate Elsewhere) has grown steadily as a common practice in the #IndieWeb community, personal sites, CMSs (like Withknown, which itself reached 10 years in May!), and services (like https://micro.blog) for over a decade. In its 12th year, POSSE broke through to broader technology press and adoption beyond the community. For example: * David Pierce’s (@pierce@mas.to) excellent article @TheVerge.com (@verge@mastodon.social): “The poster’s guide to the internet of the future” (https://www.theverge.com/2023/10/23/23928550/posse-posting-activitypub-standard-twitter-tumblr-mastodon): “Your post appears natively on all of those platforms, typically with some kind of link back to your blog. And your blog becomes the hub for everything, your main home on the internet. Done right, POSSE is the best of all posting worlds.” * David also recorded a 29 minute podcast on POSSE with some great interviews: https://podcasts.apple.com/us/podcast/the-posters-guide-to-the-new-internet/id430333725?i=1000632256014 * Cory Doctorow (@craphound.com @doctorow@mamot.fr) declared in his Pluralistic blog (@pluralisticmamot.fr) post: “Vice surrenders” (https://pluralistic.net/2024/02/24/anti-posse/): “This is the moment for POSSE (Post Own Site, Share Everywhere [sic]), a strategy that sees social media as a strategy for bringing readers to channels that you control” * And none other than Molly White (@mollywhite.net @molly0xfff@hachyderm.io) of @web3isgoinggreat.com (@web3isgreat@indieweb.social) built, deployed, and started actively using her own POSSE setup as described in her post titled “POSSE” (https://www.mollywhite.net/micro/entry/202403091817) to: "… write posts in the microblog and automatically crosspost them to Twitter/Mastodon/Bluesky, while keeping the original post on my sit…
date: 2024-06-22T01:02:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110273
enclosure: POSSE
links to: POSSE
enclosure: micro.blog
links to: micro.blog
enclosure: h-cardh-entry
links to: h-cardh-entry
enclosure: microformats.org
links to: microformats.org
enclosure: anniversaries-microformats-posse
links to: anniversaries-microformats-posse
enclosure: threads-supports-indieweb-rel-me
links to: threads-supports-indieweb-rel-me
enclosure: posse-posting-activitypub-standard-twitter-tumblr-mastodon):
links to: posse-posting-activitypub-standard-twitter-tumblr-mastodon):
links to: https://podcasts.apple.com/us/podcast/the-posters-guide-to-the-new-internet/id430333725
enclosure: ):
links to: ):
enclosure: https://www.mollywhite.net/micro/entry/202403091817
links to: https://www.mollywhite.net/micro/entry/202403091817
enclosure: dev*
links to: dev*
enclosure: bottom
links to: bottom
enclosure: minimum-interesting-service-worker
links to: minimum-interesting-service-worker
enclosure: CMSh-card
links to: CMSh-card
enclosure: h-entryh-feed
links to: h-entryh-feed
enclosure: h-feedmicroformats2
links to: h-feedmicroformats2
enclosure: microformats2-parsingrel-me
links to: microformats2-parsingrel-me
enclosure: rel-meSSG
links to: rel-meSSG
enclosure: SSGWebmention
links to: SSGWebmention
enclosure: WebmentionWithknown
links to: WebmentionWithknown
enclosure: KnownReferences:¹
links to: KnownReferences:¹
enclosure: Letterboxd
links to: Letterboxd
tagged: concept

indiewebcamp-auto-linking
date: 2024-08-30T01:23:31-04:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : Nice #IndieWebCamp discussion session with @KevinMarks.com (@kevinmarks@xoxo.com @kevinmarks) on the topic of auto-linking¹.I’ve implemented an auto_link function² that handles quite a few use-cases of URLs (with or without http: or https:), @-name @-domain @-domain/path @-@-handles, hashtags(#), and footnotes(^).Much of it is based on what I’ve seen work (or implemented) on sites and software, and some of it is based on logically extending how people are using text punctuation across various services.It may be time for me to write-up an auto-link specification based on the algorithms I’ve come up with, implemented, and am using live on my site. All the algorithms work fully offline (none of them require querying a site for more info, whether well-known or otherwise), so they can be used in offline-first authoring/writing clients.I have identified three logical chunks of auto-linking functionality, each of which has different constraints and potential needs for local to the linking context information (like hashtags need a default tagspace). Each would be a good section for a new specification. Each is used by this very post.* URLs, @-s, and @-@-s* # hashtags* ^ footnotes#IndieWeb #autoLink #hashtag #hashtags #footnote #footnotesPreviously, previously, previously:* https://tantek.com/2024/070/t1/updated-auto-linking-mention-use-cases* https://tantek.com/2023/100/t1/auto-linked-hashtags-federated* https://tantek.com/2023/043/t1/footnotes-unicode-links* https://tantek.com/2023/019/t5/reply-domain-above-address-and-siloReferences:¹ https://indieweb.org/autolink² https://github.com/tantek/cassis/blob/main/cassis.jsThis is post 18 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2024/238/t1/indiewebcamp-portland→ 🔮
link: https://status.blaise.ca/notice/116212
description: 's status on Sunday, 25-Aug-2024 19:00:00 EDT
encoded: Nice #IndieWebCamp discussion session with @KevinMarks.com (@kevinmarks@xoxo.com @kevinmarks) on the topic of auto-linking¹. I’ve implemented an auto_link function² that handles quite a few use-cases of URLs (with or without http: or https:), @-name @-domain @-domain/path @-@-handles, hashtags(#), and footnotes(^). Much of it is based on what I’ve seen work (or implemented) on sites and software, and some of it is based on logically extending how people are using text punctuation across various services. It may be time for me to write-up an auto-link specification based on the algorithms I’ve come up with, implemented, and am using live on my site. All the algorithms work fully offline (none of them require querying a site for more info, whether well-known or otherwise), so they can be used in offline-first authoring/writing clients. I have identified three logical chunks of auto-linking functionality, each of which has different constraints and potential needs for local to the linking context information (like hashtags need a default tagspace). Each would be a good section for a new specification. Each is used by this very post. * URLs, @-s, and @-@-s * # hashtags * ^ footnotes #IndieWeb #autoLink #hashtag #hashtags #footnote #footnotes Previously, previously, previously: * https://tantek.com/2024/070/t1/updated-auto-linking-mention-use-cases * https://tantek.com/2023/100/t1/auto-linked-hashtags-federated * https://tantek.com/2023/043/t1/footnotes-unicode-links * https://tantek.com/2023/019/t5/reply-domain-above-address-and-silo References: ¹ https://indieweb.org/autolink ² https://github.com/tantek/cassis/blob/main/cassis.js This is post 18 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2024/238/t1/indiewebcamp-portland → 🔮
date: 2024-08-25T19:00:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110281
tagged: concept

indiewebcamp-portland
date: 2024-09-02T21:41:18-04:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : Had a great time at IndieWebCamp Portland 2024 this past Sunday — our 10th IndieWebCamp in Portland!https://events.indieweb.org/2024/08/indiewebcamp-portland-2024-8bucXDlLqR0kBeing a one day #IndieWebCamp, we focused more on making, hacking, and creating, than on formal discussion sessions.Nearly everyone gave a brief personal site intro with a summary of how they use their #IndieWeb site and what they would like to add, remove, or improve.* https://indieweb.org/2024/Portland/IntrosThere were lots of informal discussions, some in the main room, on the walk to and from lunch, over lunch in the nearby outdoor patio, or at tables inside the lobby of the Hotel Grand Stark.We wrapped up with our usual Create Day¹ Demos session, live streamed for remote attendees to see as well. Lots of great demos of things people built, designed, removed, cleaned-up, documented, and blogged! Everyone still at the camp showed something on their personal site!* https://indieweb.org/2024/Portland/DemosGroup photo and lots more about IndieWebCamp Portland 2024 at the event’s wiki page:* https://indieweb.org/2024/PortlandThanks to everyone who pitched in to help organize IndieWebCamp Portland 2024! Thanks especially to Marty McGuire (@martymcgui.re) for taking live notes during both the personal site intros and create day demos, to @KevinMarks.com (@kevinmarks@xoxo.zone @kevinmarks @kevinmarks@indieweb.social) for the IndieWebCamp live-tooting, and Ryan Barrett (@snarfed.org) for amazing breakfast pastries from Dos Hermanos.The experience definitely raised our hopes and confidence for returning to Portland in 2025.²References:¹ https://indieweb.org/Create_Day² https://indieweb.org/Planning#PortlandThis is post 19 of #100PostsOfIndieWeb. #100Posts #2024_238← https://tantek.com/2024/238/t3/indiewebcamp-auto-linking→ 🔮
link: https://status.blaise.ca/notice/116213
description: 's status on Friday, 30-Aug-2024 00:09:00 EDT
encoded: Had a great time at IndieWebCamp Portland 2024 this past Sunday — our 10th IndieWebCamp in Portland! https://events.indieweb.org/2024/08/indiewebcamp-portland-2024-8bucXDlLqR0k Being a one day #IndieWebCamp, we focused more on making, hacking, and creating, than on formal discussion sessions. Nearly everyone gave a brief personal site intro with a summary of how they use their #IndieWeb site and what they would like to add, remove, or improve. * https://indieweb.org/2024/Portland/Intros There were lots of informal discussions, some in the main room, on the walk to and from lunch, over lunch in the nearby outdoor patio, or at tables inside the lobby of the Hotel Grand Stark. We wrapped up with our usual Create Day¹ Demos session, live streamed for remote attendees to see as well. Lots of great demos of things people built, designed, removed, cleaned-up, documented, and blogged! Everyone still at the camp showed something on their personal site! * https://indieweb.org/2024/Portland/Demos Group photo and lots more about IndieWebCamp Portland 2024 at the event’s wiki page: * https://indieweb.org/2024/Portland Thanks to everyone who pitched in to help organize IndieWebCamp Portland 2024! Thanks especially to Marty McGuire (@martymcgui.re) for taking live notes during both the personal site intros and create day demos, to @KevinMarks.com (@kevinmarks@xoxo.zone @kevinmarks @kevinmarks@indieweb.social) for the IndieWebCamp live-tooting, and Ryan Barrett (@snarfed.org) for amazing breakfast pastries from Dos Hermanos. The experience definitely raised our hopes and confidence for returning to Portland in 2025.² References: ¹ https://indieweb.org/Create_Day ² https://indieweb.org/Planning#Portland This is post 19 of #100PostsOfIndieWeb. #100Posts #2024_238 ← https://tantek.com/2024/238/t3/indiewebcamp-auto-linking → 🔮
date: 2024-08-30T00:09:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110282
tagged: concept

read-write-suggest-edit-web
date: 2024-09-03T02:52:22-04:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : ✏️ I want the Read Write Suggest-Edit Accept-Edit Update Web.The consumer Infinite Scroll Web leaves us feeling empty.Too few of us participate in the Read Write Web, whether with personal sites or Wikipedia.A week ago when we wrapped up #IndieWebCamp Portland and I was reading @KevinMarks.com (@kevinmarks@indieweb.social @kevinmarks@xoxo.zone @kevinmarks) live-tooting of the demos¹, I noticed a few errors, typos or miscaptures, and pointed them out in-person.Kevin was able to quickly edit his toots and update them for anyone reading, thanks to #Mastodon’s post editing feature and its support of #ActivityPub Updates. But this shouldn’t require being in the same room, IRL or chat.We should be able to suggest edits to each other’s posts, as easily as we can reply and add a comment.13 years ago I wrote²: “The Read Write Web is no longer sufficient. I want the Read Fork Write Merge Web.”Now I want the Read Write Suggest-Edit Accept-Edit Update Web.The ↪ Reply button is fairly ubiquitous in modern post user interfaces (UIs).Why not also a ✏️ Suggest Edit button, to craft a fix for a typo, grammar, or other minor error, and send the author for their review, and acceptance or rejection? Perhaps viewable only by the suggester and the author, to avoid "performative" suggested edits.If the author’s posts provide revision histories, when a suggested edit is accepted, a post’s history could show the contributor of the edit.Instead of asking Kevin in-person, what if I could have posted special "Suggested Edit" responses in reply to his toots, for which he would receive special notifications, and could choose to one-click accept and update (or further edit) his toots?To enable such UIs and interactions across servers and implementations, we may need a new type of response³, perhaps with a special property (or more) to convey the edits being suggested.There is documentation of this and similar use-cases, prior art / UIs, as well as some brainstorming on the #IndieWeb wiki:* http…
link: https://status.blaise.ca/notice/116214
description: 's status on Sunday, 01-Sep-2024 17:51:00 EDT
encoded: ✏️ I want the Read Write Suggest-Edit Accept-Edit Update Web. The consumer Infinite Scroll Web leaves us feeling empty. Too few of us participate in the Read Write Web, whether with personal sites or Wikipedia. A week ago when we wrapped up #IndieWebCamp Portland and I was reading @KevinMarks.com (@kevinmarks@indieweb.social @kevinmarks@xoxo.zone @kevinmarks) live-tooting of the demos¹, I noticed a few errors, typos or miscaptures, and pointed them out in-person. Kevin was able to quickly edit his toots and update them for anyone reading, thanks to #Mastodon’s post editing feature and its support of #ActivityPub Updates. But this shouldn’t require being in the same room, IRL or chat. We should be able to suggest edits to each other’s posts, as easily as we can reply and add a comment. 13 years ago I wrote²: “The Read Write Web is no longer sufficient. I want the Read Fork Write Merge Web.” Now I want the Read Write Suggest-Edit Accept-Edit Update Web. The ↪ Reply button is fairly ubiquitous in modern post user interfaces (UIs). Why not also a ✏️ Suggest Edit button, to craft a fix for a typo, grammar, or other minor error, and send the author for their review, and acceptance or rejection? Perhaps viewable only by the suggester and the author, to avoid "performative" suggested edits. If the author’s posts provide revision histories, when a suggested edit is accepted, a post’s history could show the contributor of the edit. Instead of asking Kevin in-person, what if I could have posted special "Suggested Edit" responses in reply to his toots, for which he would receive special notifications, and could choose to one-click accept and update (or further edit) his toots? To enable such UIs and interactions across servers and implementations, we may need a new type of response³, perhaps with a special property (or more) to convey the edits being suggested. There is documentation of this and similar use-cases, prior art / UIs, as well as some brainstorming on the #IndieWeb …
date: 2024-09-01T17:51:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110283
tagged: concept

twenty-years-microformats
date: 2024-09-03T02:52:25-04:00
type: text/html; charset=UTF-8

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

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

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

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

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

read-write-suggest-edit-update-web
type: item
type: MicroblogPost
title: : ✏️ I want the Read Write Suggest-Edit Accept-Edit Update Web.The consumer Infinite Scroll Web leaves us feeling empty.Too few of us participate in the Read Write Web, whether with personal sites or Wikipedia.A week ago when we wrapped up #IndieWebCamp Portland and I was reading Kevin Marks (@kevinmarks@indieweb.social) live-tooting of the demos¹, I noticed a few errors, typos or miscaptures, and pointed them out in-person.Kevin was able to quickly edit his toots and update them for anyone reading, thanks to #Mastodon’s post editing feature and its support of #ActivityPub Updates. But this shouldn’t require being in the same room, whether IRL or chat.We should be able to suggest edits to each other’s posts, as easily as we can reply and add a comment.13 years ago I wrote²: “The Read Write Web is no longer sufficient. I want the Read Fork Write Merge Web.”Now I want the Read Write Suggest-Edit Accept-Edit Update Web.The ↪ Reply button is fairly ubiquitous in modern post user interfaces (UIs).Why not also a ✏️ Suggest Edit button, to craft a fix for a typo, grammar, or other minor error, and send the author for their review, and acceptance or rejection? Perhaps viewable only by the suggester and the author, to avoid "performative" suggested edits.If the author’s posts provide revision histories, when a suggested edit is accepted, a post’s history could show the contributor of the edit.Instead of asking Kevin in-person, what if I could have posted special "Suggested Edit" responses in reply to his toots, for which he would receive special notifications, and could choose to one-click accept and update (or further edit) his toots?To enable such UIs and interactions across servers and implementations, we may need a new type of response³, perhaps with a special property (or more) to convey the edits being suggested.There is documentation of this and similar use-cases, prior art / UIs, as well as some brainstorming on the #IndieWeb wiki:* https://indieweb.org/editOur inter…
link: https://status.blaise.ca/notice/116219
description: 's status on Sunday, 01-Sep-2024 17:51:00 EDT
encoded: ✏️ I want the Read Write Suggest-Edit Accept-Edit Update Web. The consumer Infinite Scroll Web leaves us feeling empty. Too few of us participate in the Read Write Web, whether with personal sites or Wikipedia. A week ago when we wrapped up #IndieWebCamp Portland and I was reading Kevin Marks (@kevinmarks@indieweb.social) live-tooting of the demos¹, I noticed a few errors, typos or miscaptures, and pointed them out in-person. Kevin was able to quickly edit his toots and update them for anyone reading, thanks to #Mastodon’s post editing feature and its support of #ActivityPub Updates. But this shouldn’t require being in the same room, whether IRL or chat. We should be able to suggest edits to each other’s posts, as easily as we can reply and add a comment. 13 years ago I wrote²: “The Read Write Web is no longer sufficient. I want the Read Fork Write Merge Web.” Now I want the Read Write Suggest-Edit Accept-Edit Update Web. The ↪ Reply button is fairly ubiquitous in modern post user interfaces (UIs). Why not also a ✏️ Suggest Edit button, to craft a fix for a typo, grammar, or other minor error, and send the author for their review, and acceptance or rejection? Perhaps viewable only by the suggester and the author, to avoid "performative" suggested edits. If the author’s posts provide revision histories, when a suggested edit is accepted, a post’s history could show the contributor of the edit. Instead of asking Kevin in-person, what if I could have posted special "Suggested Edit" responses in reply to his toots, for which he would receive special notifications, and could choose to one-click accept and update (or further edit) his toots? To enable such UIs and interactions across servers and implementations, we may need a new type of response³, perhaps with a special property (or more) to convey the edits being suggested. There is documentation of this and similar use-cases, prior art / UIs, as well as some brainstorming on the #IndieWeb wiki: * https://indieweb.org/e…
date: 2024-09-01T17:51:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110288
tagged: concept

concept
type: Tag
label: accepteditreferences

concept
type: Tag
label: editableweb

concept
type: Tag
label: suggestedit

indiewebcamp-portland-10
type: item
type: MicroblogPost
title: : Had a great time at IndieWebCamp Portland 2024 this past Sunday — our 10th IndieWebCamp in Portland!https://events.indieweb.org/2024/08/indiewebcamp-portland-2024-8bucXDlLqR0kBeing a one day #IndieWebCamp, we focused more on making, hacking, and creating, than on formal discussion sessions.Nearly everyone gave a brief personal site intro with a summary of how they use their #IndieWeb site and what they would like to add, remove, or improve.* https://indieweb.org/2024/Portland/IntrosThere were lots of informal discussions, some in the main room, on the walk to and from lunch, over lunch in the nearby outdoor patio, or at tables inside the lobby of the Hotel Grand Stark.We wrapped up with our usual Create Day¹ Demos session, live streamed for remote attendees to see as well. Lots of great demos of things people built, designed, removed, cleaned-up, documented, and blogged! Everyone still at the camp showed something on their personal site!* https://indieweb.org/2024/Portland/DemosGroup photo and lots more about IndieWebCamp Portland 2024 at the event’s wiki page:* https://indieweb.org/2024/PortlandThanks to everyone who pitched in to help organize IndieWebCamp Portland 2024! Thanks especially to Marty McGuire (@martymcgui.re) for taking live notes during both the personal site intros and create day demos, to Kevin Marks (@kevinmarks@indieweb.social @kevinmarks@xoxo.zone @kevinmarks) for the IndieWebCamp live-tooting, and Ryan Barrett (@snarfed.org) for amazing breakfast pastries from Dos Hermanos.The experience definitely raised our hopes and confidence for returning to Portland in 2025.²References:¹ https://indieweb.org/Create_Day² https://indieweb.org/Planning#PortlandThis is post 19 of #100PostsOfIndieWeb. #100Posts #2024_238← https://tantek.com/2024/238/t3/indiewebcamp-auto-linking→ https://tantek.com/2024/245/t1/read-write-suggest-edit-web
link: https://status.blaise.ca/notice/116220
description: 's status on Friday, 30-Aug-2024 00:09:00 EDT
encoded: Had a great time at IndieWebCamp Portland 2024 this past Sunday — our 10th IndieWebCamp in Portland! https://events.indieweb.org/2024/08/indiewebcamp-portland-2024-8bucXDlLqR0k Being a one day #IndieWebCamp, we focused more on making, hacking, and creating, than on formal discussion sessions. Nearly everyone gave a brief personal site intro with a summary of how they use their #IndieWeb site and what they would like to add, remove, or improve. * https://indieweb.org/2024/Portland/Intros There were lots of informal discussions, some in the main room, on the walk to and from lunch, over lunch in the nearby outdoor patio, or at tables inside the lobby of the Hotel Grand Stark. We wrapped up with our usual Create Day¹ Demos session, live streamed for remote attendees to see as well. Lots of great demos of things people built, designed, removed, cleaned-up, documented, and blogged! Everyone still at the camp showed something on their personal site! * https://indieweb.org/2024/Portland/Demos Group photo and lots more about IndieWebCamp Portland 2024 at the event’s wiki page: * https://indieweb.org/2024/Portland Thanks to everyone who pitched in to help organize IndieWebCamp Portland 2024! Thanks especially to Marty McGuire (@martymcgui.re) for taking live notes during both the personal site intros and create day demos, to Kevin Marks (@kevinmarks@indieweb.social @kevinmarks@xoxo.zone @kevinmarks) for the IndieWebCamp live-tooting, and Ryan Barrett (@snarfed.org) for amazing breakfast pastries from Dos Hermanos. The experience definitely raised our hopes and confidence for returning to Portland in 2025.² References: ¹ https://indieweb.org/Create_Day ² https://indieweb.org/Planning#Portland This is post 19 of #100PostsOfIndieWeb. #100Posts #2024_238 ← https://tantek.com/2024/238/t3/indiewebcamp-auto-linking → https://tantek.com/2024/245/t1/read-write-suggest-edit-web
date: 2024-08-30T00:09:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110289
tagged: concept

concept
type: Tag
label: 2024238

indiewebcamp-auto-link
type: item
type: MicroblogPost
title: : Nice #IndieWebCamp discussion session with Kevin Marks (@kevinmarks@indieweb.social @kevinmarks@xoxo.zone @kevinmarks) on the topic of auto-linking¹.I’ve implemented an auto_link function² that handles quite a few use-cases of URLs (with or without http: or https:), @-name @-domain @-domain/path @-@-handles, hashtags(#), and footnotes(^).Much of it is based on what I’ve seen work (or implemented) on sites and software, and some of it is based on logically extending how people are using text punctuation across various services.It may be time for me to write-up an auto-link specification based on the algorithms I’ve come up with, implemented, and am using live on my site. All the algorithms work fully offline (none of them require querying a site for more info, whether well-known or otherwise), so they can be used in offline-first authoring/writing clients.I have identified three logical chunks of auto-linking functionality, each of which has different constraints and potential needs for local to the linking context information (like hashtags need a default tagspace). Each would be a good section for a new specification. Each is used by this very post.* URLs, @-s, and @-@-s* # hashtags* ^ footnotes#IndieWeb #autoLink #hashtag #hashtags #footnote #footnotesPreviously, previously, previously:* https://tantek.com/2024/070/t1/updated-auto-linking-mention-use-cases* https://tantek.com/2023/100/t1/auto-linked-hashtags-federated* https://tantek.com/2023/043/t1/footnotes-unicode-links* https://tantek.com/2023/019/t5/reply-domain-above-address-and-siloReferences:¹ https://indieweb.org/autolink² https://github.com/tantek/cassis/blob/main/cassis.jsThis is post 18 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2024/238/t1/indiewebcamp-portland→ https://tantek.com/2024/242/t1/indiewebcamp-portland
link: https://status.blaise.ca/notice/116221
description: 's status on Sunday, 25-Aug-2024 19:00:00 EDT
encoded: Nice #IndieWebCamp discussion session with Kevin Marks (@kevinmarks@indieweb.social @kevinmarks@xoxo.zone @kevinmarks) on the topic of auto-linking¹. I’ve implemented an auto_link function² that handles quite a few use-cases of URLs (with or without http: or https:), @-name @-domain @-domain/path @-@-handles, hashtags(#), and footnotes(^). Much of it is based on what I’ve seen work (or implemented) on sites and software, and some of it is based on logically extending how people are using text punctuation across various services. It may be time for me to write-up an auto-link specification based on the algorithms I’ve come up with, implemented, and am using live on my site. All the algorithms work fully offline (none of them require querying a site for more info, whether well-known or otherwise), so they can be used in offline-first authoring/writing clients. I have identified three logical chunks of auto-linking functionality, each of which has different constraints and potential needs for local to the linking context information (like hashtags need a default tagspace). Each would be a good section for a new specification. Each is used by this very post. * URLs, @-s, and @-@-s * # hashtags * ^ footnotes #IndieWeb #autoLink #hashtag #hashtags #footnote #footnotes Previously, previously, previously: * https://tantek.com/2024/070/t1/updated-auto-linking-mention-use-cases * https://tantek.com/2023/100/t1/auto-linked-hashtags-federated * https://tantek.com/2023/043/t1/footnotes-unicode-links * https://tantek.com/2023/019/t5/reply-domain-above-address-and-silo References: ¹ https://indieweb.org/autolink ² https://github.com/tantek/cassis/blob/main/cassis.js This is post 18 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2024/238/t1/indiewebcamp-portland → https://tantek.com/2024/242/t1/indiewebcamp-portland
date: 2024-08-25T19:00:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110290
enclosure: reply-domain-above-address-and-silo
links to: reply-domain-above-address-and-silo
enclosure: footnotes-unicode-links
links to: footnotes-unicode-links
enclosure: auto-linked-hashtags-federated
links to: auto-linked-hashtags-federated
enclosure: updated-auto-linking-mention-use-cases
links to: updated-auto-linking-mention-use-cases
enclosure: autolink²
links to: autolink²
enclosure: cassis.jsThis
links to: cassis.jsThis
enclosure: indiewebcamp-portland
links to: indiewebcamp-portland
tagged: concept

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

footnotes-unicode-links
date: 2023-02-14T17:50:22-05: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

updated-auto-linking-mention-use-cases
date: 2024-03-13T00:20:15-04:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : Updated the auto-linking code¹ on my website last Sunday to handle a few more @-mention use-cases.In particular:* @-domains with dashes/hyphens like @sonja-weckenmann.de* @-@ with (some) Unicode alphabetic characters like @briansuda@loðfíll.is* @-domain-and-path for indicating @-mentions of silo profiles that don’t support @-@ syntax, like @flickr.com/people/tantek or @instagram.com/tantekI also dropped auto-linking of URLs with user:password "userinfo", since they’ve been long abandoned and effectively deprecated because there’s fairly wide agreement that such "basic HTTP auth"^2 was poorly designed and should not be used (and thus should not be linked).If you’re curious you can take a look at https://tantek.com/cassis.js, which has updated functions:* auto_link_re() — regular expression to recognize URLs, @-mentions, @-@, and footnotes to link* auto_link() — specifically the code to recognize different kinds of @-@ and @-mentions and link them properly to profiles, domains, and paths.This code is only live on my website (testing in production³ as it were) for now, and you’re welcome to copy/paste to experiment with it. I plan to test it more over the coming weeks (or so) and when I feel it is sufficiently well tested, will update it on GitHub⁴ as well.With this additional auto-linking functionality, I feel I have a fairly complete implementation of how to auto-link various URLs and @-mentions, and plan to write that up at least as a minimal “list of use-cases and how they should work” auto-linking specification.This (blog post) is my contribution to today’s #IndieWebCamp Brighton⁵ #hackday!This was originally a project I wanted to complete during IndieWebCamp Nuremberg last October, however I was pre-occupied at the time with fixing other things.⁶#autolink #atmention #atmentions #atat #atatmentionThis is post 12 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2024/047/t1/indieweb-major-update-design→ 🔮¹ https://tantek.com/cassis.js² https://en.wikipedia.or…
link: https://status.blaise.ca/notice/116189
description: 's status on Sunday, 10-Mar-2024 10:55:00 EDT
encoded: Updated the auto-linking code¹ on my website last Sunday to handle a few more @-mention use-cases. In particular: * @-domains with dashes/hyphens like @sonja-weckenmann.de * @-@ with (some) Unicode alphabetic characters like @briansuda@loðfíll.is * @-domain-and-path for indicating @-mentions of silo profiles that don’t support @-@ syntax, like @flickr.com/people/tantek or @instagram.com/tantek I also dropped auto-linking of URLs with user:password "userinfo", since they’ve been long abandoned and effectively deprecated because there’s fairly wide agreement that such "basic HTTP auth"^2 was poorly designed and should not be used (and thus should not be linked). If you’re curious you can take a look at https://tantek.com/cassis.js, which has updated functions: * auto_link_re() — regular expression to recognize URLs, @-mentions, @-@, and footnotes to link * auto_link() — specifically the code to recognize different kinds of @-@ and @-mentions and link them properly to profiles, domains, and paths. This code is only live on my website (testing in production³ as it were) for now, and you’re welcome to copy/paste to experiment with it. I plan to test it more over the coming weeks (or so) and when I feel it is sufficiently well tested, will update it on GitHub⁴ as well. With this additional auto-linking functionality, I feel I have a fairly complete implementation of how to auto-link various URLs and @-mentions, and plan to write that up at least as a minimal “list of use-cases and how they should work” auto-linking specification. This (blog post) is my contribution to today’s #IndieWebCamp Brighton⁵ #hackday! This was originally a project I wanted to complete during IndieWebCamp Nuremberg last October, however I was pre-occupied at the time with fixing other things.⁶ #autolink #atmention #atmentions #atat #atatmention This is post 12 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2024/047/t1/indieweb-major-update-design → 🔮 ¹ https://tantek.com/cassis.js ² https:/…
date: 2024-03-10T10:55:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110258
tagged: concept

autolink²
date: 2024-08-25T21:56:52-04:00
type: text/html; charset=UTF-8

cassis.jsThis
date: 2024-08-25T21:56:53-04:00
type: text/html; charset=utf-8

indiewebcamp-portland
date: 2024-08-25T21:56:53-04:00
type: text/html; charset=UTF-8
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: autolink

concept
type: Tag
label: footnote

concept
type: Tag
label: footnotespreviously

concept
type: Tag
label: hashtag

concept
type: Tag
label: hashtags

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
enclosure: years-posse-microformats-adoption
links to: years-posse-microformats-adoption
tagged: concept

POSSE
date: 2020-01-02T00:13:24-05:00
type: text/html; charset=UTF-8

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

h-cardh-entry
date: 2023-02-16T20:15:30-05:00
type: text/html; charset=UTF-8

microformats.org
date: 2023-06-21T04:00:16-04:00
type: text/html; charset=UTF-8

anniversaries-microformats-posse
date: 2023-08-22T19:29:07-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

posse-posting-activitypub-standard-twitter-tumblr-mastodon):
date: 2024-06-22T03:08:12-04:00
length: 11
type: text

):
date: 2024-06-22T03:08:14-04:00
type: text/html; charset=UTF-8

https://www.mollywhite.net/micro/entry/202403091817
date: 2024-06-22T03:08:16-04:00
length: 10866
type: text/html; charset=utf-8

dev*
date: 2024-06-22T03:08:16-04:00
length: 169
type: text/html

bottom
date: 2024-06-22T03:08:17-04:00
type: text/html; charset=UTF-8

minimum-interesting-service-worker
date: 2024-06-22T03:08:21-04:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : Yesterday I proposed the idea of a “minimum interesting service worker” that could provide a link (or links) to archives or mirrors when your site was unavailable as one possible solution to the desire to make personal #indieweb sites more reliable by providing at least a user path to “soft repair” links to your site that may otherwise seem broken.Minimum because it only requires two files and one line of script in site footer template, and interesting because it provides both a novel user benefit and personal site publisher benefits.The idea occurred to me during an informal coffee chat over Zoom with a couple of other Indieweb community folks yesterday, and afterwards I braindumped a bit into the IndieWeb Developers Chat channel¹. Figured it was worth writing up rather than waiting to implement it.Basic idea:You have a service worker (and “offline” HTML page) on your personal site, installed from any page on your site, that all it does is cache the offline page, and on future requests to your site checks to see if the requested page is available, and if so serves it, otherwise it displays your offline page with a “site appears to be unreachable” message that a lot of service workers provide, AND provides an algorithmically constructed link to the page on an archive (e.g. Internet Archive) or static mirror of your site (typically at another domain).This is minimal because it requires only two files: your service worker (a JS file) and your offline page (a minimal self-contained static HTML file with inline CSS). Doable in <1k bytes of code, with no additional local caching or storage requirements, thus a negligible impact on site visitors (likely less than the cookies that major sites store).User benefit:If someone has ever visited your personal site, then in the future whenever they click a link to your pages or posts, if your site/domain is unavailable for any reason, then the reader would see a notice (from your offline page) and a link to view an archive/mirr…
link: https://status.blaise.ca/notice/116203
description: 's status on Thursday, 30-May-2024 14:21:00 EDT
encoded: Yesterday I proposed the idea of a “minimum interesting service worker” that could provide a link (or links) to archives or mirrors when your site was unavailable as one possible solution to the desire to make personal #indieweb sites more reliable by providing at least a user path to “soft repair” links to your site that may otherwise seem broken. Minimum because it only requires two files and one line of script in site footer template, and interesting because it provides both a novel user benefit and personal site publisher benefits. The idea occurred to me during an informal coffee chat over Zoom with a couple of other Indieweb community folks yesterday, and afterwards I braindumped a bit into the IndieWeb Developers Chat channel¹. Figured it was worth writing up rather than waiting to implement it. Basic idea: You have a service worker (and “offline” HTML page) on your personal site, installed from any page on your site, that all it does is cache the offline page, and on future requests to your site checks to see if the requested page is available, and if so serves it, otherwise it displays your offline page with a “site appears to be unreachable” message that a lot of service workers provide, AND provides an algorithmically constructed link to the page on an archive (e.g. Internet Archive) or static mirror of your site (typically at another domain). This is minimal because it requires only two files: your service worker (a JS file) and your offline page (a minimal self-contained static HTML file with inline CSS). Doable in <1k bytes of code, with no additional local caching or storage requirements, thus a negligible impact on site visitors (likely less than the cookies that major sites store). User benefit: If someone has ever visited your personal site, then in the future whenever they click a link to your pages or posts, if your site/domain is unavailable for any reason, then the reader would see a notice (from your offline page) and a link to view an archive…
date: 2024-05-30T14:21:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110272
enclosure: web.archive.org
links to: web.archive.org
enclosure: created-at-indiewebcamp-brighton
links to: created-at-indiewebcamp-brighton
enclosure: GitHub PagesHTML
links to: GitHub PagesHTML
enclosure: HTMLJS
links to: HTMLJS
enclosure: jsrel-canonical
links to: jsrel-canonical
enclosure: rel-canonicalservice
links to: rel-canonicalservice
enclosure: service workerSpiderpig
links to: service workerSpiderpig
enclosure: SpiderpigSSG
links to: SpiderpigSSG
enclosure: SSG
links to: SSG
enclosure: t1717006352142600²
links to: t1717006352142600²
enclosure: Trigger an Archive
links to: Trigger an Archive
tagged: concept

CMSh-card
date: 2024-06-22T03:08:23-04:00
type: text/html; charset=UTF-8

h-entryh-feed
date: 2024-06-22T03:08:24-04:00
type: text/html; charset=UTF-8

h-feedmicroformats2
date: 2024-06-22T03:08:24-04:00
type: text/html; charset=UTF-8

microformats2-parsingrel-me
date: 2024-06-22T03:08:25-04:00
type: text/html; charset=UTF-8

rel-meSSG
date: 2024-06-22T03:08:26-04:00
type: text/html; charset=UTF-8

SSGWebmention
date: 2024-06-22T03:08:26-04:00
type: text/html; charset=UTF-8

WebmentionWithknown
date: 2024-06-22T03:08:27-04:00
type: text/html; charset=UTF-8

KnownReferences:¹
date: 2024-06-22T03:08:28-04:00
type: text/html; charset=UTF-8

Letterboxd
date: 2024-06-22T03:08:30-04:00
type: text/html; charset=UTF-8

concept
type: Tag
label: distributed

concept
type: Tag
label: letterboxd

concept
type: Tag
label: microformats2

concept
type: Tag
label: relme

concept
type: Tag
label: threads

concept
type: Tag
label: verification

concept
type: Tag
label: webmentionbeyond

web.archive.org
date: 2024-05-30T16:05:17-04:00
type: text/html

created-at-indiewebcamp-brighton
date: 2024-05-30T16:05:19-04:00
type: text/html; charset=UTF-8
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

GitHub PagesHTML
date: 2024-05-30T16:05:20-04:00
type: text/html; charset=UTF-8

HTMLJS
date: 2024-05-30T16:05:21-04:00
type: text/html; charset=UTF-8

jsrel-canonical
date: 2024-05-30T16:05:22-04:00
type: text/html; charset=UTF-8

rel-canonicalservice
date: 2024-05-30T16:05:23-04:00
type: text/html; charset=UTF-8

service workerSpiderpig
date: 2024-05-30T16:05:24-04:00
type: text/html; charset=UTF-8

SpiderpigSSG
date: 2024-05-30T16:05:25-04:00
type: text/html; charset=UTF-8

SSG
date: 2024-05-30T16:05:26-04:00
type: text/html; charset=UTF-8

t1717006352142600²
date: 2024-05-30T16:05:28-04:00
type: text/html; charset=utf-8

Trigger an Archive
date: 2024-05-30T16:05:28-04:00
type: text/html; charset=UTF-8

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

https://indieweb.org/wiki/index.php
date: 2024-03-13T00:20:13-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

concept
type: Tag
label: atatmentionthis

concept
type: Tag
label: hackday

indieweb-major-update-design
type: item
type: MicroblogPost
title: : New this week: the #IndieWeb community deployed a major modern update to the design, usability, and cross-device support of the https://indieweb.org/ home page and wiki in general! In brief:* Updated MediaWiki install, updated themes, better mobile device support* New default theme: Vector (2022), the same as English Wikipedia* Lots of CSS fixes for content, sidebars, etc.* Home page content simplification and more pleasing design updateLots more details on the 2024 homepage and design update project page:* https://indieweb.org/2024/homepageThis was a community effort, with many people pitching in with major & minor contributions, spending weeks, days, hours, or a few minutes here and there helping out. From server work, to PHP coding, to HTML+CSS (re)coding, to testing variants of MediaWiki themes, browsers, and devices.Huge thanks in particular to @PaulRobertLloyd.com for both driving this design update (e.g. said project page) and doing the heavy lifting of debugging, patching, and testing the latest MediaWiki Vector theme, documenting before & after screenshots, and @AaronParecki.com for all the server-side software updates, PHP/IndieAuth wrangling, and critical devops too.Go try the new https://indieweb.org/ on any browser, on any device, and share your experience!#IndieNewsThis is post 11 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2024/046/t1/the-ephemeral-web→ 🔮
link: https://status.blaise.ca/notice/116172
description: 's status on Friday, 16-Feb-2024 17:25:00 EST
encoded: New this week: the #IndieWeb community deployed a major modern update to the design, usability, and cross-device support of the https://indieweb.org/ home page and wiki in general! In brief: * Updated MediaWiki install, updated themes, better mobile device support * New default theme: Vector (2022), the same as English Wikipedia * Lots of CSS fixes for content, sidebars, etc. * Home page content simplification and more pleasing design update Lots more details on the 2024 homepage and design update project page: * https://indieweb.org/2024/homepage This was a community effort, with many people pitching in with major & minor contributions, spending weeks, days, hours, or a few minutes here and there helping out. From server work, to PHP coding, to HTML+CSS (re)coding, to testing variants of MediaWiki themes, browsers, and devices. Huge thanks in particular to @PaulRobertLloyd.com for both driving this design update (e.g. said project page) and doing the heavy lifting of debugging, patching, and testing the latest MediaWiki Vector theme, documenting before & after screenshots, and @AaronParecki.com for all the server-side software updates, PHP/IndieAuth wrangling, and critical devops too. Go try the new https://indieweb.org/ on any browser, on any device, and share your experience! #IndieNews This is post 11 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2024/046/t1/the-ephemeral-web → 🔮
date: 2024-02-16T17:25:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110245
tagged: concept

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

indiewebcamp-brighton-tickets-available
date: 2024-02-15T19:54:52-05:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : #Brighton #London and other #England & #Europe friends:🎪 #IndieWebCamp Brighton tickets are available!🎟 https://ti.to/indiewebcamp/brighton-2024🗓 2024-03-09…10🏢 The Skiff, Brighton, England🌐 https://indieweb.org/2024/BrightonGrab an in-person ticket (limited capacity) then optionally add yourself to the list of participants: https://indieweb.org/2024/Brighton#In_personFor more information, see organizer @paulrobertlloyd.com (@paulrobertlloyd@mastodon.social)’s post: https://paulrobertlloyd.com/2024/032/a1/indiewebcamp_brighton/Also check out @ClearLeft.com (@clearleft@mastodon.social @clearleft)’s “Patterns Day” (https://patternsday.com/) in Brighton the Thursday (2024-03-07) beforehand!Previously: https://tantek.com/2024/022/t1/indiewebcamp-brighton-plannedThis is post 9 of #100PostsOfIndieWeb. #100Posts #IndieWeb← https://tantek.com/2024/035/t1/greshams-law-developers-users-jargon→ 🔮
link: https://status.blaise.ca/notice/116167
description: 's status on Sunday, 04-Feb-2024 23:08:00 EST
encoded: #Brighton #London and other #England & #Europe friends: 🎪 #IndieWebCamp Brighton tickets are available! 🎟 https://ti.to/indiewebcamp/brighton-2024 🗓 2024-03-09…10 🏢 The Skiff, Brighton, England 🌐 https://indieweb.org/2024/Brighton Grab an in-person ticket (limited capacity) then optionally add yourself to the list of participants: https://indieweb.org/2024/Brighton#In_person For more information, see organizer @paulrobertlloyd.com (@paulrobertlloyd@mastodon.social)’s post: https://paulrobertlloyd.com/2024/032/a1/indiewebcamp_brighton/ Also check out @ClearLeft.com (@clearleft@mastodon.social @clearleft)’s “Patterns Day” (https://patternsday.com/) in Brighton the Thursday (2024-03-07) beforehand! Previously: https://tantek.com/2024/022/t1/indiewebcamp-brighton-planned This is post 9 of #100PostsOfIndieWeb. #100Posts #IndieWeb ← https://tantek.com/2024/035/t1/greshams-law-developers-users-jargon → 🔮
date: 2024-02-04T23:08:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110240
enclosure: indiewebcamp-brighton-planned
links to: indiewebcamp-brighton-planned
enclosure: brighton-2024
links to: brighton-2024
enclosure: BrightonGrab
links to: BrightonGrab
enclosure: In personFor
links to: In personFor
enclosure: Also
links to: Also
enclosure: patternsday.com
links to: patternsday.com
enclosure: greshams-law-developers-users-jargon
links to: greshams-law-developers-users-jargon
tagged: concept

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

indiewebcamp-brighton-planned
date: 2024-01-23T21:32:47-05:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : The first IndieWebCamp of the year has been planned!🎪 IndieWebCamp Brighton🗓 2024-03-09…10🏢 The Skiff, Brighton, England🎟 Tickets available 2024-02-01!Event: https://events.indieweb.org/2024/03/indiewebcamp-brighton-2024-xRTP2hAZOvZdWiki: https://indieweb.org/2024/Brighton Questions about #IndieWebCamp? Ask in #IndieWeb chat!💬 https://chat.indieweb.org/This is post 3 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2024/003/t1/2023-indieweb-gift-calendar-numbers→ 🔮
link: https://status.blaise.ca/notice/116159
description: 's status on Tuesday, 23-Jan-2024 02:20:00 EST
encoded: The first IndieWebCamp of the year has been planned! 🎪 IndieWebCamp Brighton 🗓 2024-03-09…10 🏢 The Skiff, Brighton, England 🎟 Tickets available 2024-02-01! Event: https://events.indieweb.org/2024/03/indiewebcamp-brighton-2024-xRTP2hAZOvZd Wiki: https://indieweb.org/2024/Brighton Questions about #IndieWebCamp? Ask in #IndieWeb chat! 💬 https://chat.indieweb.org/ This is post 3 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2024/003/t1/2023-indieweb-gift-calendar-numbers → 🔮
date: 2024-01-23T02:20:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110232
tagged: concept

brighton-2024
date: 2024-02-05T01:17:30-05:00
type: text/html; charset=utf-8

BrightonGrab
date: 2024-02-05T01:17:31-05:00
type: text/html; charset=UTF-8

In personFor
date: 2024-02-05T01:17:32-05:00
type: text/html; charset=UTF-8

Also
date: 2024-02-05T01:17:33-05:00
type: text/html; charset=utf-8

patternsday.com
date: 2024-02-05T01:17:34-05:00
length: 44627
type: text/html; charset=UTF-8

greshams-law-developers-users-jargon
date: 2024-02-05T01:17:35-05:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : Similar to @paulgraham.com (@paulg@mas.to @paulg)’s 2008 observation about trolls¹, there’s a sort of Gresham's Law of developers (vs users): developers are willing to use a forum with a lot of users in it, but users aren’t willing to use a forum with a lot of developer-speak.Whether such forums are email lists, chat (IRC, #Matrix, #Slack, #Discord), or, well, online forums (#Reddit, #HackerNews), when discussions either start or shift into technical details, jargon, or acronyms, users (in a very broad sense) tend to stop participating, and sometimes leave, never to return.Users in this context are anyone with a desire (or a preference) not to chat or even be bothered spending time reading about technical plumbing & #jargon, and see such discussions as a distraction at best, and more like noise to be avoided.Paraphrasing Paul Graham again: once technical details, jargon, acronyms “take hold, it tends to become the dominant culture” and discourages users from showing up, discussing user-centric topics, or even staying in said forum.The #IndieWeb community started in 2011 as a single #indiewebcamp IRC channel (no email list²) because it was tightly coupled to IndieWebCamp events, which were both highly technical and yet focused on actually making things work on your personal site that you need³, that you will use⁴ yourself. Conversations bridged real world use-cases and technical details.It only took us five years after the first IndieWebCamp in Portland to recognize that the community had grown beyond the events, and had a clear need for a separate place for deep discussions of developer topics.As part of renaming the community from IndieWebCamp to IndieWeb⁵, we created the #indieweb-dev (dev) channel for such technical topics like protocols, formats, tools, coding libraries, APIs, and any other acronyms or jargon.The community did a good job of keeping technical topics in the dev channel, and encouraging new folks in the main #indieweb channel who started technica…
link: https://status.blaise.ca/notice/116166
description: 's status on Sunday, 04-Feb-2024 18:05:00 EST
encoded: Similar to @paulgraham.com (@paulg@mas.to @paulg)’s 2008 observation about trolls¹, there’s a sort of Gresham's Law of developers (vs users): developers are willing to use a forum with a lot of users in it, but users aren’t willing to use a forum with a lot of developer-speak. Whether such forums are email lists, chat (IRC, #Matrix, #Slack, #Discord), or, well, online forums (#Reddit, #HackerNews), when discussions either start or shift into technical details, jargon, or acronyms, users (in a very broad sense) tend to stop participating, and sometimes leave, never to return. Users in this context are anyone with a desire (or a preference) not to chat or even be bothered spending time reading about technical plumbing & #jargon, and see such discussions as a distraction at best, and more like noise to be avoided. Paraphrasing Paul Graham again: once technical details, jargon, acronyms “take hold, it tends to become the dominant culture” and discourages users from showing up, discussing user-centric topics, or even staying in said forum. The #IndieWeb community started in 2011 as a single #indiewebcamp IRC channel (no email list²) because it was tightly coupled to IndieWebCamp events, which were both highly technical and yet focused on actually making things work on your personal site that you need³, that you will use⁴ yourself. Conversations bridged real world use-cases and technical details. It only took us five years after the first IndieWebCamp in Portland to recognize that the community had grown beyond the events, and had a clear need for a separate place for deep discussions of developer topics. As part of renaming the community from IndieWebCamp to IndieWeb⁵, we created the #indieweb-dev (dev) channel for such technical topics like protocols, formats, tools, coding libraries, APIs, and any other acronyms or jargon. The community did a good job of keeping technical topics in the dev channel, and encouraging new folks in the main #indieweb channel who started tec…
date: 2024-02-04T18:05:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110239
enclosure: indieweb-for-everyone-internet-of-people
links to: indieweb-for-everyone-internet-of-people
enclosure: earthquake-sanfrancisco-shifted
links to: earthquake-sanfrancisco-shifted
enclosure: IndieWebIndieWebCamp
links to: IndieWebIndieWebCamp
enclosure: jargonLoqi
links to: jargonLoqi
enclosure: Loqimain
links to: Loqimain
enclosure: metaMediaWiki
links to: metaMediaWiki
enclosure: Project:Categoriesplumbing
links to: Project:Categoriesplumbing
enclosure: plumbingprotocol
links to: plumbingprotocol
enclosure: silos¹
links to: silos¹
enclosure: Email³
links to: Email³
enclosure: make what you need⁴
links to: make what you need⁴
enclosure: use what you make⁵
links to: use what you make⁵
enclosure: rename to IndieWeb⁶
links to: rename to IndieWeb⁶
enclosure: jargon⁷
links to: jargon⁷
enclosure: Loqi Nudge⁸
links to: Loqi Nudge⁸
enclosure: Chat Channels Purposes⁹
links to: Chat Channels Purposes⁹
enclosure: t1705883690759800
links to: t1705883690759800
enclosure: devDiscord
links to: devDiscord
enclosure: Discordformat
links to: Discordformat
enclosure: formatHacker
links to: formatHacker
enclosure: Hacker NewsIndieWeb
links to: Hacker NewsIndieWeb
enclosure: IndieWebCampIRC
links to: IndieWebCampIRC
enclosure: IRCjargon
links to: IRCjargon
enclosure: indiewebMatrix
links to: indiewebMatrix
enclosure: Matrixmeta
links to: Matrixmeta
enclosure: protocolReddit
links to: protocolReddit
enclosure: Reddittools
links to: Reddittools
enclosure: toolsSlack
links to: toolsSlack
enclosure: Slacksocial
links to: Slacksocial
enclosure: trolls.html
links to: trolls.html
tagged: concept

concept
type: Tag
label: brighton

concept
type: Tag
label: england

concept
type: Tag
label: europe

concept
type: Tag
label: london

indieweb-for-everyone-internet-of-people
date: 2024-01-27T06:09:55-05:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : The #IndieWeb is for everyone, everyone who wants to be part of the world-wide-web of interconnected people. The social internet of people, a network of networks of people, connected peer-to-peer in human-scale groups, communities of locality and affinity.These peer-to-peer links should not require corporate platforms or other organizational intermediaries, nor should they require depending on developer intermediaries, nor server administrator intermediaries.This is the "indie" in IndieWeb, independence from intermediaries, not independence from people. Because the "web" in IndieWeb, is yes the Web of the World Wide Web, and it is also the Web of people.The "indie" in IndieWeb is also the independent agency to opt-into human-scale groups, opt-into peer-to-peer connections, opt-into communities, opt-into publics. As the POSSE page says: “Figure out how you want to fit into the network”. The "web" in IndieWeb is also an open acknowledgment and acceptance that regardless of what groups, connections, communities, and publics you opt-into, that they are all interconnected in a larger web, that even without connecting, you can accept and respect from a distance.The IndieWeb is for everyone, everyone who wants independence from organizations, independence of agency to associate, and who embraces the web of humans that want to interconnect, to communicate, to value and respect each other, whether one degree apart or thirty.¹This is post 5 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2024/023/t1/should-public-posts-flow-across-sites→ 🔮Post glossary:IndieWeb https://indieweb.org/POSSE https://indieweb.org/POSSEpublics https://indieweb.org/publics¹: https://www.theguardian.com/technology/2008/aug/03/internet.email
link: https://status.blaise.ca/notice/116161
description: 's status on Saturday, 27-Jan-2024 01:40:00 EST
encoded: The #IndieWeb is for everyone, everyone who wants to be part of the world-wide-web of interconnected people. The social internet of people, a network of networks of people, connected peer-to-peer in human-scale groups, communities of locality and affinity. These peer-to-peer links should not require corporate platforms or other organizational intermediaries, nor should they require depending on developer intermediaries, nor server administrator intermediaries. This is the "indie" in IndieWeb, independence from intermediaries, not independence from people. Because the "web" in IndieWeb, is yes the Web of the World Wide Web, and it is also the Web of people. The "indie" in IndieWeb is also the independent agency to opt-into human-scale groups, opt-into peer-to-peer connections, opt-into communities, opt-into publics. As the POSSE page says: “Figure out how you want to fit into the network”. The "web" in IndieWeb is also an open acknowledgment and acceptance that regardless of what groups, connections, communities, and publics you opt-into, that they are all interconnected in a larger web, that even without connecting, you can accept and respect from a distance. The IndieWeb is for everyone, everyone who wants independence from organizations, independence of agency to associate, and who embraces the web of humans that want to interconnect, to communicate, to value and respect each other, whether one degree apart or thirty.¹ This is post 5 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2024/023/t1/should-public-posts-flow-across-sites → 🔮 Post glossary: IndieWeb https://indieweb.org/ POSSE https://indieweb.org/POSSE publics https://indieweb.org/publics ¹: https://www.theguardian.com/technology/2008/aug/03/internet.email
date: 2024-01-27T01:40:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110234
tagged: concept

earthquake-sanfrancisco-shifted
date: 2024-02-04T21:30:22-05:00
type: text/html; charset=UTF-8
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

IndieWebIndieWebCamp
date: 2024-02-04T21:30:25-05:00
type: text/html; charset=UTF-8

jargonLoqi
date: 2024-02-04T21:30:26-05:00
type: text/html; charset=UTF-8

Loqimain
date: 2024-02-04T21:30:27-05:00
type: text/html; charset=UTF-8

metaMediaWiki
date: 2024-02-04T21:30:29-05:00
type: text/html; charset=UTF-8

Project:Categoriesplumbing
date: 2024-02-04T21:30:30-05:00
type: text/html; charset=UTF-8

plumbingprotocol
date: 2024-02-04T21:30:31-05:00
type: text/html; charset=UTF-8

silos¹
date: 2024-02-04T21:30:33-05:00
type: text/html; charset=UTF-8

Email³
date: 2024-02-04T21:30:34-05:00
type: text/html; charset=UTF-8

make what you need⁴
date: 2024-02-04T21:30:35-05:00
type: text/html; charset=UTF-8

use what you make⁵
date: 2024-02-04T21:30:36-05:00
type: text/html; charset=UTF-8

rename to IndieWeb⁶
date: 2024-02-04T21:30:37-05:00
type: text/html; charset=UTF-8

jargon⁷
date: 2024-02-04T21:30:38-05:00
type: text/html; charset=UTF-8

Loqi Nudge⁸
date: 2024-02-04T21:30:39-05:00
type: text/html; charset=UTF-8

Chat Channels Purposes⁹
date: 2024-02-04T21:30:41-05:00
type: text/html; charset=UTF-8

t1705883690759800
date: 2024-02-04T21:30:43-05:00
type: text/html; charset=utf-8

devDiscord
date: 2024-02-05T00:34:49-05:00
type: text/html; charset=UTF-8

Discordformat
date: 2024-02-05T00:34:50-05:00
type: text/html; charset=UTF-8

formatHacker
date: 2024-02-05T00:34:51-05:00
type: text/html; charset=UTF-8

Hacker NewsIndieWeb
date: 2024-02-05T00:34:52-05:00
type: text/html; charset=UTF-8

IndieWebCampIRC
date: 2024-02-05T00:34:53-05:00
type: text/html; charset=UTF-8

IRCjargon
date: 2024-02-05T00:34:54-05:00
type: text/html; charset=UTF-8

indiewebMatrix
date: 2024-02-05T00:34:55-05:00
type: text/html; charset=UTF-8

Matrixmeta
date: 2024-02-05T00:34:56-05:00
type: text/html; charset=UTF-8

protocolReddit
date: 2024-02-05T00:34:57-05:00
type: text/html; charset=UTF-8

Reddittools
date: 2024-02-05T00:34:58-05:00
type: text/html; charset=UTF-8

toolsSlack
date: 2024-02-05T00:34:59-05:00
type: text/html; charset=UTF-8

Slacksocial
date: 2024-02-05T00:34:59-05:00
type: text/html; charset=UTF-8

trolls.html
date: 2024-02-05T00:35:00-05:00
type: text/html

concept
type: Tag
label: discord

concept
type: Tag
label: hackernews

concept
type: Tag
label: jargon

concept
type: Tag
label: matrix

concept
type: Tag
label: slack

gresham-law-developers-users-jargon
type: item
type: MicroblogPost
title: : Similar to @paulgraham.com (@paulg@mas.to @paulg)’s observation about trolls¹, there’s a sort of Gresham's Law of developers (vs users): developers are willing to use a forum with a lot of users in it, but users aren’t willing to use a forum with a lot of developer-speak.Whether such forums are email lists, chat (IRC, #Matrix, #Slack, #Discord), or, well, online forums (#Reddit, #HackerNews), when discussions either start or shift into technical details, jargon, or acronyms, users (in a very broad sense) tend to stop participating, and sometimes leave, never to return.Users in this context are anyone with a desire (or a preference) not to chat or even be bothered spending time reading about technical plumbing & #jargon, and see such discussions as a distraction at best, and more like noise to be avoided.Paraphrasing Paul Graham again: once technical details, jargon, acronyms “take hold, it tends to become the dominant culture” and discourages users from showing up, discussing user-centric topics, or even staying in said forum.The #IndieWeb community started in 2011 as a single IRC channel #indiewebcamp (no email list²) because it was tightly coupled to IndieWebCamp events, which were both highly technical and yet focused on actually making things work on your personal site that you need³, that you will use⁴ yourself. Conversations bridged real world use-cases and technical details.It only took us five years after the first IndieWebCamp in Portland to recognize that the community had grown beyond the events, and had a clear need for a separate place for deep discussions of developer topics.As part of renaming the community from IndieWebCamp to IndieWeb⁵, we created the #indieweb-dev (dev) channel for such technical topics like protocols, formats, tools, coding libraries, APIs, and any other acronyms or jargon.The community did a good job of keeping technical topics in the dev channel, and encouraging new folks in the main #indieweb channel who started technical con…
link: https://status.blaise.ca/notice/116165
description: 's status on Sunday, 04-Feb-2024 18:05:00 EST
encoded: Similar to @paulgraham.com (@paulg@mas.to @paulg)’s observation about trolls¹, there’s a sort of Gresham's Law of developers (vs users): developers are willing to use a forum with a lot of users in it, but users aren’t willing to use a forum with a lot of developer-speak. Whether such forums are email lists, chat (IRC, #Matrix, #Slack, #Discord), or, well, online forums (#Reddit, #HackerNews), when discussions either start or shift into technical details, jargon, or acronyms, users (in a very broad sense) tend to stop participating, and sometimes leave, never to return. Users in this context are anyone with a desire (or a preference) not to chat or even be bothered spending time reading about technical plumbing & #jargon, and see such discussions as a distraction at best, and more like noise to be avoided. Paraphrasing Paul Graham again: once technical details, jargon, acronyms “take hold, it tends to become the dominant culture” and discourages users from showing up, discussing user-centric topics, or even staying in said forum. The #IndieWeb community started in 2011 as a single IRC channel #indiewebcamp (no email list²) because it was tightly coupled to IndieWebCamp events, which were both highly technical and yet focused on actually making things work on your personal site that you need³, that you will use⁴ yourself. Conversations bridged real world use-cases and technical details. It only took us five years after the first IndieWebCamp in Portland to recognize that the community had grown beyond the events, and had a clear need for a separate place for deep discussions of developer topics. As part of renaming the community from IndieWebCamp to IndieWeb⁵, we created the #indieweb-dev (dev) channel for such technical topics like protocols, formats, tools, coding libraries, APIs, and any other acronyms or jargon. The community did a good job of keeping technical topics in the dev channel, and encouraging new folks in the main #indieweb channel who started technica…
date: 2024-02-04T18:05:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110238
enclosure: indieweb-for-everyone-internet-of-people
links to: indieweb-for-everyone-internet-of-people
enclosure: earthquake-sanfrancisco-shifted
links to: earthquake-sanfrancisco-shifted
enclosure: devformat
links to: devformat
enclosure: formatIndieWeb
links to: formatIndieWeb
enclosure: IndieWebIndieWebCamp
links to: IndieWebIndieWebCamp
enclosure: IndieWebCampjargon
links to: IndieWebCampjargon
enclosure: jargonLoqi
links to: jargonLoqi
enclosure: Loqimain
links to: Loqimain
enclosure: indiewebmeta
links to: indiewebmeta
enclosure: metaMediaWiki
links to: metaMediaWiki
enclosure: Project:Categoriesplumbing
links to: Project:Categoriesplumbing
enclosure: plumbingprotocol
links to: plumbingprotocol
enclosure: protocoltools
links to: protocoltools
enclosure: toolssocial
links to: toolssocial
enclosure: silos¹
links to: silos¹
links to: trolls.html²
enclosure: Email³
links to: Email³
enclosure: make what you need⁴
links to: make what you need⁴
enclosure: use what you make⁵
links to: use what you make⁵
enclosure: rename to IndieWeb⁶
links to: rename to IndieWeb⁶
enclosure: jargon⁷
links to: jargon⁷
enclosure: Loqi Nudge⁸
links to: Loqi Nudge⁸
enclosure: Chat Channels Purposes⁹
links to: Chat Channels Purposes⁹
enclosure: t1705883690759800
links to: t1705883690759800
tagged: concept

devformat
date: 2024-02-04T21:30:22-05:00
type: text/html; charset=UTF-8

formatIndieWeb
date: 2024-02-04T21:30:24-05:00
type: text/html; charset=UTF-8

IndieWebCampjargon
date: 2024-02-04T21:30:26-05:00
type: text/html; charset=UTF-8

indiewebmeta
date: 2024-02-04T21:30:28-05:00
type: text/html; charset=UTF-8

protocoltools
date: 2024-02-04T21:30:32-05:00
type: text/html; charset=UTF-8

toolssocial
date: 2024-02-04T21:30:33-05: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
type: item
type: MicroblogPost
title: : For the #IndieWeb ideals of independence from intermediaries, not requiring corporate platforms or other organizational intermediaries¹, the best systems we have still depend on organizations. However they are all swappable, at will, by the individual:1. domain names, depend on registrars, which you can switch 2. web hosts, depend on hosting providers, which you can switch3. internet access, depends on internet service providers, which you can switch4. web browsing, depends on browsers, which you can switch5. personal devices, that have choice of web browser and internet access, which you can switch, upgrade, and use multiples of simultaneouslyWhen you can migrate from one provider to another, one device to another, without disruption, without breaking your people-to-people connections, the providers and devices serve you, instead of gatekeeping you.This freedom to swap, freedom to choose, depends on practical #interoperability across multiple implementations, multiple services. Open standards are the means to encouraging, testing, and verifying this user-feature interoperability across implementations and services.This is post 6 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2024/026/t3/indieweb-for-everyone-internet-of-people→ 🔮Post glossary:domain name https://indieweb.org/personal-domaininteroperability https://www.w3.org/wiki/Interoperableweb host https://indieweb.org/web_host¹ https://tantek.com/2024/026/t3/indieweb-for-everyone-internet-of-people
link: https://status.blaise.ca/notice/116162
description: 's status on Saturday, 27-Jan-2024 03:13:00 EST
encoded: For the #IndieWeb ideals of independence from intermediaries, not requiring corporate platforms or other organizational intermediaries¹, the best systems we have still depend on organizations. However they are all swappable, at will, by the individual: 1. domain names, depend on registrars, which you can switch 2. web hosts, depend on hosting providers, which you can switch 3. internet access, depends on internet service providers, which you can switch 4. web browsing, depends on browsers, which you can switch 5. personal devices, that have choice of web browser and internet access, which you can switch, upgrade, and use multiples of simultaneously When you can migrate from one provider to another, one device to another, without disruption, without breaking your people-to-people connections, the providers and devices serve you, instead of gatekeeping you. This freedom to swap, freedom to choose, depends on practical #interoperability across multiple implementations, multiple services. Open standards are the means to encouraging, testing, and verifying this user-feature interoperability across implementations and services. This is post 6 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2024/026/t3/indieweb-for-everyone-internet-of-people → 🔮 Post glossary: domain name https://indieweb.org/personal-domain interoperability https://www.w3.org/wiki/Interoperable web host https://indieweb.org/web_host ¹ https://tantek.com/2024/026/t3/indieweb-for-everyone-internet-of-people
date: 2024-01-27T03:13:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110235
enclosure: indieweb-for-everyone-internet-of-people
links to: indieweb-for-everyone-internet-of-people
enclosure: personal-domaininteroperability
links to: personal-domaininteroperability
enclosure: Interoperableweb
links to: Interoperableweb
enclosure: web host¹
links to: web host¹
tagged: concept

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

personal-domaininteroperability
date: 2024-01-27T06:09:56-05:00
type: text/html; charset=UTF-8

Interoperableweb
date: 2024-01-27T06:09:57-05:00
length: 19722
type: text/html; charset=UTF-8

web host¹
date: 2024-01-27T06:09:58-05:00
type: text/html; charset=UTF-8

concept
type: Tag
label: interoperability

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

backfeedblog
date: 2024-01-23T21:32:48-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

2023-indieweb-gift-calendar-numbers
type: item
type: MicroblogPost
title: : 31 days of #IndieWeb gifts: the _2023 IndieWeb Gift Calendar_ (https://indieweb.org/2023-12-indieweb-gift-calendar) wrapped up a full month of IndieWeb-related creations & updates from the community (and sometimes beyond) to everyone who wants to improve their #IndieWeb experience. From plugins & libraries, to tools & services, to events & meetups, to web components & wiki pages, and blog posts & newsletters, there was something for everyone.Some numbers:🎁 67 total gifts📄 32 new IndieWeb wiki pages📜 7 posts on improving blogs, IndieWeb specs, and event summaries💻 6 Homebrew Website Club online meetups📫 5 This Week In The IndieWeb newsletters🧱 4 library updates: new web components, #microformats2 parser update 🌉 3 Bridgy Fed updates & improvements 🧩 2 plugin updates: #Elgg IndieWeb & #WordPress #IndieAuth🎪 1 #IndieWebCamp San Diego (2 days!)📚 1 indiebookclub new year in review overview feature📽 1 IndieWeb movie viewings aggregator🧶 1 #Threads federating out #ActivityPub (followable by #BridgyFed)Gift were shared by:👥 20 individuals🏢 1 companyI compiled these numbers by hand. Let me know if you see any errors. There are many more potential stats like:* average (mean and median) number of gifts per contributor* how many edits to the Gift Calendar wiki page* how many different editors of the wiki page* average (mean and median) number of edits per editorI’ll leave those as exercises for others if they wish!This is post 2 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2024/001/t1/restarting-100days-indieweb-gift-calendar→ 🔮
link: https://status.blaise.ca/notice/116151
description: 's status on Wednesday, 03-Jan-2024 19:09:00 EST
encoded: 31 days of #IndieWeb gifts: the _2023 IndieWeb Gift Calendar_ (https://indieweb.org/2023-12-indieweb-gift-calendar) wrapped up a full month of IndieWeb-related creations & updates from the community (and sometimes beyond) to everyone who wants to improve their #IndieWeb experience. From plugins & libraries, to tools & services, to events & meetups, to web components & wiki pages, and blog posts & newsletters, there was something for everyone. Some numbers: 🎁 67 total gifts 📄 32 new IndieWeb wiki pages 📜 7 posts on improving blogs, IndieWeb specs, and event summaries 💻 6 Homebrew Website Club online meetups 📫 5 This Week In The IndieWeb newsletters 🧱 4 library updates: new web components, #microformats2 parser update 🌉 3 Bridgy Fed updates & improvements 🧩 2 plugin updates: #Elgg IndieWeb & #WordPress #IndieAuth 🎪 1 #IndieWebCamp San Diego (2 days!) 📚 1 indiebookclub new year in review overview feature 📽 1 IndieWeb movie viewings aggregator 🧶 1 #Threads federating out #ActivityPub (followable by #BridgyFed) Gift were shared by: 👥 20 individuals 🏢 1 company I compiled these numbers by hand. Let me know if you see any errors. There are many more potential stats like: * average (mean and median) number of gifts per contributor * how many edits to the Gift Calendar wiki page * how many different editors of the wiki page * average (mean and median) number of edits per editor I’ll leave those as exercises for others if they wish! This is post 2 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2024/001/t1/restarting-100days-indieweb-gift-calendar → 🔮
date: 2024-01-03T19:09:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110228
enclosure: 2023-12-indieweb-gift-calendar
links to: 2023-12-indieweb-gift-calendar
enclosure: restarting-100days-indieweb-gift-calendar
links to: restarting-100days-indieweb-gift-calendar
tagged: concept

2023-12-indieweb-gift-calendar
date: 2024-01-04T06:26:24-05:00
type: text/html; charset=UTF-8

concept
type: Tag
label: elgg

concept
type: Tag
label: wordpress

concept
type: Tag
label: 100days

concept
type: Tag
label: 100daysofindieweb

concept
type: Tag
label: showdonttellthis

Tantek
type: Agent
holds account: acct