Not HDMI, but SDI over fiber is basically this. It can be muxed and is used in the broadcast industry for long haul camera feeds.

SDI over fibre with a cheap converter if you need to push multi hindered metres. Then people moves to 222-6 which packetised the SDi over IP, and now 2110 which breaks out the SDI to its components.

For most long haul links people still compress, good old h264 or 265 with latencies in the 200-500ms range (plus network propagation), or J2k/JXS and NDI which are more like 50-150ms. Ultimately 200mbit of h265 is far cheaper to transmit than 10ish gbit of 2110, and in many cases the extra 500ms doesn’t matter.

This message is for Hawaii.

Edit:

Now as of "1154 AM PST Thu Dec 5 2024" the warning is canceled:

https://www.tsunami.gov/events/PAAQ/2024/12/05/so1aq0/3/WEAK...

It's unfortunately hard to tell what regions that message is for, or whether it contradicts the other one saying the warning is still in effect: https://www.tsunami.gov/events/PAAQ/2024/12/05/so1aq0/2/WEAK....

It looks like https://tsunami.gov/?p=PHEB/2024/12/05/24340001/2/WEPA40 is the 11:29 PST message saying there is no tsunami warning for "Non-US/Canada Pacific".

And it looks like https://tsunami.gov/?p=PAAQ/2024/12/05/so1aq0/2/WEAK51 is the 11:25 PST message saying there is still a tsunami warning for "AK/BC/US West Coast".

But it's not easy to tell what one's looking at if one doesn't already understand the system, and conditions of "extreme danger" (which is what my phone told me about half an hour ago) are not a good moment to figure these out.

Edit: here we go: https://tsunami.gov/?p=PAAQ/2024/12/05/so1aq0/3/WEAK51 now says "No Tsunami Warning, Advisory, Watch, or Threat" for "AK/BC/US West Coast" as of 11:55 PST.

The "Pacific Tsunami Warning Center" is in Hawaii, which is why it is mentioned at the start of the message. Did you by chance just misread this? See the page below:

https://www.tsunami.gov/?page=history

