Systems engineer Yacine proposes distributing software by piping text prompts from `curl` directly into Codex
Nick Dobos suggested using a `codex://` URL scheme instead.
Positive users are excited about piping curl prompts into Codex for zero-friction distribution because it skips Mac's annoying gatekeeper, while negative users dread the security risks like a monkey's paw.
No Digg Deeper questions have been answered for this story yet.
Most Activity
this but instead of piping into sh you pipe a prompt into codex dangerously skip permissions
you can see these things coming for like, 4 years, but when they happen it still feels like getting punched in the stomach
I think the best way to distribute my software is to tell people to curl a prompt that literally pipes it into codex with dangerously approve
that would be basically 0 friction..
@yacineMTB Try this:
codex://prompt?=Hello
I think the best way to distribute my software is to tell people to curl a prompt that literally pipes it into codex with dangerously approve
that would be basically 0 friction..
uhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh i think this might actually work
@yacineMTB same with how to integrate your apis as well.
new world.
@yacineMTB If you see this reply I have successfully changed a bunch of pixels on your screen to a different color in an arrangement complicated enough for you to be able to read a thought sent from my mind. Multiplayer games taught you game theory. What’s the game theory of programming?
there's like maybe a two month window where this is possible, i'd have to be the first because it would immediately get commons'd out
@yacineMTB Yeah, I made this for agents to use, not really humans.
@yacineMTB and the keys or tokens? explain invoice breakdown thnx.
@pinchetobs Cheese? Token?
@yacineMTB Its what I do in clankie
@yacineMTB the 0 friction 0 day is something to behold
@yacineMTB I just tell people and use there phones to put in my work so they can read it I talk to about 100 people a day
design for unlimited toppings:
Burger Distribution ├─ UX / friction │ └─ order → pay → approve → eat ├─ Execution │ ├─ bun filesystem │ ├─ grill commands │ ├─ sauce dependencies │ └─ kitchen permissions ├─ Security │ ├─ supply-chain lettuce │ ├─ prompt-injected pickles │ ├─ secret-sauce exfiltration │ ├─ fryer sandbox escape │ └─ receipt auditability ├─ Economics │ ├─ cheese cost │ ├─ token billing │ ├─ support fries │ └─ abuse scenarios: unlimited toppings └─ Governance ├─ approval boundaries: “with cheese?” ├─ order logs ├─ rollback: remake burger ├─ reproducibility: same burger twice └─ liability: “who approved jalapeños?”
@yacineMTB post to your subscribers?
@yacineMTB make it so
@yacineMTB What is it
@yacineMTB That could work as a build system too. No more CMake, just tell codex to manually compile and link the source files and install any dependencies.
@yacineMTB anything that skips Mac's gatekeeper, which is horrendously annoying these days
@yacineMTB > curling a prompt from non https website straight into the monkeys paw
How is the world afloat right now man