I’ve been working solo on this project for the past year
The commit history is three weeks old, so that becomes difficult to believe.
Hi @curbstickle_lw, thank you for stepping in and for taking the time to actually look at the project instead of just auto-deleting it based on reports!
I did read the meta thread, and I completely understand the community’s frustration with closed-source, paid advertisements.
To be completely transparent about the two points you raised:
- Yes, I just registered. I’ve been working solo on this project for the past year and was looking for a community that appreciates self-hosted alternatives to corporate SaaS platforms. Since the project is fully open-source (AGPL), completely free, and built specifically for self-hosting, I genuinely believed it aligned with the rules and the core ethos of Lemmy.
- Federation Hub (share-by-default): The reason it connects by default is that it powers the core community features (like importing visual strategy templates from other users), rather than acting as stealth telemetry. But I want to emphasize that it is strictly privacy-by-design (no hostnames or IPs are ever stored), and anyone who wants a completely isolated, air-gapped instance can instantly disable it by setting IS_CENTRAL_HUB=true in their .env file.
I really appreciate you giving the project a fair look and making a distinction between actual open-source projects and corporate spam. I’ll gladly stick around to answer any technical questions!
non_burglar@lemmy.world 2 weeks ago
The key word there is “community”. You’re not part of this community, you just came here to shill your AI slop.
DepthSight@lemmy.world 3 weeks ago
Calling an enterprise-grade platform featuring a 40+ node visual graph editor, dual backtesting engines, and full multi-tenant isolation “AI slop” just because an LLM accelerated the syntax development is pure ideological gatekeeping. This “slop” objectively outperforms every proprietary $100/mo trading SaaS and basic CLI script in existence right now. If you have an actual architectural critique regarding the FastAPI/Celery setup, the PgBouncer integration, or the Redis ACL security model, I’m all ears. Otherwise, you’re just yelling at a cloud.
Evolve. Or Don’t Look Up.
Ooh, I made you mad enough to use your own words instead of telling the chatbot to write your reply! I’ll do it again: Slop.
DepthSight@lemmy.world 3 weeks ago
Actually, I’m still using an LLM to write this, since English isn’t my native language (as I mentioned earlier).
It’s a pity that, unlike an LLM, you clearly didn’t grasp the reference at the end of my last message. You should probably paste it into one of them—they’ll gladly explain it to you.
HelloRoot@lemy.lol 2 weeks ago
ew why are you so toxic and arrogant?
I wanted to upvote you, cause I am not psrt of the anti-ai mob, but then I read you last sentence and the rest of this thread and holy fuck are you unlikable and unbearable.
Criiiiiiingeee
Self righteous self promoting new account that uses AI to write posts for them and is proud about it.
Criiiiiiingeee
rtxn@lemmy.world 2 weeks ago
You asked for feedback. Don’t get pissy when it’s not what you were hoping for. It’s pretty clear that your project is not welcome in this community.
moonpiedumplings@programming.dev 2 weeks ago
Except you use JWT’s for auth, which is idiotic and a security nightmare. No enterprise that cares about security would ever accept this.
More info: gist.github.com/…/0d1f3d3b4745d778f78b230cf606145…
There are other problems, some of which I can see… and some of which I can’t. The problem is that I am not a comprehensive expert, I can only spot a few things here and there. Even if I was an expert, why would I audit your software for free lmao? Pay me for that shit.
What I do know, is that vibecoded apps are bad at security. Many, many vibecoded apps have been hit by horrific security bugs like remote code execution, xss, or authentication bypasses. That shit is simply unacceptable and should be extremely rare in modern apps. The fact that I’m not skilled enough to find them reliably makes me even more cautious and concerned around apps like yours.
It’s not just about the app architecture, but also about you. When a known community figure creates an app, I have confidence that they will have a good security posture and architecture. With vibecoding… not so much.
Nice bait, but the problem is this: Just because you get people to
audit“critique” your software, doesn’t fix the root cause of those problems — you. Just because you manage to re-vibecode the app to not use JWT’s or to fix any other number of issues someone would point out, doesn’t actually mean more issues exist that that person missed. Like if someone specialized in python, then they might miss database issues, and so on. The second problem is that inevitably, you will expand this software, adding more features… and vulnerabilities. That is to say, even if you manage to fix the architecture and security now, you have not demonstrated the requisite skill needed in order to keep it fixed.