#dev 2025-11-01

2025-11-01 UTC
[aciccarello]1, [Murray], sp1ff`, vidak, lanodan, jak2k, jjuran_, grufwub, bret, hidjy[d], [social], [jeremycherfas], [Joschi_Kuphal], geoffo, rgbivvv, [Al_Abut], DanQ, manuel1, nand, leandro, Florian, joel2, jonnybarnes, barnaby, ttybitnik, Paula1 and Florian1 joined the channel
# 15:03 
carrvo No one familiar with the protected resource metadata spec for a quick review to ensure I understood it?
# 15:03 
aaronpk 👋
# 15:24 
carrvo I could use a quick review of https://github.com/carrvo/mindie-client/pull/41
[capjamesg] joined the channel
# 15:26 
aaronpk what is mindie?
# 15:26 
Loqi MIndie is a minimal, self-hosted IndieAuth solution for the home, developed and used by carrvo https://indieweb.org/MIndie
# 15:27 
aaronpk so this implements indieauth as a client and passes the user information to the backend service running behind apache?
# 15:29 
aaronpk what's your goal with adding support for protected resource metadata/
# 15:29 
aaronpk ?
barnaby and proofreed joined the channel
# 17:24 
carrvo IndieAuth for Authn, OAuth for Authz. Or at least compatible. Important that both are handled by Apache and not the service behind it (SVN+WebDAV).
# 17:33 
carrvo For the goal: first I find it nice to identify things appropriately (this serves 2 roles so 2 identifications), second I like that I can build up to users Authz for a specific resource tree and have to re-approve for another app to prevent bleeding, and third I want to extend it with scope descriptions.
barnaby, ttybitnik, CrimeWave, to2ds, [Jo]1, rrix, [morganm], bterry2, DanQ and Xe_ joined the channel