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

It'll still work. OpenSSH doesn't care about output (for ~ stuff), only input, so if you type <enter>~. it will close the connection.

Does not for me, not even with busybox sh and no funky escape codes in PS1 at all. It does with cat or yes running, so just something being output is not the problem… Hm.

It does not. open ssh linux to mac, typing ~ just types it on fish shell prompt. It works after`cat` followed by ENTER

Just type <enter> without cat, your shell will show you another prompt, and the ssh escape command will also work.

No they are correct, fish seems to intercept this or something like that. Only works with cat.

In newer versions, it's disabled by default and you have to do something like this to enable in ~/.ssh/config:

    Host *
    EnableEscapeCommandline yes

`EnableEscapeCommandline` only controls the <Enter>~C commandline.

The reason that is disabled in current OpenSSH by default is OpenBSD `pledge` support:

https://security.stackexchange.com/questions/280793/what-att...

On my Linux,

    cat<Enter>~.
closes the connection as expected, and no ~ is shown in the terminal.

Are the speed limits set unreasonably low? Otherwise one could always try abiding to the speed limit.

Most US cities have lower posted speeds than average drivers’ perception of safe speeds.

Oftentimes comically lower. I remember in Chicago the interstates having posted speed limits of 45mph... the average flow of traffic outside of rush hour was easily north of 70mph.

Looking even at normal arterial streets, many streets in Seattle are marked 25, but you'd be hard-pressed to find even a cop going under 30 most of the time.

I truly don't understand US road design. The construction of the road and the posted speed limit almost never are even gently correlated other than on a few select residential side streets in a few select cities who have rebuilt streets based on safety studies.


    > I remember in Chicago the interstates having posted speed limits of 45mph... the average flow of traffic outside of rush hour was easily north of 70mph.
This comment seems a bit odd to me. I Google about it and learned (from various sources):

    > 45 mph (72 km/h) in downtown Chicago, where all the major interstates merge
This excludes construction or work zones.

That seems pretty reasonable. I've seen a few places in the US where several major interstates merge and the post speed limit is quite low -- 45-55 mph.


Well AFAIK the core seamless roaming in Unifi is using hostapd, which is the same AP software you use on OpenWrt. See 802.11r Fast Transition.

I think it should even be possible to get seamless roaming between Unifi and OpenWrt with correct configuration of hostapd.


Some carriers also require your phone to be on their whitelist - for example AT&T.

And Verizon claims they don't do it that way, but we had a phone that worked on Verizon with an old SIM card until Verizon caught on, and then suddenly it wasn't compatible with their network and couldn't be used on Verizon.


You can use ohms law - let it draw power through a 10k resistor, and put your multimeter across the resistor. Every .01 volt is 1 uA. This also means that if you're powering it with 3.3v and it browns out at 3.0v, you'll only be able to draw 30uA before browning out.

You can use a different resistor according to the power draw and how sensitive your volt meter is.

You'll probably need to power it up with the resistor shorted, and only remove the short once it's in sleep mode, to measure the current.


We have 5 computers running Firefox. One computer has regular Firefox crashes. I've done some memory testing that didn't detect anything wrong.

I've tried all kinds of things software-wise but keep getting random crashes.

I wonder if I should do a longer memory test, maybe some CPU stress testing at the same time...


If you want to dig into it, you can post a bunch of that computer's crash reports (navigate to about:crashes) on bugzilla: https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&c...

Or you can view several of them and see if there's a common pattern in the "Signature" field. Firefox really should only be regularly crashing if: (1) there's a real bug and the thing that triggers it, (2) you're running out of memory, or (3) you have hardware.

I don't know what the odds of faulty hardware are for a randomly chosen user, but they're much higher for a randomly chosen user who is seeing regular crashes.


That would be the thousands of lines of JS that they are complaining about. Except if it depends on jquery, that's even more lines.

? It's 294 lines unminified

In my opinion, anti-intellectualism is the cause of antivax, and commonly goes along with conservatism, but isn't the same thing as conservatism.

Until recently, antivax was largely a liberal form of anti-intellectualism. It was a reaction against large pharmaceutical companies.

It didn't really become a conservative position until COVID. It's mostly an anti-progressive thing, but builds on existing populist conservative anti-science attitudes. (Conservative doesn't always mean anti-science, but populist versions of it will inevitably tend that way.)


According to Wikipedia, the Power Mac G4 was the first mass produced computer with gigabit Ethernet - in 2000.

So now in 2025, 12.5 doublings later, we should have a mass produced personal computer available with a 1 gigabit times 2^12.5 = ~5 Tbps NIC.

We're not there yet. Not even close.


If a platform decides to require an account to post, or requires your message to pass an LLM sniff test before publishing it, you can break all the rules you want but your message won't be visible to others on said platform.

The example given was a ‘lightweight LLM’ by the poster, which sounded an awful lot like client side?

If server side, you already have the heavyweight stuff going on, and yes there is no need to do all the bypassable shenanigans.


Since that client side llm would be processing billions of messages each year on each person's laptop, lol

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

Search: