I understand what you mean, but when Vancouver locals say "asian", they really mean "east asian" (Chinese/Japanese/Korea). I live in Surrey, a Vancouver suburb, where ethnic Indian is about 30%-40% of population. The local newspaper often refers them as "South Asian community".

But I'm surprised that BBC use "Asian" to refer "East Asian". I'm under the impression that in UK, they use "Asian" to refer "South Asian".

UK person here. Many (most?) people would say you were "Asian" of you were from anywhere in Asia apart from the Indian subcontinent.

weekly put options. (http://www.cboe.com/products/weeklys-options)

If someone is asking a basic question like this (no offense), they probably should be dabbling in options plays.

Do you mean, "should not be dabbling in option plays"?

nftables doesn't support TPROXY.

Right, TPROXY is an iptables module (which implies that without someone to port it (assuming porting is even possible due to architectural differences), it isn't going to work on NFTables).

To clarify my original question, what will cloudflare do if/when iptables finally goes away? Has thought been put into it? Will they implement their own type of TPROXY? Will they continue to support iptables themselves? There's quite a few paths, and I'm interested in which one they deem most optimal because I respect their opinions a lot.

actually, TPROXY is very very lightly coupled with iptables. In fact, you can directly use TPROXY without iptables.

here's a 50 line kernel module that uses TPROXY to do the samething without touching iptables.

https://pastebin.com/uxUf6MFS

looking at the nftables code, I think the only reason nftables doesn't support TPROXY is that no one wrote some of the config parsing / seralization stuff.

Sounds like cloudflare might want to start trying to submit some nftables TPROXY support now, so it's there in the vanilla kernel when they end up needing it. :)

It'd expect someone to eventually submit such a patch, though I don't know how urgent this issue is. Iptables isn't going anywhere anytime soon, so Cloudflare can continue to use this method on the edge nodes.

like the other guys said, 1) use a alarm clock, 2) there's a freaking calendar app builtin.

but if you really need to "code" for whatever reason. The core logic is trivially simple. you need to 1) wait til the moment you want to wake up 2) generate some noise.

so just open mac terminal and type:

sleep 28800; while true; do say "wake up"; done

For those referring nftables, there’s a LOT of stuff in iptables that doesn't work in nftables: from simple things like xt_time to complex ones like xt_TPROXY. so nftables isn't a viable replacement for iptables just yet. In theory there's a compat layer in nftables to get around those, but I have never able to successfully build a binary that works.