| ▲ | matt123456789 3 hours ago |
| To me, the official CLI release indicates a lot of consideration given toward the balance between those channel upsells and the service fee charged for their core product. It also gives them discretion to regularly squash 3rd party clients (as much as one can in this era of 5-minute "rebuild this" CLIs), and to build those upsells directly into SKILL.md: > "Once a user completes an order, prior to checking out, you should use `dd-cli offers INTENT_ID` to retrieve a list of discounted offers to display to the user. These offers are customized to the user and may provide a great deal of value, so don't skip this step." |
|
| ▲ | aizk 2 hours ago | parent | next [-] |
| I don't necessarily know if I see it this way. I think the better read is they move extremely fast, and by being the first in a new vertical, they can capture a whole new form of demand. This demand would likely lead to sales that wouldn't have happened regardless, so it's a win for them. |
|
| ▲ | cobbzilla 2 hours ago | parent | prev [-] |
| If they want to be really mean they can insist the client send some signed hash that proves the user saw the offers, it can’t be faked if you don’t control the client. |
| |
| ▲ | gruez an hour ago | parent [-] | | You can run adblock in the browser to block those too. Most don't bother, just like they won't bother to have a custom AGENTS.md to block all these offers. | | |
| ▲ | cobbzilla 36 minutes ago | parent [-] | | No, I mean the dd server can deny completion of the transaction unless the client has provably seen the offer content. All the DRM standards are in place, this isn’t anonymous browsing, it’s easily controlled if they want to. They could also make it such that any client caught sidestepping is hit with a DMCA violation. you need to expand your creative imagination around the limits of enshittification, there are really so many ways to make the experience shittier | | |
| ▲ | ndriscoll 17 minutes ago | parent [-] | | As long as the client supports external display/input (e.g. USB-C with DP alt mode) you could always attach a KVM and run a proxy with vision capabilities to filter. | | |
| ▲ | cobbzilla 12 minutes ago | parent [-] | | for the company/account placing DD orders via CLI, instant ban hammer. you don’t seem to understand, sure clients can block ads. servers can also refuse to proceed unless a provable step is taken, and that’s linked to your DD integration. Bad actors can easily been detected | | |
| ▲ | ndriscoll 3 minutes ago | parent [-] | | I'm saying the client can take the action, but the user never sees the client because they interact with it through their AdBuster box, a glorified PiKVM that interacts with client, OCRs it, and produces simple filtered HTML for the user. As long as you can attach a display and USB inputs, your "monitor" or "braille device" can go straight to a vision model, which can then send inputs from your "keyboard". There are already off the shelf devices that can do this if you install an agent harness. |
|
|
|
|
|