This might sound wild or controversial, but has anyone thought about using the bluesky app and adapt it to work with the mastodon API? By this way making it easier for more people?
Did you mean SkyBridge, but in reverse?
It seems like it, hahaha. What I wanted to convey was a fork of https://github.com/bluesky-social/social-app built to work with Mastodon API.
I think often people find it easier to write their own code than to make changes to other people’s projects, so it’s not necessarily very easy to change the Bluesky app to work with the Mastodon API rather than the Bluesky one.
That said, I don’t think it’s a dumb idea. Bluesky has a lot of money to pump into UX development, so making sure Mastodon users could benefit from this wouldn’t be a bad thing. Personally I am perfectly happy with the alternatives already out there (Phanpy is better than anything else that has ever existed), but it’s all about choice. :)
I think often people find it easier to write their own code than to make changes to other people’s projects
A rarely mentioned weakness of open source, and it can only be getting worse given the narcissism of younger generations.
I regularly see cases of multiple projects with exactly the same goals. All that duplication of effort just to serve the vanity of the respective project leaders. The wasted potential for good software has to be huge.
I feel like this is part of what makes @[email protected] one of the most important fediverse projects at the moment - it aims to keep everyone from having to do the same, overly complicated job of activitypub integration over and over and over again.
It’s frustration that nobody wants to dig into old code, but I get frustrated having to re-work my own code from a year ago. So I guess I sympathize.
Interesting insight, thx.
Never used BlueSky but what’s wrong with the multitude of apps already written for Mastodon? Also, do the features nap one to one with Mastodon or will some features work and not others?
I find using the Mastodon apps easy. What I don’t find easy is getting the same level of engagement and an app won’t solve that. But it’s a totally different beast so I am ok with that.
-
People are more familiar with the UI
-
They are microblogging services, so yeah, I don’t see any feature that cannot be translated to the UI.
-
I find it easy, but for other’s that’s not the case.
-
The level of engagement can be hard to get on a decentralized service in a network that suffers from fragmentation. Besides, the way the developers of Mastodon (and other services) built their software was by in fact not federating things like likes to other instances, making it so that the level of interaction yoi see form a remote server is not actually the correct one.
Re: 4
No app for Bluesky will help with this, because the purpose for the client (“app”) is to use the API (a Bluesky one right now). And Mastodon’s API provides exactly these not-federating like numbers - the problem you actually try to solve.
The number of likes and boosts has to be fetched directly from an original instance. Moshidon for Android does already like this and Fedilab for Android allows to fetch an entire conversation.
Bluesky clients have no concept for this they needed it.
-
This is kinda what Surf will be, no? Still in closed beta but it aims to be a browser for the entire federated net, including Threads and Bluesky and all.
openvibe
I will check it out, but for what I heard is to post in multiple sites with the same app, right?
I feel like billionaire media isnt okay so no, the thought would never ever cross my mind.
But i can see how different folks need different strokes so go ahead.
All I ask is that folks keep in mind that this is a centralized social media platform that has a size advantage over the fedisverse (i assume) and therefore poses a threat of barren wasteland attack.
I think you misunderstood what I’m referring to. The bluesky app is open source and it has the same UI as twitter, basically. I’m talking about forking the project to make it compatible with Mastodon.
I perfectly well understood what you meant. The issue is that bluesky is barely different from xitter and threads. If those two brought an open source app I wouldnt touch that either. Mind you, meta releases open source stuff, as does microsoft. Just because they’re evil doesnt mean they wouldnt do it.
We have an ongoing debate in the fediverse if we should be open to (e.g.) federating with those services if it comes to it (in case of threads, it did). I‘m a signee of the fedipact but I hold all billionaire media in that regard for the future.
Working on intercompatibility is the same thing and everyone has the right to do whatever they like. I have the right to let you know that there are risks involved. One example out of the top of my head: bluesky could decide to block your app or display ads for the „real app“ since it is a proprietary backend that you have to call from the app.
