bridgy
bridgy copied to clipboard
snarfed
Consider support for Pixelfed (blocked on Pixelfed bugs)
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.
(Originally published at: https://renem.net/notes/github/2020-03-16-1/)
yes! great idea. thanks for filing!
(i assume you've looked at https://fed.brid.gy/ ? it's another good approach, but not for the faint of heart.)
when i first implemented mastodon, i tried pixelfed, and it wasn't quite compatible enough, so i detect and block it explicitly: https://github.com/snarfed/oauth-dropins/commit/8b8405aa0c5ae14d11eade3f16b6c5535e51fd52 . if it's more compatible now, it might be as easy as removing that block and trying again!
any interest in trying? i'm happy to help you get the dev environment set up!
Thanks for the info. I try to get GAE up and running on my local MacBook and see what I can achieve. But I'm honest, I'm just at the beginning for now 😀 For example, I still don't know why your answer to my Issue isn't sent back to my webmention endpoint. Brid.gy says "no webmention targets". (Not a topic of the current issue, so maybe in IRC/Slack).
huh. thanks for reporting, and sorry for the trouble! that may indeed be a bug. i'll file a new issue for it.
note to myself: my pixelfed account, mostly just for testing this, is https://piconic.co/snarfed .
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.
filed an issue with more details: https://github.com/pixelfed/pixelfed/issues/2102
Looks like much of the work is done in https://github.com/snarfed/bridgy/commit/bd900cf6436e221eb36e6179b163de13720fcd07 - is this considered ready for production yet?
you're right! the bridgy work is largely done, in that commit. deploying to production is currently blocked on a handful of pixelfed bugs that affect both backfeed and publish. fortunately @dansup et al have usually been quick to respond to these, so i'm optimistic those will get fixed pretty soon.
Not a problem and thanks for the status update. Really do appreciate all that you do!
[dansup] After some thought, I've decided to add Webmention support to Pixelfed, users will be able to opt out) ... [snarfed] dansup++ webmention support in pixelfed! exciting! i assume you just mean directly, ie receiving and sending with links to/from posts? not bridgy-style backfeed for posts that are syndicated from people's web sites?
Sure! I haven't followed its evolution. How do you think we should revise this?
Hey @dansup any chance you could look at the bugs ^ blocking Bridgy Pixelfed support? I'd love to get this moving again!
...or if you're close to shipping built in webmention support, that'd be awesome, and I could close this altogether!
Is there a chance to revisit the topic? Would love it ... https://indieweb.social/@kiko/111041958999794580
…any updates on this?🙏🏾
I just found out this wasn’t working myself.
In reply tohttps://github.com/snarfed/bridgy/issues/927#issuecomment-911780729.
(Originally published at: https://starrwulfe.xyz/b/jf8)
Good question! Some of the bugs ^ are still open, but maybe they've improved? Feel free to try and let us know how it goes!
@snarfed
Bridgy still comes back with errors as if Pixelfed isn’t an ActivityPub server. I’m not sure what behavior is being expected, but Pixelfed (at least the flagship server at pixelfed.social) isn’t doing what Bridgy expects…
Looked into this a bit. Sounds like Pixelfed fixed some of these bugs! Not all though, evidently. Looks like we're still stuck on OAuth scope parity with Mastodon:
- Does Pixelfed not support fine-grained scopes? When I try to use eg
scope=read:accountswith https://piconic.co/oauth/authorize, it redirects back with HTTP 400invalid_scope The requested scope is invalid, unknown, or malformed - https://github.com/pixelfed/pixelfed/issues/2106 is evidently still outstanding, we need that to work too