Don't go putting people into boxes. That's the path of persecution.

You have the inalienable right to say what you want on a plane, limited by what the government is allowed to prosecute. In a confined space, that is a bit riskier. That's a solely personal choice - no laws are being broken. The Captain has the right to ask you to conform or leave, but that's a separate issue.

People are being overly sensitive. A wifi name is not a protest. It does not disturb personal privacy and tranquility. It's about as offensive as an article titled "We’re All Gonna Die!" from your favorite news outlet - which by the way, is not an uncommon headline.

What if my wifi name was "peanut butter for all!" but unbeknownst to me and by some rare cosmic coincidence everyone on the plane was deathly allergic to peanut butter. Does that make me a terrorist? No! But I swear someone would try to drag me through decades of litigation regardless. These people seem to have divorced words and meanings from the mechanics of how the world works. Like, "this piece of paper says you shouldn't say this, so off with your head".

For supported devices, which include Pixel 8, Pixel 9, and Pixel 10 series, the Find Hub network can locate your phone for several hours even if the battery runs out or the device is powered off. """

https://support.google.com/android/answer/3265955?hl=en#zipp...

Couldn't find any official documentation from Apple, but there's this:

https://www.howtogeek.com/805624/what-does-iphone-findable-a...

The ask being, how in the world do I make use of Codex's proxy networking? I wanted Codex to have access to local services (not MCP servers) running outside its bubblewrap. The default config.toml file ships with this:

  [permissions.network]
  # enabled = true
  # proxy_url = "http://127.0.0.1:43128"
  # admin_url = "http://127.0.0.1:43129"
  # enable_socks5 = false
  # socks_url = "http://127.0.0.1:43130"
  # enable_socks5_udp = false
  # allow_upstream_proxy = false
  # dangerously_allow_non_loopback_proxy = false
  # dangerously_allow_non_loopback_admin = false
  # dangerously_allow_all_unix_sockets = false
  # mode = "limited"                           # limited | full
  # allowed_domains = ["api.openai.com"]
  # denied_domains = ["example.com"]
  # allow_unix_sockets = ["/var/run/docker.sock"]
  # allow_local_binding = false

Anyway what I have here [1] is somewhat of a one-off, but also a really useful guide to building a network namespace container. Hopefully it'll be a useful roadmap for others.

1. https://gist.github.com/orbisvicis/347fb8439b658fd6161486f3de1e1ea0

Comments URL: https://news.ycombinator.com/item?id=47760640

Points: 2

# Comments: 0

What you want is a context mipmap.

Then there was the Claude article describing using filesystem hierarchy to organize markdown knowledge, which apparently beats RAG.

Good. The internet is meant to uplift human society, not enable petty theft. If only they could have gone after each thief to take back the money they stole.

- signed, not-Asooka

https://www.unison-lang.org/