zlacker

I'd not be surprised if that would lead to job with REMOTE (US EXCEPT WA) soon.

>>zegerj+(OP)
It would have to be "REMOTE (US EXCEPT CA, CO, CT, MD, NV, NY, RI, WA)" unless there is something different about the WA transparency law that I don't know.

>>zegerj+(OP)
I'm in CO so pay a lot of attention to this as it's a law to post salaries here. I really haven't seen THAT many CO excluded jobs. I definitely have seen them. More often than not I just see no mention of the statute/salary at all.

We used to have a site to track them but he shut it down https://mentallyanimated.com/coloradoexcluded.html There were big names, like Spotify, IIRC Adobe, on it.

https://www.forbes.com/sites/isabelcontreras/2021/11/01/what...

Archive: https://web.archive.org/web/20210717051519/https://www.color...

>>swozey+45
this looks like something i could host for the community, but wayback is having issues letting me look at more than just the page you linked. If you remember anything about the architecture or how the data was portrayed/displayed, email me at my webzone (i just updated my profile).

It looks like it was manually vetted, which i could not do for the community. i could see it being gamified or otherwise attacked, and i'm loathe to say it but LLM+RAG and a way for users to flag records might suffice to start.

In fact, what might be easier is a fediverse bot or similar that is both input from users to a job posting URL, as well as posting automatically vetted "excluded in <territory>" that's backed by an rss feed of a simple LIFO index page. That way you get the best of all three worlds for the UI and i don't have to set up email.