Tantek Çelik

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

💬 👏
  1. Great #indieweb sessions at #btconf #Berlin!

    Yesterday, Sacha Judd (@sachajudd.com) reminded us to “teach someone …. something about building for the web”, and to “take back control of your feeds, your attention, and … go exploring again”. She encouraged us to “build healthy online neighborhoods”. That’s a great metaphor and very complementary to rebuilding your own home(page) on the web with perhaps a digital garden as well!

    Today, Ana Rodrigues (@anarodrigu.es @ohhelloana.blog) connected the dots from Sacha’s reminders to encouraging everyone to join burgeoning healthy online neighborhoods like:
    * 32-Bit Cafe (@32bit.cafe and see their Discord & Discourse)
    * IndieWeb Community (@indieweb.org and see @chat.indieweb.org for Discord, IRC, Slack)

    Both are filled with online neighbors helping and teaching each other how to make what people want to express on and for their personal sites!

    Know of other healthy online neighborhoods? Let me know and I’ll add them to the IndieWeb communities page!

    Want to connect your online home with online neighbors?
    * Join the IndieWeb #webring: https://indieweb.org/IndieWeb_Webring

    Prefer events? Join a virtual Frontend Study Hall, Homebrew Website Club meetup, or the next #IndieWebCamp!


    Glossary and links:

    btconf (Beyond Tellerrand conference) Berlin 2025
      https://beyondtellerrand.com/events/berlin-2025
    communities (IndieWeb)
      https://indieweb.org/communities
    digital gardens
        https://indieweb.org/digital_garden
    home (page) on the web
      https://indieweb.org/homepage
    Homebrew Website Club (HWC) online and in-person:
      https://events.indieweb.org/tag/hwc
    Front End Study Hall (FrESH)
      https://indieweb.org/fresh
    IndieWebCamps - in-person and hybrid!
      https://events.indieweb.org/tag/indiewebcamp


    This is post 16 of #100PostsOfIndieWeb. #100Posts

    https://tantek.com/2025/311/t1/indiewebcamp-berlin-sessions-demos
    → 🔮

    on
  2. IndieWebCamp Berlin was great! Participants facilitated inspiring sessions, and everyone made something on or for their personal site on our Create Day #Hackathon.

    Session notes are up from day 1, recordings to follow:
    * https://indieweb.org/2025/Berlin/Schedule

    Demos notes also up, recording to follow:
    * https://indieweb.org/2025/Berlin/Demos

    Want to keep up with #IndieWebCamp #Berlin participants? Volunteer Daniel has updated the IndieWebCamp Berlin feed:
    * https://indieweb.org/2025/Berlin#Feeds_Lists_Starter_Packs_Oh_My

    Questions about sessions or demos? Ask in #IndieWeb chat!
    * https://chat.indieweb.org/


    This is post 15 of #100PostsOfIndieWeb. #100Posts

    https://tantek.com/2025/304/t1/night-before-indiewebcamp-berlin
    https://tantek.com/2025/311/t2/indieweb-sessions-btconf-berlin

    on
  3. 🎃 Night before IndieWebCamp Berlin! Participants are (hopefully, mostly) all tucked into their beds, dreaming of what wonderful things they can brainstorm for their personal sites Saturday, and #HackTheirPlanet on Sunday.

    Want to keep up with #IndieWebCamp #Berlin participants?

    Follow their feeds and a Bluesky starter pack (happy to include more for any other formats, protocols, or platforms)
    * https://indieweb.org/2025/Berlin#Feeds_Lists_Starter_Packs_Oh_My

    We’ll add more as folks sign-in at the camp!

    This is post 14 of #100PostsOfIndieWeb. #100Posts #IndieWeb #Blogtober #IndieWebMovieClub #HackThePlanet 📟

    https://tantek.com/2025/303/t1/october-blogging-challenges
    https://tantek.com/2025/311/t1/indiewebcamp-berlin-sessions-demos

    on
  4. October is almost over! For all us procrastinators, still time to write a post or two to participate in #October blogging challenges like:

    #Blogtober
    #IndieWebMovieClub on #Hackers
    #Inktober
    #Mathober
    #WeirdWebOctober

    + coding challenges:
    #Hacktoberfesthttps://blog.holopin.io/posts/hacktoberfest-2025

    Many more at:
    * https://indieweb.org/October
    * https://indieweb.org/blog_carnival

    🎃 And tomorrow is #Halloween so consider a holiday theme for your site as well! See #IndieWeb examples for inspiration:
    * https://indieweb.org/Halloween

    Last but not least, perhaps we’ll see some of you at #IndieWebCamp Berlin this weekend!
    * https://indieweb.org/2025/Berlin

    This is post 13 of #100PostsOfIndieWeb. #100Posts

    https://tantek.com/2025/182/t1/movie-club-tomorrowland-submissions
    https://tantek.com/2025/304/t1/night-before-indiewebcamp-berlin

    on
  5. … 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
  6. 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
  7. 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
  8. 👍 to issue 80 of GitHub project “tpac2025-breakouts”

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

    on