I’d love it if the 3rd party developers burned by Reddit started developing for Lemmy/kbin/Mastodon. First, there is lots of opportunity to make Lemmy and the rest of the Fediverse more user friendly without sacrificing the benefits of federation. Second, it’s an open source ecosystem. The more developers in the space, the better for everyone.
It might require a significant amount of work to transition from the Apollo API to Lemmy. yesterday, I peeked at the Lemmy and Reddit APIs out of curiosity and they aren’t exactly similarity. So, there are two potential paths forward for the developer: either build a translation layer to preserve their existing code base, or undertake a complete re-engineering of there code base.
This issue is apparently severe enough that Fedi.Tips, decided to withdraw there support for Lemmy. The developers have seemingly not addressed these concerns since they were raised.
So ya, Lemmy isn’t exactly a squeaky clean project currently
I’m working on a Lemmy app now, and I will say the documentation is pretty rough - I’ve had to do a lot of reading through source code. The data types are well defined, but there’s no explanation - you kind of just get the name of the route, and if you’re lucky a short sentence about it.
I’ve worked with much worse, but it’s an entirely different experience than working with the Reddit API
I’d love it if the 3rd party developers burned by Reddit started developing for Lemmy/kbin/Mastodon. First, there is lots of opportunity to make Lemmy and the rest of the Fediverse more user friendly without sacrificing the benefits of federation. Second, it’s an open source ecosystem. The more developers in the space, the better for everyone.
It might require a significant amount of work to transition from the Apollo API to Lemmy. yesterday, I peeked at the Lemmy and Reddit APIs out of curiosity and they aren’t exactly similarity. So, there are two potential paths forward for the developer: either build a translation layer to preserve their existing code base, or undertake a complete re-engineering of there code base.
There’s also the challenge of identifying functional Lemmy instances, which brings us to a complex issue that was raised on Rust reddit thread about possible using Lemmy https://www.reddit.com/r/rust/comments/14921t7/alternative_rust_discussion_venues/. Where some concerning information regarding the lemmy dev was brought up.
This Mastodon post (https://mstdn.social/@feditips/106835057054633379) seems to imply some socio-political implications. Although I can’t fully understand the context, it appears to be related to concerns about human rights oppression associated with Lemmy’s developers (https://www.reddit.com/r/RedditAlternatives/comments/143o5xd/reconsidering_my_support_for_lemmy/
This issue is apparently severe enough that Fedi.Tips, decided to withdraw there support for Lemmy. The developers have seemingly not addressed these concerns since they were raised.
So ya, Lemmy isn’t exactly a squeaky clean project currently
So lets just not register on the instances they run?
I’m working on a Lemmy app now, and I will say the documentation is pretty rough - I’ve had to do a lot of reading through source code. The data types are well defined, but there’s no explanation - you kind of just get the name of the route, and if you’re lucky a short sentence about it.
I’ve worked with much worse, but it’s an entirely different experience than working with the Reddit API