Just my 2 cents…
Thanks for the heads up. Sorry that I opened it and didn’t search for the issues first. From the title lookup on the issue list, it wasn’t clear to me that it is the same issue.
However, any glue why the (Originally published… ) link in the opening comment here, points to the Issue-Tracker on Github and not to my issue-note on my blog? The log on Brid.gy has both URLs in the list. Should i open a new issue for this on Brid.gy?
Is there an issue with publishing posts to Mastodon (mastodon.social) instances? Since today (havent published to bridgy-fed for about 3 weeks) I get an HTTP 401 - not autorized error.
I 2020-10-28 21:25:22.029036 Verification failed for [renem.net](http://renem.net/)@[renem.net](http://renem.net/) https://fed.brid.gy/renem.net
E 2020-10-28 21:25:22.029431 https://mastodon.social/inbox
Traceback (most recent call last):
File "/srv/oauth_dropins/webutil/[util.py](http://util.py/)", line 1480, in call
resp.raise_for_status()
File "/env/lib/python3.7/site-packages/requests/[models.py](http://models.py/)", line 941, in raise_for_status
raise HTTPError(http_error_msg, response=self)
[requests.exceptions.HTTPError](http://requests.exceptions.httperror/): 401 Client Error: Unauthorized for url: https://mastodon.social/inbox
E 2020-10-28 21:25:22.107845 No targets or followers. Ignoring.
See the log here: https://fed.brid.gy/log?key=https%3A%2F%2Frenem.net%2Fphotos%2F2020-10-28-baguette-bateau%2F+https%3A%2F%2Fmastodon.social%2Finbox&start_time=1603920322
Looking at the latest logs, it seems I’m not alone with this issue? Any tips/hints?
sorry for the bad news. @rretsiem if you know the social.tchncs.de admin(s), feel free to ask them for any related server logs from around this time, 2020-03-24 10:46:23 UTC, they might be able to help!
Got an answer to my question for the logs from the admin (@Milan) of the instance. But sadly he can’t help here. So I think it will be as mysterios as it was.
current status: debugging pixelfed's oauth. i've gotten through to requesting the access token, but pixelfed 400s that request with The authorization grant type is not supported by the authorization server. (i'm passing `grant_type=authorization_code`.) not sure which other grant type i'd use. i'll ask them.
👍
Since posting to fed.brid.gy works fine, I tried to repost a status on Mastodon today from my site. I used Telegraph to send the request and got a “202” back, so everything seems fine.
However the repost/reblog does not appear on my account @[email protected] at Toots&Replies. Also the repost wasn’t counted on the original status. Here is the log from fed.brid.gy for this repost-of action.
I don’t know if this is the right channel to ask, or better via IRC, so I try it here first, but feel free to close this here and point me to the right “support channel”. Thanks!
To publish images to Pixelfed (Fediverse), support for those instances would be a great addition. Since the Pixelfed API is based on Mastodon V1 API, I hope that therefore not a complete new development is necessary. At least it sounds like a “low hanging fruit” 😉
A possible use case would be to publish photos posts to Pixelfed instances and also enabling Webmentions to retrieve reactions to those posts.
If this is already possible with the “Mastodon” function, a hint on how to use it would be helpful.