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

No idea, email him and ask? I don't develop desktop apps but I'm assuming it's because the original installer didn't.


ClipX has plugins that give you way more features. As a web developer I used the color picker plugin to copy the hex code of the pixel beneath my mouse to the clipboard when a hotkey is pressed, although it could be configured in many other ways.


I've used ClipX since its inception in 2004, and was shocked to learn it was recently updated by the original author for a major 2.0 revision... 18 years later! The FAQ also states that he never sold it, so it remains 100% crapware free.

I used to joke that it took Microsoft until Win 11 to create their own clipboard manager, and even then it didn't hold a candle to the 18 year old ClipX 1.0


As someone who used to submit issues to Gitlab just to see them stagnate for 6-8 years and then ceremonially get closed after being stuck in management/release bump hell (along with many 'me toos' from both Gitlab premium support staff / 3rd party contributors) I agree with your statement 100%.


If we could restore the snapshot from around the year 2000 that'd be great, would like to make some changes.


Ironically the site is now giving a "The website encountered an unexpected error. Try again later." Do I blame the cloud?


Definitely.

  x-cache: Error from cloudfront


That's assuming ASML and co would even supply the required tech should that happen.


Would have been a great domain with the rise of AI, shocking they didn't adapt the persona.


What is the rationale behind naming CVEs and individual domains? Marketing?


It's an advertisement for their tool that found the exploit: https://copy.fail/#contact, https://xint.io/products/xint-code


can you remember what CVE-2021-44228 is without looking it up? CVE-2014-6271? CVE-2017-5753?

i bet if i told you their names, you would instantly know what vulns those are.

its easier to talk about things with names. it hurts no one. it takes approximately no effort or time.

CVEs are, for whatever reason, like the only thing on the planet that people seem to have a problem with when they receive a name. i am not sure why.


> CVEs are, for whatever reason, like the only thing on the planet that people seem to have a problem with when they receive a name. i am not sure why.

What, you guys talk about books based on their “title” instead of just memorising the ISBN of each book? Pssh, count me disappointed!


after work i have to stop at Y87794H0US1R65VBXU25 for some groceries.


I only refer to my kids by their social security numbers until they do something suitably remarkable.

I guess it’s a good thing I’m not a SovCit or I’d just have to call them Traveller Three and Traveller Four


For anyone else that was curious they're log4j, shellshock, and spectre


It's certainly marketing, but it's prosocial: there's no scarcity of names, and "copy.fail" is much easier to remember and talk about than "CVE-2026-31431".


The AI generated prose screams marketing. Marketing is why there's a "Contact our Security Team" form at the bottom of the page.


Probably to some extent it is marketing, but generally it has to do with significant bug finds to get the message out to the people who need to apply patches and/or be informed. Heartbleed, Log4Shell, etc.

Very few CVE’s get names dedicated to them like this, because usually when they do - it is very serious, as in this case.


Giving catchy names for bad exploits has been a thing for a while. Probably to make sure it's easy to reference and make sure you're patches as opposed to passing numbers around. Heartbleed, Shellshock, BEAST, Goto Fail, etc


Yes, originally it was to help spread awareness. Now it has become more of a gimmick I would say


It makes sure people don't forget about the vulnerabilities, at least


Same reason they name storms, numbers scare normies


I desperately miss PureDJ online radio, pretty much exclusively streamed EDM DJ sets. Would do anything to see the archive restored in some fashion.


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

Search: