#mayoaaronpk: I was trying to figure out the point of including user IDs in the aperture microsub URLs (eg. /microsub/34). When a request comes in to /microsub/34, user id 34 is looked up in db, token is verified at the token endpoint, and me URLs are compared. My approach was to validate token, get the me URL, lookup user in db by their me URL (its hash, actually). Am I missing something security wise? Or just a case of different approach?
#mayoaaronpk: I suppose DoS on my /microsub would propagate requests at the token server, but so would attach on /microsub/34
treora joined the channel
#aaronpkmayo: for a single user system there's no need for user IDs in the Microsub URL. But for Aperture, a request comes in with a token to the Microsub endpoint, and Aperture doesn't know how to validate the token since it was created by someone's own token endpoint. So it looks up the token endpoint in the DB given the user ID in the Microsub url and validates the token there
#aaronpkIn your description, the step "validate the token and then get the 'me' URL" isn't possible because Aperture doesn't have any way to validate a token it hasn't seen before.
#mayoaaronpk: ah right, doh! I totally missed that.
#mayoaaronpk: I (mistakenly) assumed indieauth token endpoint was required because of the example in the docs. But of course that’s just a quick start to get people going.
#aaronpkIndieAuth.com? Yeah that's the QuickStart version
#aaronpkwhoa why does autocorrect capitalize QuickStart
[jgmac1106], benwerd, jgmac1106, spugachev, eli_oat, mblaney, [eddie], cweiske and [keithjgrant] joined the channel
#[keithjgrant]Oh man, Cloudinary is fantastic for image optimization. I can now use micropub to post images from my phone without feeling guilty about the uncompressed 12MP filesize
#[eddie]!tell aaronpk With Moves no longer existing, how much would you like to make Overland be a Moves replacement? There are a couple ideas that come to mind and I'm not sure if they belong in Overland or a separate app.
#[eddie]First is the timeline. It would be awesome to be able to see a timeline similar to moves of your day and the different types of transportation and how long you were sitting in one location. That would involve using the read API from a server with Compass' interface
#[eddie]The second would be defining the locations where you stopped along the way. That would get more involved as that would require venue searching and Micropub as opposed to just Compass' API Interface. So this second one definitely starts to tread on other app territory, but it seems like it would be great to have one app that could completely replace Moves' functionality. The places could do a Micropub query to get checkins for the day and when ad
#[eddie]where you were, it could then do Micropub create or updates
#aaronpkwith Moves no longer around, it is certainly tempting to expand the functionality
#Loqiaaronpk: [eddie] left you a message 9 minutes ago: With Moves no longer existing, how much would you like to make Overland be a Moves replacement? There are a couple ideas that come to mind and I'm not sure if they belong in Overland or a separate app.
#aaronpkthe big thing for me is i'm not an iOS developer by any stretch of the imagination, so all the UI work needed for that is way beyond something I can do myself
#aaronpkI'd also be inclined to completely rethink the model of how that works if we were to start trying to replace Moves' timeline view, like storing the data in icloud rather than on a separate server, so that it's more self-contained and relies less on other software
#aaronpkpeople keep asking me for other export options too, like writing to google sheets or saving to dropbox, since they don't have the expertise required to set up a server like Compass for it
#[eddie]That makes sense. I guess the question is how do you get the data out? Different export options?
#aaronpknot sure yet. i'm definitely open to discussion on this especially if you're volunteering to help out with the iOS side of things :)
#aaronpkbut we should probably move the discussion elsewhere since it's kind of beyond the scope of indieweb stuff
#[eddie]But, in answer to volunteering yes. 🙂 Behind Indigenous for interacting with my website, tracking my location and checkins is my second priority, so Overland and anything that can track where and what I'm doing is a big priority for my time and effort
#[eddie]For further conversation, should we just open up an issue on Overland and if the discussion spins into something else, that would allow a future project to reference that GH ticket?