HN user

Izkata

9,871 karma
Posts1
Comments6,668
View on HN

It's been there just as long, turn it on with "privacy.userContext.ui.enabled" and manage them at "about:preferences#containers"

The addons added extra functionality but everything they've listed in this announcement is already there. Sounds like they're just flipping these two flags by default.

No, it's at about:preferences#containers and has been for years if you turn it on in about:config (privacy.userContext.enabled and privacy.userContext.ui.enabled).

I don't use Nightly and I've been using containers for I think that long without any extension for it.

Edit: looks like I enabled them manually and couldn't remember/find it, it's in about:config under the name "privacy.userContext" instead of "containers".

The singularity is the tipping point where the AI can improve itself faster than humans can comprehend, so the software at least wouldn't be human-designed anymore.

It requires a level of self-driven intent and access to their own code LLMs aren't capable of on their own. They might be one component of such a future system though, we just don't know yet. Even then it would probably take quite a while to reach that tipping point. GP is just wrong, talking as if we'd already reached it.

Yeah, this is much more accurate to what was actually happening. During that high period they struggled to get people to stop posting low-quality "do my homework" style questions - despite what people on here say the barrier for entry was extremely low and those made up the vast majority of what was posted.

I've maintained that if they handled this AI-caused decline well, they could return the site to its better days before the flood of people who didn't know what they were doing, offloading the bad questions while getting still getting all the good ones. I'm not sure they're even trying.

As I understand it, in America "it's just a tool" is shorthand for "guns should be regulated like hammers, i.e. barely at all, responsibility lies with the user not those who make, market and sell it"

You're partially right about the responsibility part, but I think the rest is going too far. The phrase is a direct response to media and gun control advocates who treat the existence of guns as the cause of crime instead of the people using the gun.

There is 4th option that looks like a combination of how all three are described here: If J1 is running and J2 gets queued, then when J3 gets queued you cancel J2 but not J1. Prefer the oldest running (well, any running, just don't kill them) and newest queued, which waits on the running one. This is how we had long-running test suites configured on Jenkins/Hudson/buildbot ages ago (though it wasn't exactly a queue, more just a flag that the job needed to be run and the job pulled in the latest state).

Also I think that they would get a better "feel" for working numbers in general.

This is called "number sense". I'm pretty sure we do have evidence under searches for that term, it was well-enough known as a concept when I was in school decades ago and is the reason we don't use calculators when first learning math.

But to latch onto the calculator argument: if you outsource adding numbers to a calculator, you're still you.

Except calculators have been a problem for decades, it's why they're not allowed in school when you're still learning. Without doing the math yourself and internalizing how it works, you won't develop the number sense to tell if the result makes sense (broken calculator, typo, wrong equation, etc).

I still remember my physics teacher using one of the student's test answers as an example of how he should have known it was wrong and gone back over it (I think it was a pendulum on an elevator, his result had negative gravity (so gravity going upwards)).

I do multiple times a week, with repos that have barely been touched in a decade and all the original devs are gone. Squashing would make figuring out why something is the way it is a lot more painful, so I'm glad these repos are svn where squashing wasn't an option. Several times I've discovered bugs that were introduced in linting commits that would have been squashed, so the fix ends up trivial since the intention is already there in the previous commit.

...this is a completely normal thing to do in linux, it's the most basic form of access control. There's like a dozen non-human accounts in a clean install before adding your own like this, and a lot of software adds their own. Edit: I have 54 entries on my personal laptop, just one of which is actually me.

The singularity is when an AI can improve itself, which among the results include humans no longer being able to understand its code and exponential improvements so we can't catch up either.

It requires a level of self-driven intent LLMs aren't capable of on their own.

It was established pretty firmly by the end of 2021 or early 2022. There was even at least one site that gamified it, by showing graphs of infections/deaths for similar US states and similar European countries and having you guess which ones did/didn't do various measures (lockdowns, masks, etc) or having you guess at what point in time they were instituted/repealed. None of it had any effect. IIRC the only real visible patterns involved latitude, time of year, and average population age. It's just really hard for most people to accept just how much their lives were disrupted from lies (if they ever even encountered the truth).

Decades ago, really. Before IDEs were remotely as capable as they are now, it was just generally assumed you'd advance from a basic text editor like notepad or nano into vim or emacs.