I don't think that's describing nano or pico, at least, no version I've ever used had those keys doing useful stuff. Maybe this is supposed to reference some other editor?
3,881 karma · joined March 16, 2011
My books: https://rachelbythebay.com/store/ - The Stupid Hour (2013) and The Bozo Loop (2012) - a trip into the world of systems administration, programming, networking, tech support, and living in Silicon Valley. Also available on Amazon!
https://rachelbythebay.com/ - top page, mostly leading to:
https://rachelbythebay.com/w/ - writing about software, technology, sysadmin war stories, and more.
Past project:
http://scanner.rachelbythebay.com/ - Fully parallel software-based radio scanner: puts standalone hardware scanners and mere online streams to shame. Fresh, local, unfiltered.
I don't think that's describing nano or pico, at least, no version I've ever used had those keys doing useful stuff. Maybe this is supposed to reference some other editor?
<me> team: hey, sanity check this please: hsh -A "dumb_thing && other_thing --foo --bar" <teammate> shipit
[ I type the command ]
<me> ok, running as job 1234
The last part was a courtesy done so that they could watch the progress of it too without having to dig to find my request. It also meant they could kill it easily if something went wrong and they couldn't raise me for some reason.
Tools like this are best used outside the solo realm.
And yeah, physical machines, not VMs. Sometimes they're blades, sometimes they're sleds, but I mean real hardware made out of metal that you can pick up and use to defend the datacenter if you have to.
(Although, honestly, I was talking about global counts in the million+ range when I wrote it since it was referencing the past, but by now, a region with a million+ is not far-fetched.)
I love finding out that this stuff works.
The rest of the network doesn't care what they look like at certain scopes. Those devices just know to route it to the next hop, and when that next-hop is your box with a bunch of interfaces/aliases/whatever configured, it'll just handle it.
Try it, you'll like it.
(Edit: IPv4 here, hence /32. No such foolery needed with v6.)
Things change...
What actually happened that night is far more complicated, and has nothing to do with people intentionally disconnecting the site from the internet.
Of course, the ones who see your name dialing in and then spot you outside the room a few seconds later will be confused at first, and later may get annoyed with you, but remember, they were the ones who were being abusive.
Important to note that this is Envoy the company, not Envoy the pink mustache factory thing used to let people do terrible things with HTTP.
Random note: red teams <3 the networks used by "room tools" and the like. They usually have access to all kinds of tasty tasty data!
The radishes were neat since they managed to do what they did from whatever power they could scrape from their solar cells. This is impressive when you consider they were indoors! They also had some 802.15 type thing going on, albeit with funky little boxes scattered throughout doing gateway work. I was disappointed when that project was discontinued before it got very far.
You like owning your output, right? Don't risk it.
I knew it was probably trouble just from a glance. Knowing this topic would bring out every single nitpicker, I did the actual research to be doubly-sure before writing the post.
You might be surprised how much extra shit goes into my posts just to avoid the inevitable backlash. It's not good enough to have a reasonable amount of knowledge. You have to go well beyond into the arcane to avoid the sniping from this crew.
And even then, well, THE ONE shows up time and again.
Not saying it's being used here (I honestly have no idea), but it's not that much of a stretch.
I figured they were tied into the marketing feed that gets updates when people register for "all in" forwarding.
It's a good opportunity to get some idea of how quickly things will move, and whether the other end is willing and able to have a solid chat at that time. This applies to being either party in the chat: the asker or the asked!
What's far more annoying is when the [typing] indicator goes on and stays on for a couple of minutes, at which point you are "rewarded" with a wall of text. By then, they have filibustered the chat, and are probably three steps down the wrong road if they got off on the wrong foot, and they need to be backed up and pointed in another direction.
If they start small and evolve it as a natural conversation with back and forths, then a whole lot of needless typing can be avoided.
Wouldn't it.
Put another way, some bad situations are not accidental. If you try to fix them, you become the problem in the eyes of those maintaining it.
A couple of days later I caught up with the people allegedly responsible for this stuff in the bigger review meeting. "Shouldn't you open a SEV because you are shipping stuff that can't possibly work and aren't catching it pre-release?" The response was a lot of hand-waving and stupid manager-speak that boiled down to "no, go away".
I basically wrote them off at that point. If they could act that way and get away with it by way of implicit acceptance from upper management, that's just the way it was going to be.
I see the quality is as high as always.
You can't connect to that over the Internet. Of course, from what little has been shared here, it's not clear exactly what you are up to and whether that address being in there makes any sense.