gRegorLove, [jgmac1106], jjuran, snarfed, brett-soric, treora, [eddie], gRegorLove_, KartikPrabhu, cweiske and vilhalmer joined the channel; brett-soric left the channel
[jgmac1106]cweiske I don't know the answer to this can you have two omnibear exentsions installed? of without signing out maybe [grantcodes] is right, publish to your site and not display but then syndicate to a different site or just have a view for all your bookmarks
[grantcodes]The way I imagine that bookmark problem in a perfect indieweb world, would be you publish it to your own website via micropub, but have it unlisted or private so it doesn't show up on the frontend of your site, then there could be a bookmark display service / software that you could read your bookmarks via micropub queries and display them in a nice format, without you having to program it yourself.
[grantcodes]Sure, that's the other option if you store & display everything within your own site. But then with that your cms or you have to build a specialised layout for that type of content, or live with the default layout
leg, [kimberlyhirsh], gRegorLove_ and [jgmac1106] joined the channel
LoqiIt looks like we don't have a page for "taskwarrior" yet. Would you like to create it?_K (Or just say "taskwarrior is ____", a sentence describing the term)
LoqiIt looks like we don't have a page for "Taskwarrior" yet. Would you like to create it?_L (Or just say "Taskwarrior is ____", a sentence describing the term)
[jgmac1106][Khurt] coming here from IndieWeb... Yeah I didn't migrate... Moving content in and out of WP huge pita. Instead I just added a subdomain and then moved on with different solution
[eddie]!tell cweiske regarding multiple micropub endpoints, there are a couple things. Omnibear *could* add multiple endpoint support. You could also add multiple "destinations" into your endpoint, and one destination could forward it somewhere else. I'm not sure if Omnibear support destinations, but again, that could be requested.
[grantcodes]jackjamieson so there's not great user facing errors at the moment but if you dig into network requests there might be details on any errors
[grantcodes]Cool I'll have a look at some point, but it's definitely because it is expecting the photo property to be an array, but it might just be something I need to normalize on the together server
jackjamieson[grantcodes] So I think [author][url] should be a string instead of an array (which can be addressed in Yarns and/or Parse-This - I'll check where the error originates). But it would still be nice for the client to be able to render the rest of the feed. But this just helped me find a bug in Yarns, which means I can fix it :)
[grantcodes]Yeah that's the thing with graphql, it is strict with its types so I can't have the properties that are sometimes an array, sometimes a sting and try to normalise stuff like that
[grantcodes]So the only one I actually normalize is `quotation-of` because there is a bug in aperture that doesn't make it an array by default. I'm not sure if it's a good idea for me to do string -> array in together server or force the actual microsub servers to do it
jackjamiesonGWG, At least with the arxiv.org feed I've been testing with, doesn't look like it. The multiple authors are returned as a single h-card with null values
jackjamiesonGWG, I think (from the error I was seeing with [author][url] earlier) that Together returns null for cases like this where it's expecting one value and finds another (e.g. expecting one h-card and receives multiple).
sebsel[grantcodes]: I am not an expert on GraphQL, just starting myself too. But I've been digging into it a lot over the past weeks, so happy to look at the server :)
jackjamiesonIn which case, I'd suggest collapsing the multiple author h-cards into a string with all of the author names. Unfortunate to lose URLs etc, but seems better than omitting people
jackjamiesonGWG, I think it's worth thinking through. For my use-case of academic articles, I don't like the hierarchy implied by authors and contributors since many articles I read have multiple authors who contributed equally.
jackjamiesonOn the one hand, I'd really like to see all of the authors of an article in Microsub, or at least an indication if anyone has been omitted (e.g. "Shanske et. al" or a more colloquial version of that)
jackjamiesonFor that purpose I'd be willing to sacrifice things like author images and other h-card elements in order to get all the author names. At least as long as we can't count on Microsub clients to handle arrays of authors
jackjamiesonOnce I reply to a post, however, it's great that Post Kinds can handle multiple author h-cards. Certainly once I'm posting something on my own site, I'd like the citation to be as complete as possible
jackjamiesonAs for authors vs contributors, the feeds I'm looking at for academic articles use <dc:creator> for all of the authors, so I wouldn't see a need to use contributors to represent those, at least
[grantcodes]I think there's a bit of confusion because the microsub jf2 does not follow the spec exactly regarding arrays or strings with the idea that the client shouldn't have to check every property to see if it's an array of not
[grantcodes]GWG: together does not support multiple authors as that isn't in the microsub spec I don't think. But it absolutely does support refs and I'm pretty sure other readers do too