Muse's utility has significantly dropped with the blockages.
To become truly useful again they will need to use residential proxies, but I can't see them use those due to the risks and reputational damage.
So of course I clicked yes and it dutifully convinced the site that it was not a bot.
dvt•37m ago
Not sure if I should release it, but I'm sure more people are catching onto the power of agentic browsing.
ares623•31m ago
d0vs•28m ago
frabcus•27m ago
dvt•15m ago
bayindirh•26m ago
Also it’s great(!) to see that we’re going from “but ethics” to “I got mine, who cares”.
Humans are interesting creatures.
pcthrowaway•11m ago
afro88•2m ago
It's not that "we" are going from one thing to another. It's that these are two different people, with different ethical boundaries.
bel8•21m ago
dvt•19m ago
rjtc•13m ago
the only solution is to drive your regular browser with all your sessions/cookies via an extension
dvt•10m ago
This is exactly what I'm doing, but mocking/randomizing all the sessions/cookies/params (like resolution, OS, WebGL , etc.) in a separate Chromium binary. It's popular these days, but imo using your normal browser for agenting stuff is a very bad idea. These models do dumb stuff all the time.
carsoon•6m ago
For testing proxies should be used to avoid IP ban issues but given enough time modern agents can figure out how to bypass most of the modern scraping/automation prevention mechanisms.
I have built and used a lot of different automations and web scraping implementations for my business and it's never got permanently stuck yet, some take a bit longer, some shorter, but all within a reasonable time with little external help they have succeeded in their tasks.
kurisufag•9m ago
pprotas•6m ago
onion2k•6m ago
Is that necessary? You could start Chromium with an open debug port and use Chrome Devtools Protocol to send commands.