Winnie Lim » this website as a learning and reflection tool

I love reading about how—and why—people tinker with their personal sites. This resonates a lot.

This website is essentially a repository of my memories, lessons I’ve learnt, insights I’ve discovered, a changelog of my previous selves. Most people build a map of things they have learnt, I am building a map of how I have come to be, in case I may get lost again. Maybe someone else interested in a similar lonely path will feel less alone with my documented footprints. Maybe that someone else would be me in the future.

Oh, and Winnie, I can testify that having an “on this day” page is well worth it!

#indieweb #personal #publishing #writing #sharing #notes #onthisday #history #archives #stories #learning #reflection
Gordon Brander’s article "Building a Second Subconscious" is nice.

His properties for what might make what you could call ‘convivial tools for thought’ are all pretty IndieWebby.

Also on:

Told my sister I was building a new website for a writing project and she asked me how anyone was supposed to find it if it was its own independent website instead of a bigger site and boy howdy I’ve been failing in my indieweb duties
My social media usage is something like this.

– Follow people wherever they are (including the big silos).
– Write locally, in my ‘digital garden’, first.
– Publish on my own site. I for sure own the data this way.
– Syndicate things elsewhere, wherever the community best fits for my post. But don’t feed the big tech beasts.
– Interact with people wherever they are.

At present, a combo of org-mode, IndieWeb, Fediverse, Agora make this possible for me.

Also on:

fluffy rambles: Some thoughts on comments and interaction

#rss #personal-website #indieweb #blogging

Check meta headers for HTTP Status

“The internet wasn’t designed to breach national boundaries” - Rest of World

Say you’re into the indie web without saying you’re into the indie web…

The internet wasn’t really convenient in 1994 or 1995, but it was a very collaborative space.

There was a moment where we replaced this idea of the internet being a medium that we can all write to and participate in to one that is mediated. That happened at some point after social networks started to arrive and when the smartphone started to arrive. It’s a combination of the nature of those platforms and the prevalence of the technologies, which meant the economic rewards of getting this right rose significantly.

And so there’s a really distinctly different feel in the 2013, or 2014, internet to the one that you might have had in 1997, or 1998. It’s not just that it’s easier and I’m yearning for a world of cars with manual choke and manual transmission and crank-up starter handles, but it’s that the programmability of the internet and its endpoints has turned into something that is increasingly permissioned by major platforms.

#indieweb #platforms #publishing #decentralisation #silos #regulation #governance #facebook
I'm interested.

Seems like a fun way of catching up with some IndieWeb folks!

Feature request: Bridgy backfeed reacjis on POSSEd comments

Last year last times:
Mar 2
* lunch with co-workers
Mar 4
* bus ride
* in the office
* #IndieWeb HWC @MozSF
* train ride
Mar 5
* haircut
* indoor yoga @YogaFlowSF
Mar 7
* movie @AMCTheatres (Knives Out)
& @Benihana for nephew1 bday

One Year Since The #IndieWeb Homebrew Website Club Met In Person And Other Last Times

Life Happens: Towards Community Support For Prioritizing Life Events And Mutual Care, Starting With The #IndieWeb

@toddbarnard indeed.

Also mentioned in #IndieWeb chat^:

“all you have to do is”

Still looking for a category for these words/phrases.

Maybe “trivializers”?

Minor #OwnYourLinks #IndieWeb trick I setup a while ago:

Top level /github redirect to my profile so I can link to: instead of linking to @Github directly.

Enables eventual moving/selfhosting repos/issues without breaking links.
#OwnYourLinks #IndieWeb
@stop I went to my own site to point it out ;) which is also what @aaronpk did.

What you’re seeing on Twitter is merely a syndicated copy, for those who use Twitter as their reader, AKA POSSE:

This reply is also from my site.
you know what's *not* down right now?

my personal site & blog ⬇


(copied from @aaronpk
This is precisely what the microformats2 "u-" property prefix is for, to instruct the  parser to retrieve and parse for URL-like information from an element, from its URL-related attribute if any, and text content as a fallback, including relative URL resolution if applicable. E.g. in the example you gave, try u-tel instead of p-tel:

 <a class="u-tel" href="tel:13335553483">(333) 555 FIVE</a>

If that works as desired, go ahead and close this issue.
Hey #future #optimist #creatives, #artists, & #writers:
* #Solarpunk Art Contest
* Submissions for Solarpunk Anthology
cc @solarpunk_girl #indieweb

Also #DisneyPlus started streaming #TomorrowLand🔮 today!
#future #optimist #creatives #artists #writers: #Solarpunk #indieweb #DisneyPlus #TomorrowLand gave me a heads-up about this.

tl;dr: All the same reasons for not re-using WebID apply to Web Sign-in (and Sign-on is too similar), and thus we object to the proposed re-use.

There’s already an existing set of related specs[1][2][3], numerous deployed & in-use implementations[4][5], and an open standards community actively using (including numerous actual users using) the term / phrase / technology[6][7]. wrote in
> Naming is hard and taking an existing name from an existing community doesn't win you any friends or collaborators.


To state it even more strongly, Google of all parties must not act in a bullying way (we must consider the outsized influence & power dynamics), even within the auspices / context of a CG (using a vote in a CG to justify squatting over an existing active spec and a community’s use thereof). Rallying more folks to tacitly or otherwise approve of bullying is still bullying, perhaps even a worse form of doing so.

I can sympathize with the naming challenges in the area of identity (seems fitting).

That noted, an exploration in a CG seems premature to worry so much about a "marketable" name, especially in an area where naming is hard.

Instead, make up a throwaway placeholder name (like WID2021), first get the technology right, working across at least a few different vendors relying/consuming each others identities interoperably, and then worry about an actual marketable name, perhaps at WD/CR time. We know this can work per the prior example of "Atom" which went through a few throwaway names like "Pie" before being standardized as Atom in RFC 4287 at IETF.

Thanks for your consideration,


[3] (previously a W3C Note published by the Social Web Working group: