[chrisaldrich]GWG I'll see your amen and raise you one. It's one thing to have 8+ year old issues, 4 year old issues with potential PRs that need testing, but this is just sadly beyond the pale.
doubleloopIs state a required parameter for indieauth? indieauth on WP gives a parameter absent error if state is not present, but gimme-a-token does not provide it.
sknebel!tell jeremycherfas seems like my theory was right and webmention.heroku.app uses a parser that doesn't follow the current rules for implied name properties - the post doesn't have one, so it tries to guess one badly :/
Loqijeremycherfas: sknebel left you a message 22 minutes ago: seems like my theory was right and webmention.heroku.app uses a parser that doesn't follow the current rules for implied name properties - the post doesn't have one, so it tries to guess one badly :/
ZegnatBest would be to find some people who work with Node for their indieweb tools and see if they are willing to have another look at the mf2 parser? It is a little murky
jeremycherfas!tell [Rose] when you were developing your site in Grav, were you using a child of Antimatter, or something else? I feel I ought to switch to Quark, as it is now the default and Anitmatter is not being developed much, but I don't really like it, so there would be a lot of customisation.
Zegnatvoxpelli, while true, I think the real problem is also users. E.g. I do not think I have ever used the node parser, so I do not really notice the problems
voxpellijeremycherfas: you can always add an issue there and ping him, or add a PR for it and mention that it shouldnβt be merged until [tonz] approve it
voxpellisknebel: would be great if the formerly mentioned issue could be linked to an issue there, then Iβll find it and maybe fix it when I arrive at fixing the issue in my repo
voxpellijeremycherfas: the other project provides real world HTML for endpoints to use when testing their endpoints and is included as a βreal worldβ test in my webmention endpoint but also used by others
voxpelliWhatβs more important than fixing a bug here and now is to ensure that the same bug doesnβt occur again and tests are great at that β great in avoiding a bug whack-a-mole
GWGI want to split the code that allows an endpoint to authenticate to an IndieAuth endpoint into it's own library as it is bundled with both Micropub and Microsub for redundancy.
ZegnatIf a plugin does nothing other then replacing the usual username & password login flow for the WP admin with a web sign-in flow, that is when I would call it web sign-in. Nothing else, as it may just make it murky what tech is meant or what feature is expected to be part of web sign-in.
aaronpkIf it were me, I would make a new plugin for the web sign in part, which replaces the Wordpress login form with web sign in, and then keep the IndieAuth plugin doing just the IndieAuth server parts of issuing tokens and managing the consent screen. I would drop the external IndieAuth endpoint thing entirely, as I really don't think it provides much value and is mostly just confusing
aaronpkYou'd need the IndieAuth server plugin on both, but again how you log in to your site is independent of whether that site is an IndieAuth server
ZegnatI agree with aaronpk ... You'd still run all the same plugins, micropub/IndieAuth, just also happen to run a webs sign-in plugin to replace your login screen with something that accepts IndieAuth
aaronpkRemember when I suggested writing all these use cases down on the wiki and even started doing that but then the page got collapsed and everything was removed? This is why I was trying to do that
ZegnatIf you have micropub you probably want the IndieAuth endpoint yourself, always. Because you can trust tokens that you yourself have issued the most.
aaronpkif anything, using an external token endpoint or auth endpoint should be a totally separate plugin that you'd install instead of the IndieAuth plugin.