If your original comment is solely about this revised 6 words statement, then, yes, you are correct, the claim is objectively untrue.
I'm no mind reader though, I assumed you were talking about the whole thing ¯\_(ツ)_/¯.
2,324 karma · joined February 1, 2012
If your original comment is solely about this revised 6 words statement, then, yes, you are correct, the claim is objectively untrue.
I'm no mind reader though, I assumed you were talking about the whole thing ¯\_(ツ)_/¯.
> The creators knew that when they wrote that disclaimer and we all know that reading the disclaimer.
This is the idea I'm pushing back against.
Yes, you are very likely correct in your assessment that the creators know that their software will be used illegally.
No, you are incorrect, in saying this is 1- "objectively untrue" and 2- implying the statement might _not_ have some protective qualities.
To take a purposefully exaggerated analogy: you can believe all day long someone committed murder, it still doesn't make it true. You can argue all day long the authors aren't being truthful, it still doesn't make it true.
> Yet the disclaimer is still placed there like it has some reason for existing beyond allowing everyone to pretend something that is happening isn’t happening
I'd agree with this, and, add that, at the same time, (assuming the USA here) it's probably placed there for legal reasons (whether it factually matters legally or not is a question for an actual lawyer, which, objectively, I am not).
> I’m just remarking on the silliness of the disclaimer.
It feels a bit silly, yes, and at the same time... needed?
The statement "We do not endorse, promote, or facilitate copyright infringement, illegal streaming, or piracy in any form", might be poorly written with regards to the fact that just by existing this torrent streaming program _does_ facilitate piracy, but I don't think this was your original argument.
It's not unlawful to use bittorent.
But they are not "objectively untrue". You can argue all day long that you don't believe the author are being truthful, it doesn't make it true.
edit: that being said, in juxtaposition with a copyrighted Marvel image, I could see it being used in court against the author to prove they were all along catering to piracy.
edit2: clearly, I'm not a lawyer
Loud explosions happen all the time in SF. Particularly in the Lower Nob Hill / Tenderloin area.
I lived an Lower Nob Hill for many years and heard countless explosions, most often in the middle of the night (2am-4am) or early hours (6am). Often times these explosions M80s-M1000s being dropped and detonated.
Someone was arrested back in 2019 and the explosions reduced dramatically.
This article[0] goes into detail about it.
[0]: https://maxleanne.medium.com/tracking-san-franciscos-mythica...
I wonder what crypto-currency looked like before the digital age...
Edit: added -currency suffix to crypto :p
Dark background, too many colors, inconsistent spacing, inconsistent font-size and/or family, some links appear fully pink with pink underline, some links aren't pink and only have the underline, inline <code> is blue, but large code blocks are the same color as regular text – on black background, etc.
I had to stop reading unfortunately.
Saying that Natasha and Boris both choose a prime number and then "create a safe" with it, is the same as telling someone that to make cake Alice and Bob went to the store and bought flour and eggs.
If you want a real, good and visual explanation of _how_ it works, with simple maths, go watch Computerphile's video[0] about Diffie-Hellman.
Well, that’s kind of the problem isn’t it?
Yes, you can put bogus URLs, but it’s far from a great user experience
50k corresponds to the money they made with unrelated bug bounties.
I wish they would fix the title so that it properly calls out zendesk refused to pay for a serious bug.
Same thing happened to me years ago. Interviewed with them and it was the worst “screening” experience I ever had. After getting a rejection email, I thanked them for their time and said I had feedback about the interview should they want to hear it. They said yes, please.
Sent my feedback, never heard from them again.
I can't imagine someone calling themselves a developer finding writing asciidoc difficult. It isn't any harder than markdown. It only has a slightly different syntax[0], and more features.
I've also faced a lot of resistance from people when asking them to migrate from markdown. My, unfavorable, opinion is that it's simply the usual reluctance to change and unwillingness to learn something new, deal with the short term pain of learning, despite longer term advantages.
[0]: https://docs.asciidoctor.org/asciidoc/latest/asciidoc-vs-mar...
I would love to know how one can get what I'd imagine is at least a 6 figures contract with the government? How does this work?
I imagine the author of FlyCASS must be making a good amount of money off their product.
They wouldn't, for example, just barge in an oss project with arguably low value statements like "Python 2 is retiring in thirty months. Calibre needs to convert to Python 3."
Some programmers (like myself) have little patience for people they consider should know better and are wasting their time. These same programmers are far more charitable to newbies because they know newbies are still learning.
> Remember that this is the guy who said he would personally maintain python 2 because he didn't want to rewrite calibre for python 3 [0].
I read his "I am perfectly capable of maintaining python 2 myself." as "I am perfectly capable of maintaining [calibre running on] python2 myself", which is completely different.
I'm sure some people might also find his answer quite terse and dismissive ("No, it doesn't."), but I read it as a simple statement of facts, using the same tone as the original bug report, which itself is quite terse and imperative "Python 2 is retiring in thirty months. Calibre needs to convert to Python 3."
However it is loaded with so many footguns that I spend my time redoing and debugging others engineers work.
I’m hoping this new tool called « timoni » picks up steam. It fixes pretty every qualm I have with helm.
So if like me you’re looking for a better solution, go check timoni.
One particularity of the EAV system is that you end up having tables with hundreds (and growing) of columns. It made Magento itself extremely hard to work with and optimize. I hope they moved away from this model since.
To be fair, this was before nosql databases were a thing.
[0]: https://en.wikipedia.org/wiki/Magento
[1]: https://en.wikipedia.org/wiki/Entity%E2%80%93attribute%E2%80...
Very long, windy and hard to parse sentences.
For example, Part 2
> There are two basic techniques that you can employ when analyzing malware. The first being static analysis and the other being dynamic analysis.
> Static analysis uses software tools to examine the executable without running the actual decompiled instructions in Assembly. We will not focus on this type of analysis here as we are going to focus on actual disassembled binaries instead however in future courses we will.
> Dynamic analysis uses disassemblers and debuggers to analyze malware binaries while actually running them. The most popular tool in the market today is called IDA which is a multi-platform, multi-processor disassembler and debugger. There are other disassembler/debugger tools as well on the market today such as Hopper Disassembler, OllyDbg and many more.
> A disassembler will convert an executable binary written in Assembly, C, C++, etc into Assembly Language instructions that you can debug and manipulate.
> Reverse engineering is much more than just malware analysis. At the end of our series, our capstone tutorial will utilize IDA as we will create a real-world scenario where you will be tasked by the CEO of ABC Biochemicals to secretly try to ethically hack his companies software that controls a bullet-proof door in a very sensitive Bio-Chemical lab in order to test how well the software works against real threats. The project will be very basic however it will ultimately showcase the power of Assembly Language and how one can use it to reverse engineer and ultimately provide solutions on how to better design the code to make it safer.
> In our next lesson we will discuss various types of malware.
could be written:
> There are two basic techniques that you can employ when analyzing malware: static analysis and dynamic analysis.
> Static analysis examines the executable without running it. We will not focus on this type of analysis here, however in future courses we will.
> Dynamic analysis uses disassemblers and debuggers to analyze malware binaries while running them.
> A disassembler converts an executable binary into Assembly Language instructions that you can debug and manipulate. There are many disassembler/debugger tools available such as Hopper, OllyDbg, IDA and many more. The most popular being IDA, a multi-platform, multi-processor disassembler and debugger.
> Reverse engineering is much more than just malware analysis.
> At the end of our series, we will use IDA in a fictional scenario where you will be tasked by the CEO of ABC Biochemicals – a very sensitive Bio-Chemical lab – to ethically hack his company’s bullet-proof door control-system.
> The project, while basic, will showcase the power of Assembly Language and how one can use it to reverse engineer black-box binaries and ultimately find solutions to make the code safer.
> In our next lesson we will discuss various types of malware.
I wonder how much money in total they represent, and if CrowdStrike would have come out better saying "We've immediately allocated $X amount of funds to making sure this issue won't happen again" instead of dividing in x * $10 uber eats insults.
Opting-out isn't "making a scandal".
You can both opt-out and "talk with the people who make the laws", one doesn't preclude the other.
> If the law is like that, it's because we have a "majority" (unless democracy is cheated) who voted for such things
That is an idealistic view not grounded in reality at all.
Your original comment at the top of the thread implies the engineer who wrote the blog post is a 1x engineer because they spent so much time finding and fixing this bug.
A "workaround" isn't an adequate substitute for actual the understanding and fixing of the root cause of a bug.
What you think is a 10x developer is, in fact, a short-term 10x developer, medium-term 1x developer, long-term -10x developer. Their work while seemingly great at first is just accrued debt with an incredibly high interest rate. But they're rarely the ones fixing it.
Now, like everything, a balance needs to be struck between spending hours fixing a bug _the right way_, or, finding a temporary workaround. The real 10x developer is incredibly good at finding this balance.