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

w3ctpac
type: Container
type: channel
description: Updates tagged with w3ctpac on stadeus!
licence: http://creativecommons.org/licenses/by/3.0/
items: tpac-breakouts-reactions
items: w3ctpac-2024
items: w3c-advisory-committee-meetings
items: thoughtful-reading-writing-web
items: summary-w3c-tpac-2023
items: socialweb-cg-w3ctpac
items: w3ctpac-sustainability-values
items: future-w3c-tpac-improve-web
items: : at #w3cTPAC all weekMT: @CSSWG made a new draftW: Explained & facilitated @W3C Plenary day #BarCampThF #WPWG #WICG

tpac-breakouts-reactions
type: item
type: MicroblogPost
title: : Numerous #w3cTPAC breakout sessions have been proposed. * https://github.com/w3c/tpac2025-breakouts/issues/?q=is%3Aissue%20state%3Aopen%20sort%3Acreated-ascIf you plan to participate in TPAC breakouts, whether in-person or remote, take a look and give the ones that look interesting to you thumbs-up 👍, heart ❤️, or rocket 🚀 reactions.For more information about TPAC 2025 Breakout sessions and how they work, see: * https://github.com/w3c/tpac2025-breakouts
link: https://status.blaise.ca/notice/116284
description: 's status on Monday, 27-Oct-2025 22:23:00 EDT
encoded: Numerous #w3cTPAC breakout sessions have been proposed. * https://github.com/w3c/tpac2025-breakouts/issues/?q=is%3Aissue%20state%3Aopen%20sort%3Acreated-asc If you plan to participate in TPAC breakouts, whether in-person or remote, take a look and give the ones that look interesting to you thumbs-up 👍, heart ❤️, or rocket 🚀 reactions. For more information about TPAC 2025 Breakout sessions and how they work, see: * https://github.com/w3c/tpac2025-breakouts
date: 2025-10-27T22:23:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110350
enclosure: https://github.com/w3c/tpac2025-breakouts/issues/
links to: https://github.com/w3c/tpac2025-breakouts/issues/
enclosure: tpac2025-breakouts
links to: tpac2025-breakouts
tagged: concept

https://github.com/w3c/tpac2025-breakouts/issues/
date: 2025-10-28T03:27:08-04:00
type: text/html; charset=utf-8

tpac2025-breakouts
date: 2025-10-28T03:27:09-04:00
type: text/html; charset=utf-8

concept
type: Tag
label: w3ctpac

