typ1cal_c0ffxe3, Matt1, Eddy04[d], P1000[d], Seirdy, darkkirb, jjuran and cygnoir[d] joined the channel
#Ruxton"remember how you used to have to actually *click* on each person one at a time to read their posts? instead of "just" scrolling?" uhh yeah but then I also remember just scrolling later on when peopled cottoned onto that concept. RSS/ATOM enabled me to read everyone that did it properly in one place and that was awesome. The people I followed stopped blogging and bigger sites stop giving out full
#Ruxtonfeeds, that's the ONLY reason I stopped using it
#[jeremycherfas]I currently still like scanning the titles in my reader and clicking only when I need to. And a keyboard shortcut takes me to the next person/feed I am following.
MarkJR84[d] joined the channel
#ZegnatMy reading experience hasn’t changed since the Google Reader days. Select the folder I want to read, be presented with a post I had not yet read, use j/k keys to go to next/previous post.
#ZegnatI have never even had a need to relearn keyboard shortcuts. j/k worked in Google Reader, but also in applications like Reeder, in the Feedbin web version, on Facebook, basically anywhere I read things.
#[grantcodes]I used the web share api in together, works pretty well on android these days, no idea if apple has bothered to support it though. It could definitely be made to work directly on your own website though.
#@clivewalkerRedeveloping own site. Unsure whether to keep blog post comments and webmentions. Comments just attract spam. Webmentions seems like a bit of "developer" indulgence? Probably need to think on this some more though. (twitter.com/_/status/1483080472238469123)
Ramon[d] joined the channel
#GWGcapjamesg[d]: Thinking about registering some targets to share links to my site.
#GWGIt was actually one of the action items from the web action session at IWC SF 2019
#[Joe_Crawford]_[tantek]: “also remember how you used to have to actually *click* on each person one at a time to read their posts? instead of “just” scrolling?” -_ I concur with the bold / unbolding irritation — when I was stuck in a reader that treated RSS like a 3-pane email inbox. I’m much happier now that I can group feeds and scroll through and they get implicitly marked as read as I go. I can star later as need be. I als
#[Joe_Crawford]about subbing/unsubbing from feeds, creators. I feel like this is a requirement in the current infosphere. We are responsible (for better/worse — mostly worse) for curating the news and information we are presented with. This is the complaint people have about IG, Twitter - “the algorithm” is in control, yes? Well, the only way to beat the algorithm is to BE the algorithm.
#[tantek]interesting point (which I agree with, UX > DX) and actually thoughtful debate in the replies: https://twitter.com/kentcdodds/status/1482390454389805058. I do think IndieWeb development mixes the two heavily (as it happens when you have a feedback loop of cooking what you want, then eating what you cook, then iterating)
#@kentcdoddsUser experience (UX) and developer experience (DX) are both important. UX is more important than DX. @remix_run has taught me: It's easier to start with a great UX and work toward a good DX than it is to start with a great DX and work toward a good UX. (twitter.com/_/status/1482390454389805058)
#LoqiIt looks like we don't have a page for "Developer Experience" yet. Would you like to create it? (Or just say "Developer Experience is ____", a sentence describing the term)
#capjamesg[d]Developer Experience is a term used to describe the way in which a developer interacts with a tool, and should be prioritized behind user experience when building websites.
#capjamesg[d]One thing I might write about is how social readers might need to come with some kind of default publishing mechanism.
#capjamesg[d]Right now, I publish from my feed reader through my Microsub endpoint to my site. Most users would not care about that and would not want to set up three different services just to post something.
#capjamesg[d]A feed reader that had a default — opinionated — publishing interface could give people a place to say “hey! You can see my content at X!”
#jackyand yeah capjamesg[d]; that's something I ran into when I wanted to make a social reader - people need a bit more than expected if it's their first foray into the IndieWeb as well
#capjamesg[d]Which I think is a key part of making a good reader UX. You sign up for Instagram and within a minute or two you can make a post and share it.
#capjamesg[d]I would love to bundle a Micropub server with a reader but the server handling would be contingent upon how people want to publish their data.
#jackythe thing is I wouldn't want to have too much control over that b/c that can implictly create lock-in (Mastodon and server movability after years being a prime example)
#jackytbh not too bad! it's slow (as expected, it has the specs of a phone from 2015 - 2016) but it's nice to use the same apps across device form factors
#jackyCozy, for example, is an audiobook app and just being able to plug in the phone to sync the files with Calibre is nifty
#jackywhat it made me really interesting for is building a desktop client for indieweb stuff
#jackythere's a few native ones for things like AP (Tusky, Todon, etc)