Yesterday I improved the authorization endpoint. It will work now with more clients. I found that still quite a few clients need the "me" parameter, which I think should not be needed, because there is a "state" parameter.
Next I will need to implement the channels that I added to the authentication screen. This will allow to connect auth tokens with channels. The channels will be special "feeds" so not all items will end up on the homepage.
Authentication works.
Screenshot tool
This is a simple screenshot tool that I wrote to send screenshots to this weblog. It works by connecting gnome-screenshot, pinta and shpub.
#!/bin/bash
bkdest=$HOME/Desktop/Screenshots/
target=${bkdest}/$(date +%Y_%m_%d_%H_%M_%S).png
mkdir -p $bkdest
/usr/bin/gnome-screenshot -f $target -a
/usr/bin/pinta "$target"
MEDIA=`shpub -d -s $SHPUB_SERVER upload $target | tail -n 1`
shpub -d -s $SHPUB_SERVER note -c screenshots -f $MEDIA --json ScreenshotTest note from shpub
test
The problem with the authorization_endpoint is already fixed. It seems I should handle HEAD requests and not return 500 http errors. I can now read my feeds.
I have been buildling a microsub server. It's not perfect, but it works. It works with Monocle. The code is open source and can be found on Github here: https://github.com/pstuifzand/microsub-server/
But sadly it seems I can't use my own authorization endpoint. It can't be found. It did work when I used indieauth.com for authorization.
But sadly it seems I can't use my own authorization endpoint. It can't be found. It did work when I used indieauth.com for authorization.
Let's if the reply works through syndication.
