Birbla

Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

Sign in
  • Hacker News
  • I think it would help demo an app or two that use this BaaS. Even better, if all those apps use/display the same data in different ways.
    by gurjeet
  • This sounds cool, but how do you protect your product from pirating?

    If your entire product is turned into a frontend app, and all of the infrastructure is stored on the users backend, doesn't this effectively mean they can just use your service for free?

    And if you try and gate it in the frontend, obviously that can just be stripped out with an LLM in 3 seconds.

    Am I missing something?

    Also curious about how payments would work in a system like this.

    by nullbio
  • I had a similar idea but with a much lower-brained approach of security through purely uuid uniqueness (to some degree, similar to the initial writer controlling access), and without any actual constructs built into it:

    https://github.com/matthewscholefield/blobse

    Which powers a few small apps like https://matthewscholefield.github.io/votosphere/

    Have you considered adding an llms.txt for linkedrecords? I'd love to be able to just tell my agent to build something and point it at your llms.txt and have it just build it out on its own reliably without having to clone the repo, go through the docs, etc.

    by _matthew_
  • Sounds cool, but you never got around to explaining how “users control where their data is stored “, which is odd because that’s the title of your post.

    So if I’m a user of an app built with your thing, how do I go about controlling where my data is stored? What’s the experience like for the end user to set this up and connect it to an app?

    by jasonkester
  • I've been working on a similar product. Started working on it 14 years ago and pivoted it to vibe coding. https://saasufy.com/

    I'm thinking to open source it but I want to see some traction before doing that since I don't want to open source then someone else takes my code and I get nothing out of it.

    by socketcluster
  • Anything that explores triple stores in production more is interesting to me, nice one!

    That said, the load test immediately stuck out to me as being too small scale. Triple stores can have performance issues, and the amount of operations in the load test isn't enough to exhaust a single node, let alone a multi-node setup. If you're looking to make a more convincing case I'd benchmark where one node falls over and get some sense of the ability to horizontally scale.

    by danpalmer
  • This is especially interesting for API products. The tricky part is not just where user data lives, but where logs, traces, backups, and billing metadata live too.
    by Avery29
  • Have you looked at the W3C's SOLID standard? I haven't looked deeply into what you're doing, but it sounds like a less interoperable version of what SOLID already does. https://solidproject.org/TR/protocol
    by thraxil

Explore Birbla archives