Tantek Çelik

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

💬 👏
  1. 👍 to a comment on issue 500 of GitHub project “interop”

    on
  2. Implemented liking/favoriting of #Mastodon posts via Bridgy Fed on my site! (Actually of any post on any site that #BridgyFed can discover an #ActivityPub endpoint to send likes to.)

    Tested it by liking @evanp.me (@evan@cosocial.ca @evanpro)’s reply¹ confirming that he received a notification from my prior post². I sent a #Webmention from my like post³ to Bridgy Fed, and it #federated the like to Evan’s server, which subsequently showed up in the "favourites" list of Evan’s post:

    https://cosocial.ca/@evan/111237962392745000/favourites

    Every step that connects heterogenous #socialWeb systems & protocols feels like progress.

    This is day 45 of #100DaysOfIndieWeb. #100Days #IndieWeb #like #likes #fediverse #favorite #favourite #favourites

    ← Day 44: https://tantek.com/2023/234/t1/threads-supports-indieweb-rel-me
    → 🔮

    ¹ https://cosocial.ca/@evan/111237962392745000
    ² https://tantek.com/2023/287/t1/federating-mentions
    ³ https://tantek.com/2023/289/f1

    on
  3. likes evan’s reply

    on
  4. Bridgy Fed (#BridgyFed) recently added support for federating @-@-mentions to #Mastodon: https://fed.brid.gy/docs#mention

    So here’s a test:

    Happy birthday @evanp.me (@evan@cosocial.ca @evanpro)!!!


    Let’s see if Evan receives one or more notifications of these mentions, especially on cosocial, directly from my blog to his Mastodon account.


    Previous related posts on how to @-mention across the #IndieWeb, #fediverse, and silos:
    * https://tantek.com/2023/014/t4/domain-first-federated-atmention
    * https://tantek.com/2023/017/t1/socialweb-blogs-reply-comment-post
    * https://tantek.com/2023/018/t1/elevate-indieweb-above-silo
    * https://tantek.com/2023/019/t5/reply-domain-above-address-and-silo
    which is enough material on the subject to be worth a broader overall blog post on at-mentions, @-mentions, @-@-mentions, how to write them, how to send #Webmentions or #federate them, and perhaps how to recognize & send notifications for them.

    on
  5. 👍 to a comment on issue 435 of GitHub project “strategy”

    on
  6. ❤️ to a comment on issue 435 of GitHub project “strategy”

    on
  7. More Thoughtful Reading & Writing on the Web

    Ben Werdmuller recently published an inspiring and thought-provoking blog post: “Subscribing to the blogs of people I follow on Mastodon”. Beyond the insights and excellent developer how-to in his post, I believe it points to something larger: a fundamental thoughtfulness difference between writing rapid short-form posts (whether tweets or toots) and medium or longer form writing (on blogs or journals), and the impact of that difference on readers: that the act of reading more thoughtful writing nudges & reinforces a reader into a more thoughtful state of mind.

    If you have not read Derek Powazek’s watershed blog post “The Argument Machine”, I highly recommend you do so. In the nearly ten years since his post, Derek’s hypothesis of Twitter’s user interface design being the ultimate machine to create & amplify disputes has been repeatedly demonstrated.

    Derek’s post predated Mastodon’s release by nearly three years. Ironically, by replicating much of Twitter’s user experience, Mastodon has in many ways also replicated its Argument Machine effects, except distributed across more servers.

    I’ve witnessed numerous otherwise rational, well-intentioned individuals write reactive posts on Mastodon, exactly what the Twitter-like interface encourages. Quick emotional responses rather than slower, more thoughtful posts and replies.

    I’ve seen the artificial urgency of tweets & toots bleed over into emotional essays on public mailing lists. New participants join a list and immediately make entitled demands. Fearful bordering on paranoid assumptions are used to state assertions of “facts” without citations. Arguments are made that appeal to emotion (argumentum ad passiones) rather than reasoning from principles and shared values.

    Implicit in Ben’s post, “Subscribing to the blogs of people” (emphasis mine), is a preference for reading longer form writing, published on a site a human owns & identifies with (a la #indieweb), neither silo nor someone else’s garage.

    The combination of taking more time (as longer form writing encourages) and publishing on a domain associated with your name, your identity, enables & incentivizes more thoughtful writing. More thoughtful writing elevates the reader to a more thoughtful state of mind.

    There is also a self-care aspect to this kind of deliberate shift. Ben wrote that he found himself “craving more nuance and depth” among “quick, in-the-now status updates”. I believe this points to a scarcity of thoughtfulness in such short form writings. Spending more time reading thoughtful posts not only alleviates such scarcity, it can also displace the artificial sense of urgency to respond when scrolling through soundbyte status updates.

    When I returned from #W3CTPAC, I made a list of all the thoughts, meetings, sessions that I wanted to write-up and publish as blog posts to capture my experiences, perspectives, and insights beyond any official minutes.

    Yet due to distractions such as catching up on short form posts, it took me over a week to write-up even a summary of my TPAC week, nevermind the queue of per-topic notes I wanted to write-up. To even publish that I had to stop and cut-off reading short form posts, as well as ignoring (mostly postponing) numerous notifications.

    There’s a larger connection here between thoughtful reading, and finding, restoring, and rebuilding the ability to focus, a key to thoughtful writing. It requires not only reducing time spent on short form reading (and writing), but also reducing notifications, especially push notifications. That insight led me to wade into and garden the respective IndieWeb wiki pages for notifications, push notifications, and document a new page for notification fatigue. That broader topic of what do to about notifications is worth its own blog post (or a few), and a good place to end this post.

    Thanks again Ben for your blog post. May we spend more time reading & writing such thoughtful posts.

    on
  8. I recently wrote a high level summary blog post:

    W3C Technical Plenary and Advisory Committee (TPAC) Meetings 2023

    https://tantek.com/2023/262/b1/w3c-technical-plenary-tpac

    of my time at the #W3C (@W3.org, @w3c@w3c.social, @W3C) #TPAC the week before.

    Posting this note to explicitly #hashtag that article with topics mentioned therein:

    #Sevilla #Seville #Spain #WICG #SocialCG #SWICG #Fediverse #SocialWeb #sustainability #IndieWeb #ActivityPub

    because I forgot to put explicit categories (p-category markup) in the article post.

    Adding that markup after publishing, and then sending an ActivityPub update (via #BridgyFed) is apparently not enough for #Mastodon to notice that the Update has new tags to display and aggregate on tag pages. In my next #w3cTPAC article post I’ll be sure to include category markup before publishing and see if that works.

    Post glossary:

    article post
      https://indieweb.org/article
    note post
      https://indieweb.org/note
    p-category
      https://indieweb.org/p-category
    tags
      https://indieweb.org/tags

    on
  9. W3C Technical Plenary and Advisory Committee (TPAC) Meetings 2023

    This year’s W3C TPAC (Technical Plenary and Advisory Committee) meetings felt denser in many ways, packed tighter with more topics, and more active participants. There were so many specific things in specific meetings, new connections, victories, new challenges, that in addition to capturing summary notes, I'm considering writing blog posts about each meeting or session.

    Nearly all of them have public minutes that document both participants, and a good portion of what was discussed. I have my own notes, and combined with recollected details of what was minuted, I have my own observations to share. I encourage everyone who participated at TPAC (whether in-person or remote) to consider either writing a summary blog post about the experience, perhaps highlighting a few things that stood out, or if there were specific technical discussions that advanced something in a positive direction, or challenges blocking progress, those are worth their own blog posts as well.

    TPAC week 2023 took place from Monday through Friday , in Sevilla, Spain.

    Here is a summary outline of meetings, sessions, and discussions I participated in. Not listed: conversations at breakfasts, morning & afternoon breaks, lunches, dinners, and of course hallways. Unlinked for now, each of these has a calendar event with description, minutes, almost all of which are public.

    • Monday
      • WICG (Web Incubator Community Group)
    • Tuesday
      • Social Web Incubator CG (community group), AKA SocialCG or SWICG
      • DID WG rechartering discussion
      • AC meeting
      • Vision TF
      • Fediverse meetup
    • Wednesday — Breakouts day!
      • Chartering at W3C
      • Technical Roadmap at W3C
      • SocialWeb Test Suite Discussion
      • SocialWeb Data Portability Discussion
      • Introducing the Web Sustainability Guidelines (WSGs)
      • Report to Members, Hearing from Members
      • Technical Plenary reception
    • Thursday
      • CSS WG, briefly
      • Afternoon break: Solid charter discussions, use-cases, IndieWeb Micropub, ActivityPub
    • Friday
      • Social CG planning
      • Departing conversations & reflections

    Those are the sessions & discussions that I found in my notes. I also met a lot of new people during meetings, meals, and discussions at breaks. As I write up my notes on specific sessions and their minutes (and hyperlink the above list items), I expect to recall more context and details. If you were at TPAC in Seville, I encourage you to write-up your experiences as well, while the thoughts, feelings, and insights are fresh in your mind. By documenting & publishing our collective experiences (using the #w3cTPAC hashtag) we can build upon them together.

    on
  10. 👍 to a comment on issue 113 of GitHub project “AB-public”

    on
  11. 👍 to a comment on issue 8693 of GitHub project “html”

    on
  12. 👍 to issue 387 of GitHub project “activitypub”

    on
  13. 👍 to a comment on issue 96 of GitHub project “AB-public”

    on
  14. 👍 to issue 112 of GitHub project “AB-public”

    on
  15. RSVP yes to: www.w3.org’s post going to the #SocialWeb CG meeting @W3C #w3cTPAC tomorrow (2023-09-12) at 09:30 CEST.

    Looking forward to seeing @evanp.me (@evan@cosocial.ca @evanpro) and many others!

    So many advances in #ActivityPub, #Webmention, Micropub, #IndieAuth etc. that it may be time to restart the #SocialWebWG to officially update all our active specifications.

    We can & should also reach out to #Bluesky & #Nostr communities to work together on shared semantics and bridging protocols to continue growing a heterogenous #fediverse built on the #OpenWeb.

    We know it is possible. We worked hard in the Social Web working group to align a lot of semantics across #ActivityStreams and #microformats2. The fruitful results of that are services like http://fed.brid.gy/ which I myself use to send a Webmention when I make a new post (like this one) and have #BridgyFed automatically federate it via ActivityPub using my personal site identity to #Mastodon followers and others.

    @snarfed.org wrote up a recent comparison of top #decentralized #socialProtocols that can help inform a lot of this discussion: https://snarfed.org/2023-09-04_50856

    on
  16. 👍 to a comment on issue 43 of GitHub project “tpac2023-breakouts”

    on
  17. ↳ In reply to Tantek’s note Shared times with Molly mostly captured on Flickr, our community sharing site of that era.

    https://flickr.com/photos/tantek/tags/mollyholzschlag

    Conferences like #SXSW #WWW2005 #OpenWebCamp and a @CSSWG meeting @W3C #w3cTPAC 2006.

    But this one hurts the most:
    Molly Holzschlag and Cindy Li at Web Directions North 2007.

    on
  18. ↳ In reply to @zeldman’s tweet @Zeldman day by day my friend. If you would have asked a month ago I would have said no, for unrelated reasons which are thankfully mostly resolved.

    At #w3cTPAC this week, with many who also knew Molly. I expect there’ll be a lot of sharing.

    Day by day.

    on
  19. I was traveling when I heard the news about Molly Holzschlag (@mholzschlag).

    https://www.tucsonsentinel.com/local/report/090523_molly_holzschlag/tucsons-molly-holzschlag-known-as-the-fairy-godmother-web-dead-60/

    Her #CSS #accessibility #OpenWeb contributions are well documented. May she be at peace. Appreciated @Zeldman.com’s (@Zeldman) note: https://twitter.com/zeldman/status/1699395939792822335

    on
  20. Threads.net now supports the #indieWeb #microformats #openStandard rel-me for distributed ✅ verification!¹ (supported since 2023-08-09)

    My Threads profile already had my domain since it was created from my Instagram profile.

    View source on https://www.threads.net/@tantek and you can see the #relMe on a link tag:
     <link rel="me" href="https://tantek.com/" />

    Instructions to add yours:
    * Add your domain to your Threads profile "Link" field. That’s it.
    Longer explicit steps: https://indieweb.org/rel-me#Threads

    Thanks especially to @timothychambers.net (@tchambers@indieweb.social,  @timothyjchambers@threads.net) for requesting rel-me support² which one Threads engineer “decided to hack it together” one night!³

    You can view Tim’s profile @tchambers@indieweb.social for a real world example of a Mastodon profile showing a green text ✅ verified link to a Threads profile.

    Tim made several good points in his request:

    “… a small, but disproportionately helpful addition would be to support this "rel=me" feature in your profiles. That could launch well before full ActivityPub, & show the first real integration to open social web standards”

    Microformats (and IndieWeb) standards in general are deliberately designed as small, incremental building blocks which are disproportionately helpful as Tim says.

    These small building blocks which directly enable user features are usually something a web developer can code at least some (often complete!) support for in one day/night which makes them particularly appealing as a way to rapidly support open #socialWeb standards used by the #fediverse and beyond.

    Incrementally implementing microformats & IndieWeb standards also demonstrates good will and good intentions for supporting the #openWeb.


    This is day 44 of #100DaysOfIndieWeb. #100Days

    ← Day 43: https://tantek.com/2023/171/t1/anniversaries-microformats-posse
    → Day 45: https://tantek.com/2023/289/t1/bridgyfed-webmention-like-fediverse


    Previously:
    * 2023-02-01 Wikipedia.org supports multiple rel=me links: https://tantek.com/2023/139/t1/wikipedia-supports-indieweb-rel-me


    ¹ https://www.threads.net/@mosseri/post/Cvu2eXurRbB
    ² https://www.threads.net/@timothyjchambers/post/CupCvChAxI8
    ³ https://www.threads.net/@0xjessel/post/Cvu7-A4viZu
    https://spec.indieweb.org/

    on
  21. ↳ In reply to a comment on issue 852 of GitHub project “standards-positions” Thanks https://github.com/bgrins for this summary write-up. Per this analysis I’m going to label our position on this proposal as negative.

    Since this is a proposal in a personal GitHub repo, and not standards track work nor in any open incubation group, there is no need for a dashboard entry. Closing accordingly.

    on
  22. ↳ In reply to issue 8930 of GitHub project “csswg-drafts” Regarding History:
    > The earliest such proposal I could find was this one from 2009. (https://lists.w3.org/Archives/Public/www-style/2009Apr/0225.html)

    This sounded familiar (as in I thought I had proposed something similar a while ago), and it turns out I had proposed exactly a "tooltip pseudo-element" nine years earlier 🙈😭

    https://lists.w3.org/Archives/Public/www-style/2000Apr/0014.html

    Note that the year 2000 was before the WG switched to the "::" prefix for pseudo-element selectors, so all pseudo-elements and pseudo-classes used the single ":" prefix.

    on
  23. June #trailRunner #ultraRunner weekends
    3 finished #MUC50k @InsideTrail #RodeoBeach 9:38:28, my 3rd #50k #ultraMarathon #trailRace
    11 volunteered @TheDipsea #DipseaRace at #MuirWoods
    18 finished @BrokenArrowCA #BA23k 5:22:54 #RingDasBell, my 1st #skyRace
    24-25 crewed pal @davidtlam @wser.org 100mi to a successful #WS100 finish!

    #runner #running #trailRunning

    Heart & mind full, body pushed to its limits, capturing my experiences in a few write-ups.

    on
  24. Two anniversaries today: microformats (18y) and POSSE (11y).

    Happy 18 years of https://microformats.org/ #microformats!

    Most prominent this past year (again) has been the littlest #microformat that could:

    rel=me — AKA #relMe, now effectively the standard for #distributed #verification on the web:
    * https://microformats.org/wiki/rel-me (originally introduced in 2004¹)

    with support added in the past year for:
    * #GitHub multiple rel-me links²
    * #Wikipedia User page rel-me link³

    Figure out how you want to fit into the network.
    #POSSE, short for “Publish (on your) Own Site, Syndicate Elsewhere”, as a term of use is now 11 years old, which is surprising since when it was conceived, the #IndieWeb community was in a period of very rapid innovation & iteration.

    POSSE itself replaced a previous term, "POSE", short for “Publish Once Syndicate Everywhere”, which had only been around a year or two at most (I’m still looking for the first use of the "POSE" abbreviation for that meaning).

    Since “publish once” was vague enough to include practices of publishing once on a social media silo, or in someone else’s garage, we needed to clearly express the requirement to use your own site instead, first, as the source of your truth. Cross-posting to other sites & channels, is a second, optional step, ideally with a permalink linking back to your original post so viewers can easily discover and use your site.

    That distinction was enough for POSSE to express a strong creator-owned-first publishing model that resonated and grew. Every time a silo shutdown at the end of its incredible journey, removing posts & permalinks from the web, POSSE was there for people who were tired of losing their data, permalinks, & profiles, and wanted an alternative.


    This is day 43 of #100DaysOfIndieWeb. #100Days

    ← Day 42: https://tantek.com/2023/160/t1/mastodon-activitypub-follow-form-bridgy-fed
    → Day 44: https://tantek.com/2023/234/t1/threads-supports-indieweb-rel-me


    Glossary

    permalink
      https://indieweb.org/permalink
    POSE
      https://indieweb.org/POSE
    POSSE
      https://indieweb.org/POSSE
    silo
      https://indieweb.org/silo

    References

    ¹ https://gmpg.org/xfn/11#me
    ² https://tantek.com/2023/032/t1/years-relmeauth-replace-openid
    ³ https://tantek.com/2023/139/t1/wikipedia-supports-indieweb-rel-me
    https://tantek.com/2012/173/t1/posse-core-indieweb-approach
    https://tantek.com/2023/001/t1/own-your-notes
    https://indieweb.org/site-deaths
    https://ourincrediblejourney.tumblr.com/

    on
  25. ↳ In reply to hachyderm.io user renegadejade’s post @renegadejade@hachyderm.io in short, yes, it is a thing!

    Lots of great replies to your post already about directly using #WithKnown or #WordPress with the #ActivityPub plugin, or cross-posting from/via GitHub.

    Another #IndieWeb compatible option is Bridgy Fed (https://fed.brid.gy/) which can proxy posts, replies, likes etc. directly from a blog to #fediverse / ActivityPub (no #Mastodon account needed). Details: https://fed.brid.gy/docs

    This very reply to your toot is from my own domain, and its #hashtags are also discoverable via fediverse hashtags.

    I set up #BridgyFed last October¹ along with the broader #TwitterMigration I saw happening in my circles, and am quite happy with it. Posted more about my experience after a few months², and using BridgyFed to add a fediverse follow form to my homepage³.

    Whether WordPress, Known, or with another blog setup & Bridgy Fed, pick what works best for you and your setup. There’s #IndieWeb folks using each, feel free to drop by https://chat.indieweb.org/dev to chat more about any IndieWeb/fediverse option!

    ¹ https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indieweb
    ² https://tantek.com/2023/008/t7/bridgy-indieweb-posse-backfeed
    ³ https://tantek.com/2023/020/t2/bridgy-fed-follow-form

    on
  26. If you added a #Mastodon / #ActivityPub follow form to your #IndieWeb site based on Bridgy Fed (e.g. using code/instructions I previously posted¹), you need to update it to add another invisible input element for the "protocol", e.g.:

    <input name="protocol" type="hidden" value="web" />

    Otherwise people trying to use your form to follow you may see an error from #BridgyFed like:
    > Bad Request
    > Missing required parameter protocol

    Here is the complete example that I posted previously with the new invisible input:

    <form method="post" action="https://fed.brid.gy/remote-follow">
     <label for="follow-address">🐘 Follow
      <kbd>@tantek.com@tantek.com</kbd>:<br />
      enter your @-@ fediverse address:</label>
     <input id="follow-address" name="address" type="text" required="required"
            placeholder="@you@instance.social" title="Type your @-@ address" value="" />
     <input name="domain" type="hidden" value="tantek.com" />
     <input name="protocol" type="hidden" value="web" />
     <button type="submit">Follow</button>
    </form>

    I also updated that previous post with the new input in case people find that instead.


    This is day 42 of #100DaysOfIndieWeb. #100Days

    ← Day 41: https://tantek.com/2023/139/t1/wikipedia-supports-indieweb-rel-me
    → Day 43: https://tantek.com/2023/171/t1/anniversaries-microformats-posse


    ¹ https://tantek.com/2023/020/t2/bridgy-fed-follow-form

    on
  27. ↳ In reply to an IndieWeb page @tchambers@indieweb.social thanks Tim! And now two more years of work on AB Priority projects¹ (and whatever else we come up with @AB@W3C.social).

    ¹ https://www.w3.org/wiki/AB/Priorities

    on
  28. Congrats to fellow re-elected W3C Advisory Board (@AB@W3C.social @W3CAB) members:
    * @cwilso.com (@cdub@mastodon.social @cwilso)
    * @fantasai.inkedblade.net (@fantasai@w3c.social @fantasai)
    * Avneesh Singh
    and newcomers:
    * @reidmore@mastodon.social (@wendy_a_reid)
    * Song XU

    Thanks to Heejin Chung and Charles Nevile for your service on the #W3CAB.

    https://www.w3.org/blog/news/archives/9933
    via #W3C (@w3.org @w3c@w3c.social @w3c): https://w3c.social/@w3c/110491804762139049

    Previously: https://tantek.com/2023/128/t1/w3c-advisory-board-election-support

    on
  29. Ran my 11th #BayToBreakers in 1:47:11 on Sunday 2023-05-21, again the day after an @sfrunco.com (@SFRunCo) Saturday trail #run, but this time in the middle of a very long training run, my last before the rescheduled #MUC50k trail race. Ran over 4 miles to the start, hopped in the next race corral, ran Bay to Breakers with the colorfully costumed crowd, picked up my medal, ate a banana, ran back through Golden Gate Park, and then a bit more up city hills to round out 18 miles and 1000'.

    #2023_141 #SanFrancisco #runner

    2022: https://tantek.com/2022/138/t1/ran-baytobreakers

    on
  30. 👍 to issue 493 of GitHub project “bridgy-fed”

    on
  31. ↳ In reply to alpaca.gold user Jeremiah’s post @jeremiahlee.com (@Jeremiah@alpaca.gold) you’re right that the #IndieWeb is more of a movement. It’s a community based on shared values & principles¹, one of which is plurality², explicitly prioritizing interoperability over any “particular piece of technology”.

    As to “subdomains as usernames using #ActivityPub?”, myself and others are using our (sub)domains as usernames, e.g. via the #BridgyFed service³. Mine should be self-evident in the header of this post wherever you’re reading #fediverse posts.

    Completely agree that “a link that also works as a mention name is obvious / intuitable”, have been practicing that for a while, and wrote up some notes about how & why:

    * https://tantek.com/2023/011/t1/indieweb-evolving-at-mention
    * https://tantek.com/2023/014/t4/domain-first-federated-atmention
    * https://tantek.com/2023/018/t1/elevate-indieweb-above-silo
    * https://tantek.com/2023/019/t5/reply-domain-above-address-and-silo

    which I should organize into a longer blog post at some point.


    ¹ https://indieweb.org/principles
    ² https://indieweb.org/plurality
    ³ https://indieweb.org/Bridgy_Fed#IndieWeb_Examples

    on