w3ctpac-2024
type: item
type: MicroblogPost
title: : Last week I participated in #w3cTPAC 2024¹ in Anaheim, California. It was quite packed, and often started early, from 8am informal breakfast meetings at a nearby IHOP, to Working Group, Community Group, and other small group meetings every day (but Wednesday) til 18:00.Midweek at TPAC was the usual Breakouts Day where a record 87 breakouts² were proposed³ and run by members of the community, deftly organized into rooms, timeslots, and a handful of themes⁴ by the W3C Team. In the evening there was an open Plenary Session⁵ open to all instead of an Advisory Committee (AC) meeting, where the result of the recent W3C Board Election⁶ was announced. Congratulations to the newly elected W3C Board of Directors!I’m still compiling my own notes and observations. For now, the minutes of (nearly?) all the meetings and breakouts are available if you know how to find them.Hint: W3C minutes URLs have the form (without spaces):https:// www . w3 . org / YYYY / MM / DD-IRCNAME-minutes . htmlE.g. to find the second day (2024-09-24) of CSS Working Group (which just uses "css", all lower case, as their IRC channel name) minutes, you would go to:* https://www.w3.org/2024/09/24-css-minutes.htmlEvery Working Group and Community Group links to its IRC Channel (all lowercase), and breakout proposals link to the channel used for each breakout. Thus the minutes links to specific groups on specific days are left as a web discovery exercise for the reader.Last year: https://tantek.com/2023/262/b1/w3c-technical-plenary-tpac¹ https://www.w3.org/wiki/TPAC/2024² https://www.w3.org/2024/09/TPAC/breakouts.html#grid³ https://github.com/w3c/tpac2024-breakouts/⁴ https://github.com/orgs/w3c/projects/57/views/1⁵ https://www.w3.org/2024/09/26-tpac-minutes.html⁶ https://www.w3.org/2024/09/26-tpac-minutes.html#x215
link: https://status.blaise.ca/notice/116227
description: 's status on Thursday, 03-Oct-2024 18:02:00 EDT
encoded: Last week I participated in #w3cTPAC 2024¹ in Anaheim, California. It was quite packed, and often started early, from 8am informal breakfast meetings at a nearby IHOP, to Working Group, Community Group, and other small group meetings every day (but Wednesday) til 18:00. Midweek at TPAC was the usual Breakouts Day where a record 87 breakouts² were proposed³ and run by members of the community, deftly organized into rooms, timeslots, and a handful of themes⁴ by the W3C Team. In the evening there was an open Plenary Session⁵ open to all instead of an Advisory Committee (AC) meeting, where the result of the recent W3C Board Election⁶ was announced. Congratulations to the newly elected W3C Board of Directors! I’m still compiling my own notes and observations. For now, the minutes of (nearly?) all the meetings and breakouts are available if you know how to find them. Hint: W3C minutes URLs have the form (without spaces): https:// www . w3 . org / YYYY / MM / DD-IRCNAME-minutes . html E.g. to find the second day (2024-09-24) of CSS Working Group (which just uses "css", all lower case, as their IRC channel name) minutes, you would go to: * https://www.w3.org/2024/09/24-css-minutes.html Every Working Group and Community Group links to its IRC Channel (all lowercase), and breakout proposals link to the channel used for each breakout. Thus the minutes links to specific groups on specific days are left as a web discovery exercise for the reader. Last year: https://tantek.com/2023/262/b1/w3c-technical-plenary-tpac ¹ https://www.w3.org/wiki/TPAC/2024 ² https://www.w3.org/2024/09/TPAC/breakouts.html#grid ³ https://github.com/w3c/tpac2024-breakouts/ ⁴ https://github.com/orgs/w3c/projects/57/views/1 ⁵ https://www.w3.org/2024/09/26-tpac-minutes.html ⁶ https://www.w3.org/2024/09/26-tpac-minutes.html#x215
date: 2024-10-03T18:02:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110296
enclosure: 24-css-minutes.htmlEvery
links to: 24-css-minutes.htmlEvery
enclosure: w3c-technical-plenary-tpac
links to: w3c-technical-plenary-tpac
enclosure: 2024²
links to: 2024²
enclosure: grid³
links to: grid³
links to: https://github.com/w3c/tpac2024-breakouts/⁴
links to: 1⁵
enclosure: 26-tpac-minutes.html⁶
links to: 26-tpac-minutes.html⁶
enclosure: x215
links to: x215
tagged: concept

24-css-minutes.htmlEvery
date: 2024-10-03T20:36:08-04:00
type: text/html; charset=iso-8859-1

w3c-technical-plenary-tpac
date: 2024-10-03T20:36:09-04:00
type: text/html; charset=UTF-8

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

grid³
date: 2024-10-03T20:36:09-04:00
type: text/html; charset=utf-8

26-tpac-minutes.html⁶
date: 2024-10-03T20:36:10-04:00
type: text/html; charset=iso-8859-1

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

