Hacker Newsnew | past | comments | ask | show | jobs | submit | milisp's commentslogin

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.


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


this reads like ai generated response, which itself breaks the HN rules, which an ai will often do in the immediate response to being told it broke the rules, your comment history shows a pattern of this

stop using ai bots for your writing, be a human


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.


I won't do it again.

With a suspended account, yes.


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

Common Ai response when being called out.


Tired of copy-pasting code into AI just to explain your bug?

I built a desktop app (Tauri + React + MCP) where you browse your files in a tree view, and just click + next to any file to add it to your AI conversation.

- No more manual context setup - Works offline, privacy-first - Cross-platform (macOS, Windows, Linux) - Connects to 600+ tools via MCP server

It feels obvious in hindsight, but it's been a game-changer for my workflow.

Would love feedback or ideas. Repo here: [https://github.com/milisp/plux]

Blog: https://github.com/milisp/plux/blob/dev/docs/BLOG.md


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.


I'm sorry, miss a g word, here is the new url:

https://github.com/milisp/misleading-macos-damaged-warning


macOS often shows this message: App is damaged and should be moved to the Trash. But most of the time, the app is just unsigned — not actually damaged. This repo collects real-world cases, time lost, and proposes a fix. https://github.com/milisp/misleading-macos-damaged-warning


How is it costing the ecosystem? And why is this any different than Windows, for example?

And - if you cannot afford a $99 / yr developer ID, how could you possibly afford a signing key for Windows or other platforms?


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.


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.


I just released a big update to MCP Linker last week, an open-source Tauri GUI tool to manage and sync MCP (Model Context Protocol) servers across AI clients.

Enable/disable servers from a panel

We’re building the best open-source MCP manager. Feedback, stars, or contributions welcome!


If you’re using Claude Desktop, Cursor, or hosting your own MCP servers, I’d love to hear your setup or how you organize them.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: