stadeus
  • Login
Show Navigation
  • Public

    • Groups
    • Recent tags

Notices tagged with indieweb, page 3

  1. Tantek ()'s status on Friday, 02-Feb-2024 16:49:00 EST Tantek Tantek
    I felt the #earthquake here in #SanFrancisco. A single quick sharp jolt with rapid decay, duration less than 2s, meaning it was relatively nearby and small in magnitude

    I was about to say, perhaps #earthquakes are the last use-case for #Twitter because yes I reflexively checked it and did see posts about it from folks, including a few friends.

    Then I checked https://indieweb.social/tags/earthquake and it has plenty of recent #fediverse posts about the earthquake, several @sfba.social.

    Feels like something big has shifted.

    The #federated #IndieWeb has replaced another #socialMedia silo use-case.

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

    ← https://tantek.com/2024/027/t1/indieweb-ideals-systems-swappable
    → 🔮


    Post glossary:

    silo
      https://indieweb.org/silo
    social media
      https://indieweb.org/social_media
    use-case
      https://indieweb.org/use_case
    Friday, 02-Feb-2024 16:49:00 EST from tantek.com permalink

    Attachments

  2. Tantek ()'s status on Saturday, 27-Jan-2024 03:13:00 EST Tantek Tantek
    For the #IndieWeb ideals of independence from intermediaries, not requiring corporate platforms or other organizational intermediaries¹, the best systems we have still depend on organizations. However they are all swappable, at will, by the individual:

    1. domain names, depend on registrars, which you can switch
    2. web hosts, depend on hosting providers, which you can switch
    3. internet access, depends on internet service providers, which you can switch
    4. web browsing, depends on browsers, which you can switch
    5. personal devices, that have choice of web browser and internet access, which you can switch, upgrade, and use multiples of simultaneously

    When you can migrate from one provider to another, one device to another, without disruption, without breaking your people-to-people connections, the providers and devices serve you, instead of gatekeeping you.

    This freedom to swap, freedom to choose, depends on practical #interoperability across multiple implementations, multiple services. Open standards are the means to encouraging, testing, and verifying this user-feature interoperability across implementations and services.

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

    ← https://tantek.com/2024/026/t3/indieweb-for-everyone-internet-of-people
    → 🔮


    Post glossary:

    domain name
      https://indieweb.org/personal-domain
    interoperability
      https://www.w3.org/wiki/Interoperable
    web host
      https://indieweb.org/web_host

    ¹ https://tantek.com/2024/026/t3/indieweb-for-everyone-internet-of-people
    Saturday, 27-Jan-2024 03:13:00 EST from tantek.com permalink
  3. Tantek ()'s status on Saturday, 27-Jan-2024 01:40:00 EST Tantek Tantek
    The #IndieWeb is for everyone, everyone who wants to be part of the world-wide-web of interconnected people. The social internet of people, a network of networks of people, connected peer-to-peer in human-scale groups, communities of locality and affinity.

    These peer-to-peer links should not require corporate platforms or other organizational intermediaries, nor should they require depending on developer intermediaries, nor server administrator intermediaries.

    This is the "indie" in IndieWeb, independence from intermediaries, not independence from people. Because the "web" in IndieWeb, is yes the Web of the World Wide Web, and it is also the Web of people.

    The "indie" in IndieWeb is also the independent agency to opt-into human-scale groups, opt-into peer-to-peer connections, opt-into communities, opt-into publics. As the POSSE page says: “Figure out how you want to fit into the network”.

    The "web" in IndieWeb is also an open acknowledgment and acceptance that regardless of what groups, connections, communities, and publics you opt-into, that they are all interconnected in a larger web, that even without connecting, you can accept and respect from a distance.

    The IndieWeb is for everyone, everyone who wants independence from organizations, independence of agency to associate, and who embraces the web of humans that want to interconnect, to communicate, to value and respect each other, whether one degree apart or thirty.¹

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

    ← https://tantek.com/2024/023/t1/should-public-posts-flow-across-sites
    → 🔮


    Post glossary:

    IndieWeb
      https://indieweb.org/
    POSSE
      https://indieweb.org/POSSE
    publics
      https://indieweb.org/publics


    ¹: https://www.theguardian.com/technology/2008/aug/03/internet.email
    Saturday, 27-Jan-2024 01:40:00 EST from tantek.com permalink

    Attachments

  4. Tantek ()'s status on Tuesday, 23-Jan-2024 20:20:00 EST Tantek Tantek
    @snarfed.org posted a great overview of thoughtful (and sometimes heated) discussions across blogs and the #fediverse about how freely should “public” posts & comments on the web flow across sites:

    “Moderate people, not code” (https://snarfed.org/2024-01-21_moderate-people-not-code)

    If you are designing or creating any kind of publishing or social features on the web, this post is for you.

    It touches on topics ranging from #contextCollapse to #federation to #moderation and everything in between.

    Does your choice of publishing tool set expectations about where your content might propagate, or whether it will be indexed by search engines? Should it?

    Do the limitations of your server (e.g. js;dr) imply limitations of where your posts go, or whether they can be searched or archived? Should they?

    When you post something publicly, are you truly posting it for a global audience for all time, or only for one or a few more limited #publics for an ephemerality?

    When you reply to a post, do you expect your reply to only be visible in the context you posted it, or do you expect it to travel alongside that post to anywhere it might propagate to?


    On the #IndieWeb, especially for public posts, some of these questions have easier and more obvious answers, because the intent of nearly all public IndieWeb posts is to interact across the web with other posts and sites, typically via the #Webmention protocol. However there are still questions.

    Are the expectations for a blog and blogging different from a social media site, whether a silo or an instance on a network?

    Is a personal website with posts still just a blog, or does it become something new when you start posting responses from your site, or receiving (e.g. via Webmention) and displaying responses from across the web to your posts on your site? Or is it now a “social website”?

    If you have a social website, what is your responsibility for keeping it, well, social? Do you moderate Webmentions by default? Do you use the Vouch extension for some automatic moderation?

    Are #POSSE & #backfeed different from federation or are they the same thing from a user-perspective, with merely different names hinting at different implementations?

    Do you allow anyone from any site to respond or react to your posts? Or do you treat your social website like your home, and follow what I like to call a "house party protocol", only letting in those you know, and perhaps allowing them to bring a +1 or 2?

    I have many more questions. Each of these deserves thoughtful discussions, documentation of what different tools & services do today that we can try out, learn from, and use to make considered decisions when creating new things to post on and across websites.

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

    ← https://tantek.com/2024/022/t1/indiewebcamp-brighton-planned
    → 🔮


    Post glossary:

    backfeed
      https://indieweb.org/backfeed

    blog
      https://indieweb.org/blog

    blogging
      https://indieweb.org/blogging
     
    comments
      https://indieweb.org/comments

    context collapse
      https://indieweb.org/context_collapse

    ephemerality
      https://indieweb.org/ephemerality

    js;dr
      https://indieweb.org/js;dr

    moderation
      https://indieweb.org/moderation

    POSSE
      https://indieweb.org/POSSE

    posts
      https://indieweb.org/posts

    publics
      https://indieweb.org/publics

    reply
      https://indieweb.org/reply

    Vouch
      https://indieweb.org/Vouch
     
    Webmention
      https://indieweb.org/Webmention
    Tuesday, 23-Jan-2024 20:20:00 EST from tantek.com permalink
  5. Tantek ()'s status on Tuesday, 23-Jan-2024 02:20:00 EST Tantek Tantek
    The first IndieWebCamp of the year has been planned!

    🎪 IndieWebCamp Brighton
    🗓 2024-03-09…10
    🏢 The Skiff, Brighton, England
    🎟 Tickets available 2024-02-01!

    Event: https://events.indieweb.org/2024/03/indiewebcamp-brighton-2024-xRTP2hAZOvZd
    Wiki: https://indieweb.org/2024/Brighton

    Questions about #IndieWebCamp? Ask in #IndieWeb chat!
    💬 https://chat.indieweb.org/

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

    ← https://tantek.com/2024/003/t1/2023-indieweb-gift-calendar-numbers
    → 🔮
    Tuesday, 23-Jan-2024 02:20:00 EST from tantek.com permalink
  6. Tantek ()'s status on Wednesday, 03-Jan-2024 19:09:00 EST Tantek Tantek
    31 days of #IndieWeb gifts: the _2023 IndieWeb Gift Calendar_ (https://indieweb.org/2023-12-indieweb-gift-calendar) wrapped up a full month of IndieWeb-related creations & updates from the community (and sometimes beyond) to everyone who wants to improve their #IndieWeb experience.

    From plugins & libraries, to tools & services, to events & meetups, to web components & wiki pages, and blog posts & newsletters, there was something for everyone.

    Some numbers:
    🎁 67 total gifts
    📄 32 new IndieWeb wiki pages
    📜  7 posts on improving blogs, IndieWeb specs, and event summaries
    💻  6 Homebrew Website Club online meetups
    📫  5 This Week In The IndieWeb newsletters
    🧱  4 library updates: new web components, #microformats2 parser update
    🌉  3 Bridgy Fed updates & improvements
    🧩  2 plugin updates: #Elgg IndieWeb & #WordPress #IndieAuth
    🎪  1 #IndieWebCamp San Diego (2 days!)
    📚  1 indiebookclub new year in review overview feature
    📽  1 IndieWeb movie viewings aggregator
    🧶  1 #Threads federating out #ActivityPub (followable by #BridgyFed)

    Gift were shared by:
    👥 20 individuals
    🏢  1 company

    I compiled these numbers by hand. Let me know if you see any errors. There are many more potential stats like:
    * average (mean and median) number of gifts per contributor
    * how many edits to the Gift Calendar wiki page
    * how many different editors of the wiki page
    * average (mean and median) number of edits per editor
    I’ll leave those as exercises for others if they wish!

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

    ← https://tantek.com/2024/001/t1/restarting-100days-indieweb-gift-calendar
    → 🔮
    Wednesday, 03-Jan-2024 19:09:00 EST from tantek.com permalink
  7. 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
  8. 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
  9. 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
  10. 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

  11. 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
  12. 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
  13. 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
  14. 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
  15. 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
  16. 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
  17. 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

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

    Attachments

  19. 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
  20. 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

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