sorz

They do test continuous (1-hour) gaming performance in controlled environment regularly. Thermal throttling can be easily spotted on the frame rate vs time graph.

I just come back from a furry con hosted in hotel in China, and learn how every furry con like this completely break hotel's elevators:

- rooms are all booked

- young furries usually share one room with 4 or even up to 6 friends

- more guest room-lobby-ballroom traffic

- far more inter-guest-floor traffic than their usual tourists

- one full-suit furry take 1.5-2 human's space

Their elevators are not designed for this scenario and got overloaded all the day. Queueing for tens of minutes is not uncommon.

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.

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

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.

Better be "three months of the country's GDP".

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.

In the mug-scrubbing video, the person clearly pretends to wash the cup but does not seem to want to get their hands wet anyway. I'm curious as to when models can figure out that subtle thing.

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.