faithcure

@faithcure@lemmy.world

• ⁨Comment⁩ on ⁨[deleted]⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:

  i updated the description. This project has nothing to do with vibe coding. If someone here knows code, come and i show you the infrastructure :)

  But yes, i use AI translation for answering comments and fixing my spelling mistakes. My english is not good. I just want to answer you fast and correct. I guess this feels not genuine to you. I understand but this is not our intention…

  If your criticism is not about the site, i think just skip it instead of wasting your time.

  Please make your harsh criticism about the project…

• ⁨Comment⁩ on ⁨[deleted]⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:

  Not spam. I’m just using translation for best communication. Thank you.

• ⁨Comment⁩ on ⁨[deleted]⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:

  This is exactly how an AI would respond, complete with fancy-quotes, em-dashes, a three-bullet-point list, and empty justifications throughout. Any AI would probably be able to provide more technical detail if we wanted to get into that, but I think a real human would be able to respond with a recipe for peach cobbler, and you’re a real human, right? What is your favorite recipe like?

  My English isn’t great. I use translation help so I don’t talk nonsense or make spelling mistakes. It seems like instead of critiquing a new product, you’re hung up on the help I use to get back to you in the best and fastest way possible? I think you should use it too… Is there a need to be a Luddite? Or is this just empty criticism? If the site interests you, please comment on its functionality if possible. Not on the fact that I use translation purely so I can communicate with you better!

• ⁨Comment⁩ on ⁨[deleted]⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:

  I cannot signup. The email address cannot be checked (whatever that means).

  Thanks for the report — that’s on us, looking into it right now. Could you let me know which email provider you were using (gmail, proton, etc.)? That’d help narrow it down.

• ⁨Comment⁩ on ⁨[deleted]⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:

  hank you — adding this to the to-do list. Genuinely appreciate the second pair of eyes, this is exactly the kind of feedback that’s useful. Not antagonistic at all :)

• ⁨Comment⁩ on ⁨[deleted]⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:

  Thanks — and you’ve actually got it right, that’s exactly what we are.

  The thing is, existing sites are just databases. Info that exists on one site is missing on another. It’s scattered and incomplete. And honestly, their interfaces aren’t user-friendly at all. On the database side, that’s the gap we’re filling — bringing it together and making it actually usable.

  Worth adding: a lot of those sites run on user contributions and then sell the data you entered as a paid API. IGDB and RAWG don’t fully do this, to be fair. But either way — what does the user actually get back? A rating. That’s it.

  We give the user their own stats, analytics, and a genuine answer to “what should I play next” based on how they actually rate games. Plus a level system on top of that.

  So no, we’re not trying to replace IGDB. IGDB is one of the layers underneath us. We’re solving what happens after the raw data.

• ⁨Comment⁩ on ⁨[deleted]⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:

  Great questions, let me break down how the pipeline works:

  Our first layer is deterministic — we pull core data from free APIs. Then multiple layers of cross-querying happen on the backend, and the results get merged before anything hits the site. After that, an AI agent runs research across the web (always with source attribution) and fills in the highest-confidence data.

  On top of that, there’s a report feature so users can flag incorrect info. Honestly, I’d argue our data quality is already higher than most sites in this space because of this layered approach.

  That said, the system is still in testing — nothing here is final, and it’ll settle into place and improve over time.

  On the “5 sources” point: which piece of info came from where is actually indicated as subtext on the page. But I hear you that it could be surfaced more clearly.

  On sourcing and licensing — we’re strict about this. We only use free APIs. For example, we don’t pull any data from MobyGames because their terms are restrictive; we only do read-only matching to check whether existing data lines up.

  As for licensing our own page content (the Terraria wiki example) — that’s a really good catch, and it’s not something we’ve formalized yet. Adding it to the to-do list. Genuinely valuable feedback, thank you.

• ⁨Comment⁩ on ⁨[deleted]⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:

  I’m thinking these communities need to add a rule no sharing Vibecoded projects …

  Just to clarify — this project isn’t vibe-coded. We’re a team of 4 friends building this together. Nothing is “nulled” or copy-pasted from a template.

  • Frontend: built with React
  • Backend: built with C#
  • UI/UX: designed from scratch in Figma

  The site does use AI as a feature (for things like the recommendation engine and metadata enrichment), but that’s a deliberate part of the product, not how the codebase itself was written. There’s a real engineering process behind it — architecture decisions, data pipelines, a proper team.

  Happy to go into more technical detail if you’re curious!

• ⁨Comment⁩ on ⁨[deleted]⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:

  Thank you so much for the valuable feedback! I’m taking all of this in and starting to work on fixes right now.

  Also, regarding the Steam connection — you need to grant permission from Steam’s side when linking. I’ve added an explanation about this in the user settings section. So far, 10 members have successfully linked their Steam accounts, and the same goes for PlayStation.

  So the Steam error isn’t on our end, it requires you to grant permission through Steam’s authorization step. If you go to user settings, there’s a directive/instructions there explaining it.

  Thanks again!