HN user

sorz

53 karma

[ my public key: https://keybase.io/sorz; my proof: https://keybase.io/sorz/sigs/c57FmDYJ5auGR6VnlMzPMsi3ygA0EvGYE53gJvDsJnM ]

Posts2
Comments26
View on HN
How does GPS work? 3 months ago

So gound stations need keep measuring their own positions due to continental drift! Never thought that before. Thanks.

I feels wrong to not mention IPv6 in 2026.

- net.ipv6.conf.all.forwarding=1

- nftables is default to `ip` family which only applies to IPv4. Setting it to `inet` will allow rules to apply to both IPv4 & 6; or `ip6` for IPv6 only. You can skip NAT rules, usually.

- dnsmasq: in addition to DNS and DHCP, turns on router advertisement with SLAAC. Some devices can get IPv6 address from stateful DHCPv6 server, others (e.g. Android) only work with SLAAC.

Gpg.fail 7 months ago

Lots of issues follow the pattern "ANSI escape code inside untrusted text". It feels like XSS but for terminal.

Tunnl.gg 8 months ago

Random thoughts: one can get user's ssh public keys from GitHub on the fly (from `https://github.com/<username>.keys`), so that it requires a valid GitHub account to use this service, without (extra) auth process.

The time at which scalpers buy tickets becomes irrelevant. They can resell tickets at arbitrary-high-price + margin because buyer know they will receive refund for the exceed amount, thus pay only (final price + scalper margin) for the ticket eventually.

Bonus: buy ticket from scalpers after price settled, you will get a determined price, no more guessing and find inner peace.

The problem for scalpers is that if they buy too many tickets, the final price may become too high to be attractive for real buyers.

The whole post is on base on the fact that "TW" in their URL. But I think this is really just a internal implementation detail of Google Translate, which is not intended to display to users (e.g. complete hidden on their app). Everywhere on their UI shows "Chinese (Traditional)". That is what they try to communicate with users.

Sure, zh-TW is somewhat misleading. But they nor say that parameter is a ISO 639 or RFC 5646 conformed.

OpenAI did exact the test for GPT-4. The raw, non-fine-tune GPT-4 is quite good at predicting confidence level ("highly calibrated" by their words). But the RLHF fine-tuning process seems ruin its calibration. Figure 8 on page 12 of GPT-4 Technical Report shows this dramatic changes before & after fine-tuning.

Won't I have to reload my browser if I change a file?

Yep! Welcome to the joys of Javascript.

Although it (re-)sends file for every request, the file content must be identical. So the relay server may just cache the file.

Once you do that, it becomes more like a traditional static file hosting w/ on-demand file uploading via browser.

Windows Firewall worked on WSL Pico processes for example.

In WSL1 they share the same IP addresses and TCP/UDP port space, while WSL2 has an separated IP address. I suppose there is some NAT to make the network working in WSL2.

At the end of Q&A part they mentioned that sharing localhost, IP addresses, and port number space (which is a WSL1 feature) may be done in future, but they have no roadmap for it right now.