I use this zsh function and define my git alias in my git config.

    # No arguments: `git status`
    # With arguments: acts like `git`
    function g() {
      if [[ $# > 0 ]]; then
        git $@
      else
        git st 
      fi
    }

    # Complete g like git
    compdef g=git

    # Complete g like git
    compdef g=git

That's brilliant.

I have my zsh set up so that if I just press Enter without writing anything it will run ls -l or git status if it's a git directory.

How do you do that? Is it part of your PROMPT?

Sorry for the lag, I'll just drop the answer anyway in case it still can be helpful to you or anybody else.

It's actually a oh-my-zsh plugin, called "magic-enter".

I defined MAGIC_ENTER_GIT_COMMAND="git status" and then included the plugin.

You can find a different but similar plugin here: https://github.com/zshzoo/magic-enter/blob/main/magic-enter....

Neat, thanks!

I'm getting some. 1.1.1.1 isn't responding to any DNS requests for me.

You can also use add a hyphen ( <<-EOF ) to suppress leading tabs but not spaces. https://linuxhint.com/bash-heredoc-tutorial/

I've always avoided that for fear that my or someone else's editor will accidentally replace the tabs with space. Mixed is not a common configuration, these days.

This makes me want to use this just to get people to fix their broken editors.

Oh, that's nice! And in spite of the labeling on that page, it doesn't seem to be a BASHism; it at least works in dash, too.

And ksh.

Bash? It's POSIX: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/V....

Ruby and Perl have `here` docs as well.

And Ruby 2.5 has an enhancement which preserves leading whitespace.

Location: Seattle Area Remote: Yes Willing to relocate: No Technologies: Linux, NixOS, Python, Docker, iOS, Networking. Résumé/CV: Available upon request. Email: admin [at] psophis.com

Looking for a mid level devops position somewhere in the Seattle area. Currently working as a Network/Linux Admin and sole developer at a local small school district.

What's the difference between this and a properly setup file type plugin? As here [0] with python lets you open imported modules using `gf`.

[0]: https://github.com/vim/vim/blob/a87b72cc316e065d66dcbcf7ec1c...

Another thing I just tested using “includeexpr”, “path” and “suffixesadd” is that it is not possible (as far as my knowledge goes) to let vim open files correctly if the import path is a directory. Which my module does very well for javascript-like projects.

I am not sure if I get your point according to your reference, but the expression in your reference is way simpler than mine, although I should have used includeexpr rather than remapping fg itself. I’ll put that on my todo list, since that is the recommended way.

The main difference is that I want “fg” to be better, smarter to detect file paths. As I mentioned already, javacript-like projects use lots of absolute imports these days and these are not resolved by gf.

This is very cool. Though I’ve always done remote wireshark captures:

    ssh root@sniff_server_ip -p port tcpdump -U -s0 'not port 22' -i eth0 -w - | wireshark -k -i -

Source: https://serverfault.com/questions/362529/how-can-i-sniff-the...

It works very well on low volume captures.

I've made a simple script based on your example:

wirelive.sh:

  #!/bin/bash
  
  if [[ -z "$1" ]]; then
      echo -e "Usage: $(basename $0) <host[:port]> <interface> [filters]"
      exit
  fi
  
  ssh_host=$(echo $1 | cut -d: -f1)
  ssh_port=$(echo $1 | cut -s -d: -f2)
  [[ -z "$ssh_port" ]] && ssh_port=22
  [[ -z "$2" ]] && tcpdump_interface="any" || tcpdump_interface="$2"
  [[ ! -z "$3" ]] && tcpdump_filters="and \($3\)"
  
  ssh root@${ssh_host} -p ${ssh_port} \
      tcpdump -U -s0 "not port ${ssh_port} ${tcpdump_filters}" -i ${tcpdump_interface} -w - \
      | wireshark -k -i -

nice, but a small nit: you don't need to quote variables inside bash double brackets.

This method even worked for Wiresharking all PS3 traffic in real time for a GTA Online session, running the tcpdump on a little plastic old mipsel SoC OpenWrt router that was also doing all the routing (not a passive sniffing box), without noticeable effect on gameplay. (I was trying to detect cheaters.)

BTW, for anyone new to tcpdump, you can also specify selectors/filtering on the command line, to reduce the traffic. The filtering in Wireshark is on top of that.

online games are pretty low volume though, data is usually transmitted at a few Kbps per player. Just out of interest, how did you try to spot cheaters doing that?

Not quite in their interest to publicly explain methods of how they detect cheaters :)

It's one of best guarded secrets in gaming industry.

OP does not sound like he was actually working for Rockstar on GTA, more like a hobby project

Correct, not working for Rockstar. And I'm pretty sure R* stopped caring about cheaters ruining Online for last-gen console, shortly after that could push people to buy the game again, for current-gen. :)

Wouldn't they just cheat with some of the common methods and train some AI with the packet dumps to spot it?

Perhaps he was looking for an abnormal amount of traffic, attempting to resend the same message, and hoping the server will do it multiple times in the same frame. I would guess trying to find spots where the client is overly trusted.

Game traffic is usually encrypted. How good depends on the game. So you might only see some packets with a larger payload and deduce stuff from there.

Came here to write the very same command. I only use -l instead of -U. In Windows using WSL I use something like this:

  ssh root@remotehost "tcpdump -i eth1 -s0 -l -w - 'udp'" | /mnt/c/Program\ Files/Wireshark/Wireshark.exe -k -i -

Option "-l" only supposed to be used with text output. When mis-applied to binary (-w) output, it will:

- On Linux, flush buffer at wrong places, breaking last (few) packet(s);

- On Windows, flush buffer after every byte (which gives acceptable result, but is very inefficient).

With "-w", always use "-U" instead.

Thank you so much, not had a clue

Who would have known that :) I sense a project developer is contributing to the discussion here :).

Indeed, this method is cool. It allowed me to sniff the traffic between some poorly documented IoT device and a remote server (unencrypted, what else) via OpenWrt:

[0] https://openwrt.org/docs/guide-user/firewall/misc/tcpdump_wi...

ah, very handy!

About a month ago I found a similar device on aliexpress that has GPS and SIM card slot:

https://www.aliexpress.com/item/1m-USB-Charging-Data-Cable-f...?

And it's only 10 bucks!

> "Sorry, this product is sold out"

I wonder how many things like this are in the wild and nobody's noticed.

Would be even scarier with eSIM, but I suppose it's just a matter of time before we get that.

I bet it's there, someplace, for sometime now.

Wow, do you know it actually works? Seems cool.

Looking at the reviews, it seems that the "GPS" is just a cell tower ID, and the microphone is very quiet.

OK, it's not NSA-level tech, but a $10 hidden mic with location and GSM cellular built into a charging cable, that 95% of us never think twice about is scarey cool.

99.9%