#indieweb 2021-08-08
2021-08-08 UTC
Seirdy, n8chz and alex11 joined the channel
# 
[chrisaldrich] GWG++ for the new dark mode on his site
# [chrisaldrich] Better than the bright only mode I'm sporting. 😎
hendursa1, jacky and neceve joined the channel
# 
[tantek]1 snarfed, my intuition is that it does seem quite complicated to make the use-case work that's mentioned in the issue. both the work for a default rendering as you put it (proposal in the wiki section you linked to), and on the part of the developer with the class names
# [tantek]1 I haven't found a lot of instances of this since the examples I documented at that wiki link either
# [tantek]1 maybe worth discussing the class name approach more in #indieweb-dev?
nertzy_, jeremycherfas, [Rose]1, nertzy__, kir0ul3, bneil, selectric, eco, angelo, jmac, vroman, neceve, jamietanna1, jamietanna, tetov-irc, rockorager, Kai` and j0hnny joined the channel
Zegnat[d] joined the channel
# Kai` good days of indieweb
anyhow, chenghiz_ and Sam2 joined the channel
# Sam2 Hey all, my name is Sam. Been following indieweb for awhile, wanted to jump in the discussion here
# Sam2 Thanks so much! Something I wanted to share with the community, which has parallels to the indieweb/POSSE visions — would love to hear folks thoughts on it
# Sam2 For this use case, and many others, it seems uncontroversial that we'll move away from centralized social networks — to networks that are more free, user-centric, and dynamic. To start this transition, it seems that the simplest and surest first step is having access to our graph data — so that we can use it and build/experiment on it. Specifically, I'm talking about: 1. Export my contacts from LinkedIn, Facebook, and other social
# Sam2 I've started using LinkedIn as a way to communicate above the walled garden chat communities. I'm doing this to enable discoverability + accessibility + knowledge-sharing with my work. Much of the professional world — at least in subject areas I'm focused on — is on LinkedIn. By posting content and having discussions there, it enables anybody who may be interested in what I'm working on it to discover it — and likewise, me to discover
# Sam2 networks, using their APIs 2. Import those contacts into a new substrate/protocol, with some simple structure to help with identification. (For example, to tell the difference between two contacts named "Amy Bee." Or, if each of us have a "Amy Bee" in our contacts, an intelligent way to recognize if they are or are not the same person. Email or phone number or even domain name could be a useful "anchor" for this — and better approaches
# Sam2 could certainly be possible as well. ) 3. Once I have all of my contacts accessible — I just want some simple functionality to send messages, and the ability to tinker/experiment with new ways of interacting on top of this new substrate. Part 1 is feasible today. Part 2 seems like it requires some dedicated thought and design. Part 3 only comes after Part 1, and along with Part 2. If anybody is interested in this type of thing, I'd love
# Sam2 to hear thoughts and collaborate. Note that this approach isn't about onboarding to a new network, it's about migrating our existing networks to a new and dynamic environment. Also this is envisioned more of a commons / protocol / infrastructure initiative, not as a new network itself.
# Sam2 Absolutely!
# Sam2 My mistake
[Sam_Butler], anyhow, jacky and hendursaga joined the channel
# 
[jgmac1106] If anyone in edu or parents who went through a year of remote teaching on Google Classroom I would love to find out about why they went with an almost plain text editor with no images (why it takes fourteen tons of javascript to make happen...different question)
peterrother, mgdm, jbove, KartikPrabhu, hendursa1 and hendursaga joined the channel
# 
Loqi [indienews] New post: "How I Book Blog" https://blog.b-ark.ca/2021/08/07/how-i-book-blog.html
tetov-irc, Rattroupe and [Emma_Humphries] joined the channel