I am the CTO for an early-stage FinTech startup, and am looking to connect with architect-level developers who have managed their own self-hosted instance of Lemmy to help stand up a standalone, non-federated instance on a cloud provider such as AWS or Azure. This would be paid work, can be part-time to fit your schedule, and will have the option to become full-time upon our next round of funding.
Please reply or DM me if you have any interest and would like more details. Thanks!
Jason
We’re looking for a Community Management platform that has the features and usability of Reddit. Unfortunately we are not experts in Community Management tools, so are doing analysis a bit blindly.
We initially liked Discourse, as it is a pretty common open-source platform for online forums. However after standing up a proof of concept we are now highly skeptical that it scales horizontally enough for our needs…the concept of “infinite user-created sub-reddits” are an absolute must-have, and has been the major sticking point on the tools we have reviewed and piloted so far (including a number of proprietary non-open source options). Discourse themselves told us to limit the number of Categories that should be used, so my sense is that this is an inherent architectural limitation that can’t be overcome without significant investment and branching of the code base. Comment voting is also a must-have, as well as a few other things. We are finding that these seem to be strengths of Lemmy and other Reddit-style platforms. And Lemmy seems to be the most popular…with the most community support. However if there is another platform that might better option, I’m open to it.
Meaning no offense to Lemmy devs, Lemmy still has some things to iron out until they can safely say “we’re at version 1.0” - it’s in beta, being battle tested as we speak, and it’s not afraid to push feature breaking changes. For example, the latest version, 0.18, fixed a very annoying bug that pushed new posts in real-time (websockets) when using the web interface, but disabled captcha. Jerboa, the main Android client, pushed an update that removed compatibility with Lemmy below 0.18. lemmy.world, who competes with lemmy.ml for the first two instances by number of users, refused to upgrade to 0.18 because it needs captcha to ward off bots - now you can’t use Jerboa with lemmy.world, and the web interface has the bug with new posts. So, all this rant should give you the idea that Lemmy is far from production ready, and it’s not a desirable choice, yet.
I’ve been the engineering manager for a Twitch clone that got sold for the tech part a couple of years ago - check your DM, sent a personal link, you can use the email there if you want me to help.
Aren’t those specs that would be better served by designing your own tool than introducing a complexe codebase that solves way more than the feature set you’re after and whose knowledgeable people will be difficult to find and hire?
I would say what you really need is to take the time of specifying what are the very concrete features you put in the idea of a community management platform, then see if there is not a simple path to implement them incrementally (protip : remove the “platform” in the label, it immediately looks less scary and it serves no purpose anyway, that’s a word you use to impress investors).
Of course, I say that from an external and naive viewpoint after reading your short description, sorry if I’m far off.
We have a detailed feature roadmap/prioritization laid out. I only mentioned the two most-critical items that I am seeing as real differentiators between the tools we have reviewed. And we have evaluated quite a few in addition to Lemmy: Discourse was (is?) the front-runner, but also proprietary, paid, non open-source ones like Khoros, Verint, and numerous others.
The challenge is that:
a) My business partners are keen on the Reddit style interface, but it must be a standalone instance and white-labeled.
b) Our business case requires near-infinite sub-reddits, which most of these tools can’t provide
c) Our unique user base and business model is the special sauce of our investor pitch, not the tech. In a pinch, any of these tools can work, but we need something that scales in the right way. Replatforming down the road is expensive and impactful to users, whereas spending a bit of time up front to do tool eval is much cheaper. You can’t “fail fast” when it comes to significant strategic decisions like this.
d) We don’t yet have the funding for a full-spectrum, full-time dev team. We can afford one or two tech people part-time right now, with the assumption that standing up a pilot can be done part-time if the person has done it before. Once we are funded though, we can share fixes/features that we build back into the Lemmy community. That level of control is why I like open source tools over proprietary (where you don’t have the ability to modify code or define the roadmap priorities).
Hence we don’t want to build our own tool from scratch if Lemmy can check enough of the feature boxes. But I want to pressure test that, as I am concerned greatly about its overall lack of maturity as a platform (as @FleaCatcher also mentions below).