#[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
#[tantek][jgmac1106] feel free to add to Brainstorming there stuff like that!
#[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?
jmac, eli_oat, jgmac1106 and [eddie] joined the 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!)
#aaronpkI was also interested in that convo but don't have time/energy to catch up
#[eddie]I added the chat time stamps to /follow brainstorming so it’s easy to find on another day with more time and energy available 👍
jgmac1106, [manton] and [eddie] joined the channel
#[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)
#[eddie]Now I just need to be able to add and retrieve the h-cards through my Micropub endpoint
#[eddie]and then a Micropub client that supports it, of course, haha
#[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.
#[eddie]For fetching people for auto-complete that is an extension, using the Micropub query syntax
#[eddie]Right now I’m testing out ?q=contacts&search={nickname}
#[eddie]The returned objects are h-cards so I have the url to attach to the h-entry for the actual post
#[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... 🙂
#[eddie]so the actual micropub post itself isn’t being altered, it’s still just using the person’s url
#[eddie]any suggestions? That part hasn’t been implemented by anyone yet so it’s still totally flexible
#sknebelan interesting question is how to put e.g. links to people in the content
#sknebeldo you expect the client to produce html content then?
#[eddie]I think links to people in content and person tags should always be the url
#[eddie]But a smart website can use that url to modify the url based on syndication
#[eddie]so I’m storing all my contacts profiles under properties.url
#[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.
#sknebelok, so the client generates links, so the server doesn't strictly have to understand any @username syntax
#[eddie]manton that makes sense. We thought about ?q=cards but some people might store venues as cards
#[manton]Cool. I don't have a strong opinion about it yet, so don't let me hold you up.
#[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
[kevinmarks] joined the channel
#sknebela, so naked plaintext urls in the content?
#[eddie]it’s not a thing that people are really using currently
#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]When foursquare maps checkins to twitter does it @ the venue?
#[eddie]sknebel: true, I guess the url wouldn’t HAVE to be a requirement it could be like syndication with an id
#[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)
#sknebelI've been recently looking at the various rich text editor libraries out there, but they get complicated quickly :/
#[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)
#[eddie]I either use Quill (when sends html) or the iOS app Drafts where I type everything in Markdown
#sknebelyeah, maybe looking into adding easy publishing for one of the existing markdown editors isn't a bad idea
#sknebelnot the biggest fan of markdown, but also not sure what's better and still somewhat stable
[Khurt], [pfefferle] and [kim_landwehr] joined the channel
#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
#sknebeli.e. having a q=contacts vs a contacts url in q=config
[kevinmarks] joined the channel
#[kevinmarks]Were I still in sf having 21st amendment in my nickname cache would make sense.
[cleverdevil] and [eddie] joined the channel
#[eddie]Yes, it would. But you would want to CHECK IN there, not tag it like a person
#[eddie]That’s the key issue, it’s all about the right data for the UI
#[eddie]the UI for checking in to a venue is different than the UI for mentioning someone or tagging someone with you
[schmarty] joined the channel
#[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.
#Loqisebsel has 6 karma in this channel over the last year (25 in all channels)
#[schmarty]Ah, as soon as I installed the micropub endpoint shortcut, the post shortcut found it.
#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,
#GWGI'd still like something like q=mp to get a list of mp parameters the endpoint accepted.
#[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]They aren’t both in the same storage? Database or flat file?
jjuran joined the channel
#[eddie]I guess they don’t have to integrate but could they be on separate servers?
#sknebelon the other hand, it's not that much work to have the endpoint proxy a bunch of names
#sknebeland I guess having them external has some security implications too, since there's no obvious way of using lesser-privileged tokens
#[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
#sknebelI mean, the url can point to just a new parameter :D
#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]Has anyone implemented muting or blocking in a microsub client yet?
#tantekmuting would make sense in a microsub client and server
#tantekblocking is more webmention related which you'd need to implement on your own site, or rather, what CMSs have implemented blocking
#[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
#tantekinteresting. yes from a reader perspective I don't quite understand why you'd need to block rather than just (and definitely) unfollow.
#jackymaybe it's a legacy function from silo subscription approaches?
#tantekeven "a certain author on a multi author feed", mute is sufficient
#tantekI'd expect block to be something you might do via Micropub, that is, posting an addition to your blocklist
#tantekA reader might support block in the UI, but not through Microsub, just as readers support "liking", but do so through Micropub
#[grantcodes]Yeah that's kinda what I'm thinking too. But maybe it was related to some future functionality that I've not though of yet
#jacky!tell swentel I'm having some problems setting up Indigenous for Android for development; looking to use this app as my daily driver
#sknebel[grantcodes]: muting could also hide likes/reposts/... from other people
#sknebeland agreed, block is described in a way that it needs deep integration into the site, not just the reader backend
#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][jgmac1106] I have three h-feeds on my home page
#[tantek]primary/main, articles only, and manual h-event entries of events I'm going to or hosting
#GWGtantek, and it is a challenge for me to parse that
#jgmac1106yeah that’s what made me think of doing it, gonna just highlight a few pieces, will do some manual articles when I want full control
#[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
#[tantek]GWG, why? Thought we solved it in the past few days
#GWGtantek, I wish each feed had a fragment identifier
#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
#jgmac1106unmung didn’t list any author for my h-entries