{
"type": "entry",
"published": "2024-04-20T19:56:30-07:00",
"url": "https://aaronparecki.com/2024/04/20/9/",
"syndication": [
"https://bsky.app/profile/aaronpk.com/post/3kqmdvyw4ic2k"
],
"content": {
"text": "oh no, it finally happened. I left my AirPods in a pocket and they went through the washer and dryer \ud83d\ude31",
"html": "oh no, it finally happened. I left my AirPods in a pocket and they went through the washer and dryer <a href=\"https://aaronparecki.com/emoji/%F0%9F%98%B1\">\ud83d\ude31</a>"
},
"author": {
"type": "card",
"name": "Aaron Parecki",
"url": "https://aaronparecki.com/",
"photo": "https://aperture-media.p3k.io/aaronparecki.com/cceb2dc6df9c1d6f8ddab96940af3703a1564b730af015cb2e82c2b2e921f7b7.jpg"
},
"post-type": "note",
"_id": "40896758",
"_source": "16"
}
{
"type": "entry",
"published": "2024-04-19 10:38-0700",
"url": "https://gregorlove.com/2024/04/want-to-watch-will-ai/",
"category": [
"to-watch"
],
"content": {
"text": "Want to watch: \u201cWill AI Also Remember the Days of Slavery?,\u201d a lecture by Charles Mudede",
"html": "<p>Want to watch: \u201c<a href=\"https://www.e-flux.com/events/581284/will-ai-also-remember-the-days-of-slavery-a-lecture-by-charles-mudede/\">Will AI Also Remember the Days of Slavery?</a>,\u201d a lecture by Charles Mudede</p>"
},
"author": {
"type": "card",
"name": "gRegor Morrill",
"url": "https://gregorlove.com/",
"photo": "https://gregorlove.com/site/assets/files/6268/profile-2021-square.300x0.jpg"
},
"post-type": "note",
"_id": "40886531",
"_source": "95"
}
I’m the current editor of the Vision for W3C and helped get it across the line this year to reach #w3cAB (W3C Advisory Board @ab@w3c.social) consensus to publish as an official Group Note, the first official Note that the AB (Advisory Board) has ever published.
I’m very proud of this milestone, as I and a few others including many on the AB¹, have been working on it for a few years in various forms, and with the broader W3C Vision TF² (Task Force) for the past year.
W3C also recently announced the Vision for W3C in their news feed:
One of the key goals of this document was to capture the spirit of why we are at #W3C and our shared values & principles we use to guide our work & decisions at W3C.
If you work with any groups at W3C, anything from a Community Group (CG) to a Working Group (WG), I highly recommend you read this document from start to finish.
See what resonates with you, if there is anything that doesn’t sound right to you, or if you see anything missing that you feel exemplifies the best of what W3C is, please file an issue or a suggestion:
Check that list to see if your concerns or suggestions are already captured, and if so, add an upvote or comment accordingly.
Our goal is to eventually publish this document as an official W3C Statement, with the consensus of the entire #w3cAC (W3C Advisory Committee).
One key aspect which the Vision touches on but perhaps too briefly is what I see as the fundamental purpose of why we do the work we do at W3C, which in my opinion is:
To create & facilitate user-first interoperable standards that improve the web for humanity
“Interoperability: We verify the fitness of our specifications through open test suites and actual implementation experience, because we believe the purpose of standards is to enable independent interoperable implementations.”
These are both excellent, and yet, I think we can do better, with adding some sort of explicit statement between those two about that “We will” create & facilitate user-first interoperable standards that improve the web for humanity.
In the coming weeks I’ll be reflecting how we (the VisionTF) can incorporate that sort of imperative “We will” statement about interoperable standards into the Vision for W3C, as well as working with the AB and W3C Team on defining a succinct updated mission & purpose for W3C based on that sort of input and more.
In a related effort, I have also been leading the AB’s “3Is Priority Project³” (Interoperability and the Role of Independent Implementations), which is a pretty big project to define and clarify what each of those three Is mean, with respect to each other and Incubation, which is its own Priority Project⁴.
As part of the 3Is project, the first “I” I’ve been focusing on has unsurprisingly been “Interoperable”. As with other #OpenAB projects, our work on understanding interoperability, its aspects, and defining what do we mean by interoperable is published and iterated on the W3C’s public wiki:
This is still a work in progress, however it’s sufficiently structured to take a look if interoperability is something you care about or have opinions about.
In particular, if you know of definitions of interoperable or interoperability that resonate and make sense to you, or articles or blog posts about interoperability that explore various aspects, I am gathering such references so we can make sure the W3C’s definition of interoperable is both well-stated, and clearly reflects a broader industry understanding of interoperability.
{
"type": "entry",
"published": "2024-04-18 20:20-0700",
"url": "https://tantek.com/2024/109/t1/published-vision-for-w3c",
"category": [
"w3cAB",
"W3C",
"w3cAC",
"OpenAB"
],
"content": {
"text": "Recently @W3.org (@w3c@w3c.social) published the first Group Note of the Vision for W3C:\n\nhttps://www.w3.org/TR/2024/NOTE-w3c-vision-20240403/\n\nI\u2019m the current editor of the Vision for W3C and helped get it across the line this year to reach #w3cAB (W3C Advisory Board @ab@w3c.social) consensus to publish as an official Group Note, the first official Note that the AB (Advisory Board) has ever published.\n\nI\u2019m very proud of this milestone, as I and a few others including many on the AB\u00b9, have been working on it for a few years in various forms, and with the broader W3C Vision TF\u00b2 (Task Force) for the past year.\n\u00a0\nW3C also recently announced the Vision for W3C in their news feed:\n\nhttps://www.w3.org/news/2024/group-note-vision-for-w3c/\n\n\nOne of the key goals of this document was to capture the spirit of why we are at #W3C and our shared values & principles we use to guide our work & decisions at W3C.\n\nIf you work with any groups at W3C, anything from a Community Group (CG) to a Working Group (WG), I highly recommend you read this document from start to finish.\n\nSee what resonates with you, if there is anything that doesn\u2019t sound right to you, or if you see anything missing that you feel exemplifies the best of what W3C is, please file an issue or a suggestion:\n\nhttps://github.com/w3c/AB-public/issues?q=is%3Aissue+is%3Aopen+label%3A%22Project+Vision%22+-label%3ADefer\n\nCheck that list to see if your concerns or suggestions are already captured, and if so, add an upvote or comment accordingly.\n\nOur goal is to eventually publish this document as an official W3C Statement, with the consensus of the entire #w3cAC (W3C Advisory Committee).\n\nOne key aspect which the Vision touches on but perhaps too briefly is what I see as the fundamental purpose of why we do the work we do at W3C, which in my opinion is:\n\nTo create & facilitate user-first interoperable standards that improve the web for humanity\n\n\nThe Vision does mention \u201c#interoperable\u201d explicitly as part of our Vision for the Web in https://w3c.github.io/AB-public/Vision#vision-web:\n\n\u201dThere is one interoperable world-wide Web.\u201d\n\nThe Vision also mentions \u201c#interoperability\u201d explicitly in our Operational Principles https://w3c.github.io/AB-public/Vision#op-principles: \n\n\u201cInteroperability: We verify the fitness of our specifications through open test suites and actual implementation experience, because we believe the purpose of standards is to enable independent interoperable implementations.\u201d\n\nThese are both excellent, and yet, I think we can do better, with adding some sort of explicit statement between those two about that \u201cWe will\u201d create & facilitate user-first interoperable standards that improve the web for humanity.\n\nIn the coming weeks I\u2019ll be reflecting how we (the VisionTF) can incorporate that sort of imperative \u201cWe will\u201d statement about interoperable standards into the Vision for W3C, as well as working with the AB and W3C Team on defining a succinct updated mission & purpose for W3C based on that sort of input and more.\n\n\nIn a related effort, I have also been leading the AB\u2019s \u201c3Is Priority Project\u00b3\u201d (Interoperability and the Role of Independent Implementations), which is a pretty big project to define and clarify what each of those three Is mean, with respect to each other and Incubation, which is its own Priority Project\u2074.\n\nAs part of the 3Is project, the first \u201cI\u201d I\u2019ve been focusing on has unsurprisingly been \u00a0\u201cInteroperable\u201d. As with other #OpenAB projects, our work on understanding interoperability, its aspects, and defining what do we mean by interoperable is published and iterated on the W3C\u2019s public wiki:\n\nhttps://www.w3.org/wiki/Interoperable\n\nThis is still a work in progress, however it\u2019s sufficiently structured to take a look if interoperability is something you care about or have opinions about.\n\nIn particular, if you know of definitions of interoperable or interoperability that resonate and make sense to you, or articles or blog posts about interoperability that explore various aspects, I am gathering such references so we can make sure the W3C\u2019s definition of interoperable is both well-stated, and clearly reflects a broader industry understanding of interoperability.\n\nReferences:\n\n\u00b9 https://www.w3.org/TR/w3c-vision/#acknowledgements\n\u00b2 https://www.w3.org/wiki/AB/VisionTF\n\u00b3 https://www.w3.org/wiki/AB/2024_Priorities#Interoperability_and_the_Role_of_Independent_Implementations\n\u2074 https://www.w3.org/wiki/AB/2024_Priorities#Incubation",
"html": "Recently <a href=\"https://W3.org\">@W3.org</a> (<a href=\"https://w3c.social/@w3c\">@w3c@w3c.social</a>) published the first Group Note of the Vision for W3C:<br /><br /><a href=\"https://www.w3.org/TR/2024/NOTE-w3c-vision-20240403/\">https://www.w3.org/TR/2024/NOTE-w3c-vision-20240403/</a><br /><br />I\u2019m the current editor of the Vision for W3C and helped get it across the line this year to reach #<span class=\"p-category\">w3cAB</span> (W3C Advisory Board <a href=\"https://w3c.social/@ab\">@ab@w3c.social</a>) consensus to publish as an official Group Note, the first official Note that the AB (Advisory Board) has ever published.<br /><br />I\u2019m very proud of this milestone, as I and a few others including many on the AB<a href=\"https://tantek.com/#t5WX1_note-1\">\u00b9</a>, have been working on it for a few years in various forms, and with the broader W3C Vision TF<a href=\"https://tantek.com/#t5WX1_note-2\">\u00b2</a> (Task Force) for the past year.<br />\u00a0<br />W3C also recently announced the Vision for W3C in their news feed:<br /><br /><a href=\"https://www.w3.org/news/2024/group-note-vision-for-w3c/\">https://www.w3.org/news/2024/group-note-vision-for-w3c/</a><br /><br /><br />One of the key goals of this document was to capture the spirit of why we are at #<span class=\"p-category\">W3C</span> and our shared values & principles we use to guide our work & decisions at W3C.<br /><br />If you work with any groups at W3C, anything from a Community Group (CG) to a Working Group (WG), I highly recommend you read this document from start to finish.<br /><br />See what resonates with you, if there is anything that doesn\u2019t sound right to you, or if you see anything missing that you feel exemplifies the best of what W3C is, please file an issue or a suggestion:<br /><br /><a href=\"https://github.com/w3c/AB-public/issues?q=is%3Aissue+is%3Aopen+label%3A%22Project+Vision%22+-label%3ADefer\">https://github.com/w3c/AB-public/issues?q=is%3Aissue+is%3Aopen+label%3A%22Project+Vision%22+-label%3ADefer</a><br /><br />Check that list to see if your concerns or suggestions are already captured, and if so, add an upvote or comment accordingly.<br /><br />Our goal is to eventually publish this document as an official W3C Statement, with the consensus of the entire #<span class=\"p-category\">w3cAC</span> (W3C Advisory Committee).<br /><br />One key aspect which the Vision touches on but perhaps too briefly is what I see as the fundamental purpose of why we do the work we do at W3C, which in my opinion is:<br /><br />To create & facilitate user-first interoperable standards that improve the web for humanity<br /><br /><br />The Vision does mention \u201c#interoperable\u201d explicitly as part of our Vision for the Web in <a href=\"https://w3c.github.io/AB-public/Vision#vision-web:\">https://w3c.github.io/AB-public/Vision#vision-web:</a><br /><br />\u201dThere is one interoperable world-wide Web.\u201d<br /><br />The Vision also mentions \u201c#interoperability\u201d explicitly in our Operational Principles <a href=\"https://w3c.github.io/AB-public/Vision#op-principles:\">https://w3c.github.io/AB-public/Vision#op-principles:</a> <br /><br />\u201cInteroperability: We verify the fitness of our specifications through open test suites and actual implementation experience, because we believe the purpose of standards is to enable independent interoperable implementations.\u201d<br /><br />These are both excellent, and yet, I think we can do better, with adding some sort of explicit statement between those two about that \u201cWe will\u201d create & facilitate user-first interoperable standards that improve the web for humanity.<br /><br />In the coming weeks I\u2019ll be reflecting how we (the VisionTF) can incorporate that sort of imperative \u201cWe will\u201d statement about interoperable standards into the Vision for W3C, as well as working with the AB and W3C Team on defining a succinct updated mission & purpose for W3C based on that sort of input and more.<br /><br /><br />In a related effort, I have also been leading the AB\u2019s \u201c3Is Priority Project<a href=\"https://tantek.com/#t5WX1_note-3\">\u00b3</a>\u201d (Interoperability and the Role of Independent Implementations), which is a pretty big project to define and clarify what each of those three Is mean, with respect to each other and Incubation, which is its own Priority Project<a href=\"https://tantek.com/#t5WX1_note-4\">\u2074</a>.<br /><br />As part of the 3Is project, the first \u201cI\u201d I\u2019ve been focusing on has unsurprisingly been \u00a0\u201cInteroperable\u201d. As with other #<span class=\"p-category\">OpenAB</span> projects, our work on understanding interoperability, its aspects, and defining what do we mean by interoperable is published and iterated on the W3C\u2019s public wiki:<br /><br /><a href=\"https://www.w3.org/wiki/Interoperable\">https://www.w3.org/wiki/Interoperable</a><br /><br />This is still a work in progress, however it\u2019s sufficiently structured to take a look if interoperability is something you care about or have opinions about.<br /><br />In particular, if you know of definitions of interoperable or interoperability that resonate and make sense to you, or articles or blog posts about interoperability that explore various aspects, I am gathering such references so we can make sure the W3C\u2019s definition of interoperable is both well-stated, and clearly reflects a broader industry understanding of interoperability.<br /><br />References:<br /><br /><a href=\"https://tantek.com/#t5WX1_ref-1\">\u00b9</a> <a href=\"https://www.w3.org/TR/w3c-vision/#acknowledgements\">https://www.w3.org/TR/w3c-vision/#acknowledgements</a><br /><a href=\"https://tantek.com/#t5WX1_ref-2\">\u00b2</a> <a href=\"https://www.w3.org/wiki/AB/VisionTF\">https://www.w3.org/wiki/AB/VisionTF</a><br /><a href=\"https://tantek.com/#t5WX1_ref-3\">\u00b3</a> <a href=\"https://www.w3.org/wiki/AB/2024_Priorities#Interoperability_and_the_Role_of_Independent_Implementations\">https://www.w3.org/wiki/AB/2024_Priorities#Interoperability_and_the_Role_of_Independent_Implementations</a><br /><a href=\"https://tantek.com/#t5WX1_ref-4\">\u2074</a> <a href=\"https://www.w3.org/wiki/AB/2024_Priorities#Incubation\">https://www.w3.org/wiki/AB/2024_Priorities#Incubation</a>"
},
"author": {
"type": "card",
"name": "Tantek \u00c7elik",
"url": "https://tantek.com/",
"photo": "https://tantek.com/photo.jpg"
},
"post-type": "note",
"_id": "40881075",
"_source": "2460"
}
{
"type": "entry",
"published": "2024-04-17T15:12:43-07:00",
"url": "https://aaronparecki.com/2024/04/17/16/",
"category": [
"travel"
],
"syndication": [
"https://bsky.app/profile/aaronpk.com/post/3kqecnqvykf23"
],
"content": {
"text": "This was my first time traveling with a USB-C iPhone and I definitely forgot that my AirPods still charge with a Lightning cord oops"
},
"author": {
"type": "card",
"name": "Aaron Parecki",
"url": "https://aaronparecki.com/",
"photo": "https://aperture-media.p3k.io/aaronparecki.com/41061f9de825966faa22e9c42830e1d4a614a321213b4575b9488aa93f89817a.jpg"
},
"post-type": "note",
"_id": "40868163",
"_source": "16"
}
I got an Aranet4 CO2 sensor at the end of last year. My home is usually around 600ppm, which is decent. I turned on one gas burner on the stove and it quickly jumped to 1300 (poor). Opening a window and turning on a fan brought it back to about 1000. Ventilation is important!
{
"type": "entry",
"published": "2024-04-16 19:57-0700",
"url": "https://gregorlove.com/2024/04/i-got-an-aranet/",
"category": [
"AirQuality"
],
"content": {
"text": "I got an Aranet4 CO2 sensor at the end of last year. My home is usually around 600ppm, which is decent. I turned on one gas burner on the stove and it quickly jumped to 1300 (poor). Opening a window and turning on a fan brought it back to about 1000. Ventilation is important!",
"html": "<p>I got an Aranet4 CO2 sensor at the end of last year. My home is usually around 600ppm, which is decent. I turned on one gas burner on the stove and it quickly jumped to 1300 (poor). Opening a window and turning on a fan brought it back to about 1000. Ventilation is important!</p>"
},
"author": {
"type": "card",
"name": "gRegor Morrill",
"url": "https://gregorlove.com/",
"photo": "https://gregorlove.com/site/assets/files/6268/profile-2021-square.300x0.jpg"
},
"post-type": "note",
"_id": "40859867",
"_source": "95"
}
{
"type": "entry",
"published": "2024-04-15 12:16-0700",
"url": "https://gregorlove.com/2024/04/have-questions-about-html/",
"category": [
"indieweb"
],
"content": {
"text": "Have questions about HTML/CSS? Join the Front End Study Hall hosted by @artlung@xoxo.zone on Zoom next Wednesday, April 24!",
"html": "<p>Have questions about HTML/CSS? Join the <a href=\"https://events.indieweb.org/2024/04/front-end-study-hall-FHS5M2AofkU4\">Front End Study Hall</a> hosted by <a href=\"https://xoxo.zone/@artlung\">@artlung@xoxo.zone</a> on Zoom next Wednesday, April 24!</p>"
},
"author": {
"type": "card",
"name": "gRegor Morrill",
"url": "https://gregorlove.com/",
"photo": "https://gregorlove.com/site/assets/files/6268/profile-2021-square.300x0.jpg"
},
"post-type": "note",
"_id": "40847715",
"_source": "95"
}
Last week I participated @W3.org (@w3c@w3c.social) #w3cAC (W3C Advisory Committee¹), #w3cAB (W3C Advisory Board²@ab@w3c.social), and #w3cBoard (Board of the W3C Corporation³) meetings in Hiroshima, Japan.
The AC (Advisory Committee) meeting was two days, followed by two days of AB and Board meetings which started with a half-day joint session (including the #w3cTAG), then separate meetings to focus on their own tasks & discussions.
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 W3C Board, the W3C TAG (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¹²):
Most of the W3C meeting materials and discussions were also W3C Member-confidential, however many 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.
{
"type": "entry",
"published": "2024-04-14 19:00-0700",
"url": "https://tantek.com/2024/105/t1/w3c-advisory-committee-meetings",
"category": [
"w3cAC",
"w3cAB",
"w3cBoard",
"w3cTAG",
"w3cTPAC",
"W3C",
"OpenAB",
"IndieWeb"
],
"content": {
"text": "Last week I participated @W3.org (@w3c@w3c.social) #w3cAC (W3C Advisory Committee\u00b9), #w3cAB (W3C Advisory Board\u00b2 @ab@w3c.social), and #w3cBoard (Board of the W3C Corporation\u00b3) meetings in Hiroshima, Japan.\n\nThe AC (Advisory Committee) meeting was two days, followed by two days of AB and Board meetings which started with a half-day joint session (including the #w3cTAG), then separate meetings to focus on their own tasks & discussions.\n\nThe W3C Process\u2074 describes the twice a year AC (Advisory Committee) Meetings\u2075. 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 W3C Board, the W3C TAG (W3C Technical Architecture Group\u2076 @tag@w3c.social), Working Group\u2077 chairs, Chapter\u2078 staff, and this time also a W3C Invited Expert designated observer\u2079.\n\nThe 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\u00b9\u2070 meetings). The existence, dates, and location of the event are public\u00b9\u00b9, 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\u00b9\u00b2): \n\n* https://www.w3.org/wiki/AC/Meetings#2024_Spring\n\nMost of the W3C meeting materials and discussions were also W3C Member-confidential, however many of the presentations are publicly viewable, and a few more may be shared publicly after the fact.\n\nMyself 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.\n\nAside: 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\n\nLike most conferences, I got as much out of side conversations at breaks (AKA hallway track\u00b9\u00b3) and meals as I did from scheduled talks and panels.\n\nFor now, here are the events, slides, and videos which are publicly viewable that provide an interesting glimpse into some of the topics discussed:\n* \ud83d\udcc4 report: https://www.w3.org/reports/ai-web-impact/\n* \ud83d\uddbc slides: https://www.w3.org/2024/Talks/ac-slides/engaging-the-members/\n* \ud83d\uddbc slides: https://www.w3.org/2024/Talks/ac-slides/exploration/\n* \ud83d\uddbc slides: https://www.w3.org/2024/Talks/ac-slides/OHCHR.pdf\n* \u25b6\ufe0f video 5m42s: https://customer-0kix77mxh2zzzae0.cloudflarestream.com/9ad1e01b20d9b15d413f02c0ada3fe34/watch\n* \u25b6\ufe0f video 4m16s: https://customer-0kix77mxh2zzzae0.cloudflarestream.com/1bfde2bf614d7535b8a775217a949974/watch\n* \ud83d\uddd3 event: https://www.w3.org/events/meetings/13213a52-8159-4af8-b939-38c7880ba266/\n* \ud83d\uddbc slides: https://www.w3.org/2024/Talks/ac-slides/lt-deepfake/\n* \ud83d\uddbc slides: https://www.w3.org/2024/Talks/ac-slides/lt-accessing-llms-data/\n* \ud83d\uddbc slides: https://www.w3.org/2024/Talks/ac-slides/pac-data-sovereignty/ (nice #IndieWeb mention)\n* \ud83d\uddbc slides: https://www.w3.org/2024/Talks/ac-slides/intro-content-credentials.pdf\n* \ud83d\uddbc slides: https://w3c.github.io/adapt/presentations/ac2024/ Warning: the proposed use of .well-known therein is IMO a bad mistake. Unnecessary reinvention (most handled by existing rel values\u00b9\u2074), more complex to author (requires sidefiles\u00b9\u2075), harder to publish (requires site admin root access), likely to become inaccurate (Ruby\u2019s postulate\u00b9\u2076), and fragile (site admins frequently break .well-known for individual pages). A full critique likely requires its own blog post.\n* \ud83d\uddd3 event: https://www.w3.org/events/meetings/df0b9dd8-2356-47ec-839d-eadc06da1ca1/\n\nI\u2019ll update this list with additional resources as they are made publicly viewable.\n\nIf you work for a W3C Member Organization you can view the full list of resources linked from the Member-confidential agenda: https://www.w3.org/2024/04/AC/ac-agenda.html#monday\n\nReferences:\n\n\u00b9 https://w3.org/wiki/AC\n\u00b2 https://w3.org/wiki/AB\n\u00b3 https://w3.org/wiki/Board\n\u2074 https://www.w3.org/Consortium/Process/\n\u2075 https://www.w3.org/2023/Process-20231103/#ACMeetings\n\u2076 https://w3.org/tag\n\u2077 https://www.w3.org/groups/wg/\n\u2078 https://chapters.w3.org/\n\u2079 https://www.w3.org/invited-experts/#ac-observer\n\u00b9\u2070 https://www.w3.org/wiki/TPAC\n\u00b9\u00b9 https://www.w3.org/events/ac/2024/ac-2024/\n\u00b9\u00b2 https://www.w3.org/membership/list/\n\u00b9\u00b3 https://en.wiktionary.org/wiki/hallway_track\n\u00b9\u2074 https://microformats.org/wiki/existing-rel-values\n\u00b9\u2075 https://indieweb.org/sidefile-antipattern\n\u00b9\u2076 https://intertwingly.net/slides/2004/devcon/68.html",
"html": "Last week I participated <a href=\"https://W3.org\">@W3.org</a> (<a href=\"https://w3c.social/@w3c\">@w3c@w3c.social</a>) #<span class=\"p-category\">w3cAC</span> (W3C Advisory Committee<a href=\"https://tantek.com/#t5WT1_note-1\">\u00b9</a>), #<span class=\"p-category\">w3cAB</span> (W3C Advisory Board<a href=\"https://tantek.com/#t5WT1_note-2\">\u00b2</a> <a href=\"https://w3c.social/@ab\">@ab@w3c.social</a>), and #<span class=\"p-category\">w3cBoard</span> (Board of the W3C Corporation<a href=\"https://tantek.com/#t5WT1_note-3\">\u00b3</a>) meetings in Hiroshima, Japan.<br /><br />The AC (Advisory Committee) meeting was two days, followed by two days of AB and Board meetings which started with a half-day joint session (including the #<span class=\"p-category\">w3cTAG</span>), then separate meetings to focus on their own tasks & discussions.<br /><br />The W3C Process<a href=\"https://tantek.com/#t5WT1_note-4\">\u2074</a> describes the twice a year AC (Advisory Committee) Meetings<a href=\"https://tantek.com/#t5WT1_note-5\">\u2075</a>. 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 W3C Board, the W3C TAG (W3C Technical Architecture Group<a href=\"https://tantek.com/#t5WT1_note-6\">\u2076</a> <a href=\"https://w3c.social/@tag\">@tag@w3c.social</a>), Working Group<a href=\"https://tantek.com/#t5WT1_note-7\">\u2077</a> chairs, Chapter<a href=\"https://tantek.com/#t5WT1_note-8\">\u2078</a> staff, and this time also a W3C Invited Expert designated observer<a href=\"https://tantek.com/#t5WT1_note-9\">\u2079</a>.<br /><br />The AC currently meets in the Spring on its own and a shorter meeting in the Fall as part of the annual #<span class=\"p-category\">w3cTPAC</span> (W3C Technical Plenary and Advisory Committee<a href=\"https://tantek.com/#t5WT1_note-10\">\u00b9\u2070</a> meetings). The existence, dates, and location of the event are public<a href=\"https://tantek.com/#t5WT1_note-11\">\u00b9\u00b9</a>, 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<a href=\"https://tantek.com/#t5WT1_note-12\">\u00b9\u00b2</a>): <br /><br />* <a href=\"https://www.w3.org/wiki/AC/Meetings#2024_Spring\">https://www.w3.org/wiki/AC/Meetings#2024_Spring</a><br /><br />Most of the W3C meeting materials and discussions were also W3C Member-confidential, however many of the presentations are publicly viewable, and a few more may be shared publicly after the fact.<br /><br />Myself and others at #<span class=\"p-category\">W3C</span> 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.<br /><br />Aside: I started the #<span class=\"p-category\">OpenAB</span> 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: <a href=\"https://www.w3.org/wiki/AB#Open_AB\">https://www.w3.org/wiki/AB#Open_AB</a><br /><br />Like most conferences, I got as much out of side conversations at breaks (AKA hallway track<a href=\"https://tantek.com/#t5WT1_note-13\">\u00b9\u00b3</a>) and meals as I did from scheduled talks and panels.<br /><br />For now, here are the events, slides, and videos which are publicly viewable that provide an interesting glimpse into some of the topics discussed:<br />* \ud83d\udcc4 report: <a href=\"https://www.w3.org/reports/ai-web-impact/\">https://www.w3.org/reports/ai-web-impact/</a><br />* \ud83d\uddbc slides: <a href=\"https://www.w3.org/2024/Talks/ac-slides/engaging-the-members/\">https://www.w3.org/2024/Talks/ac-slides/engaging-the-members/</a><br />* \ud83d\uddbc slides: <a href=\"https://www.w3.org/2024/Talks/ac-slides/exploration/\">https://www.w3.org/2024/Talks/ac-slides/exploration/</a><br />* \ud83d\uddbc slides: <a href=\"https://www.w3.org/2024/Talks/ac-slides/OHCHR.pdf\">https://www.w3.org/2024/Talks/ac-slides/OHCHR.pdf</a><br />* \u25b6\ufe0f video 5m42s: <a href=\"https://customer-0kix77mxh2zzzae0.cloudflarestream.com/9ad1e01b20d9b15d413f02c0ada3fe34/watch\">https://customer-0kix77mxh2zzzae0.cloudflarestream.com/9ad1e01b20d9b15d413f02c0ada3fe34/watch</a><br />* \u25b6\ufe0f video 4m16s: <a href=\"https://customer-0kix77mxh2zzzae0.cloudflarestream.com/1bfde2bf614d7535b8a775217a949974/watch\">https://customer-0kix77mxh2zzzae0.cloudflarestream.com/1bfde2bf614d7535b8a775217a949974/watch</a><br />* \ud83d\uddd3 event: <a href=\"https://www.w3.org/events/meetings/13213a52-8159-4af8-b939-38c7880ba266/\">https://www.w3.org/events/meetings/13213a52-8159-4af8-b939-38c7880ba266/</a><br />* \ud83d\uddbc slides: <a href=\"https://www.w3.org/2024/Talks/ac-slides/lt-deepfake/\">https://www.w3.org/2024/Talks/ac-slides/lt-deepfake/</a><br />* \ud83d\uddbc slides: <a href=\"https://www.w3.org/2024/Talks/ac-slides/lt-accessing-llms-data/\">https://www.w3.org/2024/Talks/ac-slides/lt-accessing-llms-data/</a><br />* \ud83d\uddbc slides: <a href=\"https://www.w3.org/2024/Talks/ac-slides/pac-data-sovereignty/\">https://www.w3.org/2024/Talks/ac-slides/pac-data-sovereignty/</a> (nice #<span class=\"p-category\">IndieWeb</span> mention)<br />* \ud83d\uddbc slides: <a href=\"https://www.w3.org/2024/Talks/ac-slides/intro-content-credentials.pdf\">https://www.w3.org/2024/Talks/ac-slides/intro-content-credentials.pdf</a><br />* \ud83d\uddbc slides: <a href=\"https://w3c.github.io/adapt/presentations/ac2024/\">https://w3c.github.io/adapt/presentations/ac2024/</a> Warning: the proposed use of .well-known therein is IMO a bad mistake. Unnecessary reinvention (most handled by existing rel values<a href=\"https://tantek.com/#t5WT1_note-14\">\u00b9\u2074</a>), more complex to author (requires sidefiles<a href=\"https://tantek.com/#t5WT1_note-15\">\u00b9\u2075</a>), harder to publish (requires site admin root access), likely to become inaccurate (Ruby\u2019s postulate<a href=\"https://tantek.com/#t5WT1_note-16\">\u00b9\u2076</a>), and fragile (site admins frequently break .well-known for individual pages). A full critique likely requires its own blog post.<br />* \ud83d\uddd3 event: <a href=\"https://www.w3.org/events/meetings/df0b9dd8-2356-47ec-839d-eadc06da1ca1/\">https://www.w3.org/events/meetings/df0b9dd8-2356-47ec-839d-eadc06da1ca1/</a><br /><br />I\u2019ll update this list with additional resources as they are made publicly viewable.<br /><br />If you work for a W3C Member Organization you can view the full list of resources linked from the Member-confidential agenda: <a href=\"https://www.w3.org/2024/04/AC/ac-agenda.html#monday\">https://www.w3.org/2024/04/AC/ac-agenda.html#monday</a><br /><br />References:<br /><br /><a href=\"https://tantek.com/#t5WT1_ref-1\">\u00b9</a> <a href=\"https://w3.org/wiki/AC\">https://w3.org/wiki/AC</a><br /><a href=\"https://tantek.com/#t5WT1_ref-2\">\u00b2</a> <a href=\"https://w3.org/wiki/AB\">https://w3.org/wiki/AB</a><br /><a href=\"https://tantek.com/#t5WT1_ref-3\">\u00b3</a> <a href=\"https://w3.org/wiki/Board\">https://w3.org/wiki/Board</a><br /><a href=\"https://tantek.com/#t5WT1_ref-4\">\u2074</a> <a href=\"https://www.w3.org/Consortium/Process/\">https://www.w3.org/Consortium/Process/</a><br /><a href=\"https://tantek.com/#t5WT1_ref-5\">\u2075</a> <a href=\"https://www.w3.org/2023/Process-20231103/#ACMeetings\">https://www.w3.org/2023/Process-20231103/#ACMeetings</a><br /><a href=\"https://tantek.com/#t5WT1_ref-6\">\u2076</a> <a href=\"https://w3.org/tag\">https://w3.org/tag</a><br /><a href=\"https://tantek.com/#t5WT1_ref-7\">\u2077</a> <a href=\"https://www.w3.org/groups/wg/\">https://www.w3.org/groups/wg/</a><br /><a href=\"https://tantek.com/#t5WT1_ref-8\">\u2078</a> <a href=\"https://chapters.w3.org/\">https://chapters.w3.org/</a><br /><a href=\"https://tantek.com/#t5WT1_ref-9\">\u2079</a> <a href=\"https://www.w3.org/invited-experts/#ac-observer\">https://www.w3.org/invited-experts/#ac-observer</a><br /><a href=\"https://tantek.com/#t5WT1_ref-10\">\u00b9\u2070</a> <a href=\"https://www.w3.org/wiki/TPAC\">https://www.w3.org/wiki/TPAC</a><br /><a href=\"https://tantek.com/#t5WT1_ref-11\">\u00b9\u00b9</a> <a href=\"https://www.w3.org/events/ac/2024/ac-2024/\">https://www.w3.org/events/ac/2024/ac-2024/</a><br /><a href=\"https://tantek.com/#t5WT1_ref-12\">\u00b9\u00b2</a> <a href=\"https://www.w3.org/membership/list/\">https://www.w3.org/membership/list/</a><br /><a href=\"https://tantek.com/#t5WT1_ref-13\">\u00b9\u00b3</a> <a href=\"https://en.wiktionary.org/wiki/hallway_track\">https://en.wiktionary.org/wiki/hallway_track</a><br /><a href=\"https://tantek.com/#t5WT1_ref-14\">\u00b9\u2074</a> <a href=\"https://microformats.org/wiki/existing-rel-values\">https://microformats.org/wiki/existing-rel-values</a><br /><a href=\"https://tantek.com/#t5WT1_ref-15\">\u00b9\u2075</a> <a href=\"https://indieweb.org/sidefile-antipattern\">https://indieweb.org/sidefile-antipattern</a><br /><a href=\"https://tantek.com/#t5WT1_ref-16\">\u00b9\u2076</a> <a href=\"https://intertwingly.net/slides/2004/devcon/68.html\">https://intertwingly.net/slides/2004/devcon/68.html</a>"
},
"author": {
"type": "card",
"name": "Tantek \u00c7elik",
"url": "https://tantek.com/",
"photo": "https://tantek.com/photo.jpg"
},
"post-type": "note",
"_id": "40839584",
"_source": "2460"
}
I actually didn’t realize when I took this photo with my iPhone how incredible the lighting was. I saw it in my photo library a few hours later and went wait, what?? A couple tweaks for contrast and color tint in Lightroom later, and boom! 🤩 #Portland#OregonExplored#iPhonePro
{
"type": "entry",
"author": {
"name": "Jared White",
"url": "https://jaredwhite.com/",
"photo": null
},
"url": "https://jaredwhite.com/pictures/20240410/i-actually-didn-t-realize-when-i-took-this-photo-with",
"published": "2024-04-10T07:52:35-07:00",
"content": {
"html": "<img alt=\"\" src=\"https://pxscdn.com/public/m/_v2/4580/c6a394f69-21cf85/NLB88MWk39PC/zGsf0Y8HEzSamUsJ98Ny4cbkykmQNgOCJDK1est9.jpg\" /><p>I actually didn\u2019t realize when I took this photo with my iPhone how incredible the lighting was. I saw it in my photo library a few hours later and went <em>wait, what??</em> A couple tweaks for contrast and color tint in Lightroom later, and boom! \ud83e\udd29 <br /><a href=\"https://jaredwhite.com/tag/portland\">#Portland</a> <a href=\"https://jaredwhite.com/tag/oregonexplored\">#OregonExplored</a> <a href=\"https://jaredwhite.com/tag/iphonepro\">#iPhonePro</a></p>",
"text": "I actually didn\u2019t realize when I took this photo with my iPhone how incredible the lighting was. I saw it in my photo library a few hours later and went wait, what?? A couple tweaks for contrast and color tint in Lightroom later, and boom! \ud83e\udd29 \n#Portland #OregonExplored #iPhonePro"
},
"post-type": "note",
"_id": "40831581",
"_source": "2783"
}
I stopped at a convenience store at DFW that has Amazon's "Just Walk Out" tech, which is powered by *so many* cameras. Also apparently they are shutting the whole program down because it actually relies on low paid workers in India?? Surprise?
{
"type": "entry",
"published": "2024-04-13T18:46:03-05:00",
"url": "https://aaronparecki.com/2024/04/13/34/ai",
"category": [
"amazon",
"ai"
],
"photo": [
"https://aperture-media.p3k.io/aaronparecki.com/b7fee41d44b722951e1b0340bd409dcfde35751e23918c4e25f9adb3ea954f46.jpg"
],
"content": {
"text": "I stopped at a convenience store at DFW that has Amazon's \"Just Walk Out\" tech, which is powered by *so many* cameras. Also apparently they are shutting the whole program down because it actually relies on low paid workers in India?? Surprise?"
},
"author": {
"type": "card",
"name": "Aaron Parecki",
"url": "https://aaronparecki.com/",
"photo": "https://aperture-media.p3k.io/aaronparecki.com/41061f9de825966faa22e9c42830e1d4a614a321213b4575b9488aa93f89817a.jpg"
},
"post-type": "photo",
"_id": "40830064",
"_source": "16"
}
