Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test with ThreadReader #121

Open
voxpelli opened this issue Aug 6, 2020 · 2 comments
Open

Test with ThreadReader #121

voxpelli opened this issue Aug 6, 2020 · 2 comments

Comments

@voxpelli
Copy link
Owner

voxpelli commented Aug 6, 2020

See: https://boffosocko.com/2020/05/28/threadreaderapp-micropub-to-blog/

@gdecaso
Copy link

gdecaso commented Sep 18, 2020

Did you have any luck testing it with ThreadReader? I'm succeeding at registering my blog (running webpage-micropub-to-github in Heroku) but I'm getting a Error: Error: Request failed with status code 500 message from ThreadReaderApp when I hit their "Publish X tweets to blog" button.

On the Heroku logs all I get is:

2020-09-18T21:08:37.781000+00:00 app[web.1]: { body: { type: [ 'h-entry' ], properties: { content: [Array] } } } Received a request
2020-09-18T21:08:37.781442+00:00 app[web.1]: { body: { properties: { content: [Array] }, type: [ 'h-entry' ] } } Processed a request
2020-09-18T21:08:38.094809+00:00 heroku[router]: at=info method=POST path="/micropub/main" host=gdecaso-micropub-to-github.herokuapp.com request_id=29c44a49-0790-48e9-a8ac-29a00a2f8d7f fwd="18.214.212.204" dyno=web.1 connect=1ms service=323ms status=403 bytes=248 protocol=https

So it seems like the 500 error is on the ThreadReaderApp side, as the webpage-micropub-to-github is giving a 403... which I don't know why. Any clues?

@gdecaso
Copy link

gdecaso commented Sep 19, 2020

So, answering my own question... I kept digging and it seems that the problem is on ThreadReaderApp's side, as they are cropping the token from indieauth.com to 255 bytes, and the token is sometimes larger than 600 bytes.

I contacted ThreadReaderApp and they are going to fix this on their side. Will report back

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants