Imagine being able to use our app with your @Mastodon account.
-
-
replied to pixelfed@mastodon.social last edited by
Are you working on this @trwnh? i assume since Pixelfed supports the Mastodon API already its mostly about turning off pixelfed exclusive features in the interface when logged into an account that doesnt support it
-
replied to liaizon@social.wake.st last edited by
@liaizon pretty much, yeah!
-
replied to trwnh@mastodon.social last edited by
@liaizon there’s a little more to it (the longterm plan is to use a Strategy pattern so that different API backends can be hooked up to the same UI functions) but the basis of it is indeed that the current pixelfed api is very similar to / based on the mastodon api, so it amounts to more or less feature flagging based on capabilities available
-
replied to trwnh@mastodon.social last edited by
@liaizon i should also give a heavy disclaimer that in this limited "compatibility mode", you would mostly only be able to post and possibly browse public timelines or discover. there's currently no way to filter a mastodon home timeline for only_media posts.
-
replied to pixelfed@mastodon.social last edited by
@pixelfed @Mastodon @trwnh having multiple fediverse logins for each app is def a pain since you can interact with them all as well, but how will this work? Do the mastodon instances need to support pixelfed or other platforms in order for this to work as a SSO like system? I'm really curious how this will be designed and thus work
-
replied to matkeith@techhub.social last edited by
@matkeith since the current pixelfed API is based on / very similar to the mastodon API, it would not be very difficult to log into a mastodon server with the pixelfed app, but there would be missing functionality. for example, mastodon doesn't currently offer a home timeline filtered for only_media, but you could still make posts, browse the public timelines, or possibly browse the discover feed. unfortunately we can't do much more right now, but the future might be different...