samsk

MLS Listing powered AI Search and Agent is live as mlsync.ai [1].

[1] https://mlsync.ai

I’m building an AI search assistant and autonomous AI agent for real estate, powered by MLS property data via my tool mlsync.io [1].

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

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.

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

No grep ? We are lost !

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

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

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

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

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

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

Email: ja.hn4[at]mailgw.com

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 ;)

For this I use LiteLLM proxy - you can create virtual keys with daily/weekly/... budget, its pretty flexible and has a nice UI.

See https://docs.litellm.ai/docs/proxy/users

Thats why I always develop on a per customer mini VM via VSCode ssh remoting or similar, and projects are usually runned via docker-compose or devcontainers.

IANAL, but the new license applies only to new PHP versions, changing it backwards would require approvals. If you don't contribute under new license, you should be not affected.

Beautifull, everything regarding PHP licensing and its history in one place, no marketing or AI generated bs in sight - love it ;)

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

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

Email: ja.hn4[at]mailgw.com

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

Perl Backend developer, SQL expert, Monitoring Architect, Technical lead

Language: English, German

Areas of expertise:

* Fulltext/geospatial search systems with SOLR/ElasticSearch. Building REST API on top of SOLR data - see https://github.com/samsk/lua-resty-solr

* RESO MLS synchronization / data import / IDX API - see https://mlsync.io

* Cloud/On-premise asset inventory (CI creation) for ITSM systems (with https://github.com/cloudinventario/cloudinventario)

* ETL pipelines (data collection, transformation, enrichment, BI reporting...), DWH Building

* SQL data model and query optimization

* API Gateways (Kong, Apisix, OpenResty...)

* Automation with Ansible / Terraform

* Skills: Perl, C, Bash, Python, Lua, Go, Java, NodeJS, PHP...

Github: https://github.com/samsk/

Email: ja.hn4[at]mailgw.com

I'm building MLSync.io [1], an ETL platform that helps real estate companies easily access and use MLS (Multiple Listing Service) property data without the technical headaches. I've originally developed this for internal use in an IDX startup, but the complexity of RESO synchronization led me to spin it off into its own dedicated tool.

[1] https://MLSync.io

The problem with CSS selectors (at least in scrapers) is also that they change relatively often, compared to (html) document structure, thats why XPath last longer. But you are right, CSS selectors compared to 20 years old XPath are realy worse.

Nice ! I've a scrapper using XPath/XSLT extensively and 90% of the XPath selectors work like for years without a change. With CSS selectors I've had more problems...

Reading these scripts is where my efforts to speak Japanese died on Duolingo. I wanted to be able to talk and they force me to learn all the characters. But, nice writeup, I knew the writing systems, but never realized that each has its own function.

Btw. Does anybody knows some alternative to learn to speak/understand Japanese ?

Yes, there is still a problem there. Some 'clever' services are blocking probably all VOIP numbers, not only zadarma.

Try zadarma.com I've multiple numbers there

Only problematic thing might be relatively frequent storage changes (like they like to deprecate primary storage driver), otherwise its IMHO easy to setup. I'm running it on several projects, because it doesn't needs beefy machine like Elastic or even ClickHouse.

Well saying 'arse' is very dangerous, not like some lies that i.e. politician tell repeatedly to milions.

Makes totaly sense...to someone...maybe...

Oh, can't wait for the article on Medium on how they rewrote that old COBOL thing in React Native and NodeJS in 3 days and saved bilions (by not delivering them).

Whats important, its only 'love' a.k.a. no major API change twice a year, as in many of those 'modern' languages.

And its no past for me !-)

I've a shell alias for this, requiring valid hostname for reboot, halt etc...