w3c-advisory-committee-meetings
type: item
type: MicroblogPost
title: : Last week I participated @W3.org (@w3c@w3c.social) #W3CAC (W3C Advisory Committee¹), #W3CAB (W3C Advisory Board² @ab@w3c.social), and #W3CBoard³ meetings in Hiroshima, Japan.The W3C Process⁴ describes the twice a year AC (Advisory Committee) Meetings⁵. In addition to members of the AC (one primary and one alternate per W3C Member Organization), the meetings are open to the AB (Advisory Board), the Board of the W3C Corporation, the #w3cTAG (W3C Technical Architecture Group⁶ @tag@w3c.social), Working Group⁷ chairs, Chapter⁸ staff, and this time also a W3C Invited Expert designated observer⁹.The AC currently meets in the Spring on its own and a shorter meeting in the Fall as part of the annual #W3CTPAC (W3C Technical Plenary and Advisory Committee¹⁰ meetings). The existence, dates, and location of the event are public¹¹, however the agenda, minutes, and registrants are generally Member-confidential. Since those individual links have their own access controls, I collected them on a publicly-viewable wiki page for easier discovery & navigation (if you work for a W3C Member Organization¹²): * https://www.w3.org/wiki/AC/Meetings#2024_SpringMost of the W3C meeting materials and discussions were also W3C Member-confidential, however a several of the presentations are publicly viewable, and a few more may be shared publicly after the fact.Myself and others at #W3C who believe in pushing for more openness and transparency in standards work, even (or especially) governance of said work, will be doing our best to work with others at W3C to continue shifting our work accordingly.Aside: I started the #OpenAB project when I was first elected to the AB (Advisory Board) in 2013, documenting it on the publicly viewable W3C Wiki, and updated it with the help of others since: https://www.w3.org/wiki/AB#Open_ABLike most conferences, I got as much out of side conversations at breaks (AKA hallway track¹³) and meals as I did from scheduled talks and panels.For now, here are the events, sl…
link: https://status.blaise.ca/notice/116197
description: 's status on Sunday, 14-Apr-2024 21:41:00 EDT
encoded: Last week I participated @W3.org (@w3c@w3c.social) #W3CAC (W3C Advisory Committee¹), #W3CAB (W3C Advisory Board² @ab@w3c.social), and #W3CBoard³ meetings in Hiroshima, Japan. The W3C Process⁴ describes the twice a year AC (Advisory Committee) Meetings⁵. In addition to members of the AC (one primary and one alternate per W3C Member Organization), the meetings are open to the AB (Advisory Board), the Board of the W3C Corporation, the #w3cTAG (W3C Technical Architecture Group⁶ @tag@w3c.social), Working Group⁷ chairs, Chapter⁸ staff, and this time also a W3C Invited Expert designated observer⁹. The AC currently meets in the Spring on its own and a shorter meeting in the Fall as part of the annual #W3CTPAC (W3C Technical Plenary and Advisory Committee¹⁰ meetings). The existence, dates, and location of the event are public¹¹, however the agenda, minutes, and registrants are generally Member-confidential. Since those individual links have their own access controls, I collected them on a publicly-viewable wiki page for easier discovery & navigation (if you work for a W3C Member Organization¹²): * https://www.w3.org/wiki/AC/Meetings#2024_Spring Most of the W3C meeting materials and discussions were also W3C Member-confidential, however a several of the presentations are publicly viewable, and a few more may be shared publicly after the fact. Myself and others at #W3C who believe in pushing for more openness and transparency in standards work, even (or especially) governance of said work, will be doing our best to work with others at W3C to continue shifting our work accordingly. Aside: I started the #OpenAB project when I was first elected to the AB (Advisory Board) in 2013, documenting it on the publicly viewable W3C Wiki, and updated it with the help of others since: https://www.w3.org/wiki/AB#Open_AB Like most conferences, I got as much out of side conversations at breaks (AKA hallway track¹³) and meals as I did from scheduled talks and panels. For now, here are the event…
date: 2024-04-14T21:41:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110266
enclosure: 2024 SpringMost
links to: 2024 SpringMost
enclosure: Open ABLike
links to: Open ABLike
enclosure: https://www.w3.org/reports/ai-web-impact/*
links to: https://www.w3.org/reports/ai-web-impact/*
enclosure: https://www.w3.org/2024/Talks/ac-slides/engaging-the-members/*
links to: https://www.w3.org/2024/Talks/ac-slides/engaging-the-members/*
enclosure: https://www.w3.org/2024/Talks/ac-slides/exploration/*
links to: https://www.w3.org/2024/Talks/ac-slides/exploration/*
enclosure: OHCHR.pdf*
links to: OHCHR.pdf*
enclosure: watch*
links to: watch*
enclosure: https://www.w3.org/events/meetings/13213a52-8159-4af8-b939-38c7880ba266/*
links to: https://www.w3.org/events/meetings/13213a52-8159-4af8-b939-38c7880ba266/*
enclosure: https://www.w3.org/2024/Talks/ac-slides/lt-deepfake/*
links to: https://www.w3.org/2024/Talks/ac-slides/lt-deepfake/*
enclosure: https://www.w3.org/2024/Talks/ac-slides/lt-accessing-llms-data/*
links to: https://www.w3.org/2024/Talks/ac-slides/lt-accessing-llms-data/*
enclosure: pac-data-sovereignty
links to: pac-data-sovereignty
enclosure: intro-content-credentials.pdf*
links to: intro-content-credentials.pdf*
enclosure: ac2024
links to: ac2024
enclosure: https://www.w3.org/events/meetings/df0b9dd8-2356-47ec-839d-eadc06da1ca1/I
links to: https://www.w3.org/events/meetings/df0b9dd8-2356-47ec-839d-eadc06da1ca1/I
enclosure: mondayReferences:¹
links to: mondayReferences:¹
enclosure: AC²
links to: AC²
enclosure: AB³
links to: AB³
enclosure: Board⁴
links to: Board⁴
enclosure: https://www.w3.org/Consortium/Process/⁵
links to: https://www.w3.org/Consortium/Process/⁵
enclosure: ACMeetings⁶
links to: ACMeetings⁶
enclosure: tag⁷
links to: tag⁷
enclosure: https://www.w3.org/groups/wg/%E2%81%B8/
links to: https://www.w3.org/groups/wg/%E2%81%B8/
enclosure: https://chapters.w3.org/⁹
links to: https://chapters.w3.org/⁹
enclosure: ac-observer¹⁰
links to: ac-observer¹⁰
enclosure: TPAC¹¹
links to: TPAC¹¹
enclosure: ¹²
links to: ¹²
enclosure: ¹³
links to: ¹³
enclosure: hallway track¹⁴
links to: hallway track¹⁴
enclosure: existing-rel-values¹⁵
links to: existing-rel-values¹⁵
enclosure: sidefile-antipattern¹⁶
links to: sidefile-antipattern¹⁶
enclosure: 68.html
links to: 68.html
tagged: concept

