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


You are probably joking, but I think it's actually very important to look at the language we use around LLMs, in order not to get stuck in assumptions and sociological bias associated with a vocabulary usually reserved for "magical" beings, as it were.

This goes both ways by the way. I could be convinced that LLMs can achieve something the likes of intuition, but I strongly believe that it is a very different kind of intuition than we normally associate with humans/animals. Usins the same label is thus potentially confusing, and (human pride aside) might even prevent us from appreciating the full scope of what LLMs are capable of.


I think the issue is that we're suddenly trying to pin down something that was previously fine being loosely understood, but without any new information.

If someone came to the table with "intuition is the process of a system inferring a likely outcome from given inputs by the process X - not to be confused with matmultuition which is process Y", that might be a reasonable proposal.


What does being a Pakistani national have to do with anything?


He does not answer to any reasonable Western legal system.


Pretty cool!

If you go to the index page it tells you what it is; a studio for design and code based in Switzerland.

https://ertdfgcvb.xyz


Does anyone outside the US have a great time with Kagi? I tried it for a few months but found it to be very US focused. Perhaps I just didn't spend enough time shaping my queries.


Indeed! I think this is what makes this so fun. I can also highly recommend listening to various recordings of the moonlight sonata and notice how different it is depending on the precise timing the pianist uses.


The only thing I changed from the default parameters was Age == Teenager. That resulted in this error:

We detected that generated image contains nude content. Try changing parameters.

Not sure what to make of this, but it feels wrong, somehow?

Edit: This was the prompt it generated for me on page load: "Minerva McGonagall in Hogwarts, wearing Hogwarts robe and witch hat" - https://generated.photos/human-generator/64e650a39563e6000e0....


"teen" is a ubiquitous porn category that, in practice, describes a body type, not age; similar to how "babe" almost never means "infant".

I would be more surprised to get SFW results from that prompt, considering the result would be based on more heavily regulated (less common) photographs of minors.


No, teen in porn absolutely means 18 and 19, or at least "I'm '18-19' and definitely not a 26 year old"


Pick ten random 26 year old porn actors. I bet you their most recent scene was categorized as either "MILF" or "teen".


I got the same thing and am very confused. They are the ones generating the image. Why did they generate porn if they don't allow it? Also apparently clothed teenagers are now pornographic? I think their image analysis needs some work.


Over self-censoring


Cherry-picking data to support your biases hardly falls under the category of rationalist coverage. Just like the radical environmentalists, Lomborg seems particularly prone to his biases.

Unfortunately, reality is more complicated than what fits in a few tweets about wild fires, polar bears and coral reefs.


Link to the paper: https://arxiv.org/abs/2306.08023

And a video to hear the twinkling: https://www.youtube.com/watch?v=yqQViMPJxwE


Curious how much you backup, which version of restic you're running and why you think the deduplication is borderline unacceptable. There were several major (orders of magnitudes) improvements made to pruning within the past ~1 year, that's why I'm interested.


A straight upgrade, that I can do :) It's been running for years without one.

I was only edgy about it because when it takes 36h it blocks the next daily backup, and I wondered whether that was going to get worse (it hasn't).


The max-unused percentage feature is well worth it to 80/20 the prune process and only prune the data which is easiest to prune away (i.e. not try to remove small files big packs but focus on packs which have lots of garbage).

In general, there's an unavoidable trade-off between creating many small packs (harder on metadata throughout the system, inside restic and on the backing store but more efficient to prune) versus creating big packs which are more easy on the metadata but might create big repack cost.

I guess a bit more intelligent repacking could avoid some of that cost by packing stuff together that might be more likely to get pruned together.


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

Search: