Earlier attempts were mostly about money and ideology. Now its a question of security, thanks to one 'clever' 'businessman'.
So thanks to his _great_ efforts, it might actually work out this time.
Interesting tool, will definitely try - just curious, is there a tool (hexora checker) that ensures that hexora itself and its dependencies are not compromised ?
And of course if there is one, I'll need another one for the hexora checker....
We work with MLS provider(s) that requires us to keep plaintext password for our users and provide it on request in case of `breach in the security of MLS Listing Information or a violation of MLS Rules`.
The user is accessing only copy of their data in _our_ systems, the user has no contact with MLS itself directly or indirectly.
I’m still working on MLSync.io, an ETL platform designed to remove the technical friction of synchronizing MLS data using RESO protocol and provide simple access to the MLS data via SQL and REST API.
And as everyone now, I'm experimenting with LLMs to bring some new AI-related features to the service.
On another project, we've now beta testing (in ordination) Asus GX10 processing power running on-device LLMs for _local_ processing of patient medical data for 'differential diagnoses, implant plans and risk profiles in real time while the patient is in still in the chair'.