stadeus
  • Login
Show Navigation
  • Public

    • Groups
    • Recent tags

Notices tagged with indieweb, page 4

  1. Tantek ()'s status on Monday, 01-Jan-2024 22:30:00 EST Tantek Tantek
    Time to begin again: restarting my #100Days of #IndieWeb project for 2024, as a #100Posts of IndieWeb project, and congrats to the IndieWeb community on a fully completed 2023 IndieWeb Gift Calendar!

    Last year I completed 48 out of a planned 100 posts in my #100DaysOfIndieWeb project, for nearly 48 days (some days had multiple posts). Instead of resetting my goals accordingly, say down to 50, I’m going for 100 again, however, this time for 100 posts rather than 100 days, having learned that some days I find the time for multiple posts, and other days none at all.

    Looking back to the start of last year’s 100 Days project, it’s been one year since I encouraged everyone to own their own notes¹. Since then many have started, restarted, or expanded their personal sites to do so. Some have switched from a #Twitter account to a #Mastodon (or other #fediverse) account as a stopgap for short-form status posts. A step in the right direction, yet also an opportunity to take the leap this year to fully own their identity and posts on the web.

    In 2023 Twitter also broke all existing API clients (including my website). I did not feel it was worth my time to re-apply for an API key and rebuild/retest any necessary code for my semi-automatic #POSSE publishing, not knowing when they might break things again (since there was no rational reason for them to have broken things in the first place).

    I manually POSSEd a few posts after that, yet from the lack of interactions, either Twitter’s feed algorithm² isn’t showing my posts, or people have largely left or stopped using Twitter.

    Either way, when your friends stop seeing your posts on a silo, there’s no need to spend any time POSSEing to it.

    On the positive side, the IndieWeb community really came together in 2023, shining brightly even through the darker days of December.

    We, the IndieWeb community (and some beyond!) provided a gift (or often multiple) to the rest of community for every single day of December 2023³, the first time we successfully filled out the whole month since the 2018 IndieWeb Challenge⁴, and only the second time ever in the seven years of the IndieWeb Challenge-turned-Gift-Calendar.

    By going through the various gifts (more than 2 per day on average!), there are many interesting numbers and patterns we could surface. That deserves its own post however, as does a summary of the 48 posts⁵ of my 2023 100 Days of IndieWeb attempt, so I’ll end this post here.

    Happy New Year to all, with an especially well deserved congratulations to the IndieWeb community and everyone who contributed to the 2023 Gift Calendar. Well done!

    Let’s see what else we can create & share on our personal sites in 2024 and continue setting a higher bar for the independent web by showing instead of telling. #ShowDontTell

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

    ← ✨
    → 🔮


    Post glossary:

    API
      https://indieweb.org/API
    POSSE
      https://indieweb.org/POSSE
    silo
      https://indieweb.org/silo


    ¹ https://tantek.com/2023/001/t1/own-your-notes
    ² https://indieweb.org/algorithmic_feed
    ³ https://indieweb.org/2023-12-indieweb-gift-calendar
    ⁴ https://indieweb.org/2018-12-indieweb-challenge
    ⁵ https://tantek.com/2023/365/t2/no-large-language-model-llm-used
    Monday, 01-Jan-2024 22:30:00 EST from tantek.com permalink
  2. Tantek ()'s status on Sunday, 31-Dec-2023 17:56:00 EST Tantek Tantek
    No large language models (LLM) were used in the production of this post.

    Inspired by a subtle but clear sign-of-the-times one-line disclaimer at the end of RFC9518’s Acknowledgments (https://www.rfc-editor.org/rfc/rfc9518.html#appendix-A-4)

      “No large language models were used in the production of this document.”
     
    I have added a similar disclaimer to the footer of my homepage:

      “No large language models were used in the production of this site.”
     
    2023 was certainly a year that LLMs took off and stole the hypecycle from #metaverse and #blockchain before that.

    Yet unlike those previous two, #LLMs are already having real impacts on the way people create (from emails to art), communicate (LLM chat apps), and work (2023 Writer’s Strike), fueling growing concerns about the authenticity of content, especially content from human authors.

    I expect we will see more such disclaimers in the future.

    For now, if you blog on your own site with words written by you not #ChatGPT or a similar tool, I encourage you to add a similar disclaimer, and then add your site as an example to the #IndieWeb wiki:
    * https://indieweb.org/LLM#IndieWeb_Examples

    #largeLanguageModel #LLM #generativeAI #AI

    There is the related problem of, when you discover what seems to be an independent site written by a human, how do you know that human actually exists?

    For now I’ll mention that XFN rel=met links, published (e.g. metrolls / met-rolls), aggregated, indexed, and queried, can solve that problem. This will be similar to how XFN rel=me links solved #distributed verification on the web (see https://tantek.com/2023/234/t1/threads-supports-indieweb-rel-me and posts it links to).


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

    ← Day 47: https://tantek.com/2023/365/t1/capture-first-edit-publish-later
    → 🔮


    Post glossary:

    blockchain
      https://indieweb.org/blockchain
    large language model / LLM
      https://indieweb.org/large_language_model
    metaverse
      https://indieweb.org/metaverse
    rel=me
      https://indieweb.org/rel-me
    rel=met
      http://gmpg.org/xfn/11#met
    XFN
      https://gmpg.org/xfn/
    Sunday, 31-Dec-2023 17:56:00 EST from tantek.com permalink
  3. Tantek ()'s status on Sunday, 31-Dec-2023 17:04:00 EST Tantek Tantek
    Writing about writing: capture first, edit & publish later.

    Braindump timely thoughts & experiences into as many draft notes as it takes, while ideas & memories are fresh.

    Collecting higher fidelity memories seems more important than editing past writings or finishing/polishing a post for publishing, which can be done at a later time.

    Sometimes the passage of time helps provide insights and broader understandings that can help with writing more effective posts, from better summaries to narratives that help sense-making.

    Bits of even this minor post sat for weeks, and only today did I add a summary and related thoughts.

    Similarly, it makes sense to edit and publish small notes on a subject, without feeling compelled to turn them into a larger blog post, or a longer list of points.

    This is a key advantage to publishing on your own #indieweb site, you decide on the granularity of your posts, small, medium or large, instead of being constrained, burdened, or pressured by any particular #socialMedia user interface, character count limitation, or audience expectation.

    Like Twitter before it, even the default #Mastodon user interface has limitations, and the #fediverse itself as a whole has audience/cultural expectations (certainly quite a few articles have been written about that).

    On your own site you decide if you want to publish a post to make one point, or mention a related point or two, or collect things into a list or longer article, or eventually all of the above.

    On your own site you feel more free to prioritize and share what is on your mind, instead of feeling compelled to first respond to whatever topics are trending, or to whatever you happen to read in your algorithmic feed.

    #writingAboutWriting

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

    ← Day 46: https://tantek.com/2023/289/t1/bridgyfed-webmention-like-fediverse
    → Day 48: https://tantek.com/2023/365/t2/no-large-language-model-llm-used


    Related:
    * “More Thoughtful Reading & Writing on the Web” (https://tantek.com/2023/277/b1/thoughtful-reading-writing-web)


    Post glossary:

    algorithmic feed
      https://indieweb.org/algorithmic_feed
    article
      https://indieweb.org/article
    note
      https://indieweb.org/note
    post
      https://indieweb.org/post
    sense-making
      https://en.wikipedia.org/wiki/Sensemaking_(information_science)
    social media
      https://indieweb.org/social_media
    Sunday, 31-Dec-2023 17:04:00 EST from tantek.com permalink
  4. Tantek ()'s status on Thursday, 07-Dec-2023 20:09:00 EST Tantek Tantek
    at a fascinating #Threads meetup hosted by Meta in San Francisco, with a handful of great #dataportability #fediverse #indieweb #openweb folks, learning about and providing feedback to Threads folks about their #federation #ActivityPub and other #openStandards support plans.

    Chatham House rule¹ means we can quote and talk about what’s being discussed (I’m taking notes), however no attribution, which I’m extending to not saying (or @-@-mentioning) who else is here.

    If you’re also here, feel free to reply to this post or use one of the below hashtags. And since I’m publishing this, feel free to @-me as well.

    #DataDialogue #Threadiverse (unofficial hashtag suggestion from a participant)

    ¹ https://en.wikipedia.org/wiki/Chatham_House_rule
    Thursday, 07-Dec-2023 20:09:00 EST from tantek.com permalink

    Attachments

  5. Tantek ()'s status on Friday, 27-Oct-2023 19:23:00 EDT Tantek Tantek
    Inspiring mix of perspective expanding and personal talks at border:none (https://border-none.net/ @border_none) the past two days. Thanks speakers, volunteers, and especially organizers @marcthiele.com (@marcthiele@mastodon.social @marcthiele) and @jkphl.is (@jkphl@mastodon.social @jkphl).

    Looking forward to the next two days at #IndieWebCamp Nürnberg @tollwerk.de (@tollwerk@mastodon.social @tollwerk) of personal site demos, brainstorming sessions, and making, creating, & hacking things from UX to protocols to improve & interconnect our websites, with each other ( #Webmention ), #fediverse ( #BridgyFed & #ActivityPub ), and others ( #POSSE #backfeed ).

    Still a few spots if you’re in town or can hop on a train and join us Saturday & Sunday!

    🎟 Tickets: https://ti.to/beyondtellerrand/bordernone-2023/with/kqyaidtq92k
    🗓 Event: https://events.indieweb.org/2023/10/indiewebcamp-nuremberg-2023-DmXe4dYdfagc
    ℹ️ More info: https://indieweb.org/2023/Nuremberg

    #bordernone #bono23 #IndieWeb
    Friday, 27-Oct-2023 19:23:00 EDT from tantek.com permalink
  6. Tantek ()'s status on Monday, 23-Oct-2023 20:30:00 EDT Tantek Tantek
    Great article on #POSSE by David Pierce (@davidpierce@mastodon.social @pierce) @Verge:

    https://www.theverge.com/2023/10/23/23928550/posse-posting-activitypub-standard-twitter-tumblr-mastodon

    Several key points of POSSE explained in the article:


    First, post on your own site:

     “In a POSSE world, everybody owns a domain name, and everybody has a blog. (… a place on the internet where you post your stuff and others consume it.)”
     

    Second, syndicate elsewhere, appropriately for each destination:

     “Then, your long blog post might be broken into chunks and posted as a thread on X and Mastodon and Threads. The whole thing might go to your Medium page and your Tumblr and your LinkedIn profile, too. If you post a photo, it might go straight to Instagram, and a vertical video would whoosh straight to TikTok, Reels, and Shorts. Your post appears natively on all of those platforms,”

    You can use Bridgy Publish (https://brid.gy/) to POSSE to many destinations, and Bridgy Fed (https://fed.brid.gy/) to #federate to #Mastodon and other #fediverse destinations, directly from your site instead of posting a copy on yet another account on yet another server.


    Third, and this is a key piece that distinguishes proper POSSE setups, with original post perma(short)links back to your posts on your domain:

     “typically with some kind of link back to your blog.”
     

    All copies link to (your) home.

     "And your blog becomes the hub for everything, your main home on the internet."
     

    You have power over your domain (name), not outside silos.


    David embedded a screenshot of one of my posts, a reply post:


    in which I posted a reply *on my own site*¹ to @Zeldman.com’s tweet (itself a reply to a POSSE copy of one of my posts), and POSSEd my reply to Twitter so it would thread with his reply.

    This illustrates another important detail of a proper POSSE setup:

    Fourth, post *replies* and other responses from your own site, whether to other #IndieWeb sites, or to others’s silo posts (tweets etc.).

    Own your data means owning your replies as well.


    David also noted several challenges and good questions about POSSE. Some of these have answers & established practices, others are areas of exploration. E.g.

     "The first is the social side of social media: what do you do with all the likes, replies, comments, and everything else that comes with your posts?"
     
    The short answer is #backfeed: https://indieweb.org/backfeed

    Backfeed is a concept I first wrote about as “reverse syndication”².

    As you syndicate your posts out to #socialMedia silos, you reverse syndicate any responses there back to your original post.

    Your site can do this with a service like #Bridgy, which uses the #Webmention standard to forward such silo responses back to your site, and #BridgyFed which does same for responses from Mastodon to your #federated posts.


    David asked many other questions, which are deserving of their own posts to help answer, so I’ll leave you with just one more:

     "The most immediate question, though, is simply how to build a POSSE system that works."

    The short answer is: just start³.

    Even if you have to do it manually (until it hurts), even if you have to edit your posts on a static GitHub site (behind your domain name of course), and then copy & paste to your silo(s) of choice, just start.

    By practicing POSSE, even manually, you will learn what aspects of POSSE & backfeed matter the most to you, what aspects actually involve reaching & responding to friends and others you care about.

    By doing so you will naturally focus on setting up & making what you need, and you too can join the future of web publishing, today.

    Questions? Join us in the chat: https://chat.indieweb.org/ (also on Discord, IRC, and Slack⁴)


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

    ← Day 45: https://tantek.com/2023/289/t1/bridgyfed-webmention-like-fediverse
    → 🔮


    Post glossary:

    backfeed / reverse syndication
      https://indieweb.org/backfeed
    Bridgy
      https://brid.gy/
    make what you need
      https://indieweb.org/make_what_you_need
    manual (until it hurts)
      https://indieweb.org/manual_until_it_hurts
    original post link
      https://indieweb.org/original_post_link
    own your data
      https://indieweb.org/own_your_data
    own your replies
      https://indieweb.org/own_your_replies
    permalink
      https://indieweb.org/permalink
    permashortlink
      https://indieweb.org/permashortlink
    POSSE
      https://indieweb.org/POSSE
    silo
      https://indieweb.org/silo
    social media
      https://indieweb.org/social_media
    static site
      https://indieweb.org/static_site
    start
      https://indieweb.org/start
    Webmention
      https://indieweb.org/Webmention


    ¹ https://tantek.com/2023/253/t2/
    ² https://tantek.com/2010/034/t2/diso-2-personal-domains-shortener-hatom-push-relmeauth
    ³ https://tantek.com/2023/001/t1/own-your-notes
    ⁴ https://indieweb.org/discuss
    Monday, 23-Oct-2023 20:30:00 EDT from tantek.com permalink
  7. Tantek ()'s status on Monday, 16-Oct-2023 21:16:00 EDT Tantek Tantek
    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
    Monday, 16-Oct-2023 21:16:00 EDT from tantek.com permalink
  8. Tantek ()'s status on Saturday, 14-Oct-2023 22:37:00 EDT Tantek Tantek
    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.
    Saturday, 14-Oct-2023 22:37:00 EDT from tantek.com permalink
  9. Tantek ()'s status on Thursday, 05-Oct-2023 02:55:00 EDT Tantek Tantek

    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.

    Thursday, 05-Oct-2023 02:55:00 EDT from tantek.com permalink
  10. Tantek ()'s status on Sunday, 24-Sep-2023 21:33:00 EDT Tantek Tantek
    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
    Sunday, 24-Sep-2023 21:33:00 EDT from tantek.com permalink
  11. Tantek ()'s status on Tuesday, 22-Aug-2023 15:43:00 EDT Tantek Tantek
    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
    → 🔮


    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/
    Tuesday, 22-Aug-2023 15:43:00 EDT from tantek.com permalink

    Attachments

  12. Tantek ()'s status on Tuesday, 20-Jun-2023 19:52:00 EDT Tantek Tantek
    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³

    , 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
    → 🔮


    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/
    Tuesday, 20-Jun-2023 19:52:00 EDT from tantek.com permalink
  13. Tantek ()'s status on Friday, 09-Jun-2023 22:14:00 EDT Tantek Tantek
    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" alt="fediverse 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
    → 🔮


    ¹ https://tantek.com/2023/020/t2/bridgy-fed-follow-form
    Friday, 09-Jun-2023 22:14:00 EDT from tantek.com permalink
  14. Tantek ()'s status on Friday, 19-May-2023 16:19:00 EDT Tantek Tantek
    Wikipedia.org (@wikipedia@wikis.world @wikipedia) now supports #IndieWeb rel-me!¹
    Thanks to @taavi.wtf (@taavi@wikis.world) for the #MediaWiki RealMe extension²

    Added it to my #Wikipedia User: page https://en.wikipedia.org/wiki/User:Tantek

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

    Instructions to add yours here:
    * https://indieweb.org/rel-me#Wikipedia


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

    ← Day 40: https://tantek.com/2023/114/t1/venues-reviews-personal-pages
    → 🔮


    Previously:
    * 2023-02-01 GitHub supports multiple rel=me links: https://tantek.com/2023/032/t1/years-relmeauth-replace-openid


    ¹ https://wikis.world/@wikipedia/110396865170645710
    ² https://www.mediawiki.org/wiki/Extension:RealMe
    Friday, 19-May-2023 16:19:00 EDT from tantek.com permalink

    Attachments

  15. Tantek ()'s status on Monday, 08-May-2023 19:46:00 EDT Tantek Tantek
    I am running for election in this month’s #W3C (@w3.org @w3c@w3c.social @w3c) Advisory Board (AB) election¹ and blogged my personal statement: https://tantek.com/2023/128/b1/running-for-w3c-advisory-board-ab-election

    @fantasai.inkedblade.net (@fantasai@w3c.social @fantasai) is also running for the #W3CAB, and admirably blogged her imminent affiliation change *before* the election started: https://fantasai.inkedblade.net/weblog/2023/affiliation-change/ — Congrats Elika! Your new affiliation is lucky to have you.

    In addition to the two of us, @cwilso.com (@cdub@mastodon.social @cwilso) also posts on his own blog and is running for the AB.

    Those are the three candidates I know have their own personal #website, and was able to verify by searching for candidates on the web, #socialMedia, etc.

    Three out of the nine candidates² running for election to the World Wide Web Consortium’s Advisory Board.

    As I wrote in my statement:

    > “I believe governance of W3C, and advising thereof, is most effectively done by those … who directly use & create on the web using W3C standards. This direct connection to the actual work of the web and W3C is essential to prioritizing the purpose & scope of governance thereof.”

    I firmly believe that direct hands-on experience with using the web, beyond reading the web or using someone else’s apps, actually writing to the web, posting on the web, creating for the web, provides better insight into the technologies & standards necessary to evolve the web, how to improve them and represent the communities working on them.

    I ask for your support for the Advisory Board, and support for those who create on the web.

    If any other candidates have their own #IndieWeb site (or set one up!), and especially if they blog their personal statements, I will gladly link to them as well.

    Thanks for your consideration.

    ¹ https://www.w3.org/blog/news/archives/9903
    ² https://www.w3.org/2023/04/ab-nominations.html
    Monday, 08-May-2023 19:46:00 EDT from tantek.com permalink
  16. Tantek ()'s status on Monday, 24-Apr-2023 16:34:00 EDT Tantek Tantek
    🌱 I have long been a fan of @Foursquare.com and @Swarmapp.com, having created many venues, posted many tips, and (checks profile) over 45,000 checkins. I recently joined @happycow.net and before I start posting new vegan (friendly) venues or reviews there, I really need to figure out my own personal site venue pages (including URL design) and review posts design and authoring workflow.

    I’m pretty sure I can and should post h-review posts as a variant of articles (with usual h-entry markup) with an explicit article name, since most review destinations request a title (name) for the review (e.g. HappyCow, TripAdvisor), and for others with only review text (e.g. Google Maps), I can include the name at the start.

    Different review destinations have different text requirements (minimum and/or maximum lengths), and I’ll take time to document those first.

    The first destination I’ll likely try automatically syndicating to is a site created by #IndieWeb community member @jamesg.blog (@capjamesg@indieweb.social): @breakfastand.coffee

    It’s still quite new, but the thing that makes Breakfast & Coffee innovative and unique is that it encourages you to post your venue (e.g. cafe) description or review on your own site with a meaningful slug, link to https://breakfastand.coffee/ and then send a Webmention to indicate that you’d like to syndicate your venue or review into Breakfast & Coffee, like into an aggregator.

    Before I get to that point however, I feel there’s quite a few challenges in publishing a “decent” restaurant / cafe venue page, because there really is a dearth of good examples of doing so with simple semantic HTML + CSS. You really don’t need JS to post info about a restaurant.

    Setting aside the economic / intermediation challenges of "delivery apps" for now, people really want a few simple things from a restaurant site / page that could all be marked up with simple semantic HTML (thus resulting in good web search rankings) and styled in a quickly readable and mobile-friendly way.

    * hours open (perhaps kitchen hours if different)
    * location (address that links to a map UI or map embed w/o cookies/tracking)
    * nearest bus/tram/rail stop
    * payment restrictions (e.g. if only cash, or only credit) or options if you prefer
    * contact info (including a note about catering if that’s an option)
    * links to social media profiles
    * links to restaurant review sites/aggregator pages (e.g. venue permalink on Google Maps, TripAdvisor, Foursquare, Swarm, HappyCow)
    * menu with item name, description, price, optional-thumbnail, and dietary/allergy notations

    No you really don’t need the full mess of made-up things at schema-org.

    The community at OpenStreetMap has done A LOT (most? nearly all?) of the work figuring out the ways to express the above types of information, e.g.:

    https://wiki.openstreetmap.org/wiki/Key:opening_hours

    Yet has anyone actually seen a simple semantic HTML page that publishes this kind of information?

    I’ve web searched many search terms and phrases and found nothing good.

    Stylistically dated templates for sale. Examples with numerous unnecessary scripts (no your typical user does not care about your clever animated 3D-carousel of pretty photos, certainly not waiting for a megabyte of framework scripts for it). Something built on Bootstrap, unnecessary for today’s mobile-friendly HTML+CSS.

    I did find one (ONE) blog post from 2007 (those were the days) for semantic markup for a restaurant menu: https://jonchristopher.us/blog/a-semantic-breakdown-of-restaurant-menus/

    Unless I find an existing solution soon, I’m going to create something from scratch with h-card (since a restaurant is an organization / venue) and add semantic HTML & class names for various fields, re-using from OpenStreetMap Keys whenever possible.

    That leaves the URL design, where to publish my restaurant pages on my own site, and rather than rethink it, I will likely go with what I decided in my Whistle short URL design¹ many years ago, which is /v/ at the top level of my site, followed by a slug of my short name for the venue. This way I can play with static HTML pages there, with a shared style sheet in that same directory, without impacting anything else on my site.

    I have some other thoughts around iconography for various diet preferences / allergen warnings for menu items that I’ve tried (or considered), though perhaps I’ll leave those for another post.

    Or maybe I’ll braindump them now, however incomplete, to see if they resonate or anyone has better suggestions (restaurants and menus really have no standard for these)

    🌱 vegan & gluten-free
    🌱🌾 vegan + gluten
    🌱🥜 vegan + nuts
    🌱🍫 vegan + chocolate
    🌱🍯 vegetarian (has honey)
    🌱🧈 vegetarian (has butter)
    🌱🥛 vegetarian (has milk, cream, or yogurt)
    🌱🧀 vegetarian (has cheese)
    🌱🥚 vegetarian (has egg)

    with combinations as necessary.

    For example, a breakfast sandwich at Devil’s Teeth Bakery²:
    * Regular Breakfast Sandwich (no bacon!) $10.00 🌱🌾🧈🧀🥚

    Or a chocolate croissant at Arsicault³:
    * Chocolate Croissant $5.75 🌱🌾🧈🍫

    Non-vegetarian items would omit the plant 🌱 icon/emoji, but could still include allergen icons.

    If you are posting restaurants (or any other venues) to your personal site, please add a few of their permalinks to the IndieWeb Examples here: https://indieweb.org/venue#Indieweb_Examples


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

    ← Day 39: https://tantek.com/2023/112/t2/account-migration-post-blog-archive-format
    → 🔮


    Glossary

    article
     https://indieweb.org/article
    checkin
     https://indieweb.org/checkin
    h-card
     https://microformats.org/wiki/h-card
    h-entry
     https://microformats.org/wiki/h-entry
    h-review
     https://microformats.org/wiki/h-review
    POSSE
     https://indieweb.org/POSSE
    review
     https://indieweb.org/review
    URL design
     https://indieweb.org/URL_design
    venue
     https://indieweb.org/venue

    References

    ¹ https://tantek.com/w/Whistle#design
    ² https://www.devilsteethbakingcompany.com/menu
    ³ https://arsicault-bakery.com/menus
    Monday, 24-Apr-2023 16:34:00 EDT from tantek.com permalink
  17. Tantek ()'s status on Saturday, 22-Apr-2023 20:40:00 EDT Tantek Tantek
    One of the pretty neat innovations from #Mastodon has been actual, functional, and fairly reliable (from all accounts I’ve seen) distributed system account migration, with the notable exception of post migration, which has additional challenges worth exploring.

    To be clear, as far as I know, no other blogging (or chat) software, system, or even protocol comes close to achieving the level of functionality described in Mastodon’s documentation:

    https://docs.joinmastodon.org/user/moving/#migration

    In short, moving:
    * all your profile information
    * moving all your followers & followings, transparently
    * redirecting your old account to your new one

    More at that link. From the docs, it’s clear that quite a bit of thought & consideration went into the design & implementation.

    Once I had setup #BridgyFed to #federate posts from my own site¹, I myself made use of the this Mastodon feature to migrate from my try-it-out @t@xoxo.zone account to my #IndieWeb @tantek.com (move destination handled by BridgyFed).

    For me the migration experience was 100%, because I had not posted anything @t@xoxo.zone.

    The challenge of post migration is not unique to Mastodon, though I believe it goes beyond “simple” export & import support, which is still a good place to start.

    Mastodon has two forms of posts “export” currently:
    * RSS feeds, which will get you some number of recent posts, by adding ".rss" to the end of any Mastodon profile URL, e.g. https://indieweb.social/@tchambers.rss
    * Activity Streams 2.0 JSON, per https://docs.joinmastodon.org/user/moving/#export (note: it currently says “ActivityPub JSON format”, but there is no such thing, #ActivityPub uses the #ActivityStreams 2.0 JSON format and I’ve filed a PR² to fix this in the docs)

    Lots of software & services import RSS, e.g. #WordPress.

    As far as I know, nothing (not even Mastodon itself) actually supports importing Activity Streams 2.0.

    There is a more complete format (with specification!) for exporting & importing blog content:

    Blog Archive Format (.bar), first specified here with example file:
    * https://www.manton.org/2017/11/24/blog-archive-format.html
    More details and another example file:
    * https://www.manton.org/2021/12/27/importing-blog-archive.html

    Blog Archive Format has the very nice features of:
    * portable HTML feed (h-feed) and JSON Feed
    * photos and other media
    * locally browsable post archive

    Naturally, https://micro.blog/ supports both exporting & importing Blog Archive Format.

    There’s an interesting opportunity here for an open source converter
    * from Activity Streams 2.0
    * to Blog Archive Format

    Such a library would make an excellent drop-in addition to any #ActivityPub implementation, allowing both export of posts, and also a browsable archive format, so you could visually double check when importing to another service that these were the old posts you were looking for.

    This would be a good first step, using an open standard, towards Mastodon itself supporting post migration³.

    Ideally, similar to account migration, the old posts server should also at least:
    * redirect old permalinks to the new permalinks
    * redirect any replies being delivered by ActivityPub to the new location
    * provide #Webmention discovery forwarding from the old URLs to the new URLs (e.g. using HTTP LINK headers)
    for some amount of time.

    Want to add support for Blog Archive Format or got questions or feedback?

    Join in the development conversations: https://chat.indieweb.org/dev


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

    ← Day 38: https://tantek.com/2023/110/t2/beyond-mastodon-indieweb-own-domain
    → 🔮


    Glossary

    account migration
     https://indieweb.org/account_migration
    blog archive format
     https://indieweb.org/blog_archive_format
    h-feed
     https://microformats.org/wiki/h-feed
    JSON Feed
     https://www.jsonfeed.org/
    post migration
     https://indieweb.org/post_migration
    Webmention
     https://indieweb.org/Webmention

    References

    ¹ https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indieweb
    ² https://github.com/mastodon/documentation/pull/1202
    ³ https://github.com/mastodon/mastodon/issues/12423
    Saturday, 22-Apr-2023 20:40:00 EDT from tantek.com permalink

    Attachments

  18. Tantek ()'s status on Thursday, 20-Apr-2023 20:57:00 EDT Tantek Tantek
    In https://www.theverge.com/2023/4/20/23689570/activitypub-protocol-standard-social-network, author @pierce@mas.to does an excellent job covering a broad range of #ActivityPub related updates, and goes beyond the usual #Mastodon focus to describe numerous implementations.

    I was very happy to see that he also clearly communicated several #IndieWeb principles¹, practices, goals, and reasons why². Like this quote:

     “But the advice you’ll hear from most people in this space is this: own your own domain. Don’t be john@/mastodon.social or anna@/facebook.com. Have a space that is yours, that belongs to you, a username and identity that can’t disappear just because a company goes out of business or sells to a megalomaniac.”

    and this:

     “It’s [your own domain is] your YouTube channel name and your TikTok username and your Instagram handle and your phone number and your Twitter @, all in one name.”

    Great interviews with @stevetex@mozilla.social, @mike@flipboard.social, @dustycloud.org (@cwebber@octodon.social), @evanp.me (@evan@cosocial.ca), @anildash.com (@anildash@me.dm), @coachtony@me.dm, and @manton.org.

    As Manton said in the article:

     “If you solve identity with domain names, it makes things easier because it fits the way the web has been for 20 years,”

    Pierce also noted:

     “you might soon be able to turn your personal website into your entire social identity online”
     
    Already can.

    I replied to Pierce’s post³ about his article noting this⁴, from #federating directly from my website for the past ~6 months⁵, to over a decade of using it as my social identity with the POSSE method⁶ with various #socialMedia silos.

    It’s important enough that I’ll repeat part of Pierce’s quote at the top:

     “own your own domain. Don’t be john@/mastodon.social or anna@/facebook.com. Have a space that is yours”
     
    He gets it. Don’t be someone at someone else’s server.

    Big Chad or Little Chad’s garages⁷ are social media stepping stones towards owning your own domain and IndieWeb presence.

    We’re here when you’re ready to take that next step: https://chat.indieweb.org/


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

    ← Day 37: https://tantek.com/2023/109/t2/years-ago-first-federated-indieweb-thread
    → 🔮


    ¹ https://indieweb.org/principles
    ² https://indieweb.org/why
    ³ https://mas.to/@pierce/110231624819547202
    ⁴ https://tantek.com/2023/110/t1/
    ⁵ https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indieweb
    ⁶ https://indieweb.org/POSSE
    ⁷ https://tantek.com/2023/001/t1/own-your-notes
    Thursday, 20-Apr-2023 20:57:00 EDT from tantek.com permalink

    Attachments

  19. Tantek ()'s status on Wednesday, 19-Apr-2023 20:48:00 EDT Tantek Tantek
    10 years ago today the first #federated #IndieWeb comment thread was published and collected peer-to-peer IndieWeb replies across websites without any intermediary, silo or otherwise¹.

    2013-04-19 @eschnou.com posted a brief note on his personal site with #atMentions of a few domains (putting an '@' sign immediately before a domain name to indicate an explicit cross-web @-mention), which itself was also a first²

     "Testing #indieweb federation with @waterpigs.co.uk, @aaronparecki.com and @indiewebcamp.com !"

    When @aaronpk.com was notified and replied from his site within minutes³, it became the first peer-to-peer federated IndieWeb comment thread, at the time using h-entry and Pingback. I blogged about it a few days later⁴.

    Earlier this year I blogged more observations of all the user interactions that happened on that day and shortly thereafter to make this all work: https://tantek.com/2023/014/t4/domain-first-federated-atmention

    Unfortunately Laurent Eschnou’s original post is no longer up, and we only have the Internet Archive copy. However most of the IndieWeb reply posts are still up including Barnaby’s: https://waterpigs.co.uk/notes/1334/

    The oldest still working federated post and comment thread was second overall, unsurprisingly from @aaronparecki.com⁵, a whole 40 days after Laurent’s first.

    This is day 37 of #100DaysOfIndieWeb. #100Days #OpenWeb #federation #fediverse

    ← Day 36: https://tantek.com/2023/100/t1/auto-linked-hashtags-federated
    → 🔮


    Glossary

    federation
     https://indieweb.org/federation
    h-entry
     https://microformats.org/wiki/h-entry
    Pingback
     https://indieweb.org/Pingback
    reply post
     https://indieweb.org/reply

    References

    ¹ https://web.archive.org/web/20130427010301/http://eschnou.com/entry/testing-indieweb-federation-with-waterpigscouk-aaronpareckicom-and--62-24908.html
    ² https://tantek.com/2023/014/t4/domain-first-federated-atmention
    ³ https://aaronparecki.com/2013/04/19/3/indieweb
    ⁴ https://tantek.com/2013/113/b1/first-federated-indieweb-comment-thread
    ⁵ https://aaronparecki.com/2013/05/21/4/xkcd
    Wednesday, 19-Apr-2023 20:48:00 EDT from tantek.com permalink
  20. Tantek ()'s status on Wednesday, 19-Apr-2023 04:22:00 EDT Tantek Tantek
    @fredrocha.net (@john_fisherman@mastodon.social) saw your post (https://mastodon.social/@john_fisherman/110224246899618915) from the #IndieWeb stream. Beautiful photos on your site! #btconf was great wasn’t it?

    My personal URL is https://tantek.com/ and my #fediverse @ is @tantek.com. My Atom feed file is auto-discoverable by feed readers from my home page.

    Feeding (so to speak) two discovery birds with one stonefruit¹.

    Your personal website can be your fediverse address², each providing seamless discovery for the other.

    As web developers we should be building & developing our personal sites to exemplify the latest & greatest of such practices, including using Mastodon/ActivityPub as yet another distribution mechanism (ala POSSE) for your existing personal websites rather than a separate profile/stream.

    Discussed this with @nebu@mastodon.social and @kadirtopal@mastodon.social just after the last talk @beyondtellerrand.com (@btconf@mastodon.social @btconf) yesterday, fitting conference closing thoughts complementing the heartfelt opening talk by @localghost.dev (https://sophie.omg.lol/ @sophie@social.lol)³.

    Glossary

    ActivityPub
     https://indieweb.org/ActivityPub
    feed file
     https://indieweb.org/feed_file
    POSSE
     https://indieweb.org/POSSE

    References

    ¹ https://tantek.com/2020/147/t2/replace-violent-metaphors
    ² https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indieweb
    ³ https://tantek.com/2023/107/t1/beyond-tellerand-talk-love-personal-website
    Wednesday, 19-Apr-2023 04:22:00 EDT from tantek.com permalink

    Attachments

  • After
  • Before
  • Help
  • About
  • FAQ
  • TOS
  • Privacy
  • Source
  • Version
  • Contact

stadeus is a social network, courtesy of blaise.ca. It runs on GNU social, version 1.2.0-beta4, available under the GNU Affero General Public License.

Creative Commons Attribution 3.0 All stadeus content and data are available under the Creative Commons Attribution 3.0 license.

Switch to desktop site layout.