⭐️ Why The Indieweb?
(via Mrs. McKhaos)
Likes and replies in the IndieWeb
(via Mrs. McKhaos)
I am intrigued by the IndieWeb’s approach to plurality and building technologies that don’t serve the creation of monocultures or single ways of thinking about things. IndieWeb technologies help build plug-and-play social bridges. The technologies are your pipes. You get to decide how they connect and what you make with those pipes. This idea excites me to a great degree.
Could you explain what you mean by “plurality?” In the circles I run in it almost certainly means something different than what you mean by it, and the definition I’m familiar with is likely to be the more common one on the Internet in
From context it seems like you’re talking about building a (distributed) voting/polling system, which is definitely an interesting topic to think about, and the first-cut approach would probably be to do something using fragmentions or otherwise having a
u-vote-for (or similar) link either to an anchor on the page or to the resource being voted on (e.g. the image itself).
Out of curiosity, have you put any thought into adding TicketAuth/bearer token support so that folks can get private subscription content as well? There’s a bunch of security aspects to consider with that but it’s a thing I’d love to see come into a reader.
There’s also a few UX things implied by microsub which I’m not a fan of, personally, and when I get around to finally building Subl (which I’ve only been talking about for as long as I’ve been talking about Publ) I was planning on building it as a standalone thing which could maybe optionally support microsub readers later, but the UX I want to build isn’t cleanly supported by the data model implied by microsub.
(Basically I want to build Feed on Feeds except in Python and with TicketAuth support.)