Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Cursed Knowledge

immich.app

Post reply on HN
Print view View original

131–140 of 165 posts

Re: Cursed Knowledge

#131

Post by burnt-resistor »

salawat wrote: post #110
TheBicPen wrote: post #81

Earlier quoted context omitted.

Opt-out telemetry is the only useful kind of telemetry

Forces me to fork your shit and remove privacy invasive parts. Consider my computer my home, and your telemetry a camera or microphone you're adding to my place. If you don't ask me for permission first I have no reason to trust you will maintain any semblance of integrity in the long run.

Yes, it's the approach and principle of the interaction. If {{software}} asked to opt-in to collect anonymized/generic information, for what purpose(s), and how it was being stored/anonymized to "vote" for feature use/maintenance and how it was definitely not going being used, like not being sold to data-brokers, then I might say "yes".

Opt-out shows disrespect and that {{user}} is the product.

Re: Cursed Knowledge

#132

Post by mras0 »

hiAndrewQuinn wrote: post #109

>The bcrypt implementation only uses the first 72 bytes of a string. Any characters after that are ignored. Is there any good reason for this one in particular?

bcrypt is based on the blowfish cipher which "only" support keys up to 576 bits (72 bytes) in length (actually only 448 bits as spec'ed). Wikipedia has all the details.

Re: Cursed Knowledge

#133

Post by freedomben »

motorest wrote: post #96
delusional wrote: post #90

Earlier quoted context omitted.

I agree, I usually put this sort of information in the commit message itself. That way it's right there if anybody ever comes across the line and wonders "why did he write this terrible code, can't you just ___".

As a side note, it's becoming increasingly important to write down this info in places where LLMs can access it with the right context. Unfortunately commit history is not one of those spots.

Also there's a lot of humans that won't look at the commit history, and in many cases if the code has been moved around the commit history is deep and you have to traverse and read potentially quite a few commits. Nothing kills the motivation more than finally finding the original commit and it mentioning nothing of value. For some things it's worth the cost of looking, but it's ineffective often enough that many people won't bother

Re: Cursed Knowledge

#134

Post by nothrabannosir »

burnt-resistor wrote: post #129
nothrabannosir wrote: post #118

Earlier quoted context omitted.

I’ve done this with my main drive for the last ten or so years and run into not a single problem. I recommend it.

Then you don't use Time Machine, Migration Assistant, cmake, or a host of other development and systems tools that don't work correctly on case-sense APFS volumes. Sorry, but this is terrible advice unsuitable for all audiences. It might seem to work for now but it's walking in a minefield of nonstandard configuration that could bite anytime in the future. https://forums.macrumors.com/threads/does-anyone-else-use-a-.…

I did use Time Machine, but thankfully wised up and left for restic instead. Using Time Machine is worse advice than case insensitive filesystem if you ask me. Inscrutable logs and silent failures.

I’m sure there are those who found problems, but fact remains that in ten years I never have. What I have found is a lot of warnings against it by people who don’t use it themselves, like the person in the second link.

I recommend it, and the more people use it, the more people can help fix bugs they encounter (if any?) like in that last link you posted.

PS the Time Machine error in your third link is apparently about a CI source to a CS target. I hope it’s fair to say: don’t do that?

Re: Cursed Knowledge

#135

Post by mras0 »

AstralStorm wrote: post #95
Havoc wrote: post #83

One can really sense the pain just reading the headings Also a crypto library that limits passwords to 72 bytes? That’s wild

It's written with constant memory allocation in mind. Silly of them to use such a small buffer though, make it a configuration option.

No, it's due to the construction of bcrypt - it ends up using the password more or less directly as the key for blowfish (the underlying cipher) which is why the limit is there. Check wikipedia for details.

Re: Cursed Knowledge

#136

Post by rf15 »

motorest wrote: post #115
rf15 wrote: post #105

Earlier quoted context omitted.

You are sadly completely missing the point of ever-self-improving automation. Just also use the commit history. Better yet: don't be a bot slave that is controlled and limited by their tools.

> You are sadly completely missing the point of ever-self-improving automation. Just also use the commit history. I don't think you understand the issue you're commenting on. It's irrelevant whether you can inject commit history in a prompt. The whole point is that today's support for coding assistants does not support this source of data, whereas comments in source files and even README.md and markdown files in ./do…

And my answer is: stop being a user when you want to be a developer so bad. Write the tool you need.

(we certainly did with our company internal tool, but then we're all seniors who only use autocomplete and query mechanisms other than the impractical chat concept)

Re: Cursed Knowledge

#137

Post by mdaniel »

physicles wrote: post #111

Back in 2011, I wasted an entire afternoon on some string handling code that was behaving very strangely (I don’t remember exactly what the code was). It wasn’t until I loaded the content into a hex editor that I learned about U+00A0, the non-breaking space. Looks like a space, but isn’t.

Ah, yes, the 90s html was jam packed with   (aka  ) to make things not wrap, and that was stellar good fun for copy-pasting

The other "2020s" problem is some leading unicode marks which are also invisible. I thought it was BOM but those do seem to show up to cat but just a few weeks ago I had a file from a vendor's site that wouldn't parse but that both cat and vim said was fine, only to find the wtf? via the almighty xxd

Re: Cursed Knowledge

#138

Post by mdaniel »

csours wrote: post #45

You can load Java Classes into Oracle DB and run them natively inside the server. Those classes can call stored procedures or functions. Those classes can be called BY stored procedures or functions. You can call stored procedures and functions from server-side Java code. So you can have a java app call a stored proc call a java class call a stored proc ... Yes. Yes, this is why they call it Legacy.

That's ok, modern nodejs apps are represented, too, so everyone can get in on the legacy train: https://docs.oracle.com/en/database/oracle/oracle-database/2... and https://docs.aws.amazon.com/AmazonRDS/latest/AuroraPostgreSQ...

or, if the modern job postings are indicative, FastAPI to PG to PY https://www.postgresql.org/docs/17/plpython-funcs.html

Re: Cursed Knowledge

#139

Post by gsmt »

freedomben wrote: post #133
motorest wrote: post #96

Earlier quoted context omitted.

As a side note, it's becoming increasingly important to write down this info in places where LLMs can access it with the right context. Unfortunately commit history is not one of those spots.

Also there's a lot of humans that won't look at the commit history, and in many cases if the code has been moved around the commit history is deep and you have to traverse and read potentially quite a few commits. Nothing kills the motivation more than finally finding the original commit and it mentioning nothing of value. For some things it's worth the cost of looking, but it's ineffective often enough that many peo…

I usually spot these kind of changes through git blame whenever I find a line suspicious and wonder why it was written like that

Re: Cursed Knowledge

#140

Post by simpaticoder »

freedomben wrote: post #133
motorest wrote: post #96

Earlier quoted context omitted.

As a side note, it's becoming increasingly important to write down this info in places where LLMs can access it with the right context. Unfortunately commit history is not one of those spots.

Also there's a lot of humans that won't look at the commit history, and in many cases if the code has been moved around the commit history is deep and you have to traverse and read potentially quite a few commits. Nothing kills the motivation more than finally finding the original commit and it mentioning nothing of value. For some things it's worth the cost of looking, but it's ineffective often enough that many peo…

The OP solved this problem by generating a well-known url, hosting it publicly, and including a link to the commit in the cursed knowledge inventory.
Post reply on HN