[chrisbergr]Some days ago I thought about photo albums. One of my ideas was to post every image individually as photo post and than create an album like a collection of posts. So the album is just some other type containing only references. But I'm not sure if this is actually gonna be my way.
[chrisbergr]Yes, I guess I got what you're going for. In my thoughts I had considered either referencing the photo directly or a tag or a category. Or of course a combination of everything. But I'm still not sure if I really want to do it this way.
aaronpkthat means the response aperture got when looking up the token at your token endpoint says it was issued to a different URL. i'm guessing because you logged in as http and your authorizaiton endpoint verifies it as http
[chrisbergr]Yeah, it almost looks like it's a little redundant because of tag archives. The idea was to be able to mix different tags and images that don't have the tag.
[fluffy]My IndieAuth endpoint used to coerce my `me` to http, and now I changed it to coerce to https. On aperture if I sign in it gives me 424 regardless of whether I use http or https.
aaronpkand monocle is doing the right thing, looking up your microsub endpoint (which happens to be for the old URL), and correctly normalizing your URL to the https URL
[fluffy]It’s not a huge deal for me right now, because I was only using aperture for test purposes and I don’t actually use IndieAuth for anything aside from signing into my own website right now 🙂
aaronpkthere definitely is, but that's also something that has implications for each system that's consuming the identity and they each may want to handle it slightly differently
[fluffy]The way I opted to handle this in Publ is I can map multiple identities to be equivalent by just adding them as a group. It actually doesn’t distinguish between group names and usernames.
[fluffy]oh and that’s also why Twitter identities are in the form of twitter.com/username#userid - if someone changes their username I’d rather just manually update the username after verifying they’re the same person (based on userid), and I wouldn’t want someone to change usernames and then have someone else grab it and absorb their access.
[fluffy]Thanks, I thought so. It’s how I squared the circle of how twitter suggests that OAuth identities be mapped based on the twitter user ID but Authl really wants to map every identity to a URL. 🙂
[fluffy]In an older design I was thinking I’d have a local account that people create and they could add multiple auth connections to it (like what Disqus does) but that seemed, like, hard. And also stateful. Two things I dislike. 🙂
[grantcodes][chrisbergr] see photo.postrchild.com for doing album posts exactly as you and aaronpk describe. There are a bunch of features your site needs to support for it to work though.
[chrisbergr]Aaron: what will Happen with multi photo posts? Would you just ignore them (because you manually choose the images) or do you plan to include them?
[grantcodes]Cool. Fwiw I also previously used tags to do it. I would have something like gallery-gallery-name and photos with gallery-gallery-name--photo to figure out where they belong
@aswath↩️ (8/13) Next let us consider user identity. In the SIP world, the identity is SIP URI. We are free to define in #WebRTC world. My advice is to use a web-based id mechanism - like OpenID, OAuth, IndieAuth or Web ID. (twitter.com/_/status/1189841395525324800)
[jgmac1106]notes 3, 8 , 9 missing rel="canonical" really trying to nail down my design for threaded notes followed by a collection of everything in the thread
[KevinMarks]Hm, there's dt-published and dt-updated. Previously we've assumed that dt-updated >= dt-published for revisions; setting published in the future was a cue for a deferred post. Could you use updated for the edit time and pubished for the publish time, or do you want to hide that by making them the same?
[Evan_Travers]so I’ve been reading a bit… I do a monthly post where I mention and comment on stuff that I read during the month. It doesn’t seem like a single `h-entry` should have all the `in-reply-to` like I have been doing… how do I politely mention folks and include my comment? Do I really need to be making separate posts for each one? (bad example here… http://evantravers.com/articles/2019/10/31/books-and-links-october/)
[snarfed][Evan_Travers] just linking to (ie "mentioning") them is probably fine. in-reply-to is only for if you're writing a direct reply. sounds like this is a broad round-up post instead
j4y_funabashi[m]I have always saved the location of photos that have lat lng in the exif data as a geo URL so need to go back and geocode all those to human readable locations
[fluffy][KevinMarks] the intent based link might be better but this is for the purpose of a user ID for auth purposes and needs to be short and reasonably humane. At some point I might add a better user ID system to Authl but I wanted to keep it simple.
[fluffy]At some point I will probably switch to a pure numeric ID when I find the right docs on that, but only after I get around to passing along more profile information to Publ.
[fluffy][Evan_Travers] FWIW I used to do the in-reply-to en-masse thing as well because I was similarly confused about its semantics. 🙂 I feel like there needs to be a quickstart guide that explains what the various microformats are intended for and maybe how it should affect other aspects of presentation, or at least analogies to what it’s intended to be.
[fluffy]like after I understood that in-reply-to is literally intended to be like Twitter replies, where it appears only as a single direct reply to the recipient and not on my default public feed, it made a lot more sense.
gRegorLoveUnless you're posting more than 3 articles in a short timeframe, the experience will be the same from a reader perspective, so subscribing to the homepage could work
[tantek][fluffy] the meta lesson there is: be lazy. More specifically, no markup without a *specific* intended purpose. If you can't define that specific purpose, then don't add the markup. No "just to in general do the right thing" because you're likely doing the wrong thing and just don't know it.
[tantek]This go against e.g. Google/SEO advice which is usually along the lines of "Schema all the things! We (Google) might find it handy in the future, so you (web dev) please do the work for us always even if we don't promise you anything!"
[tantek]Also SEO advice to "meta tag all the things! somebody somewhere might still use it and might still help your SEO on some search engine somewhere so publish all the metacrap!"