[jgmac1106]Could see social readers even getting smart with bot/automation "I see [tantek] blogs about IndieWeb alot would you like to add them to your channel" or "Wow @kartikPrabhu posts way more than many of your followers. Want to pick specific ideas to follow?"
LoqiA recommendation engine is software or a service that recommends things to people based on their behavior or people that have behaved like them in the past, like the features of sites that say things like people that bought this also bought that, or liked, or followed, etc https://indieweb.org/recommendation_engine
[jgmac1106]Will do...never thought about recommendations of gardening feeds of who you follow rather than recommending people you don't follow... Gotta shower kids first
[jgmac1106]Logic seems simple. Person has y tag in p-category x times and you have same p-name of an h-feed (not sure if h-feeds get named) as a channel wanna add their y feed to your channel?
[eddie]tantek jgmac1106 super interesting conversation about following! No time for it now, but I’d love to continue this discussion more and see if we can take those lessons and move that forward in a positive direction. I’d love to see how Indigenous for iOS might be able to help move that “following” people goal forward (although that might require buy in from Aperture too, haha!)
[eddie]My nickname cache is officially fully converted into h-cards that are stored in individual files. Each file name is the person’s primary url (minus special characters)
[manton][eddie] Are you extending Micropub for this, or automatically converting usernames on the backend...? Sorry, haven't been following all of the earlier discussions about this.
[eddie]No worries. For adding people, it’s using Micropub very standard, no extension really, but it’s sending an h-card rather than an h-entry so a Micropub endpoint would need to watch for that distinction and behave differently.
[manton]Cool. I am also working on auto-complete right now, so I could adopt your extension in M.b. Not sure about "contacts" but I'll try not to be too picky... 🙂
[manton]Are the results a list of h-cards, or just simple JSON? From M.b's perspective, "usernames" or "people", but I could see adopting an h-card-like naming for the query.
[eddie]sknebel: person tags or linking to the person as a url in the content. Then you could just replace any urls in the content with other urls when the need exists
sknebelalternative could be a key string (which could be the url, but something else if the server prefers something different) being returned too... although that might differ between text and html...
[kevinmarks]Well, part of the goal is to pick the right url or @ for syndication, so if you have multiple urls, an h-card is a good way to express that.
sknebelno-one argued against using h-cards for venues. just that looking up venues and looking up people should be possible as different things (if both are possible, a client can still offer a combined lookup over the two if that's wanted)
[eddie]in fact, it’s the very fact that both can be defined by cards which is the challenge discussed (the fact that ?q=cards is not good for a nickname cache query, because it is not clear if you want people or venues)
sknebel[eddie]: another thing maybe, general to the micropub extensions: how do you feel about having them as part of the endpoint vs on a different url (like e.g. the media endpoint)? curious if you have thoughts about that
[schmarty]sebsel++ the IndieAuth shortcut is great and embedding it works so well! The combined shortcut you posted does not also fetch the sub-workflows. I was given the option to choose which to run, so I need to grab those separately.
klezit's not clear from https://indieweb.org/h-feed: should the page containing the h-feed (e.g. my blog's home page) contain all my articles or, in case the entries are paginated, just the latest N entries?
[eddie]GWG that’s a good idea. I’m gonna be adding post list query support to indigenous for iOS so that’ll be great for Indigenous (in both platforms) and Wordpress and Drupal to all support it!
[eddie]sknebel I don’t know how I missed your last message! I think ?q=contacts is nice because if you have 5 or 10 different query URLs then a Micropub client would have to save and remember all those query URLs,
[eddie]and in reality the same general code is probably going to be hit with any Micropub queries because they all have to access the same storage for the most part unlike the media endpoint
[eddie]Hmmmm it’s interesting there are three different types of “support” that a Micropub could expose. I wonder if these should all be merged: post-types (what types of post a server supports), mp parameters (what kind of Micropub commands can be sent via Micropub), and Micropub queries (what queries a Micropub server will respond to)
sknebelinteresting, from my first few bits category lookup and address book are fairly distinct pieces of code that wouldn't integrate in the endpoint at all if they didn't have to
[eddie]I think it’s a heavier load for people to add new URLs than new parameters. I’m not opposed to new URLs in principle but I feel like there would need to be enough of a specific reason to separate
sknebelbut it's a design philosophy thing, and it seems MP goes more for one endpoint with params, so probably makes sense to stick to that even if I dislike it
[grantcodes]Muting and blocking are already in the microsub spec. I am a bit unsure of the use case vs just unfollowing them in a reader. The only use case I can think of is to block a certain author on a multi author feed
jgmac1106can I mark up a section on a homepage as an h-feed? I was thinking of putting my three most recent articles on the home page: https://jgmac1106homepage.glitch.me/ or would I still add the h-feed on body or html?
[tantek]the more I think about it, the more I'm convinced that in a person-centric design of all this stuff, our home page should be an h-card that represents us, then inside that whatever else structured information you choose to have on your home page, e.g. feeds
jgmac1106feed discovery and parsing, I tried to hide the h-card in each n-etry since I have a big ass h-card on the homepage and it is a single author site, but I think I need to go put it in