Re: Public concerns over new W3C logo

> Time to own up to the mistake, limit damage by reverting the change and
come up with a better plan. It is clear that something went seriously wrong
here.

I don’t think there’s consensus that the rebranding itself is a mistake.
While I agree that there has been a breakdown in communication along the
way and remediation is likely necessary, that doesn’t mean the whole
branding process is a failure.

> I do not want this w3c logo to go down in design history the same way Fergie's
take on the national anthem <https://www.youtube.com/watch?v=CMA2iF6RuXk> did
- which I think it will, given how enormously bad the design is on basic
objective fronts.

Tantek shared 32 or so links to negative comments about the logo. There
have been a few more anecdotal accounts in the thread but it seems that for
the most part, the wider technical community hasn’t commented positively or
negatively.

I worry we may be blowing this out of proportion and investing excessive
time into something that ultimately most people don’t care enough about one
way or another.

Regardless of that, I think we should avoid making demands and be
respectful towards the team, CEO and board; and allow them to figure out
the appropriate next steps, if any are to be made.

Kindly,

Lola Odelola
Web Standards Technologist
lolaslab.co
I’m based in the UK & typically work UK hours.


On Wed, 22 Oct 2025 at 20:19, Simon Wijckmans <simon@cside.dev> wrote:

> I strongly believe 1 is the right action now (do not wait another week
> please) with 2 to follow soon and perhaps a good idea to start at TPAC.
> Ultimately, I believe Seth is the person to call the shots on this hence
> the direct CC on this thread.
>
> Time to own up to the mistake, limit damage by reverting the change and
> come up with a better plan. It is clear that something went seriously wrong
> here.
>
> I do not want this w3c logo to go down in design history the same way Fergie's
> take on the national anthem <https://www.youtube.com/watch?v=CMA2iF6RuXk> did
> - which I think it will, given how enormously bad the design is on basic
> objective fronts.
>
>
>
> On Wed, 22 Oct 2025 at 12:11, Sue Koomen <Sue.Koomen@aexp.com> wrote:
>
>> Thank you Steve…I concur with Option 1.
>>
>>
>>
>> *From:* Steve Capell <steve@pyx.io>
>> *Sent:* Wednesday, October 22, 2025 11:30 AM
>> *To:* Emmet McNally <info@irishmediaagency.ie>
>> *Cc:* Tatsuya.Igarashi@sony.com; Wendy Reid <wendyreid@fastmail.com>;
>> Chris Wilson <cwilso@google.com>; Tantek Ç. <tantek@mozilla.com>;
>> w3c-ac-forum <w3c-ac-forum@w3.org>; www-archive@w3.org
>> *Subject:* Re: Public concerns over new W3C logo
>>
>>
>>
>> I just realised that the new brand is already released. I thought it was
>> still an internal consultation - which would have made it easier to drop
>>
>>
>>
>> Now that it’s already live at https://www.w3.org/ it’s a bit harder to
>> bury.  I suppose there are three options
>>
>> 1- revert to the old logo with a little apology.  Most occasional
>> visitors probably won’t even notice the interlude
>>
>> 2- start another rebranding effort.  Although if this path is chosen, I’d
>> still do option 1 first.
>>
>> 3- leave the new brand in place and hope that the embarrassing memes fade
>> away and everyone just gets back to work and forgets about this awkward
>> moment.
>>
>>
>>
>> I still prefer option 1.  In the meantime I’ll try to “un-see” the
>> analogies that have been drawn.
>>
>>
>>
>> Kind regards
>>
>>
>>
>> Steve Capell
>>
>> Pyx Industries Pty Ltd
>>
>> Mob: 0410 437854
>>
>>
>>
>> On 23 Oct 2025, at 3:26 am, Steve Capell <steve@pyx.io> wrote:
>>
>> I my have missed it but I don’t remember any member consultation about
>> whether to rebrand, only on the form of the rebranding
>>
>>
>>
>> In my view you need a public reason to change a very public logo.  Whilst
>> there may be an internal eagerness to refresh, I don’t see any wider public
>> sentiment for that. A logo projects an organisations public image and I
>> can’t see any reason to change it
>>
>>
>>
>> My suggestion is not to fall for the sunk cost syndrome, accept that
>> mistakes are made from time to time, and just quietly drop the rebranding
>> project.
>>
>>
>>
>> Keep the current logo please
>>
>>
>>
>> Steve Capell
>>
>> Pyx Industries Pty Ltd
>>
>> Mob: 0410 437854
>>
>>
>>
>> On 22 Oct 2025, at 11:24 pm, Emmet McNally <info@irishmediaagency.ie>
>> wrote:
>>
>> 
>>
>> As a new member here, my perspective is admittedly limited when it comes
>> to how the logo process unfolded. My intention is simply to share a view
>> that might reflect what newer members are thinking.
>>
>> At our agency, when we work on a new logo for a client, we generally
>> wouldn’t advise a major departure from the existing style unless there’s a
>> need to move away from negative associations. Otherwise, it’s about
>> bringing the logo on a journey, evolving it gradually over time rather than
>> reinventing it in one go.
>>
>> From my perspective, W3C is an organisation that trades heavily on
>> credibility. When I first saw the new logo, though, my honest reaction was
>> that it unintentionally resembles something inappropriate. People have been
>> sketching that same shape since the dawn of time, and unfortunately, it’s
>> hard to unsee once noticed. That visual association doesn’t do much to help
>> credibility, and to be frank, I’d hesitate to display the W3C Member logo
>> on our own agency’s site because of that. Also, the previous logo clearly
>>
>> Maybe it’s an Irish thing, but I’d wager if I showed it to 100 people on
>> the street here, they’d all see the same thing.
>>
>> It might be too late on the current logo, but maybe a "phase 2" approach
>> on the logo could adapt it a little to remove the issue.
>>
>> Kind regards,
>> *Emmet*
>>
>>
>>
>>
>>
>> On Wed, 22 Oct 2025 at 07:28, Tatsuya.Igarashi@sony.com <
>> Tatsuya.Igarashi@sony.com> wrote:
>>
>> >Important things are happening within W3C and outside, is it really the
>> best use of your time to debate the finer points of whether the logo
>> process was done to everyone’s satisfaction? I don’t think so, I think
>> we ?>+are standards people and we like to follow rules, but we can
>> sometimes get so caught up in making sure how we do things is correct we
>> miss asking whether we are actually doing the right thing in the first
>> place.
>>
>> >
>>
>> >-Wendy
>>
>>
>>
>> What I have repeatedly expressed at the AB meetings is that my concern
>> regarding this logo issue is not whether the logo is good or bad, or
>> whether someone likes it or not. As Chris pointed out, the issue is that
>> the community was less involved in the logo process. Beyond this specific
>> case, I believe that how members’ opinions are reflected in W3C’s
>> strategy and operations is something that should be discussed and
>> continuously improved for the future.
>>
>>
>> I do not think the Tantek’s email is  "personal vendetta" at all.  I
>> think it is good for us to share public reactions on our organization and
>> openly discuss these matters. Before making the logo public, I believe we
>> should have the discussion about the logo change like this thread. I
>> appreciate the replies from Nayan, Don and Sue. I remember the AC reps
>> conducted a survey at the AC meeting in April to find out what the AC reps
>> think about the new logo. I want see the results of that survey and know
>> the other members’ thoughts on the strategic decision of the
>> organization.
>>
>>
>>
>> To answer the query, I searched Japanese social media but did not find
>> any particularly negative comments. There may be cultural differences, as
>> Japanese people tend not to express their true feelings openly or directly.
>> What concerned me more was that there were very few reactions about the W3C
>> logo change in Japan.  To be honest, I don’t really see how changing the
>> logo is meaningful for W3C.  I hope that the team will report
>>  internal/external feedback on the new W3C logo and  the reputation the
>> logo change.
>>
>>
>> PS. I believe that openly discussing issues and seeking ways to improve
>> how we should do thing for the future is the right thing to do for a
>> membership organization.
>>
>>
>>
>> Thank you.
>>
>>
>> *****************************************
>>
>> Tatsuya Igarashi   Sony Group Corporation
>>
>>
>>
>>
>>
>>
>>
>> *From:* Wendy Reid <wendyreid@fastmail.com>
>> *Sent:* Wednesday, October 22, 2025 2:04 AM
>> *To:* Chris Wilson <cwilso@google.com>
>> *Cc:* Tantek Ç. <tantek@mozilla.com>; w3c-ac-forum <w3c-ac-forum@w3.org>;
>> www-archive@w3.org
>> *Subject:* Re: Public concerns over new W3C logo
>>
>>
>>
>> There is always room for improvement and I look forward to future
>> iterations and initiatives on this. There is something being unspoken in
>> all of this. I find it really concerning that this is where people are
>> putting their energy when there
>>
>> There is always room for improvement and I look forward to future
>> iterations and initiatives on this.
>>
>>
>>
>> There is something being unspoken in all of this. I find it really
>> concerning that this is where people are putting their energy when there
>> are far more important and interesting things the AC could (and should) be
>> discussing. I also believe it is petty behaviour like this that makes
>> participation in this list so undesirable.
>>
>>
>>
>> Just in the last month there are several things that have happened that I
>> think would benefit tremendously from conversation between AC reps, such as
>> the announcement about Privacy Sandbox
>> <https://urldefense.com/v3/__https:/privacysandbox.com/news/update-on-plans-for-privacy-sandbox-technologies/__;!!O7_YSHcmd9jp3hj_4dEAcyQ!zJ1teFcEHQwAFXB7fPgOqa6vKpQndzevToKKY_S1mvu-63KWXjX15CgKG712SEXI65_ryo8vKUatywoWTt3urUGB$>,
>> open charters for PNG and Media, the US Justice Department potentially
>> reviewing their decision on ADA Title II (which involves WCAG), charter
>> refinement for MiniApps, the publication of the Web Sustainability
>> Guidelines Draft, or plans for TPAC in a few weeks.
>>
>>
>>
>> Important things are happening within W3C and outside, is it really the
>> best use of your time to debate the finer points of whether the logo
>> process was done to everyone’s satisfaction? I don’t think so, I think
>> we are standards people and we like to follow rules, but we can sometimes
>> get so caught up in making sure how we do things is correct we miss asking
>> whether we are actually doing the right thing in the first place.
>>
>>
>>
>> -Wendy
>>
>>
>>
>> On Oct 21, 2025, at 10:52 AM, Chris Wilson <cwilso@google.com> wrote:
>>
>> 
>>
>> Firmly taking off several hats:  I am not representing the Board nor
>> Google in this particular instance, merely a long-term community member.
>>
>>
>>
>> I'd like to de-escalate the tone from "personal vendetta".  For what it's
>> worth, I too have seen far more negative comments (or "meh") than positive
>> ones.  I would feel more comfortable with an equitable collection of data
>> points than what Tantek suggests, but I do think it's worth introspection
>> that attempts to avoid confirmation bias (in both directions).  I don't
>> expect anything to change with this rebrand at this point, of course.
>>
>>
>>
>> Wendy, you identified the exact problem that a significant part of the
>> W3C community has had with this rebranding: there was an emotional
>> attachment to the old brand, and the community did not call for the erasure
>> of that identity.  I've been on record since I first saw the new logo as
>> not being a fan (I'm sophomoric enough to not be able to unsee the visual
>> associations), but I can understand why others might like it.  My primary
>> concern was always that it represented a clear and complete break from the
>> previous branding and identity. The emotional cost to the community seemed
>> unnecessary.
>>
>>
>>
>> I have to disagree that the Team had "many rounds of consultation and
>> even delayed things to address comments."  In the initial presentation, it
>> was made clear that the Team was not asking for consultation, merely
>> support, and I don't see that any changes were made to address comments.  I
>> do hope that when there is an inevitable future rebranding, the community
>> is more involved from the beginning.
>>
>>
>>
>> -Chris
>>
>>
>>
>>
>>
>> On Tue, Oct 21, 2025 at 6:52 AM Wendy Reid <wendyreid@fastmail.com>
>> wrote:
>>
>> Tantek,
>>
>>
>>
>> Your personal vendetta against this logo started when it was first
>> presented to the AB early this year, and does not seem to have subsided. I
>> understand you don’t like it, that is perfectly ok, not everyone needs
>> to like everything.
>>
>>
>>
>> The points you raise here are the same ones we spent far too long
>> debating earlier this year. Choosing to focus on some negative responses on
>> socials is confirmation bias. There were many positive ones too, I note
>> those aren’t part of your analysis.
>>
>>
>>
>> When change happens, especially in branding, there is always an
>> inevitable divide in reactions. Some people like a thing immediately, some
>> hate it, most are ambivalent. The W3C logo was the same for a long time,
>> emotional attachment, or at least comfort, are inevitable. For what it’s
>> worth, I really like it, I’m sure others do too.
>>
>>
>>
>> What I do want to call out here is how disrespectful and disappointing
>> this approach is. The Team worked hard to make this happen, they had many
>> rounds of consultation and even delayed things to address comments. At this
>> point, you are just mad they didn’t listen to you, and I think you need
>> to take a hard look at yourself to question why you felt this was a good
>> use of your time and efforts. It’s clear you care about the community,
>> but choosing to publicly and repeatedly undermine the work of the Team is
>> not the kind of behaviour I think appropriate for a member of the AC. It is
>> not the AC vs the Team, we are all in this together.
>>
>>
>>
>> Have some faith in the people we work with everyday.
>>
>>
>>
>> -Wendy
>>
>>
>>
>> On Oct 21, 2025, at 1:25 AM, Tantek Ç. <tantek@mozilla.com> wrote:
>>
>> 
>>
>> Dear AC:
>>
>>
>>
>> Summary: The new W3C logo has generated non-trivial public negative
>> feedback and reactions that are both concerning and may merit action. This
>> email summarizes the patterns I have seen so far. If you are also a
>> concerned Member who has, or has heard, negative feedback, please feel free
>> to email me directly.
>>
>>
>>
>> The intent of this thread is to document negative public reactions.
>> Please only reply if you have more negative public reactions to add, with
>> new public citations (URLs). If you want to make a different sort of
>> comment please start a new email thread (with new subject) accordingly.
>>
>>
>>
>> Negative public reactions to the new W3C logo fall into the following
>> categories (in order of instances found so far):
>>
>>
>>
>>    1. (17) genitalia
>>    2. (7) excrement
>>    3. (6) unclear, unreadable, illegible, confusing, or distracting
>>    4. (3) body parts (other than genitalia, or in general)
>>    5. (2) coat hanger
>>    6. (2) obscenity, perversion, or vulgarity
>>
>>
>>
>> I believe these public concerns are of broader public W3C community
>> interest so I have cc’d www-archive for the record.
>>
>>
>>
>> Sources of negative feedback:
>>
>>    - Replies to the W3C.social post:
>>    https://w3c.social/@w3c/115299385112878605
>>    <https://urldefense.com/v3/__https:/w3c.social/@w3c/115299385112878605__;!!O7_YSHcmd9jp3hj_4dEAcyQ!zJ1teFcEHQwAFXB7fPgOqa6vKpQndzevToKKY_S1mvu-63KWXjX15CgKG712SEXI65_ryo8vKUatywoWTuxxVpvK$>
>>
>>    - #W3C hashtag: https://mastodon.social/tags/w3c
>>    <https://urldefense.com/v3/__https:/mastodon.social/tags/w3c__;!!O7_YSHcmd9jp3hj_4dEAcyQ!zJ1teFcEHQwAFXB7fPgOqa6vKpQndzevToKKY_S1mvu-63KWXjX15CgKG712SEXI65_ryo8vKUatywoWTvwYuJ3T$>
>>
>>    - Reddit posts:
>>    https://www.reddit.com/r/web_design/comments/1o6kl2k/w3c_logo_refresh/
>>    <https://urldefense.com/v3/__https:/www.reddit.com/r/web_design/comments/1o6kl2k/w3c_logo_refresh/__;!!O7_YSHcmd9jp3hj_4dEAcyQ!zJ1teFcEHQwAFXB7fPgOqa6vKpQndzevToKKY_S1mvu-63KWXjX15CgKG712SEXI65_ryo8vKUatywoWTppuVAKm$>
>>
>>
>> https://www.reddit.com/r/webdev/comments/1o6kled/w3c_logo_refresh/
>> <https://urldefense.com/v3/__https:/www.reddit.com/r/webdev/comments/1o6kled/w3c_logo_refresh/__;!!O7_YSHcmd9jp3hj_4dEAcyQ!zJ1teFcEHQwAFXB7fPgOqa6vKpQndzevToKKY_S1mvu-63KWXjX15CgKG712SEXI65_ryo8vKUatywoWTrIvIhBZ$>
>>
>>    - Hackernews post: https://news.ycombinator.com/item?id=45578265
>>    <https://urldefense.com/v3/__https:/news.ycombinator.com/item?id=45578265__;!!O7_YSHcmd9jp3hj_4dEAcyQ!zJ1teFcEHQwAFXB7fPgOqa6vKpQndzevToKKY_S1mvu-63KWXjX15CgKG712SEXI65_ryo8vKUatywoWThwJ91V_$>
>>    - Other posts folks shared with me and their replies.
>>
>>
>>
>> For reference, many of us brought up concerns like these and others in
>> feedback in meetings this past March:
>>
>>    - https://www.w3.org/2025/03/13-2025logo-minutes.html
>>    <https://urldefense.com/v3/__https:/www.w3.org/2025/03/13-2025logo-minutes.html__;!!O7_YSHcmd9jp3hj_4dEAcyQ!zJ1teFcEHQwAFXB7fPgOqa6vKpQndzevToKKY_S1mvu-63KWXjX15CgKG712SEXI65_ryo8vKUatywoWTn7hUr87$>
>>    - https://www.w3.org/2025/03/18-ac-minutes.html
>>    <https://urldefense.com/v3/__https:/www.w3.org/2025/03/18-ac-minutes.html__;!!O7_YSHcmd9jp3hj_4dEAcyQ!zJ1teFcEHQwAFXB7fPgOqa6vKpQndzevToKKY_S1mvu-63KWXjX15CgKG712SEXI65_ryo8vKUatywoWTss0embJ$>
>>
>>
>>
>>
>> What I am not looking for:
>>
>>    - Tone-policing. If the discussion of this issue offends you, please
>>    do not reply.
>>    - Rationalizations. If you feel like defending the new W3C logo, this
>>    is the wrong thread for that. This thread is for gathering public critical
>>    citations.
>>
>>
>>
>> What I am looking for:
>>
>>    - If you are an AC Representative (or Alternate) and have similar
>>    concerns, or have received similar feedback from your organization
>>    internally, please get in touch with me.
>>    - Public citations (URLs) of additional negative public reactions.
>>
>>
>>
>> Thanks,
>>
>>
>>
>> Tantek Çelik
>>
>> Mozilla AC Representative
>>
>>
>>
>> =====
>>
>>
>>
>> Citations of specific public reactions:
>>
>>
>>
>> =====
>>
>>
>>
>> CONTENT WARNING:
>>
>>
>>
>> The following may include (partial) text quotes which may have language
>> or links to images that some may consider offensive.
>>
>>
>>
>> If you are offended by such words or images, please skip the rest of this
>> email and do not click on the links provided.
>>
>>
>>
>>
>>
>> Dates/times are PDT. The letters in parentheses indicate the first letter
>> of the post’s category/categories, e.g. (b) for “body parts”.
>>
>>
>>
>> 2025-09-26:
>>
>>    - 04:38 (g): https://mastodon.social/@mariejulien/115269925623809543
>>    <https://urldefense.com/v3/__https:/mastodon.social/@mariejulien/115269925623809543__;!!O7_YSHcmd9jp3hj_4dEAcyQ!zJ1teFcEHQwAFXB7fPgOqa6vKpQndzevToKKY_S1mvu-63KWXjX15CgKG712SEXI65_ryo8vKUatywoWThfQfZzM$>
>>    (paraphrased translation: “does not pass my famously rigorous ‘cock or
>>    swastika’ test)
>>    - 04:39 (b): https://oisaur.com/@kgaut/115269930983516661
>>    <https://urldefense.com/v3/__https:/oisaur.com/@kgaut/115269930983516661__;!!O7_YSHcmd9jp3hj_4dEAcyQ!zJ1teFcEHQwAFXB7fPgOqa6vKpQndzevToKKY_S1mvu-63KWXjX15CgKG712SEXI65_ryo8vKUatywoWTsdRRslq$>
>>    (translated: “it even has a pair of buttocks”)
>>    - 05:21 (g): https://framapiaf.org/@monviolon/115270097219045974
>>    <https://urldefense.com/v3/__https:/framapiaf.org/@monviolon/115270097219045974__;!!O7_YSHcmd9jp3hj_4dEAcyQ!zJ1teFcEHQwAFXB7fPgOqa6vKpQndzevToKKY_S1mvu-63KWXjX15CgKG712SEXI65_ryo8vKUatywoWTgn7wvj0$>
>>    (cropped subset of logo)
>>
>>
>>
>> 2025-10-01:
>>
>>    - 08:00 (c): https://mastodon.ie/@rotan/115299504262096954
>>    <https://urldefense.com/v3/__https:/mastodon.ie/@rotan/115299504262096954__;!!O7_YSHcmd9jp3hj_4dEAcyQ!zJ1teFcEHQwAFXB7fPgOqa6vKpQndzevToKKY_S1mvu-63KWXjX15CgKG712SEXI65_ryo8vKUatywoWTqtghAZD$>
>>
>>    - 08:01 (g): https://mastodon.social/@mariejulien/115299494586267687
>>    <https://urldefense.com/v3/__https:/mastodon.social/@mariejulien/115299494586267687__;!!O7_YSHcmd9jp3hj_4dEAcyQ!zJ1teFcEHQwAFXB7fPgOqa6vKpQndzevToKKY_S1mvu-63KWXjX15CgKG712SEXI65_ryo8vKUatywoWTjrpFmH4$>
>>
>>    - 08:21 (g): https://mastodon.social/@mariejulien/115299585913099113
>>    <https://urldefense.com/v3/__https:/mastodon.social/@mariejulien/115299585913099113__;!!O7_YSHcmd9jp3hj_4dEAcyQ!zJ1teFcEHQwAFXB7fPgOqa6vKpQndzevToKKY_S1mvu-63KWXjX15CgKG712SEXI65_ryo8vKUatywoWTkhJQPUN$>
>>
>>    - 08:24 (g): https://indieweb.social/@jgarber/115299600896573084
>>    <https://urldefense.com/v3/__https:/indieweb.social/@jgarber/115299600896573084__;!!O7_YSHcmd9jp3hj_4dEAcyQ!zJ1teFcEHQwAFXB7fPgOqa6vKpQndzevToKKY_S1mvu-63KWXjX15CgKG712SEXI65_ryo8vKUatywoWThiqI-9V$>
>>
>>    - 08:52 (g): https://circumstances.run/@davidgerard/115299709910319727
>>    <https://urldefense.com/v3/__https:/circumstances.run/@davidgerard/115299709910319727__;!!O7_YSHcmd9jp3hj_4dEAcyQ!zJ1teFcEHQwAFXB7fPgOqa6vKpQndzevToKKY_S1mvu-63KWXjX15CgKG712SEXI65_ryo8vKUatywoWTj3wW_6V$>
>>
>>    - 08:59 (g): https://a11y.social/@mikemccaffrey/115302095326319054
>>    <https://urldefense.com/v3/__https:/a11y.social/@mikemccaffrey/115302095326319054__;!!O7_YSHcmd9jp3hj_4dEAcyQ!zJ1teFcEHQwAFXB7fPgOqa6vKpQndzevToKKY_S1mvu-63KWXjX15CgKG712SEXI65_ryo8vKUatywoWTokKJ33Q$>
>>    - 09:10 (e): https://mastodon.social/@nicofrand/115299779347599598
>>    <https://urldefense.com/v3/__https:/mastodon.social/@nicofrand/115299779347599598__;!!O7_YSHcmd9jp3hj_4dEAcyQ!zJ1teFcEHQwAFXB7fPgOqa6vKpQndzevToKKY_S1mvu-63KWXjX15CgKG712SEXI65_ryo8vKUatywoWTt9AO486$>
>>
>>    - 10:28 (e): https://mastodon.social/@davecykl/115300086586476170
>>    <https://urldefense.com/v3/__https:/mastodon.social/@davecykl/115300086586476170__;!!O7_YSHcmd9jp3hj_4dEAcyQ!zJ1teFcEHQwAFXB7fPgOqa6vKpQndzevToKKY_S1mvu-63KWXjX15CgKG712SEXI65_ryo8vKUatywoWTgw7Nzax$>
>>    - 17:55 (u): https://mamot.fr/@bohwaz/115301843996549479
>>    <https://urldefense.com/v3/__https:/mamot.fr/@bohwaz/115301843996549479__;!!O7_YSHcmd9jp3hj_4dEAcyQ!zJ1teFcEHQwAFXB7fPgOqa6vKpQndzevToKKY_S1mvu-63KWXjX15CgKG712SEXI65_ryo8vKUatywoWTliZxCKq$>
>>
>>    - 18:59 (g): https://a11y.social/@mikemccaffrey/115302095326319054
>>    <https://urldefense.com/v3/__https:/a11y.social/@mikemccaffrey/115302095326319054__;!!O7_YSHcmd9jp3hj_4dEAcyQ!zJ1teFcEHQwAFXB7fPgOqa6vKpQndzevToKKY_S1mvu-63KWXjX15CgKG712SEXI65_ryo8vKUatywoWTokKJ33Q$>
>>
>>    - 19:46 (g): https://c.im/@cwilcox808/115302279843647978
>>    <https://urldefense.com/v3/__https:/c.im/@cwilcox808/115302279843647978__;!!O7_YSHcmd9jp3hj_4dEAcyQ!zJ1teFcEHQwAFXB7fPgOqa6vKpQndzevToKKY_S1mvu-63KWXjX15CgKG712SEXI65_ryo8vKUatywoWTr0MKd7W$>
>>
>>
>>
>>
>> 2025-10-02:
>>
>>    - 04:50 (u): https://maly.io/@danielmunoz/115304420857752511
>>    <https://urldefense.com/v3/__https:/maly.io/@danielmunoz/115304420857752511__;!!O7_YSHcmd9jp3hj_4dEAcyQ!zJ1teFcEHQwAFXB7fPgOqa6vKpQndzevToKKY_S1mvu-63KWXjX15CgKG712SEXI65_ryo8vKUatywoWTkTxv74Q$>
>>
>>    - 04:52 (o):
>>    https://circumstances.run/@hipsterelectron/115304428218503093
>>    <https://urldefense.com/v3/__https:/circumstances.run/@hipsterelectron/115304428218503093__;!!O7_YSHcmd9jp3hj_4dEAcyQ!zJ1teFcEHQwAFXB7fPgOqa6vKpQndzevToKKY_S1mvu-63KWXjX15CgKG712SEXI65_ryo8vKUatywoWTma1QH5z$>
>>
>>    - 07:40 (g): https://social.unextro.net/@ondra/115305075794112412
>>    <https://urldefense.com/v3/__https:/social.unextro.net/@ondra/115305075794112412__;!!O7_YSHcmd9jp3hj_4dEAcyQ!zJ1teFcEHQwAFXB7fPgOqa6vKpQndzevToKKY_S1mvu-63KWXjX15CgKG712SEXI65_ryo8vKUatywoWTmsJDEzD$>
>>
>>    - 07:42 (g): https://mastodon.social/@tojiro/115305098273087104
>>    <https://urldefense.com/v3/__https:/mastodon.social/@tojiro/115305098273087104__;!!O7_YSHcmd9jp3hj_4dEAcyQ!zJ1teFcEHQwAFXB7fPgOqa6vKpQndzevToKKY_S1mvu-63KWXjX15CgKG712SEXI65_ryo8vKUatywoWTmxfQL5x$>
>>
>>    - 08:02 (e): https://eliitin-some.fi/@henrik/115305175046397749
>>    <https://urldefense.com/v3/__https:/eliitin-some.fi/@henrik/115305175046397749__;!!O7_YSHcmd9jp3hj_4dEAcyQ!zJ1teFcEHQwAFXB7fPgOqa6vKpQndzevToKKY_S1mvu-63KWXjX15CgKG712SEXI65_ryo8vKUatywoWThwQBcCH$>
>>
>>    - 10:42 (g): https://mastodon.gamedev.place/@aras/115305805942851640
>>    <https://urldefense.com/v3/__https:/mastodon.gamedev.place/@aras/115305805942851640__;!!O7_YSHcmd9jp3hj_4dEAcyQ!zJ1teFcEHQwAFXB7fPgOqa6vKpQndzevToKKY_S1mvu-63KWXjX15CgKG712SEXI65_ryo8vKUatywoWTs-GmV-s$>
>>
>>    - 20:04 (b): https://front-end.social/@leaverou/115308015280324416
>>    <https://urldefense.com/v3/__https:/front-end.social/@leaverou/115308015280324416__;!!O7_YSHcmd9jp3hj_4dEAcyQ!zJ1teFcEHQwAFXB7fPgOqa6vKpQndzevToKKY_S1mvu-63KWXjX15CgKG712SEXI65_ryo8vKUatywoWTubRHCsT$>
>>    - (o) https://nyan.lol/@zicklepop/115305222213744940
>>    <https://urldefense.com/v3/__https:/nyan.lol/@zicklepop/115305222213744940__;!!O7_YSHcmd9jp3hj_4dEAcyQ!zJ1teFcEHQwAFXB7fPgOqa6vKpQndzevToKKY_S1mvu-63KWXjX15CgKG712SEXI65_ryo8vKUatywoWThZlCjru$>
>>    (deleted)
>>
>>
>>    - “@w3c@w3c.social perverts”
>>
>>
>>
>> 2025-10-14
>>
>>    - 03:09 (u):
>>    https://www.reddit.com/r/webdev/comments/1o6kled/comment/njivht3/
>>    <https://urldefense.com/v3/__https:/www.reddit.com/r/webdev/comments/1o6kled/comment/njivht3/__;!!O7_YSHcmd9jp3hj_4dEAcyQ!zJ1teFcEHQwAFXB7fPgOqa6vKpQndzevToKKY_S1mvu-63KWXjX15CgKG712SEXI65_ryo8vKUatywoWTh3FTeQY$>
>>
>>    - 03:52 (e): https://news.ycombinator.com/item?id=45578474
>>    <https://urldefense.com/v3/__https:/news.ycombinator.com/item?id=45578474__;!!O7_YSHcmd9jp3hj_4dEAcyQ!zJ1teFcEHQwAFXB7fPgOqa6vKpQndzevToKKY_S1mvu-63KWXjX15CgKG712SEXI65_ryo8vKUatywoWTtZ2MU4j$>
>>
>>    - 03:56 (g): https://news.ycombinator.com/item?id=45578501
>>    <https://urldefense.com/v3/__https:/news.ycombinator.com/item?id=45578501__;!!O7_YSHcmd9jp3hj_4dEAcyQ!zJ1teFcEHQwAFXB7fPgOqa6vKpQndzevToKKY_S1mvu-63KWXjX15CgKG712SEXI65_ryo8vKUatywoWTqRPk4u1$>
>>
>>    - 09:46 (u):
>>    https://www.reddit.com/r/webdev/comments/1o6kled/comment/njh3hpu/
>>    <https://urldefense.com/v3/__https:/www.reddit.com/r/webdev/comments/1o6kled/comment/njh3hpu/__;!!O7_YSHcmd9jp3hj_4dEAcyQ!zJ1teFcEHQwAFXB7fPgOqa6vKpQndzevToKKY_S1mvu-63KWXjX15CgKG712SEXI65_ryo8vKUatywoWTljVMmJk$>
>>
>>    - 11:25 (c):
>>    https://www.reddit.com/r/web_design/comments/1o6kl2k/comment/njhnqtk/
>>    <https://urldefense.com/v3/__https:/www.reddit.com/r/web_design/comments/1o6kl2k/comment/njhnqtk/__;!!O7_YSHcmd9jp3hj_4dEAcyQ!zJ1teFcEHQwAFXB7fPgOqa6vKpQndzevToKKY_S1mvu-63KWXjX15CgKG712SEXI65_ryo8vKUatywoWTs2MSw1L$>
>>
>>    - 13:18 (e):
>>    https://www.reddit.com/r/web_design/comments/1o6kl2k/comment/njia9iz/
>>    <https://urldefense.com/v3/__https:/www.reddit.com/r/web_design/comments/1o6kl2k/comment/njia9iz/__;!!O7_YSHcmd9jp3hj_4dEAcyQ!zJ1teFcEHQwAFXB7fPgOqa6vKpQndzevToKKY_S1mvu-63KWXjX15CgKG712SEXI65_ryo8vKUatywoWTjH79sq7$>
>>
>>    - 16:31 (eg):
>>    https://www.reddit.com/r/web_design/comments/1o6kl2k/comment/njj9ad3/
>>    <https://urldefense.com/v3/__https:/www.reddit.com/r/web_design/comments/1o6kl2k/comment/njj9ad3/__;!!O7_YSHcmd9jp3hj_4dEAcyQ!zJ1teFcEHQwAFXB7fPgOqa6vKpQndzevToKKY_S1mvu-63KWXjX15CgKG712SEXI65_ryo8vKUatywoWTry9e9fX$>
>>
>>
>>
>>
>> 2025-10-15
>>
>>    - 00:14 (e):
>>    https://www.reddit.com/r/webdev/comments/1o6kled/comment/njl0n9t/
>>    <https://urldefense.com/v3/__https:/www.reddit.com/r/webdev/comments/1o6kled/comment/njl0n9t/__;!!O7_YSHcmd9jp3hj_4dEAcyQ!zJ1teFcEHQwAFXB7fPgOqa6vKpQndzevToKKY_S1mvu-63KWXjX15CgKG712SEXI65_ryo8vKUatywoWTu3-pn-g$>
>>
>>
>>
>>
>> 2025-10-16
>>
>>    - 01:07 (b):
>>    https://www.reddit.com/r/webdev/comments/1o6kled/comment/njur9s1/
>>    <https://urldefense.com/v3/__https:/www.reddit.com/r/webdev/comments/1o6kled/comment/njur9s1/__;!!O7_YSHcmd9jp3hj_4dEAcyQ!zJ1teFcEHQwAFXB7fPgOqa6vKpQndzevToKKY_S1mvu-63KWXjX15CgKG712SEXI65_ryo8vKUatywoWTrceLCjV$>
>>
>>
>>
>>
>> 2025-10-17
>>
>>    - (u):
>>    https://www.linkedin.com/feed/update/urn:li:activity:7384866217804873729/?commentUrn=urn%3Ali%3Acomment%3A%28activity%3A7384866217804873729%2C7384901225135390720%29&dashCommentUrn=urn%3Ali%3Afsd_comment%3A%287384901225135390720%2Curn%3Ali%3Aactivity%3A7384866217804873729%29
>>    <https://urldefense.com/v3/__https:/www.linkedin.com/feed/update/urn:li:activity:7384866217804873729/?commentUrn=urn*3Ali*3Acomment*3A*28activity*3A7384866217804873729*2C7384901225135390720*29&amp;dashCommentUrn=urn*3Ali*3Afsd_comment*3A*287384901225135390720*2Curn*3Ali*3Aactivity*3A7384866217804873729*29__;JSUlJSUlJSUlJSUlJSUlJQ!!O7_YSHcmd9jp3hj_4dEAcyQ!zJ1teFcEHQwAFXB7fPgOqa6vKpQndzevToKKY_S1mvu-63KWXjX15CgKG712SEXI65_ryo8vKUatywoWToLicSRB$>
>>
>>
>>
>>
>> 2025-10-20
>>
>>    - 11:18 (g): https://news.ycombinator.com/item?id=45647233
>>    <https://urldefense.com/v3/__https:/news.ycombinator.com/item?id=45647233__;!!O7_YSHcmd9jp3hj_4dEAcyQ!zJ1teFcEHQwAFXB7fPgOqa6vKpQndzevToKKY_S1mvu-63KWXjX15CgKG712SEXI65_ryo8vKUatywoWTgYhZKMX$>
>>
>>    - 13:14 (u): https://indieweb.social/@zerojames/115408325645554816
>>    <https://urldefense.com/v3/__https:/indieweb.social/@zerojames/115408325645554816__;!!O7_YSHcmd9jp3hj_4dEAcyQ!zJ1teFcEHQwAFXB7fPgOqa6vKpQndzevToKKY_S1mvu-63KWXjX15CgKG712SEXI65_ryo8vKUatywoWTtseS8ym$>
>>
>>    - 13:15 (g): https://mastodon.social/@vanderwal/115408326479382068
>>    <https://urldefense.com/v3/__https:/mastodon.social/@vanderwal/115408326479382068__;!!O7_YSHcmd9jp3hj_4dEAcyQ!zJ1teFcEHQwAFXB7fPgOqa6vKpQndzevToKKY_S1mvu-63KWXjX15CgKG712SEXI65_ryo8vKUatywoWTt1CAK7P$>
>>
>>    - 13:18 (g): https://indieweb.social/@johanna/115408340828293280
>>    <https://urldefense.com/v3/__https:/indieweb.social/@johanna/115408340828293280__;!!O7_YSHcmd9jp3hj_4dEAcyQ!zJ1teFcEHQwAFXB7fPgOqa6vKpQndzevToKKY_S1mvu-63KWXjX15CgKG712SEXI65_ryo8vKUatywoWTtLqVnJV$>
>>
>>
>>
>>
>> =====
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *American Express made the following annotations This message and any
>> attachments are solely for the intended recipient and may contain
>> confidential or privileged information. If you are not the intended
>> recipient, any disclosure, copying, use, or distribution of the information
>> included in this message and any attachments is prohibited. If you have
>> received this communication in error, please notify us by reply e-mail and
>> immediately and permanently delete this message and any attachments.
>> American Express Prospective and Existing Customers: For more information
>> about how we protect your privacy, please visit
>> www.americanexpress.com/privacy <http://www.americanexpress.com/privacy>.
>> If you are located outside the U.S., please select your location at
>> www.americanexpress.com/change-country/
>> <http://www.americanexpress.com/change-country/> and access the privacy
>> link at the bottom of the page. American Express a ajouté le commentaire
>> suivant Ce courrier et toute pièce jointe qu'il contient sont réservés au
>> seul destinataire indiqué et peuvent contenir des renseignements
>> confidentiels et protégés par le secret professionnel. Si vous n'êtes pas
>> le destinataire prévu, toute divulgation, duplication, utilisation ou
>> distribution du courrier ou de toute pièce jointe est interdite. Si vous
>> avez reçu cette communication par erreur, veuillez nous en aviser par
>> courrier et détruire immédiatement le courrier et les pièces jointes.
>> Clients et prospects d'American Express: Pour plus d'informations sur la
>> façon dont nous protégeons votre vie privée, veuillez visiter
>> www.americanexpress.com/privacy <http://www.americanexpress.com/privacy>.
>> Si vous êtes situé à l'extérieur des États-Unis, veuillez sélectionner
>> votre emplacement à l'adresse www.americanexpress.com/change-country/
>> <http://www.americanexpress.com/change-country/> et accéder au lien de
>> confidentialité en bas de la page.*
>>
>