2024 SpringMost
date: 2024-04-14T21:55:21-04:00
type: text/html; charset=UTF-8

Open ABLike
date: 2024-04-14T21:55:21-04:00
type: text/html; charset=UTF-8

https://www.w3.org/reports/ai-web-impact/*
date: 2024-04-14T21:55:22-04:00
type: text/html; charset=utf-8

https://www.w3.org/2024/Talks/ac-slides/engaging-the-members/*
date: 2024-04-14T21:55:22-04:00
type: text/html;charset=utf-8

https://www.w3.org/2024/Talks/ac-slides/exploration/*
date: 2024-04-14T21:55:22-04:00
type: text/html;charset=utf-8

OHCHR.pdf*
date: 2024-04-14T21:55:22-04:00
type: text/html; charset=iso-8859-1

watch*
date: 2024-04-14T21:55:24-04:00
length: 2153
type: text/html; charset=utf-8

watch*
date: 2024-04-14T21:55:24-04:00
length: 2153
type: text/html; charset=utf-8

https://www.w3.org/events/meetings/13213a52-8159-4af8-b939-38c7880ba266/*
date: 2024-04-14T21:55:25-04:00
type: text/html; charset=UTF-8

https://www.w3.org/2024/Talks/ac-slides/lt-deepfake/*
date: 2024-04-14T21:55:25-04:00
type: text/html;charset=utf-8

https://www.w3.org/2024/Talks/ac-slides/lt-accessing-llms-data/*
date: 2024-04-14T21:55:25-04:00
type: text/html;charset=utf-8

pac-data-sovereignty
date: 2024-04-14T21:55:25-04:00
type: text/html; charset=utf-8

intro-content-credentials.pdf*
date: 2024-04-14T21:55:25-04:00
type: text/html; charset=iso-8859-1

ac2024
date: 2024-04-14T21:55:26-04:00
length: 12641
type: text/html; charset=utf-8

https://www.w3.org/events/meetings/df0b9dd8-2356-47ec-839d-eadc06da1ca1/I
date: 2024-04-14T21:55:26-04:00
type: text/html; charset=UTF-8

mondayReferences:¹
date: 2024-04-14T21:55:26-04:00
type: text/html

AC²
date: 2024-04-14T21:55:26-04:00
type: text/html; charset=UTF-8

AB³
date: 2024-04-14T21:55:26-04:00
type: text/html; charset=UTF-8

Board⁴
date: 2024-04-14T21:55:27-04:00
type: text/html; charset=UTF-8

https://www.w3.org/Consortium/Process/⁵
date: 2024-04-14T21:55:27-04:00
type: text/html;charset=utf-8

ACMeetings⁶
date: 2024-04-14T21:55:27-04:00
type: text/html; charset=utf-8

tag⁷
date: 2024-04-14T21:55:28-04:00
type: text/html;charset=utf-8

