57 karma · joined November 28, 2018
Been there done that - SRE/DevOps/SecEng/SysEng/SoftEng
set -euf -o pipefailHaha. Fair enough!
I think need is a strong statement in this context.
echo $(( 1 + $(grep 'cpu cores' /proc/cpuinfo | head -1 | awk -F ':' '{print $2}') ))
Choosing shell vs. [insert modern] programming is a matter of trade-off of taste, time, $$$, collective consensus (in a team setting) and so forth.[edit]: Forgot code syntax on HN.
You know that no one uses Bash these days right?
Fish shell, Zsh are the much newer and friendlier shells these days. All my shells run on Fish these days.
I have to tell you that my shell ergonomics has improved a lot after I started using fish shell.
But to your point, _why_ is Bash awful?
The maintainer apparently has no transport security concerns. It takes literally two minutes to set up TLS these days
- Would love to see the ability to develop custom NiFi processors in Go/Rust/Elixir etc.
- XML is a big pain in the rear.
- Being container-aware is big win. Stateless is even better.
I see a good opportunity there for users like me to explorer NiFi's capability in the future.
> They both schedule jobs and move data according to control flow topologies that you build in a GUI, right?
Airflow on the other hand is designed to run scheduled jobs (whether it be batched or otherwise). The 'job' can really be anything - build / data processing pipelines, system configuration management pipelines and so on. In Airflow parlance, one can create connected DAG's as pipelines that massage the data in a way you intend it to.
They both share some commonalities but I do gravitate towards their use cases being subtly different and an important one highlighted above.
:-))))
One day in some utopia probably.
I as a user of BT stack do not have to worry about whether it is switched on or off. This is what I mean by _secure by default_.
Downvoter - thank you. I took time to explain what I mean this time :)
You are missing the point.
Ever heard of secure by default?
Fair enough.
Or to put it another way, it's alive and kicking ass :-)
This is absurd. Dude, let me be clear - Just because you write Java all day long does not mean that there are hundreds if not thousands of embedded system developers who engineer (quite passionately!) the thing that powers your SSD or your wireless card or the thing that heats your home.
We often take these substrates (in this context - the firmware and device drivers etc.) for granted in the modern hardware and often fail to even acknowledge them. I am not one of them and I vehemently defend these silent heroes of our generation.
Yes.
> But if the media is unwilling to budge should we just make a new word?
Not sure how that will pan out :-)
The way I see it, `going fast and breaking things' is an iterative process. IMHO, it should not be viewed as `go fast, break things and _never_ iterate to fix things'.
Just thought I'd toss my two cents on it.
> 2. How come that someone thinks of himself/herself that he/she has the right to say who is a hacker and who is not.
No idea why you feel binary. If you like to call yourself a hacker - fuck it - go for it.
The connotation in the beginning were that hackers were pioneers, thinkers, achievers and great motivators. Over time, the meaning has been mutated and engineered by the media to mean `malicious' and `conniving' thieves/criminals.
To this day, I still stick to the original definition of a `hacker'. I don't give a two fuck about what the media likes to call it.
Would you be interested in PoC'ing it out for such a trivial project?
Aha. Indeed. I would prefer to have someone actively working in ML to weigh in as well.
Hehe
I apologies but that's disappointingly vague..
Close but no cigar.
But seriously, correct me If I am wrong but if I were to propose a solution to defeat this `ML web crawler' confidence in it's results, then the first thing I would do is to feed the internet with invalid data. How does ML-based analyzers deal with this kind of data set?
Last time I checked Tor's technical paper (probably been 10 or so years), it stated the fact that a relay? node in between can only decrypt the information required to route to next hop and not the actual packet's payload. Is that correct or am I dreaming?
Also, I recall that if someone malicious flooded the tor network with malicious exit nodes, then all traffic details can be `inferred' right? i.e., the assumption was that exit nodes need to route the packet to destination thus it needed to look at every packet but couldn't infer the originating IP address (based on my dated knowledge :))
If a malicious person now floods the tor network with bazillion exit + relay nodes - then essentially all contents (payload + IP src/dst) can be aggregated. Is this still problem in tor network?
Effort and RFCs are underway to establish what would become part of TLS protocol stack. One of which is eSNI (encrypted SNI).
Woah. Hold your bong son! ;)
Any reference to documentation or any information of what you mean by `sold' on the open market?
If you wanted to prove a point by saying that internet is an insecure medium then yes I agree but `tapped' and `sold' is a whole different ball game that I am not aware of. At least in the internet I know of.
Throwing GDPR and `ftw' in the same sentence. Hmm. No GDPR does not work that way hah. At least not in the global context.
GDPR only applies to you _if_ you happen to be a European Union citizen.
What do you mean by `resource management modeling` in this context? Do you mean `capacity planning` or `system scaling planning` or something else altogether?