← Back to context

Comment by AtNightWeCode

15 hours ago

That is simply not how software works.

From the producer's side, sure, we[1]'re all pretty sympathetic to the fact that if you publish a library a bunch of random people will build bridging libraries for languages that you have no control over.

But from the consumer's side it is very much an expectation and if you find yourself in the situation above it's on you to make it very clear that such extensions and third party tools are unofficial.

In this particular case I think it's fair to say that Anthropic really dropped the ball on signaling that this was an unofficial third party tool.

1. We specifically being library and tool producers that are noticeably overrepresented on this forum.

  • > Anthropic really dropped the ball on signaling that this was an unofficial third party tool

    Had the tool been up longer than the 11 hours the malware was live? If not, then why would Anthropic try to get it marked as unofficial, as opposed to take it down?

    Or are you saying that every author and publisher should request Cursor to mark their extensions on the Cursor vsx pass-through as unofficial?