postiz-app
postiz-app copied to clipboard
Allow logging-in to Mastodon servers other than mastodon.social
🔖 Feature description
Mastodon.social is just one of many Mastodon instances but seems to be the only one that you can cross-post to from postiz. I authenticated X but then tried to authenticate my fosstodon.org account:
That takes you here:
🎤 Why is this feature needed ?
To allow Mastodon users to use the postiz
✌️ How do you aim to achieve this?
By opening this issue, hopefully!
🔄️ Additional Information
I tried authenticating via fosstodon but to no effect yet. It's possible with Buffer.
👀 Have you spent some time to check if this feature request has been raised before?
- [X] I checked and didn't find similar issue
Are you willing to submit PR?
None
@Robinlovelace Can you go to libraries/nestjs-libraries/src/integrations/integration.manager.ts
And enable MastodonCustomProvider and try it?
@Robinlovelace Can you go to
libraries/nestjs-libraries/src/integrations/integration.manager.tsAnd enableMastodonCustomProviderand try it?
@nevo-david no because I'm using it via the https://platform.postiz.com services, as shown in the link shown above.
If you enable it on that service I can try again and let you know if works.
I'm using docker image so also cannot modify the integration.manager.ts
Hey. Are there any timeframe for this feature request?
@cbirkenbeul, it's almost finished, basically.
Nudge on this. By the way @nevo-david, I read your article about ditching the corporate world and going all in on open source. Great shout, and will be great if your app can better support open source social media, such as the Mastodon server Fosstodon.
Happy to test this if there's a version ready for testing!
Nudge @nevo-david.
@Robinlovelace Can you go to
libraries/nestjs-libraries/src/integrations/integration.manager.tsAnd enableMastodonCustomProviderand try it?
Removing the comments here and enabling MastodonCustomProvider has no effect on allowing us to set a custom Mastodon instance through the UI.
https://github.com/gitroomhq/postiz-app/blob/b4a8a1332df5f6823c25573968c7e2bfdcf9c26e/libraries/nestjs-libraries/src/integrations/integration.manager.ts#L51
Just to be clear the activity on this issue was prompted by my original comment that I since deleted. I feel bad because there is no hurry whatsoever to do anything here from my perspective at least since I solved the problem by giving up and writing my own script to repost things from mastodon to bluesky since then.
Removing the comments here and enabling MastodonCustomProvider has no effect on allowing us to set a custom Mastodon instance through the UI.
For posterity I just got a bunch of type incompatibility errors when I tried going that route.
@cbirkenbeul, it's almost finished, basically.
Great! I self host my own Mastodon instance and so need to be able to use it with that - looking forward to testing it out once it's finished! 🙏
This is now the most upvoted issue: https://github.com/gitroomhq/postiz-app/issues?q=is%3Aissue%20state%3Aopen%20sort%3Areactions-%2B1-desc
Please could we have an update @nevo-david / team or at least guidance on next steps for fixing this seemingly small but high-impact change to unblock other Mastodon servers.
Am I missing something? It seems to only be hard coded in a few places.
$ fgrep -r mastodon.social .
./libraries/nestjs-libraries/src/integrations/social/mastodon.provider.ts: 'https://mastodon.social',
./libraries/nestjs-libraries/src/integrations/social/mastodon.provider.ts: 'https://mastodon.social',
./libraries/nestjs-libraries/src/integrations/social/mastodon.provider.ts: 'https://mastodon.social',
./libraries/nestjs-libraries/src/integrations/social/mastodon.custom.provider.ts: 'https://mastodon.social',
I'm going to try and make a quick pr tomorrow that migrates those to env variables like client id, or is there existing ui for providing your own client id and secret?
if this is the desired solution, https://github.com/gitroomhq/postiz-app/pull/708
if this is the desired solution, #708
Upvote for this, as a temporary workaround solution before the MastodonCustomProvider get fully tested and released
is custom mastodon integration being worked on? I was poking at it tonight. Its in a bit of a rough state. Most of the parameters are in the wrong order and such. And it looks like it makes a new client id and secret every request, and possibly will even leak secrets.
I can maybe do some cleanup, though I'd like my pr merged so i can see if i even like postiz before i commit to anything
also do integrations have db access? Would be nice to store client id and secret per instance url, and not constantly request new ones.
@cbirkenbeul, it's almost finished, basically.
So it's been more than 5 months (Dec 14, 2024) since this was "almost finished, basically."
And the feature still hasn't been released. Can we PLEASE get an update on this so we can use servers other than the default?
Has been released 👍 @dnburgess @cbirkenbeul
At least for the self hosted version it works
Deploying the latest version now! Excitedly hoping this works for me :)
edit: helps if I change the version from :latest to :v1.44.1-amd64. trying again lol
At least for the self hosted version it works
Deploying the latest version now! Excitedly hoping this works for me :)
I haven't been able to get it working :( https://github.com/gitroomhq/postiz-app/issues/780