#[KevinMarks]But they have a strong idea of what kinds of posts they want, and built a ui that encourages those (and they do a reasonable job of encouraging citing images etc)
#[KevinMarks]Medium wanted a different kind of post so built a different kind of editor (which we have a copy of in Quill.p3k.io)
#[KevinMarks]One thought with micropub could be editors tuned for different posting styles that still post in more than one place.
#[KevinMarks]How technorati bootstrapped discovery was by making a who links to whom leader board, which encouraged people to get indexed so that their links were counted (and they told people who linked to them to get indexed too as they wanted the inbound count)
Myst[d] joined the channel
#edgeduchess[d][KevinMarks]: can you expand on this?
#edgeduchess[d]the editors that post in more than one place biut
gRegor and benji joined the channel
#[KevinMarks]Micropub gives an abstraction for posting structured data, with the structure in microformats. Different backends can accept it, and different front ends can be tuned for specific cases. If the site con accept html, you can 'tunnel' structure through it. So posting to blogger or tumblr or wordpress can carry the structure with it.
#zerojames[d]This would make code management a bit more difficult but would mean I could post and consume in the same place.
#[KevinMarks]Part of the abstraction is to not need to, but it does add login steps. If you have micropub set up, monocle gives you integrated posting in the reader.
balupton[d], tetov-irc, KartikPrabhu and [tonz] joined the channel
#zerojames[d]marksuth I have got an IndieWeb Search extension working with the reader in the vein of our discussion re: finding new feeds to follow in your reader.
#ZegnatI subscribe to 703 feeds. I havev no idea how a dashboard interface like Tumblrs or like your experiment there zerojames[d] would scale to that
#LoqiTogether is a social reader that was initially conceived at the 2017 IndieWeb Summit in Portland by Jonathan LaCour and several others during the Putting it all together session https://indieweb.org/Together
#zerojames[d]I subscribe to 90 something feeds Zegnat. My server really isn't built for more than one person right now.
#zerojames[d](it's running IndieWeb Search too and that is chewing away at most of the RAM available)
#zerojames[d]In terms of design, I don't know what would work for other people. I am building for me at the moment. There is a page that lists all of the feeds you are following but my use case for that right now is mainly to unfollow feeds / double check if I have subscribed to something.
#[snarfed]zerojames: lots of historical analysis on reader UX! high level conclusion is that people have multiple usage patterns and desires that are very different and conflict, so it's hard/impossible to design a reader that works well for everyone
#[snarfed]haven't managed to find it yet, but iirc there was a good in depth history of Google Reader's development from one of the PMs a while back
#Loqi[marksuth] indigenous-android: An open social app with support for IndieWeb, Mastodon, Pleroma and Pixelfed.
#[schmarty]might also help to read through the Microsub spec, which focuses on how a client can interact with a backend, letting a client implementor focus on just the client features they want
#[KevinMarks]Right, the backend microsub server does the feed fetching and micropub server does posting so the reader can focus on ui
#[schmarty]yep, so you could stand up a backend like Aperture and build your client against it, until you run into something that the spec or that Aperture doesn't let you quite do like you want.