"Personal stories on personal #blogs are historical documents," said this Verge article.

This is so true for Christopher, who left behind a treasure trove of thoughts, a record of his brilliance on earth. I feel privileged to have found his #blog.

And that's why we need personal #blogging to return, #algorithms be damned. We can't let these stories disappear into the ether.

#IndieWeb #Writing

https://www.theverge.com/23513418/bring-back-personal-blogging

The answer to “How should you @-mention someone you are replying to?”^1 can depend on many factors or a few. Context matters somewhat, sometimes.

We can simplify it to 2 questions, based on 1 directive:

* Elevate #IndieWeb domains, above any silo or @-@ identities

Two questions and answers:

1. Do they have an #IndieWeb domain? Then @-domain mention them^2, like you are speaking to them at their domain identity. This will notify them there, or at least reinforce their domain’s importance.

2. Was their post only published on a silo (or #fediverse instance), or was it POSSEd to a silo (or fediverse instance) and you plan to POSSE (or federate) your reply^3? Then @-mention their silo @-name (or @-@ address), in parentheses if (1). This will notify them on that silo (or instance), and may help thread your POSSE reply.


Examples:


If the author has their own domain:

Reply to an IndieWeb post (& POSSE toot): https://tantek.com/2023/008/t1/
* @-domain (@-@)

Reply to an IndieWeb post (& POSSE tweet): https://tantek.com/2023/016/t1/
* @-domain [that matches their Twitter @-name]

Reply to a toot: https://tantek.com/2023/008/t4/
* @-domain (@-@)

Reply to a tweet: https://tantek.com/2023/002/t2/
* @-domain (Twitter @-name)


If the author does not have their own domain:

Reply to a toot: https://tantek.com/2023/002/t4/
* @-@

Reply to a tweet: none since this series, though it would be of the form:
* Twitter @-name


This is day 17 of #100DaysOfIndieWeb #100Days, again finished the next day.

← Day 16: https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute
→ 🔮


^1 https://tantek.com/2023/017/t1/socialweb-blogs-reply-comment-post
^2 https://tantek.com/2023/011/t1/indieweb-evolving-at-mention
^3 https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute
#IndieWeb #fediverse #100DaysOfIndieWeb #100Days

Tonight, I had some success in my #IndieWeb journey - adding #WebMentions to my blog. I took some shortcuts, but it did help me understand the concepts. Now I can go back and #POSSE it up. 💪

https://www.box464.com/indieweb/2023/01/18/indieweb-webmentions/

I’m not entirely certain when I was turned onto this phrase, but it has stuck with me for quite some time. It’s been sitting as a mobile bookmark for me for at least as long as I’ve owned an iPhone, so maybe going back to 2015-ish. Hapax legomenon – it seems so exotic, and definitely hard to pronounce in casual speech.


Hapax legomenon: a word or an expression that occurs only once within a context: either in the written record of an entire language, in the works of an author, or in a single text. (Definition courtesy of Wikipedia)


I think I may have been alerted to this phrase when doing a nostalgic look at Googlewhacking – trying to find a search result on google that only returns one result. Oddly enough, I do remember the first time hearing (and trying) the sport – it was the night before starting high school, and some friends and I learned about it and ended up finding a few.


I always thought the term would be a good name for a musical side-project, or an album title, but it looks like someone beat me to it.

#100daysofindieweb #atleast100 #indieweb

https://novakeith.net/2023/01/18/hapax-legomenon/

Managed to mess up links on my blog while changing something else. Some RSS and ActivityPub posts might be wrong while I sort it out.

Today, I am reading the Webmention and Webmention-Developer pages on the IndieWeb.org website. This is going to take a couple of days to review the examples. This is under the task to:

* Learn About Webmentions a Little More Deeply.

Day 11 of 100 #100DaysofIndieWeb, #IndieWeb, #ProjectJournal, #WordPress (https://tmichellemoore.com/?p=152149)

Support profile updates

Yes, I want to relaunch my website! Yes, I want start to blog (at least occasionally)!! And yes, I want to launch it all THIS YEAR!!! Let's see how it goes …

Thanks @matthiasott and the #IndieWeb folks for the motivation and the constant reminder to own our content.

Someone should really build a Nuzzel for the Fediverse / #IndieWeb https://daringfireball.net/linked/2021/05/05/nuzzel

Seeing as I've thought of some other things I didn't manage to squeeze in last time, here's another #introduction - Lately I've been #writing tiny generic #fantasy #horror adventures in #pocketmod format for #ttrpgs. I plan to put these up on Itch. And maybe I'll put together a #neocities page since I come from a #retroweb era and find the resurrected #indieweb movement very interesting. That dovetails with my ongoing interests in #politics #psychology and #philosophy. Proudest sport moment: I once took a brilliant hat-trick in indoor #cricket, Warne-style, with my legspin bowling - completely bamboozling the batsman. From #australia.

Planiverse: a minimalist, no-JS front-end for Mastodon (or
Peroma, or anything supporting the Mastodon API).

The Web was once a document delivery platform. It's now an
application platform, which is great if you want everything to be
an application. But what if you don't? What if you use an older
computer, or like using a text-only browser, or simply prefer to
turn JavaScript off? This is the Mastodon front-end for you.

#fediverse #mastodon #indieweb #smolnet
https://git.stjo.hn/planiverse/file/README.html

Replying to people on the social web used to be “simple” before #socialMedia, when we used blogs. You would either write:

1. a short reply — directly on someone’s blog post comment form, OR

2. a longer reply — on your own blog, in-reply-to & linking to the other post and send a Pingback, expecting at least the other post’s author to see your reply, or you would also write a short comment in their blog post comment form with a brief summary & link to your longer reply post

Aside: web forums^1 at the time were proto-silos^2, and replies/threads were generally self-contained therein.


Then social media exploded and eventually everybody was replying everywhere all at once.

This was so burdensome that some even hired social media managers to perform the labor of how (and if) to reply on each silo, and attempt to keep up with every new silo that popped up.


After a few years of this mid-to-late-2000s social web chaos, in the early 2010s many of us went back to option 2. above from the pre-social-media era, and as part of owning our data^3, started posting our replies in general on our own #IndieWeb sites:

1. Regardless of brevity or length, we resumed posting peer-to-peer replies on our personal sites (now sent site-to-site with Webmentions^4), watched destinations retrieve & display our comments, and were pleased that our peer-to-peer comments looked like any other comments (except with permalinks back to our originals).

2. We also started posting replies to tweets, GitHub issues^5, etc. on our own sites, and automatically POSSE-threading them into their sites of origin.

3. When we wrote site-to-site replies where the original post had itself been syndicated to social media^6, we did both 1 & 2. This let readers follow the conversation in either place, providing an #IndieWeb record for if/when the social media thread was taken down, or disappeared along with another silo shutdown^7.


Following this 1,2,3 approach helped conceptually simplify replying on the social web, and worked well except for a couple of interesting ongoing challenges:

* What is the most efficient user interface path from viewing someone else’s post to writing a reply from your own site?

* How should you @-mention someone you are replying to? (and how can our tools write or pre-fill that for us?)

Regarding the latter, on day 14 I wrote a bit about how should we @-mention in general https://tantek.com/2023/014/t4/domain-first-federated-atmention though that was more of a general @-mention exploration.

As a follow-up to day 14, it’s worth looking into @-reply mentions in particular, specifically for each of the above 1,2,3 contexts, analyzing examples of each, and looking for patterns of @-reply mentions best practices that we can document & recommend.

This is day 16 of #100DaysOfIndieWeb #100Days, except I didn’t finish writing it (mostly) til the morning after, and editing later that afternoon.

← Day 15: https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute
→ 🔮


^1 https://en.wikipedia.org/wiki/Internet_forum
^2 https://indieweb.org/silo
^3 https://indieweb.org/own_your_data
^4 https://tantek.com/2023/012/t1/six-years-webmention-w3c
^5 https://indieweb.org/GitHub#POSSE_to_GitHub
^6 https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute
^7 https://indieweb.org/site-deaths
#socialMedia #IndieWeb #100DaysOfIndieWeb #100Days

In the process of transforming my elizabethtai.com #website into an #indieweb #digitalgarden and I'm so hyperfocused on it it's hard to work lol.

Seeing as I've thought of some other things I didn't manage to squeeze in last time, here's another #introduction - Lately I've been #writing tiny generic #fantasy #horror adventures in #pocketmod format for #ttrpgs. I plan to put these up on Itch. And maybe I'll put together a #neocities page since I come from a #retroweb era and find the resurrected #indieweb movement very interesting. That dovetails with my ongoing interests in #politics #psychology and #philosophy. Proudest sport moment: I once took a brilliant hat-trick in indoor #cricket, Warne-style, with my legspin bowling - completely bamboozling the batsman.

Day 10 of 100 #100DaysofIndieWeb, #IndieWeb, #ProjectJournal, #ProjectManagement #WordPress

Today, I had hoped to have a plan documented to for my WordPress RSVP Block Pattern. Since yesterday I have been working on:

* Learn About Webmentions a Little More Deeply.

I read the Webmention specification from the W3C. Reading the spec was very informative. Even though I am going to have to read it again. And there will be some things that I will not understand, maybe… https://tmichellemoore.com/?p=152147

More brief thoughts on the end of Twitter apps

Personal #blog link for those who prefer the #indieweb https://mor10.com/pair-programming-with-ai/

Slowly getting #IndieWeb configurations setup on my site. Added h-card values to my post templates.

https://indiewebify.me/validate-h-entry/?url=https%3A%2F%2Fbox464.com%2Fdevops%2F2023%2F01%2F10%2Fwhats-up-doc%2F

I am having trouble figuring out how to set the way that posts display on Mastodon. There used to be a page in the IndieWeb or ActivityPub settings where you could choose the order like Title, Excerpt, Link, etc. Now I can't find it. So it just posts either an image or just the link with no context. I don't know how it got that way or how to change it. #IndieWeb #ActivityPub