samsk

It’s designed to go beyond static filters to actively research, compare listings, analyze photos, watch listings, setup notifications etc... - basically an "OpenClaw for real estate."

[1]: https://mlsync.io

Comment · 6 months ago

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.

Comment · 7 months ago

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....

Comment · 7 months ago

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.

Comment · 9 months ago

...and costs pennies compared to putting anything up there, so it can even enjoy those cosmic goodies.

Comment · 9 months ago

No grep ? We are lost !

Comment · 10 months ago

Who would tell. Economy runs on 'trust' - not on 'by tomorrow we apply this random tax rate to this pinguin island and everone else'.

Comment · 10 months ago

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'.

[1] https://MLSync.io

Comment · 1 year ago

My tl;dr is: Don't do huge updates using WHERE on fields _not_ in index, otherwise it will take days to finish and you get meaningless numbers in benchmarks...

Comment · 1 year ago

Can happen, but on the BAD website will the password manager not offer saved password, so user has higher chance of noticing smth. is wrong. Of course if he uses pass manager with complex passwords...

Comment · 1 year ago

SEEKING WORK | Remote | Worldwide (EU-based, GMT+1) | Part-Time

PERL Expert | DevOps Engineer | SQL/SOLR Specialist

Language: English, German

Areas of expertise:

    • Legacy PERL Code Maintenance
    • PERL Performance Optimization
    • PERL Security & Compliance
    • Migration Services
        → PERL to Python Migration
        → Database Version Upgrades
        → Legacy System Modernization

Other notables experiences:

    • Prometheus based monitoring systems
    • Cloud / On-premise inventory systems and synchronization to CMDB/ITSM
    • MLS data synchronization via RESO/RETS - https://mlsync.io

WEB: https://perlexpert.de/en/

Email: ja.hn4[at]mailgw.com

Comment · 1 year ago

Its a server-side proxy, so instead of ie. OpenAI url you point your AI tool to url of LiteLLM proxy, and use its virtual keys with budget limits or LLM models restrictions etc... - the features LLM providers will not give you, because it might save you money ;)