Notes, page 3

Status updates and short notes.

Subscribe to the feed

  1. Replying to a tweet from @clmnsk:

    Thanks! From what I’ve read Strava is a bit more open with its API. Garmin seems to be way more restrictive about it. Your indieweb.org link reminds me of adding some info regarding Garmin there. 👍

  2. Next step for owning more of the content I’m producing: I swaped all of my runs (368 in total) with all relevant data from the Garmin silo to the ProcessWire instance of my website. ✌️

    The runs will be part of my content stream on my website. The process of getting new runs into the system is not yet automated, I have to play around with it still to figure things out.

  3. Replying to a post on gregorlove.com:

    Very nice, I like your approach. Thanks a lot for the snippet!

    I’ve not heard from a lot of people using the module yet.

    My impression is also that the module didn’t quite get the traction it deserves. Just love the work you have put into it!

    By the way, we’ve been having weekly virtual indieweb meetups if you’d like to join.

    Awesome, I will see if I can join.

    Thanks a lot for your response, Gregor!

  4. On June 12 I asked @gRegorLove a question on Twitter. Today he responded, and he did so via his blog and with the help of webmentions, which pinged Bridgy to syndicate his response to Twitter. The result on Twitter is a usual conversation. After that I published my response to him. I also did this via my website, using the same mechanism that he used when he wrote his response to me.

    But I didn’t use the exact same mechanism: I forgot to use Bridgy to syndicate the response to Twitter and thus to his tweet, instead I replied directly to his website response. The result is that I accidentally shifted the conversation, which originated on Twitter, to our personal websites. Apart from having been an accident (and probably it is rather confusing for the conversation flow) I thought that this shows the underlying power of webmentions:

    • The ability to freely shift conversations between plattforms.
    • The ability to be in control of the conversation flow.
    • The ability to still being able to present the context of the conversation flow underneath the content it originated from.

    I’m still rather new to the Webmention and IndieWeb scene, but the underlying concepts and their implications speak to me 100 %.

  5. Replying to a post on gregorlove.com:

    Thanks a lot for the explanation!

    I’m already sending webmentions via Bridgy Publish. I altered your module to optionally include the publish URLs for (in my case) Twitter and Mastodon. I’ve done this in this file around that line. I’ve added a checkbox in my notes called “Post to Bridgy?”, and when that is checked I append the Bridgy publish URLs to $page->{$field} as additional URLs to process for webmentions.

    The core of what I need is what you wrote here:

    I wrote some more code that processes that response to get the tweet’s URL and updates the syndication link on the note.

    That’s basically exactly what I’m looking for. I see if I can achieve that by myself, playing a bit around with it.

    But thanks again for you reply, that clarifies a lot for me. And it’s also a bit sobering to see that apparently it’s really not that easy to automate the process. Looking around at all the #indieweb blogs and seeing all the syndicated links on notes frankly I felt quite stupid not understanding how all this folks are doing this automatically. Also one really can’t find a whole lot information around the web, which adds to the problem.

  6. Still not able to let Bridgy post reactions to tweets (that don’t have the URL of my website in them) back to my webmention endpoint. Tried this in the help section https://brid.gy/about#link but somehow it’s still not working. 🤷‍♂