@mattbd↩️ I've also set it up to enable use of IndieAuth. Current site does this too, but only with Twitter and Github. New one will also support mail, PGP and OpenID (twitter.com/_/status/1411473929517084678)
aaronpklol "If you would like to download the photos you’ve uploaded to the Foursquare apps, please use the reference links in the file called "photos" to download them to your device.
Loqicambridgeport90[: jacky left you a message on 2021-02-14 at 2:52am UTC: I agree to a degree. Things like Gemini are a bit akin to a 'reset' of the Web so that might be harder
cambridgeport90[Is that a new thing, though? I have never been able to download anything directly from Foursquare. Probably because I haven't touched the API?
GWGOkay, I have proof of concept code, I just need a way to test it. Right now it should support receiving and redeeming a code. Next I need to store it
[fluffy], capjamesg, samwilson, [Murray] and jamietanna joined the channel
GWGThe code is written. I want to test it a bit, and then deploy it. Also, right now it retrieves, but neither stores it nor uses it, so I need to add that
ZegnatAlso, for requesting a ticket, I have gone the way of a POST with action=ticket, inspired by action=revoke. Not sure if I like it, but could be a fairly acceptable extension on top of this. Maybe.
sknebelGWG: re "what to use for testing", don't you have an API to fetch and parse remote content in one of the plugins? giving that the option to use a token sounds like a useful building block, and its testing UI could be the first demo
Zegnatalso a problem with giving an error when the token is wrong: hard to check the token for static resources unless you put the checking on e.g. the server layer
ZegnatGWG and anyone else who has a ticket endpoint: https://vanderven.se/martijn/token/ should work, but as I do not have a ticket endpoint yet, it hasn’t been fully tested all the way through :P
ZegnatMy homepage does not have any special features yet for when you send a token along, but you can use IndieAuth token verification against that URL for now
ZegnatFor the verification, tokens will put your identity in `me` and your ticket endpoint in the `client_id`. I am not sure if it would be a good idea to change that or not. Or if I might want to extend it to add the `resource`.
ZegnatGive me a sec, I might know why my hosted instance is not working. Going to try fix that, so you can send unlimited tickets to yourself while I sleep ;)
Zegnathttps://vanderven.se/martijn/token/ should now work! You see it is succesful if you get redirected to my homepage after submitting. It was giving a white page before. Apparently I forgot to chown the SQLite db, so PHP treated it as readonly
ZegnatThe server is set to not publicly write out the PHP errors. And as PHP otherwise renders the site up to the first error … it send basically nothing.
ZegnatI was not thinking about that. I just set the resource to be the root domain. As I would expect the token to be allowed on any subpage I might host, and not just /martijn
jamietannaWould you think `iss` would be communicated by the POST to `/ticket`? I think naming wise that'd make more sense to be the IndieAuth server's base URL (that could then lead to https://github.com/indieweb/indieauth/issues/43 to auto-discover token_endpoint)
ZegnatBut after 5 hours of D&D, I can only telll you what my character would do with a server, and feel like I do not have the mindspace to come up with alternative solutions right now ;) So I am off to bed. Back in 7 hours or so!