[flagged]
Show HN: Clippy – 90s UI for local LLMs
21–30 of 300 posts
Re: Show HN: Clippy – 90s UI for local LLMs
#22This is cool, but does no one even look at what libraries they're shipping anymore? I mean, why does this Clippy-style LLM interface bundle: - A JavaScript implementation of the Jinja templating language - A full GitHub API client - A library that takes a string and tells you if it's a valid npm package name - A useless shim for the JavaScript Math module And 119 other libraries? This thing would have taken up 10% of…
Maybe it was vibe coded and the libraries were added while going down paths that turned out to be dead ends and the LLM never cleaned up after itself?
People have been perfectly capable of making that mistake themselves since long before "vibe coding" existed.
Re: Show HN: Clippy – 90s UI for local LLMs
#23[dead]
Re: Show HN: Clippy – 90s UI for local LLMs
#24Question for the devs in here...something I've been thinking about a lot recently. So I see that OP linked out to a public github repo...but when downloading the actual bundle, what's a quick way for me to determine that what I'm installing on my mac is actually the same as what's in the public repo? It's always seemed like a loophole to me ready for (potential) exploitation.
>> Ship project. >> Link out Github repo on the static site somewhere >> Gain trust instantly as users presume the public repo is what's used behind the scenes
Disclaimer: I'm a web dev and don't know a single thing about native MacOS software
Re: Show HN: Clippy – 90s UI for local LLMs
#25This is cool, but does no one even look at what libraries they're shipping anymore? I mean, why does this Clippy-style LLM interface bundle: - A JavaScript implementation of the Jinja templating language - A full GitHub API client - A library that takes a string and tells you if it's a valid npm package name - A useless shim for the JavaScript Math module And 119 other libraries? This thing would have taken up 10% of…
[deleted]
Re: Show HN: Clippy – 90s UI for local LLMs
#26Question for the devs in here...something I've been thinking about a lot recently. So I see that OP linked out to a public github repo...but when downloading the actual bundle, what's a quick way for me to determine that what I'm installing on my mac is actually the same as what's in the public repo? It's always seemed like a loophole to me ready for (potential) exploitation. >> Ship project. >> Link out Github repo…
[deleted]
Re: Show HN: Clippy – 90s UI for local LLMs
#27Question for the devs in here...something I've been thinking about a lot recently. So I see that OP linked out to a public github repo...but when downloading the actual bundle, what's a quick way for me to determine that what I'm installing on my mac is actually the same as what's in the public repo? It's always seemed like a loophole to me ready for (potential) exploitation. >> Ship project. >> Link out Github repo…
you don't, that is what reproducible builds are trying to solve, but even then it would still need someone to compile and check.
Re: Show HN: Clippy – 90s UI for local LLMs
#28Pretty sure Clippy is trademarked. Had the same idea but did not go through with it because of the TM.
The character is actually named Clippit. Although maybe MS trademarked Clippy after it became the more common name.
Re: Show HN: Clippy – 90s UI for local LLMs
#29Pretty sure Clippy is trademarked. Had the same idea but did not go through with it because of the TM.
Re: Show HN: Clippy – 90s UI for local LLMs
#30[flagged]
[flagged]