Also, kids understand perfectly well that different parents have different rules.

I don’t think the government or Apple should be responsible for protecting you from mopey teenagers by blocking free internet access for everyone just so that it “is fair”. Are you even hearing yourself?

Everything has become so incredibly expensive it just isn't fun to buy anything anymore.

My iPhone 11's FaceID broke a few weeks ago and despite that I think I will just stick with it with today's phone prices.

I've built it earlier and also did a Show HN, now I am going through some of the steps that get recommended to me such as creating Product Hunt launches, etc. But I am struggling a bit with the concept of PH. What is the audience? People into new apps? It all feels a bit desperate to be honest and this app is just a hobby side project, I am not.

So if anyone knows of a good way to get some attention to my useful fun tool, please let me know.

> Add this file to your AI assistant's system prompt or context to help it avoid common AI writing patterns.

So if I put this into my LLM's conversation it is like I am instructing it to put this into its AI assistant's system prompt, so the AI assistant's AI assistant.

The alternative is to say:

"Here is a list of common AI tropes for you to avoid"

All tropes are described for me to understand what that AIs do wrong:

> Overuse of "quietly" and similar adverbs to convey subtle importance or understated power.

But this in fact instructs the assistant to start overusing the word 'quietly' rather than stop overusing it.

This is then counteracted a bit with the 'avoid the following...' but this means the file is full of contradictions.

Instead you'd need to say:

"Don't overuse 'quietly', use ... instead"

So while this is a great idea and list, I feel the execution is muddled by the explanation of what it is. I'd separate the presentation to us the user of assistants and the intended consumer, the actual assistants.

I've had claude rewrite it and put it in this gist:

https://gist.github.com/abuisman/05c766310cae4725914cd414639...

Decoy is 10 MB vs Mockoon's 329 MB and looks and feels differently because it is a native vs cross platform app.

Mockoon seems to have lots of great features such as online mocks and proxies for which you can pay their monthly fee or you could have a lighter weight app that does one thing well natively for a one time fee purchase.

I also notice that Mockoon calls home even when I don't have an account, probably for some sort of tracking. There is no tracking in Decoy.

So overal I think it is about lightness of the applications and UX.

Decoy is a native Mac app (SwiftUI + Network.framework) that lets you create mock HTTP endpoints. You pick a method, define a response (JSON, HTML, XML, a file, a redirect), and it just works. Incoming requests show up in real time with full headers and body, which is handy for debugging webhooks. It supports parameterized paths like /users/:id and you can group endpoints into projects with subdomain support. Requests are persisted to SQLite immediately and CORS is handled automatically.

To be clear about what it isn't: it doesn't send requests (not a Postman replacement), it's not a proxy, and it's Mac only.

It's $24.99 on the Mac App Store, one-time purchase. I'm an indie developer — no team, just me building tools I want to use myself.

Happy to answer questions about Decoy!

Comments URL: https://news.ycombinator.com/item?id=47170320

Points: 7

# Comments: 4

Is there some way I can get updates about pgdog and especially when the replication you mentioned is there?

Do you have any write up on how to do this?

Opus 4.6 wrote me a working macos application.

Codex wrote me a html + css mockup of a macos application that didn't even look like a macos application at all.

Opus 4.5 was fine, but I feel that 4.6 is more often on the money on its implementations than 4.5 was. It is just slower.

It isn't strange that this is the case, because you'd be equally hard pressed to compare developers at different companies. Great to have you on the team Paul, but wouldn't it be better if we had Harry instead? What if we just tell you to think before you code, would that make a difference?

When you create a blog post about it though, I do agree that showing the projects will greatly increase the value of your claims.

"Programmers don't appreciate the fact that you can just violate terms of service."