#GWGaaronpk: While you are here, does Aperture store feeds per user?
#GWGI was thinking about your use case yesterday. If you added private feeds to your system, then wouldn't other people in Aperture get them if you use the same store?
#aaronpkit knows which users are subscribed to which feed, so i would have to treat feeds fetched with authentication as a completely separate feed per user
capjamesg, hendursaga and [mapkyca] joined the channel
#jeremycherfasCan anyone explain what would make a file readable on one machine (iMac) and not on another (MBA)? (Asking here because it is so much friendlier) Background: I save log files to Dropbox for later analysis. On my laptop, when I open the file in BBEDIT, the whole thing is upside down red question marks. On the iMac, perfectly legible.
#jeremycherfasI suppose it must be something about BBEDIT's settings, but I'm not sure where to look. Thanks.
[snarfed] joined the channel
#[snarfed]jeremycherfas: probably character encoding. run `file [filename]` and see which encoding it’s in. if it’s not ascii or utf-*, you’re going to have a bad time
#rockoragerre: ticketauth and the client_id issue....if the ticket/access_token is given to a site and not a client, then a client would need to request existing access_tokens on behalf of the site to be able to e.g. retrieve a private feed? Am I understanding that right?
#jeremycherfasI just checked on the MBA, and there the file is `data`. And that I find exceedingly odd, as it ought to be the same file in Dropbox.
#aaronpkrockorager: good question! that could be one way to handle it, but right now it's not modeled that way
#GWGrockorager: Expectation of internal integration until we model it
KartikPrabhu, [fluffy], jjuran and [jacky] joined the channel
#[jacky]okay so I'm like at the point with https://git.jacky.wtf/indieweb/sele where if someone ran it themselves, they'd be able to get a IndieAuth server for like multiple sites (or just one, that's how I use it), see which apps they've authorized and see when tokens will expire. I'm thinking more now about how to add something for TicketAuth (after I clean up some tests) and how to potentially add logic to help build something for audience
#[jacky]I saw/view "audience lists" as a only-visible-to-you list of h-cards or URLs (guess it could be a 'stubbed h-card') of people who can view a particular post but I was kinda wondering if such a list could be extrapolated from one's Microsub server instead (by pulling the authors of the feeds in a channel)
#[jacky]Does anyone have something similar to this or thoughts around this approach? Would like to pool some thoughts on it. I feel like [fluffy], you have something similar in Authl?
#[fluffy]Authl only handles login, the actual access control is a function of Publ. And in Publ there’s a config file which declares access control lists and then individual entries can reference those lists.
#[fluffy]There’s no h-card involvement for any of that.
#sknebel[jacky]: not sure how that'd link to a microsub server. I guess you could take feeds from there as suggestions? but generally, "I follow this feed" does not mean any meaningful trust level for me
#[jacky]Yeah, mainly for suggestions tbh, I was wondering about a good place to 'prime' such feeds from
#[jacky]Okay, I might be playing with some green-field stuff here then lol
#[fluffy]Having an integration point between microsub and publish ACLs would be interesting. I don’t think it’d fit Publ’s overall model especially since Publ itself tries to be pretty IndieWeb-agnostic (ticket auth is technically the only indieweb-specific thing it has in the code directly but it’d make a lot of sense for a more indieweb-specific social stack.
[jgmac1106], [aciccarello], doosboox and [tantek] joined the channel
#[jacky]Yeah! I think it might reinforce a "you should be able to align a channel to people you want to share with" but not completely force it