784 karma · joined November 2, 2019
https://github.com/m3047/
...or...
hackernews3047as@m3047.netmeet.hn/city/us-Tacoma
Socials:
- github.com/m3047
---
It's actually a welfare issue for chickens. They have feathers, and they molt. Just like hair, feathers need methionine. Methionine is very hard to get solely from plant sources. If they don't get enough methionine they eat each other's feathers, not just the discarded feathers (which left on their own they do normally).
I use pointy-clicky software for visualizing relationships and correlations. I use draggy droppy software for building complex data workflows (including ML elements). I use desktop publishing software rather than LaTEX. I suffer industrial interfaces for (most of) my own software (where I am the chief customer) because it's easy for me to sling simple server-side UIs, but there are standalone servers out there which make creating apps (with RFID, QR, accellerometer support) just like, yes JUST like, desktop publishing (especially as you get closer to industrial control applications); one of my faves has a widget which is a "choose your own adventure" dashboard widget so that the users can create a dashboard customized just for them, yes, Inception (granted, that widget does need some configuration which requires a keyboard).
Granted, behind every one of those slick interfaces is a drippy gob of data. I have to create a CSV in the correct format for the visualizer, or surrender to their integrated "partner solutions"; or for a different visualizer I have to create some network services which it consumes for "enrichment". My data workflow tool has generic python "actions" so you can create custom tasks (it presents the data to your scripts using pandas). On very rare occasions I have a need to hack on DTP docs to format obscene amounts of repetitive data; but a lot of the time it's back to making a CSV and putting that in a spreadsheet / database which the software can then utilize for quaintly-named "mail merge". The UI software which I refer to integrates with SQL databases and authorization / access management engines, somebody still needs to set those up; and I stumbled across it in the first place because somebody needed a little (surprisingly little) help connecting to an obscure HTTP resource.
To short circuit a bunch of off track commentary: LLMs are not speaking english to other LLMs to design new LLMs AFAIK. I have never seen a debate or article about whether it is better for LLMs to utilize english or russian for this task. I just don't like the menu that is offered on this ship Titanic, and I'm uncomfortable with the majority of the passengers being incarcerated belowdecks; I'll book different passage, thanks.
This video demonstrates that when it comes down to it the blunt end of law enforcement is oftentimes a shit show of "seems to work for me" and that goes for facial recognition, shot spotter, contraband dogs, drug & DNA tests, you name it.
That means that if an officer is caught lying on the stand – as shown by a
contradiction between their courtroom testimony and their earlier police
report – they could point to the contradictory parts of their report and say,
“the AI wrote that.”
IANAL but if they signed off on it then presumably they own it. Same as if it was Microsoft Dog, an intern, whatever. If they said "the AI shat it" then I'd ask "what parts did you find unacceptable and edit?" and then expect we'd get the juicy stuff hallucinations or "I don't recall". Did they write this, or are they testifying to the veracity of hearsay?From what I've seen reports written by / for lawyers / jurists / judges already "pull" to a voice and viewpoint; I'll leave it there.
> You can drop arbitrary logs to stay within ingestion rate.
Another way I've heard this framed in a production environments ingesting a firehose is: you can drop individual logging events because there will always be more.
"Bug parts" (as in "acceptable number of bug parts per candy bar") logging should include the precursors of processing metrics. I think what he calls "wide events" I call bug parts logging in order to emphasize that it also may include signals pertaining to which code paths were taken, how many times, and how long it took.
Logging is not metrics is not auditing. In particular processing can continue if logging (temporarily) fails but not if auditing has failed. I prefer the terminology "observables" to "logging" and "evaluatives" to "metrics".
In mature SCADA systems there is the well-worn notion of a "historian". Read up on it.
A fluid level sensor on CANbus sending events 10x a second isn't telling me whether or not I have enough fuel to get to my destination (a significant question); however, that granularity might be helpful for diagnosing a stuck sensor (or bad connection). It would be impossibly fatiguing and hopelessly distracting to try to answer the significan question from this firehose of low-information events. Even a de-noised fuel gauge doesn't directly diagnose my desired evaluative (will I get there or not?).
Does my fuel gauge need to also serve as the debugging interface for the sensor? No, it does not. Likewise, send metrics / evaluatives to the cloud not logging / observables; when something goes sideways the real work is getting off your ass and taking a look. Take the time to think about what that looks like: maybe that's the best takeaway.
IOW: who owns the backups owns the data... until proven otherwise. My default presumption from space is that 1) there are document management policies and 2) document management policies apply.
We call this the "scream test" in BOFH land.
No one is innocent. I refuse to use LE and operate my own CA instead, and as a consequence of scareware browser warnings I publish http: links instead of https: (if anyone cares, you know to add the "s" don't you?). I run my own mailserver which opportunistically encrypts, and at least when it gets to me it's on hardware which I own and somebody needs a search warrant to access.. as opposed to y'all and your gmail accounts. I do have a PGP key, but I don't include it on the first email with every new correspondent because too many times it's been flagged as a "virus" or "malicious".
Clearly we live in a world only barely removed from crystals and ouija boards.
Location: Tacoma, WA, USA
Remote: Sure, that's an option.
Willing to relocate: No, but willing to drive around the greater Pacific Northwest.
Technologies: Python, Redis, C, DNS, Ignition SCADA / HMI, SQL, Bash, Linux, TCP/UDP,
old school ML & numerical methods, threat hunting, electronics, handy
with a wrench, dangerous with acetylene.
Résumé/CV: https://github.com/m3047 https://www.linkedin.com/in/fred-morris-03b6952/
Email: m3047-wantstobehired-t5b@m3047.net
Let's have a conversation, I like working with people. Not looking for the same old thing, have had a business license since 1984; prior to 2000 about a third of my work was firm bid (why did that go out of fashion?). Technologist and problem solver. Cloud skeptic, but I use what works. I prefer contracts to promises. W2 / contract: it depends, let's choose the correct vehicle for the scenario, and risk has a lot to do with it. Part time, seasonal, campaign... it's all good.In the middle are Mule, Rabbit, Kafka, ZMQ.
At the other end is UDP multicast, and I still use that for VM hosts or where I can trust the switch.
So, my impression from the doc (and a quick browse of the code) is that this is a tool for monitoring DNS caching / recursing resolver (RD) performance, not authoritative. If performance really matters to you, you should be running your own resolver(s). [0] Granted, you will quickly realize that some outfits running auth servers seem to understand that they're dependent on caching / recursing resolvers, and some are oblivious. Large public servers (recursing and auth) tend to "spread the pain" and so most people don't feel the bumps; but when they fall over they fall over large, and they bring some principles (and thereby create "vulnerabilities") at odds with what the DNS was architected for and throw the mitigation on the other operators, including operators who never accepted these self-anointed principles to begin with.
I have a hard time understanding how DNS is adding 300ms to every one of your API requests... unless DNS is both the API and transport, or you're using negative TTLs /s.
Good doc, by the way.
[0] Actual resolvers. Not forwarders.
(An Alibaba /16? I block not just 3/8, but every AWS range I can find.)
pam-config -d --env
[0] Crowded elevator atrium. Multiple elevators running. Elevator wants to close, another one is coming (oh! I heard it "ding"!). Somebody is holding the elevator which wants to depart and trying to wave me in. Why doesn't somebody push them out?[1] I'm at a stop sign. Some complete idiot is trying to turn left onto the street I'm leaving and waving me to turn left in front of them. Fuck no! I turn in front of you, somebody rearends you, you fly forward into me: my fault! You should be able to make this turn, if you can't go around the block! [2]
[2] I could go out of my way and turn right. Or I can just wait and see what happens.
I think you've got that backwards. Crims gonna crim. A clever hacker will evaluate ALL the risks, whereas a moral flaw blinds people to risks. Doesn't mean somebody can't have both attributes.
I quite literally stole an education, and there's a college transcript to prove it. I was a clever hacker, and I worked hard; I was aided and abetted by the college administration, inducted into the Masters candidate ghetto as an honorary member. When they made it a felony I quit that path, and following Hunter S. Thompson's advice [0] I went into business so that I could continue learning "on the job". (Nowadays they call it "OPT". Served today with a very thin glaze of sarcasm.)
During that tenure I met people who wrote theses for a living, who appreciated my industriousness and offered to admit me to their fold. I drank with foreigners ("muslims") who wanted information I might have or be able to obtain; I suggested that they get their home countries to forge documents and and then get admitted as students.
I've quit jobs after an appropriate "honeymoon period" when I still hadn't been furnished documentation demonstrating that we had customers' permission to be doing what we were doing. I've quit jobs when government compliance was considered a game rather than a minimum standard of performance. [1]
I pass government background checks just fine; no reason I shouldn't. I get the "dgaf" attitude, but I strongly suggest getting it in writing. Doing things off the books is a cancer; and it's contagious, like that 10,000 year old dog cancer which now moves from host to host.
[0] "When the going gets weird, the weird turn pro."
[1] If you need somebody who takes risk assessment seriously, we should talk.
(I have no commercial connection with them.)