HN user

fogof

573 karma
Posts1
Comments120
View on HN

Do you think there is a tradeoff in this case? If so, what is the best counterargument against making PACER records free? I think it's important to note, as the article does, that these records are already "public" (that's what the "P" stands for) what's at issue is whether you should be charged a fee to access them.

I am looking at the last image in the article, captioned "The encrypted message instructs the viewer to appease the gods with offerings". The picture shows ... a person kneeling in front of a throned figure, offering something with both hands. Is something about this message supposed to be hidden?

Inside ArXiv 1 year ago

Not sure I agree with the comment you're responding to. But the article discusses some of their funding troubles, and the main mage of arxiv.org itself has a donate link. So I think perhaps the media presence might be motivated by a desire to fundraise (and IMO they absolutely deserve funding because of the important work they do).

A lot of thoughts in this thread on what academic papers are or should be, let me give my own opinion as a person who tries to write papers.

Papers should be structured like fractals - that is, they should be "self-similar". The main text of the paper after the introduction should go into all the necessary details demonstrating the origins of the idea and proving that it has value. Then the introduction section should summarize all this, and take a less rigorous tone. The abstract should be a summary of the introduction. And then the title should summarize the abstract. If you really have a lot of technical work to do, maybe you can write a super long appendix and have the main body summarize that.

I myself probably spend as much time reading paper introductions as I do reading paper bodies, which means that probably 90% of the papers I read, I only read the introduction. I do this because I enjoy it more - I like new ideas, and the intros are a great way to get a lot of them. This blog post reads like a great paper introduction to me. It's easy to trick yourself into believing something is easy though, so an academic paper would have to back this up with an experiment.

He says in the very first paragraph:

I lost a series of pitched battles against Pytorch and biblatex, so I figured I’d just write a blog post instead.

So I think your accusation of his burying the lede on the lack of experiment is unwarranted.

What rubs me the wrong way about the mhils Github response is that it fails to answer the question that the commenter asked: Is there or is there not a target date for the next release (and if so, what is it)? It's fine to charge money to move the date up, but it seems like if you are going to make that offer, you should try to tell the person how much time they would actually be buying.

I disagree that this would have been the right thing to do. There's nothing wrong with explaining why something could be useful in an open source project - if the reason seems like something important that a lot of other users of the software would also need, the maintainers of the software might want to know about it so that they can add the feature or fix the bug sooner. It can also help if there's some way of working around the problem.

Calling the developer extortionate was unreasonable, but I don't think there's anything wrong with the first message.

They address this at the end of the article

Our calculations account for air drag and the effects of gravity.

While the return velocity is dependent upon a number of factors, firing angle is extremely important. Bullets fired at an angle maintain their angular ballistic trajectory and are less likely to tumble, allowing them to pick up more speed on the way down.

You make a good point about the infographic showing a cartridge being fired, but as far as I can tell there is only one infographic on the page that actually shows this. These factors make me suspect that you didn't actually read the article to the end before criticizing it. "Intellectual rigor" indeed.

Anyone can see what amount of money one address has put into Tornado Cash, so it’s no surprise that we can estimate how much money North Korea has put in. The whole reason they do put that money in, though, is so that they can have a different account take that money out, and have it not be clear where the money came from. For a sanctioned country, that output seems much more spendable.

In fact, someone would appear to be trolling the authorities by sending small amounts from prohibited Tornado Cash addresses to prominent people; those transactions cannot be declined, but receiving such a "gift" is technically in violation of the sanctions.

How can I be violating sanctions as a result of someone else’s actions? I’m not a lawyer, but I imagine one could just argue that receiving an output from a transaction that touches Tornado is considered different from interacting with Tornado oneself.

I would personally recommend Susskind’s videos on cosmology. Seems like the main ideas are surprisingly simple and I walked away feeling like I had learned something.

Not sure how the second example of buying a shiny new wallet is different from the first example of buying a shiny new cup. Seems like a better example for “wabi-sabi” would be continuing to use a wallet even after one of the flaps breaks, as long as the other flaps hold what you need them to.

The two things I really want from a SSG for my blog are the ability to avoid indexing posts by dates and the ability to link from md files to other md or image files in the same directory. I’ve tried maybe 8 or so of the most popular options and haven’t found this.

Whether or not there's an opportunity cost does matter, but why should this mean that the mining algorithm "paying off anyway" mean it can't be used? If the mining algorithm has an independent payoff whether or not you mine on the main chain, then there's still the same opportunity cost of the mining rewards.

For what it’s worth I think that if people were downvoting you because of your position, they would be downvoting the parent as well. They’re downvoting you because saying “I was going to say the same thing” doesn’t contribute to the conversation.

If you ask a Python developer about [private instance variables], they’ll respond with: “don’t access the instance variables of another class, lol”.

only in Python will the difference between tabs and spaces cause the interpreter to have a heart attack.

The question of making a variable constant came up on Stack Overflow and a Python developer’s advice was “just don’t change it”.

All of these critiques seem to amount to: If I do something dumb, then Python will break on me. While I respect that other languages have protections, it's sort of like asking "why doesn't Python have static types?".