Replies: 3 comments 3 replies
-
|
One of my ideas for the future in Sunset, was adding Mastodon support due to components being pretty reusable, just need to add a different service for Mastodon. To me, having one client for both would be really amazing and useful. I can help on this project, if it's needed. |
Beta Was this translation helpful? Give feedback.
-
Can’t it be done the same way but here then, in the very mature Elk project? Simplistically put, all I want as a user is two separate app-interfaces (albeit with loads of shared components) that I can toggle between with an account switcher. |
Beta Was this translation helpful? Give feedback.
-
Not sure in Elk, since I didn't check enough the code, but probably. |
Beta Was this translation helpful? Give feedback.
-
|
If you’re able to start chipping away at this from the Elk-end then you’ll have the benefit of reviews & feedback from the Elk devs ✨ In which case it would instead be a matter of making Bluesky components for Elk, yes? |
Beta Was this translation helpful? Give feedback.
-
|
Just adding support. I'm seeing a lot more people either moving to BlueSky or opening an additional account there, but I miss Elk's UI. It would be great if I could use one app on my phone to keep up with both feeds; even better if they could somehow be combined! EDIT: Returning to say that you can use BlueSky today with Elk via the Sky Bridge server. Seems to work pretty well so far: Sky Bridge |
Beta Was this translation helpful? Give feedback.
-
|
Turns out the aforementioned Gobo is open source, so that provides a very useful reference for a cross-platform client/backend: https://github.com/iDPI-Umass/gobo-client I wonder how the approach of Gobo compares to the API calls conversion of SkyBridge by @videah 🤔 |
Beta Was this translation helpful? Give feedback.
-
This isn’t so much a request but rather just an open tracker of progress towards an open cross-platform client.
With the rise of Bluesky, many of us are now dividing our microblogging time evenly between both Mastodon and Bluesky, hopping between two separate client experiences, even though the content format is 95% the same.
The prospect of a cross-platform client has been lauded and pursued by open web advocates for a long time:
There’s at least one live example already, but it’s a closed client: https://openvibe.social/
One possible stepping stone would be a fork of Elk to make a Bluesky client:
https://bsky.app/profile/patak.dev/post/3l72elk6ip32r
Meanwhile, there are several Nuxt/Vue devs now working on standalone Bluesky clients, so even though there’s no fork (which could chart a path to a merger) yet, we can glean from these what a hybrid Masto/Bsky codebase in Elk might look like in the future:
Beta Was this translation helpful? Give feedback.
All reactions