mblaneyaaronpk I have a use-case that the resource identifier you mentioned earlier might help with, though it might not be what the change was intended for.
mblaneyI currently use unicyclic.com as my microsub server, and mblaney.xyz is my microsub client. the server identifies my requests via the bearer token.
mblaneynothing is failing, it's just that there's nothing to identify me with my microsub server. I guess this is why you provide unique urls with aperture?
mblaney...and actually I use the fact that it's a Micropub client to let me know when there's new reader content so I don't have to poll. I added a new Micropub action called notify so I only fetch new reader items when I get a notification. yes it got complicated real quick :-)
aaronpkit's funny cause last week I kept hearing all these complicated enterprisey use cases around OAuth and then as I was thinking them through I would realize that there's an exact analogy in the indieweb world too since we tend to split up components so much
mblaneyah ok. I get that servers shouldn't hold tokens but I don't have a clear definition of a server anymore.... it's just two computers doing different things.
aaronpk"client" is the computer making a request on behalf of the user. "resource server" is the computer that has resources the client is trying to access.
mblaneyyeah it's just that the two computers I'm using play both those roles at different times. I guess I'm wondering if sharing a token to perform those roles is a good idea or not.
[KevinMarks], uniquerockrz, KartikPrabhu, [tantek], chrisaldrich, gxt, wagle, mblaney, cweiske and krychu joined the channel
GWG[snarfed]: Saw your message, will try not to leave you behind... but will not put the same level of features into the non hosted version unless I can just copy the same code
GWGOther than an Authorization header, is there any alternative method of passing tokens? I know that IndieAuth allows it being passed as a parameter, but not everyone supports that. Wondering current school of thought
aaronpkOAuth only ever specified three: Authorization header, post body parameter, query string parameter. the query string parameter was always discouraged
[Rose]If we need the body and the headers then we can’t do a auth flow in Shortcuts on iOS. Though if we can ensure there’s another way to get a token it can be considered unnecessary
[schmarty]my understanding is that it is also one of the more flexible generators. jekyll and hugo are very opinionated about how content should be organized, what data can be used to generate pages, etc.
[schmarty]been meaning to try it out for that reason, though tbh after going through the pain of learning how to work with jekyll and then hugo i am wary of starting over again, despite it sounding so good. 😅
beko[m]jamietanna: about Hugo this one here https://jlelse.blog/ uses hugo iirc and he is coding a lot IndieWeb related stuff for it. Mayhap this helps.
[fluffy]I really need to get around to building a proper demo site for it. That’s on the list along with a dozen other important projects I haven’t gotten to. The struggle is real.
LoqiEleventy is a JavaScript based static site generator that allows the user to select their own preferred template engine and theme, which in practice can and does enable use of microformats2 https://indieweb.org/Eleventy
jamietanna[m]Beko thanks! I'm using Hugo on www.jvt.me and have really enjoyed it, especially for its speed against something like Jekyll for a smallish site at the time. I dread to think what my site builds would take now, with thousands of more pages of content in my site now