https://www.w3.org/groups/wg/%E2%81%B8/
date: 2024-04-14T21:55:28-04:00
type: text/html; charset=UTF-8

https://chapters.w3.org/⁹
date: 2024-04-14T21:55:28-04:00
type: text/html; charset=UTF-8

ac-observer¹⁰
date: 2024-04-14T21:55:29-04:00
type: text/html; charset=UTF-8

TPAC¹¹
date: 2024-04-14T21:55:29-04:00
type: text/html; charset=UTF-8

¹²
date: 2024-04-14T21:55:30-04:00
type: text/html; charset=UTF-8

¹³
date: 2024-04-14T21:55:30-04:00
type: text/html; charset=UTF-8

hallway track¹⁴
date: 2024-04-14T21:55:30-04:00
type: text/html; charset=UTF-8

existing-rel-values¹⁵
date: 2024-04-14T21:55:31-04:00
type: text/html; charset=UTF-8

sidefile-antipattern¹⁶
date: 2024-04-14T21:55:31-04:00
type: text/html; charset=UTF-8

68.html
date: 2024-04-14T21:55:33-04:00
type: text/html; charset=utf-8

concept
type: Tag
label: indieweb

concept
type: Tag
label: openab

concept
type: Tag
label: w3c

concept
type: Tag
label: w3cab

concept
type: Tag
label: w3cac

concept
type: Tag
label: w3cboard³

concept
type: Tag
label: w3ctag

