milisp

Update:

I successfully created a ticket in normal Safari mode without using other people’s accounts.

I tried Chrome and Safari private mode (401) failed, so maybe this is a GitHub cookie issue because.

Thank you for your attention.

1. Sorry for trigger your bad memory

2. I successfully created a ticket in normal(not private) Safari mode without using other people’s accounts. Maybe GitHub cookie issue because private mode.

I'm sorry, now I know the comment rule too, Thank you. the post was written by myself, but the comment I learn from AI, not send by bot. I'll write everything by myself next time, Just use google translate.

You're right. I understand why this was inappropriate, and I won't do it again.

For context, these vendors had submitted PRs to my own directory to list their MCP servers

You’re right — those numbers are illustrative. It’s a hypothetical estimate based on a real-world scenario where a minor install issue (like Gatekeeper rejecting downloads) leads to a non-trivial drop in conversion. Even if it’s just 1% of downloads failing, at a $5 CAC, that’s serious money at scale.

I’m open to better sources — and would love to improve the repo with more concrete stats if anyone has them.

Not trying to spam HN, promise — but yeah, I want to change this situation for indie devs, and I’ll keep improving and sharing until it actually helps more people.

This isn’t just about me — it’s about a misleading message that affects thousands of developers and users. Even if I pay $99, the warning remains a problem for the entire open-source and indie dev ecosystem.

Thank you for the thoughtful questions!

Why It’s Different From Windows

On Windows, unsigned apps usually trigger a “Unknown Publisher” warning, which: - Clearly labels the app as unsigned — not “damaged” - Still allows the user to easily override the warning and open the app - Doesn’t falsely imply the app is corrupted

On macOS, the message is:

“App is damaged and should be moved to the Trash”

This: - Strongly implies the app is broken or dangerous - Misleads non-technical users into deleting safe software - Can trigger across all user files or multiple apps after updates, as seen in real cases

Cost to the Ecosystem

It’s not just about the $99/year: - Small devs, educators, hobbyists, open-source projects often can’t justify the fee for a free tool - Explaining this to every user takes hours of support time - Thousands of safe apps are abandoned or ignored due to the scary warning - Users lose trust in perfectly good software

We’ve estimated: - Over 1 million users have abandoned apps due to this message - Devs waste millions of dollars worth of time explaining workarounds

The Goal Here

We’re not asking Apple to remove security — just to make the message accurate.

Changing “damaged” to something like:

“App is not signed and may be from an unknown developer”

…would solve 90% of the confusion, with no loss in security.