[go: up one dir, main page]

Tantek Çelik

inventor, connector, writer, runner, scientist, more.

💬 👏

  1. … speaking of badges (Wikipedia User: 20 year editor badge in my previous post) …

    Pixelated space man on a black background with a lavender decorative border and text at bottom LEVEL 0 Contributor and light green bursts behind itI got the #Hacktoberfest 2025: Level 0 Registered badge from Hacktoberfest @hacktoberfest @digitalocean! https://www.holopin.io/hacktoberfest2025/userbadge/cmhas5f6h003bje041kcld1is via @holopin_

    on

  2. Saturday was my 20th #Wikipedia editing anniversary.

    I have created:
    * over 25 content articles (that have survived), averaging just over 1 per year
    * over 100 redirects to make it easier to find pages, and to find topics which are only documented as sections of existing pages.

    This year I’ve created five content articles (so far). Most recently:
    * https://en.wikipedia.org/wiki/Governors_Public_Health_Alliance
    * https://en.wikipedia.org/wiki/RaptureTok
    * https://en.wikipedia.org/wiki/Northeast_Public_Health_Collaborative
    * https://en.wikipedia.org/wiki/West_Coast_Health_Alliance
    * https://en.wikipedia.org/wiki/Take_California

    I have had quite the range of experiences editing and creating articles.

    Many of my contributions to pages eventually disappeared after iterative edits or outright rewrites. I have seen repetitive wiki edits, repeatedly undoing changes made.

    I have also seen others build on my edits, sometimes taking a correction I made and expanding upon it, with more citations, more details, or both.

    Over time I learned various techniques, or patterns for editing, especially for creating new pages, to increase their chances of survival, while also discouraging vandalism or other attacks. I have found ways of writing that somehow get other editors to show up and help defend articles.

    If I could summarize it in a few words, I'd say aim for short, boring, and factual content (with high-quality citations). New articles work best when they’re similar to and based on existing well-established articles, no matter how small.

    I have learned that it is possible to defend the accuracy of an article even if you are outnumbered, by accurately documenting erroneous additions or changes on the article’s :Talk page, along with calm and thorough refutation of those erroneous additions. Doing so makes it much easier to revert any similar changes, and point to the pre-existing analysis on the :Talk page to discourage repetitive edits.

    Wikipedia has a fascinating set of rules, guidelines, and mechanisms for working in the open, and especially in the context of attacks by all sorts of bad actors, whether griefers, or politicians and businesses scrubbing (or self-promoting) their image.

    I found this article on Wikipedia’s systems and their resilience particularly inspiring:
    * https://www.theverge.com/cs/features/717322/wikipedia-attacks-neutrality-history-jimmy-wales

    I believe every open source project and open standards organization can learn from how Wikipedia works and thrives, especially in the face of antagonists large and small. I certainly have.

    If you do not have a Wikipedia account, I recommend creating one and using it to edit so you too can learn firsthand. Make an account, then browse your areas of interest or expertise to see if you can find pages to improve. Be bold.

    I was proud to add the 20 year editor badge to my User page.

    https://en.wikipedia.org/wiki/Template:User_Twenty_Year_Society

    It’s never too late to start.

    on

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

    on

  4. 👍 to issue 80 of GitHub project “tpac2025-breakouts”

    on

  5. 👍 to issue 75 of GitHub project “tpac2025-breakouts”

    on

  6. 👍 to issue 71 of GitHub project “tpac2025-breakouts”

    on

  7. 👍 to issue 67 of GitHub project “tpac2025-breakouts”

    on

  8. 👍 to issue 63 of GitHub project “tpac2025-breakouts”

    on

  9. 🚀 to issue 57 of GitHub project “tpac2025-breakouts”

    on

  10. 👍 to issue 57 of GitHub project “tpac2025-breakouts”

    on

  11. ❤️ to issue 57 of GitHub project “tpac2025-breakouts”

    on

  12. 👍 to issue 46 of GitHub project “tpac2025-breakouts”

    on

  13. 👍 to issue 41 of GitHub project “tpac2025-breakouts”

    on

  14. 👍 to issue 37 of GitHub project “tpac2025-breakouts”

    on

  15. 👍 to issue 36 of GitHub project “tpac2025-breakouts”

    on

  16. 👍 to issue 35 of GitHub project “tpac2025-breakouts”

    on

  17. 👍 to issue 28 of GitHub project “tpac2025-breakouts”

    on

  18. 👍 to issue 27 of GitHub project “tpac2025-breakouts”

    on

  19. 👍 to issue 17 of GitHub project “tpac2025-breakouts”

    on

  20. 👍 to issue 13 of GitHub project “tpac2025-breakouts”

    on

  21. 👍 to issue 12 of GitHub project “tpac2025-breakouts”

    on

  22. Happy #8bitday yesterday! It was the 256th day of the year.

    See last year’s post for why the 256th day is 8-Bit Day: https://tantek.com/2024/256/t1/happy-8bitday-binary-byte

    Since last year, the related Wikipedia article on “Programmer’s Day” (https://en.wikipedia.org/wiki/Programmer%27s_Day) was updated to finally acknowledge worldwide observation of the day.

    This year, inspired by the old 5k (bytes) competition (https://the5k.org/about.php), I suggested to a few friends that it may be possible to build an entire website where each resource fits into at most 8-bits worth of bytes. 255 bytes maximum size HTML, and maximum size of any linked external stylesheet, image, or even script file.

    Constraints are key to good, creative, and often innovative design.
    https://www.smashingmagazine.com/2023/06/design-constraints-challenges-opportunities-practical-strategies/

    I have some ideas for how to create meaningful HTML documents in ≤ 255 bytes. I also have some experience with creating interesting style sheets under similar constraints with the invention of TSS (Tweet Style Sheets or Text Style Sheets) at the 2010 Twitter Annotations Hackfest (#tanhf). TSS links and details on https://indieweb.org/TSS

    Intuitively I think a home page ≤255 bytes may be the most challenging, like displaying and linking to a stream of posts, in addition to basic about info. Post permalinks could display short notes (like old 140 character posts), requiring pagination to view anything longer. Images would be another interesting challenge, since even a 32x32 black & white (1-bit) icon would already be 128 bytes. What can fit into a 255 byte PNG or JPEG?, nevermind SVG, which will be much harder than HTML due to its much longer tags and attributes.

    The archived FAQ for the5k competition is a good start for answering various questions about how to build an "8-bit" website: https://web.archive.org/web/20050310075803/http://www.the5k.org:80/2001faq.asp
    I would add to that proper use of progressive enhancement (https://en.wikipedia.org/wiki/Progressive_enhancement), that is, all the content on a page is viewable, and all links, buttons, forms etc. work without loading any scripts.

    Besides the5k.org, have there been any similar challenges or competitions for 1k bytes, or 512 bytes? Why did Stewart pick 5k bytes instead of something smaller?

    Update:

    8-bit examples — HTML, CSS, JS files all ≤255 bytes
    * https://tantek.com/8bit.html HTML+CSS
    * https://jamesg.blog/8bit HTML+CSS
    * https://tilde.club/~artlung/miniclock/ HTML+CSS+JS
    * https://villepreux.net/8bits/ HTML+CSS+JS
    * https://pcarrier.com/smol valid HTML!
    * https://pcarrier.com/packed HTML (with inline CSS+JS)
    * https://lab.lunaseeker.com/tests/256bytes.html valid HTML+CSS!
    * https://256-byte-site.netlify.app/ valid & accessible HTML+CSS+SVG+WebP!!!
    * ... who will be next?

    Responses:
    * 2025-258 https://jamesg.blog/2025/09/15/a-255-byte-web-page
    * 2025-259 https://indieweb.social/@villapirorum/115213910454844925 and blog post https://villepreux.net/blog/myweb/8bit-day/
    * 2025-260 https://nothing.pcarrier.com/posts/255/
    * 2025-264 https://front-end.social/@AmeliaBR/115245263894149770

    on

  23. fire, water, wind, steam, electric, solar, nuclear

    on

  24. What are the things on your bucketlist that being a billionaire would make no difference?

    When I was in Berlin at the end of last month, I was chatting with my pal Mo, and noted a sticker I’d seen that said “ELON MUSK DIDN’T GET INTO BERGHAIN” with a QR code that linked to: https://berlinguide.de/money-cant-buy-you-love-the-story-behind-elon-musks-berghain-rejection/

    Mo has been to Berghain, and I shared that especially after hearing that a billionaire was rejected, I put it on my list: go clubbing at Berghain.

    Having completed my responsibilities for July (hosting the W3C Advisory Board at Mozilla Berlin), I started to focus on my next big goal, finishing (or attempting to finish) a 50k that Sunday (3 days from then).

    I realized those two goals had something in common: being a billionaire makes no difference to achieving them. Being a billionaire won’t help you achieve them.

    You can’t buy your way into Berghain, you have to show up with an authentic vibe that feels right to the bouncers.

    You can’t pay someone to do the work of running a 50k, you have to personally train consistently, train hard, show up, and run it yourself. Or any other race distance.

    I told her these two things inspired me to come up with the idea of:

    The anti-billionaire bucketlist (I’d prefer a better, positively framed phrase)

    And filtered my prior goals accordingly.

    She said I should post about it.

    At the time I had only a few things in mind:
    * Run the Skyline 50k (August 3rd)
    * Get into Berghain
    * Finish a 50 mile race
    * Finish a 100km race

    I checked that first one off (https://tantek.com/2025/216/t1/finished-skyline50k-ultra — still writing up my race report) and am reflecting on others.

    What’s on your anti-billionaire bucketlist?

    on
  25. New issue on GitHub project “AB-public”

    Fall virtual-only AC meeting inconsistent with W3C Process

    As requested by an Advisory Board (AB) member, I am filing an issue for consideration by the AB. The upcoming Advisory Committee (AC) meeting, that is normally part of the annual TPAC week, is currently scheduled to be a virtual-only Advisory Committee session before TPAC week. This seems inconsistent with the W3C Process requirement for a face-to-face AC meeting twice a year.

    The face-to-face AC Meeting at TPAC is a key reason for AC Representatives (AC reps) to go to TPAC in-person, both for the AC Meeting itself and the opportunity to meet and interact directly with other AC reps, during the meeting, e.g. to discuss raising issues or asking questions during Q&A, and after the meeting for informal chats about the overall state of W3C, the most pressing issues, what collective actions the AC may wish to pursue or provide feedback or requests to the AB.

    A virtual-only meeting provides no such easy opportunities for direct informal interactions among AC reps or between AC reps and members of the AB, which are usually one of the most valuable aspects of a face-to-face AC meeting.

    By removing the face-to-face AC Meeting from TPAC week, one of the key (for many, the primary) reason(s) for traveling to TPAC is/are removed, and thus makes it hard (or harder) for at least some AC reps to justify the time and travel to TPAC, despite all the secondary and additional benefits of participating in TPAC in-person.

    Thank you for considering this issue, and how to best drive a resolution.

    on

  26. 👍 to issue 1082 of GitHub project “process”

    on

  27. 👍 to a comment on issue 459 of GitHub project “w3c-website”

    on

  28. 👍 to a comment on issue 459 of GitHub project “w3c-website”

    on

  29. 👍 to issue 459 of GitHub project “w3c-website”

    on

  30. Finished the #Skyline50k #trailRace in 9:34:51 yesterday! My 3rd best 50k, and first 50k in over two years since the Marin Ultra Challenge 50k in 2023.

    It was quite the journey to get back here, and a lot went well in this race. From training to preparing and planning, the temperate cool weather for most of the day, and executing perhaps the best I have in a race.

    For now, I am very happy with my performance in this #Skyline race, and want to express my thanks to Scena Performance (@scenaperformance.com @ScenaPerform) for putting on such a welcoming, friendly, and supportive event.

    Lots more thoughts and feelings to share.

    Strava: https://www.strava.com/activities/15336739842/overview

    Previously: https://tantek.com/2022/289/t1/hot-skyline50k-ultra-finish

    #run #trailRun #trailRunning #ultraRunning #trailRunner #ultraRunner #50k #50kTrailRace #50kFinish #50kFinisher #ultraMarathon #2025_215 #20250803

    on

  31. The Vision for W3C has been officially published as a ratified W3C Statement: https://www.w3.org/TR/2025/STMT-w3c-vision-20250729/

    As one of the editors, along with Chris Wilson (@cwilso.com @cdub@mastodon.social), I’m both proud of this multi-year W3C Advisory Board (AB) effort, and grateful to everyone who contributed and gave feedback that helped improve the document.

    Writing down and openly publishing our collective values and principles is an important step forward for W3C. We now have a shared reference to both guide our priorities and cite to help resolve differences in opinion (rather than having to appeal to authority).

    The AB (@w3.org/wiki/AB @ab@w3c.social) has prioritized work on the Vision project for many years (https://www.w3.org/wiki/AB/Vision), and personally, co-leading this project during my time on the AB has been inspiring, challenging, and a source of many lessons learned. Lots more to share on all that. For now, happy to take a moment to celebrate this milestone.

    #w3cVision #VisionForW3C #WorldWideWeb #W3C (@w3.org @w3c@w3c.social) #w3cAB #Vision #VisionTF
    #openWeb #webStandards

    Previously:
    * https://tantek.com/2025/100/t1/vision-for-w3c-please-vote

    More posts:
    * https://www.w3.org/news/2025/vision-for-w3c-is-a-w3c-statement/
    * https://www.w3.org/blog/2025/vision-for-w3c-a-manifesto-for-our-operations-and-decision-making/

    on