thoughtful-reading-writing-web
type: item
type: MicroblogPost
title: : Ben Werdmuller recently published an inspiring and thought-provoking blog post: “Subscribing to the blogs of people I follow on Mastodon”. Beyond the insights and excellent developer how-to in his post, I believe it points to something larger: a fundamental thoughtfulness difference between writing rapid short-form posts (whether tweets or toots) and medium or longer form writing (on blogs or journals), and the impact of that difference on readers: that the act of reading more thoughtful writing nudges & reinforces a reader into a more thoughtful state of mind. If you have not read Derek Powazek’s watershed blog post “The Argument Machine”, I highly recommend you do so. In the nearly ten years since his post, Derek’s hypothesis of Twitter’s user interface design being the ultimate machine to create & amplify disputes has been repeatedly demonstrated. Derek’s post predated Mastodon’s release by nearly three years. Ironically, by replicating much of Twitter’s user experience, Mastodon has in many ways also replicated its Argument Machine effects, except distributed across more servers. I’ve witnessed numerous otherwise rational, well-intentioned individuals write reactive posts on Mastodon, exactly what the Twitter-like interface encourages. Quick emotional responses rather than slower, more thoughtful posts and replies. I’ve seen the artificial urgency of tweets & toots bleed over into emotional essays on public mailing lists. New participants join a list and immediately make entitled demands. Fearful bordering on paranoid assumptions are used to state assertions of “facts” without citations. Arguments are made that appeal to emotion (argumentum ad passiones) rather than reasoning from principles and shared values. Implicit in Ben’s post, “Subscribing to the blogs of people” (emphasis mine), is a preference for reading longer form writing, published on a site a human owns & identifies with (a la #indieweb), neither silo nor someone else’s garage. The combination of…
link: https://status.blaise.ca/notice/116136
description: 's status on Thursday, 05-Oct-2023 02:55:00 EDT
encoded: Ben Werdmuller recently published an inspiring and thought-provoking blog post: “Subscribing to the blogs of people I follow on Mastodon”. Beyond the insights and excellent developer how-to in his post, I believe it points to something larger: a fundamental thoughtfulness difference between writing rapid short-form posts (whether tweets or toots) and medium or longer form writing (on blogs or journals), and the impact of that difference on readers: that the act of reading more thoughtful writing nudges & reinforces a reader into a more thoughtful state of mind. If you have not read Derek Powazek’s watershed blog post “The Argument Machine”, I highly recommend you do so. In the nearly ten years since his post, Derek’s hypothesis of Twitter’s user interface design being the ultimate machine to create & amplify disputes has been repeatedly demonstrated. Derek’s post predated Mastodon’s release by nearly three years. Ironically, by replicating much of Twitter’s user experience, Mastodon has in many ways also replicated its Argument Machine effects, except distributed across more servers. I’ve witnessed numerous otherwise rational, well-intentioned individuals write reactive posts on Mastodon, exactly what the Twitter-like interface encourages. Quick emotional responses rather than slower, more thoughtful posts and replies. I’ve seen the artificial urgency of tweets & toots bleed over into emotional essays on public mailing lists. New participants join a list and immediately make entitled demands. Fearful bordering on paranoid assumptions are used to state assertions of “facts” without citations. Arguments are made that appeal to emotion (argumentum ad passiones) rather than reasoning from principles and shared values. Implicit in Ben’s post, “Subscribing to the blogs of people” (emphasis mine), is a preference for reading longer form writing, published on a site a human owns & identifies with (a la #indieweb), neither silo nor someone else’s garage. The combination of t…
date: 2023-10-05T02:55:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110213
tagged: concept

summary-w3c-tpac-2023
type: item
type: MicroblogPost
title: : I recently wrote a high level summary blog post:W3C Technical Plenary and Advisory Committee (TPAC) Meetings 2023https://tantek.com/2023/262/b1/w3c-technical-plenary-tpacof my time at the #W3C (@W3.org, @w3c@w3c.social, @W3C) #TPAC the week before.Posting this note to explicitly #hashtag that article with topics mentioned therein:#Sevilla #Seville #Spain #WICG #SocialCG #SWICG #Fediverse #SocialWeb #sustainability #IndieWeb #ActivityPubbecause I forgot to put explicit categories (p-category markup) in the article post.Adding that markup after publishing, and then sending an ActivityPub update (via #BridgyFed) is apparently not enough for #Mastodon to notice that the Update has new tags to display and aggregate on tag pages. In my next #w3cTPAC article post I’ll be sure to include category markup before publishing and see if that works.Post glossary:article post https://indieweb.org/articlenote post https://indieweb.org/notep-category https://indieweb.org/p-categorytags https://indieweb.org/tags
link: https://status.blaise.ca/notice/116135
description: 's status on Sunday, 24-Sep-2023 21:33:00 EDT
encoded: I recently wrote a high level summary blog post: W3C Technical Plenary and Advisory Committee (TPAC) Meetings 2023 https://tantek.com/2023/262/b1/w3c-technical-plenary-tpac of my time at the #W3C (@W3.org, @w3c@w3c.social, @W3C) #TPAC the week before. Posting this note to explicitly #hashtag that article with topics mentioned therein: #Sevilla #Seville #Spain #WICG #SocialCG #SWICG #Fediverse #SocialWeb #sustainability #IndieWeb #ActivityPub because I forgot to put explicit categories (p-category markup) in the article post. Adding that markup after publishing, and then sending an ActivityPub update (via #BridgyFed) is apparently not enough for #Mastodon to notice that the Update has new tags to display and aggregate on tag pages. In my next #w3cTPAC article post I’ll be sure to include category markup before publishing and see if that works. Post glossary: article post https://indieweb.org/article note post https://indieweb.org/note p-category https://indieweb.org/p-category tags https://indieweb.org/tags
date: 2023-09-24T21:33:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110212
enclosure: articlenote
links to: articlenote
enclosure: notep-category
links to: notep-category
enclosure: p-categorytags
links to: p-categorytags
enclosure: tags
links to: tags
tagged: concept

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

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

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

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

concept
type: Tag
label: activitypubbecause

concept
type: Tag
label: bridgyfed

concept
type: Tag
label: fediverse

concept
type: Tag
label: hashtag

concept
type: Tag
label: mastodon

concept
type: Tag
label: seville

concept
type: Tag
label: socialcg

concept
type: Tag
label: socialweb

concept
type: Tag
label: spain

concept
type: Tag
label: sustainability

concept
type: Tag
label: swicg

concept
type: Tag
label: tpac

concept
type: Tag
label: wicg

socialweb-cg-w3ctpac
type: item
type: MicroblogPost
title: : going to the #SocialWeb CG meeting @W3C #w3cTPAC tomorrow (2023-09-12) at 09:30 CEST.Looking forward to seeing @evanp.me (@evan@cosocial.ca @evanpro) and many others!So many advances in #ActivityPub, #Webmention, Micropub, #IndieAuth etc. that it may be time to restart the #SocialWebWG to officially update all our active specifications.We can & should also reach out to #Bluesky & #Nostr communities to work together on shared semantics and bridging protocols to continue growing a heterogenous #fediverse built on the #OpenWeb.We know it is possible. We worked hard in the Social Web working group to align a lot of semantics across #ActivityStreams and #microformats2. The fruitful results of that are services like http://fed.brid.gy/ which I myself use to send a Webmention when I make a new post (like this one) and have #BridgyFed automatically federate it via ActivityPub using my personal site identity to #Mastodon followers and others.@snarfed.org wrote up a recent comparison of top #decentralized #socialProtocols that can help inform a lot of this discussion: https://snarfed.org/2023-09-04_50856
link: https://status.blaise.ca/notice/116133
description: 's status on Monday, 11-Sep-2023 19:06:00 EDT
encoded: going to the #SocialWeb CG meeting @W3C #w3cTPAC tomorrow (2023-09-12) at 09:30 CEST. Looking forward to seeing @evanp.me (@evan@cosocial.ca @evanpro) and many others! So many advances in #ActivityPub, #Webmention, Micropub, #IndieAuth etc. that it may be time to restart the #SocialWebWG to officially update all our active specifications. We can & should also reach out to #Bluesky & #Nostr communities to work together on shared semantics and bridging protocols to continue growing a heterogenous #fediverse built on the #OpenWeb. We know it is possible. We worked hard in the Social Web working group to align a lot of semantics across #ActivityStreams and #microformats2. The fruitful results of that are services like http://fed.brid.gy/ which I myself use to send a Webmention when I make a new post (like this one) and have #BridgyFed automatically federate it via ActivityPub using my personal site identity to #Mastodon followers and others. @snarfed.org wrote up a recent comparison of top #decentralized #socialProtocols that can help inform a lot of this discussion: https://snarfed.org/2023-09-04_50856
date: 2023-09-11T19:06:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110210
enclosure: fed.brid.gy
links to: fed.brid.gy
enclosure: 2023-09-04 50856
links to: 2023-09-04 50856
tagged: concept

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

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

concept
type: Tag
label: activitypub

concept
type: Tag
label: activitystreams

concept
type: Tag
label: bluesky

concept
type: Tag
label: decentralized

concept
type: Tag
label: indieauth

concept
type: Tag
label: microformats2

concept
type: Tag
label: nostr

concept
type: Tag
label: openwebwe

concept
type: Tag
label: socialprotocols

concept
type: Tag
label: socialwebwg

concept
type: Tag
label: webmention

w3ctpac-sustainability-values
type: item
type: MicroblogPost
title: : Led two virtual #w3cTPAC breakout sessions this week:* Environmental Concerns and #Sustainability (#s12y) of Web Technologies[1]* What is the value of and are the values of @W3C[2]and helped @seaotta with:* What is the WebWeWant.fyi[3]Notes:[1] https://www.w3.org/2021/10/19-sustainability-minutes.html[2] https://www.w3.org/2021/10/22-what-values-minutes.html [3] https://www.w3.org/2021/10/19-webwewant-minutes.htmlAlso participated in Accessibility & CSS (https://www.w3.org/2021/10/20-cssa11y-minutes.html).Preparing for, speaking, facilitating, and participating in virtual TPAC sessions a second year in a row was very draining. Despite that, I thought the sessions went fairly well overall.Most passionate and contentious was the session on sustainability, especially regarding what we should (or should not) do @W3C. There was a lot more alignment on the seriousness and urgency to act than I expected, and I was pleased to see that.There was a lot of support for figuring out how to establish Sustainability as an aspect of Horizontal Review of all technical specifications, as important as Accessibility (a11y), Internationaliation (i18n), Security, and Privacy. This would likely require an explicit Interest Group, with a charter, discussed and voted on by the W3C’s Advisory Committe (AC).Our shared sense of urgency made it clear we needed to start something sooner rather than later. A Community Group (CG) makes the most sense in the short term, chartered to work on both immediate horizontal review and the establishement of a more official Interest Group.I created a #sustainability channel on the W3C’s Community Slack instance to start informal discussions to get a Community Group started.Join us: https://twitter.com/w3c/status/1252972104456306688
link: https://status.blaise.ca/notice/115782
description: 's status on Friday, 22-Oct-2021 21:33:00 EDT
encoded: Led two virtual #w3cTPAC breakout sessions this week: * Environmental Concerns and #Sustainability (#s12y) of Web Technologies[1] * What is the value of and are the values of @W3C[2] and helped @seaotta with: * What is the WebWeWant.fyi[3] Notes: [1] https://www.w3.org/2021/10/19-sustainability-minutes.html [2] https://www.w3.org/2021/10/22-what-values-minutes.html [3] https://www.w3.org/2021/10/19-webwewant-minutes.html Also participated in Accessibility & CSS (https://www.w3.org/2021/10/20-cssa11y-minutes.html). Preparing for, speaking, facilitating, and participating in virtual TPAC sessions a second year in a row was very draining. Despite that, I thought the sessions went fairly well overall. Most passionate and contentious was the session on sustainability, especially regarding what we should (or should not) do @W3C. There was a lot more alignment on the seriousness and urgency to act than I expected, and I was pleased to see that. There was a lot of support for figuring out how to establish Sustainability as an aspect of Horizontal Review of all technical specifications, as important as Accessibility (a11y), Internationaliation (i18n), Security, and Privacy. This would likely require an explicit Interest Group, with a charter, discussed and voted on by the W3C’s Advisory Committe (AC). Our shared sense of urgency made it clear we needed to start something sooner rather than later. A Community Group (CG) makes the most sense in the short term, chartered to work on both immediate horizontal review and the establishement of a more official Interest Group. I created a #sustainability channel on the W3C’s Community Slack instance to start informal discussions to get a Community Group started. Join us: https://twitter.com/w3c/status/1252972104456306688
date: 2021-10-22T21:33:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/109994
enclosure: 19-sustainability-minutes.html
links to: 19-sustainability-minutes.html
enclosure: 22-what-values-minutes.html
links to: 22-what-values-minutes.html
enclosure: 19-webwewant-minutes.htmlAlso
links to: 19-webwewant-minutes.htmlAlso
enclosure: 20-cssa11y-minutes.html).Preparing
links to: 20-cssa11y-minutes.html).Preparing
enclosure: https://twitter.com/w3c/status/1252972104456306688
links to: https://twitter.com/w3c/status/1252972104456306688
tagged: concept

