[dead]
Instant 1.0, a backend for AI-coded apps
131–133 of 133 posts
Re: Instant 1.0, a backend for AI-coded apps
#132Earlier quoted context omitted.
I would argue that saying the accounts are logically separated is a snarky comment. It’s akin to patting the reader on the head and saying “don’t you worry your pretty little head”. Logically separated says nothing. Distinct VMs are logically separated, containers are logically separated, as are storing data in different files which self-modifying PHP code which doesn’t check its inputs tries to keep distinct. It’s b…
My choice of the word "logically separated", was meant to specifically answer the question the reader asked: > If someone else's account is compromised, how do I know I won't be? If you have other questions, you can feel free to ask, and I'd be happy to answer in more detail.
It'd be useful to understnad the nature of that logical separation: for example is data from different tenants stored on disk using different encryption keys? what about in memory? or perhaps there's no encryption-level isolation but you're relying on an authorization layer to authorize to different pieces of data: if that's the case is that built on Postgres's row-level security, for example?
These are fundamental points to be open and transparent about to instill confidence
Re: Instant 1.0, a backend for AI-coded apps
#133Earlier quoted context omitted.
>multiplayer How does it compare to photon networking? I've been using photon and webrtc mostly. I haven't had any issues, but I'm always interested in finding better solutions!
Photon looks interesting! I am not too familiar with it, but from what I understand Photon and WebRTC are for communicating messages between clients. Those messages can be very fast, because they aren't blocked by writes to disk. Instant has two similar services, Presence & Streams. The primary sync engine is more for storing relational data.
So not for real time applications?
Still very interesting, thank you for the information!