19-sustainability-minutes.html
date: 2021-10-22T22:05:15-04:00
length: 58085
type: text/html; charset=utf-8

22-what-values-minutes.html
date: 2021-10-22T22:05:15-04:00
length: 48783
type: text/html; charset=utf-8

19-webwewant-minutes.htmlAlso
date: 2021-10-22T22:05:15-04:00
type: text/html; charset=iso-8859-1

20-cssa11y-minutes.html).Preparing
date: 2021-10-22T22:05:16-04:00
type: text/html; charset=iso-8859-1

https://twitter.com/w3c/status/1252972104456306688
date: 2021-10-22T22:05:16-04:00
type: text/html; charset=utf-8

future-w3c-tpac-improve-web
type: item
type: MicroblogPost
title: : At #w3cTPAC this week: @CSSWG, #Future of @W3C, #WICG. Come say hi!Still reflecting on #XOXOFest themes & learnings. Particularly how much online abuse & harassment is growing. Let’s chat about this at TPAC, brainstorm if/how we can improve web building blocks to reduce harm, especially toward marginalized individuals & communities.
link: https://status.blaise.ca/notice/113607
description: 's status on Monday, 16-Sep-2019 02:36:00 EDT
encoded: At #w3cTPAC this week: @CSSWG, #Future of @W3C, #WICG. Come say hi! Still reflecting on #XOXOFest themes & learnings. Particularly how much online abuse & harassment is growing. Let’s chat about this at TPAC, brainstorm if/how we can improve web building blocks to reduce harm, especially toward marginalized individuals & communities.
date: 2019-09-16T02:36:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/108104
tagged: concept

concept
type: Tag
label: future

concept
type: Tag
label: xoxofest

: at #w3cTPAC all weekMT: @CSSWG made a new draftW: Explained & facilitated @W3C Plenary day #BarCampThF #WPWG #WICG
type: item
type: MicroblogPost
link: https://status.blaise.ca/notice/105078
description: 's status on Wednesday, 08-Nov-2017 16:19:00 EST
encoded: at #w3cTPAC all week MT: @CSSWG made a new draft W: Explained & facilitated @W3C Plenary day #BarCamp ThF #WPWG #WICG
date: 2017-11-08T16:19:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/101549
tagged: concept

concept
type: Tag
label: barcampthf

concept
type: Tag
label: wpwg

Tantek
type: Agent
holds account: acct