skysight-inc/HackerNews huggingface dataset:
The author has been clear it shouls be pronounced as J.

> Giraffe as jiraffe?
??
> The Fediverse, as a whole, doesn't want to be associated with the web3 space

The funny thing is, ActivityPub is vaguely under the banner of the Semantic Web. Which, at one time, was sometimes called, semi-jokingly... Web 3.0.
I think the inventor of the internet shouldn't have to work another day in his life. In our society that means money.
Why wouldn't everyone roll their own solution? Doesn't seem to be a huge thing to me, but I could be wrong...
None of these points have any legal standing, from a copyright perspective.

https://news.ycombinator.com/item?id=29868199
Correct. Jraphics Interchange Format. :P. My friends and I called it Gif-with-a-hard-G all through the (late) 80s (edit: more like the 90s, but anyway) and unlike now, nobody corrected us then. I never heard the format’s creator pronounce it though.
If you have a cat which uses the litter box without any problems, count your blessings and call it a day. Having a cat use the toilet is counter to their instincts to bury their business from other animals. If they fall in, they’ll be traumatized and start doing their business in other unpleasant places.

I’ve used the litter robot, and honestly I think a plain old litter box is easier to keep clean, and in general better for all parties.
I think the answer is that when the FED prints more money, the "value" of 1 dollar doesn't change much, so the ratio of dollar to euros doesn't change.

Sure with more money, people in the US spend more, US inflation increase, as in stuff gets more expensive, but none of this directly impacts the ratio of the value of the dollar with respect to the EUR.

So the original claim, which is essentially that there is some company called "The US", of which dollars act like a stock, and the FED printing more money is like diluting the stock, is just not true. Dollars don't behave like stocks.
An easy answer would be "we import thousands of packages either directly or recursively, so while we may be able to replicate the work of any one of those (which is unlikely to be true in the first place), it would take thousands+ of engineer hours to replicate all of them, and there was no way of knowing that this one among thousands would be sabotaged."
I live in the US and got Chickenpox as a child, I think from a classic "Chickenpox party". I'm not sure if I was also vaccinated against it or not...

I got Shingles at 25 (I'm 30 now). I didn't believe it at first because I thought Shingles was an "old person's disease". I remember going to the doctor the day it started, and he just prescribed me some painkillers. I said, "I don't think I'll need those I don't feel too bad." He just looked me in the eyes and said, "Oh, you will." It was awful. Some of the worst pain I've ever been in. I laid in bed for almost a week basically hallucinating.

Apparently, Shingles can come up multiple times in your life. I wonder if getting exposed to Chickenpox again would decrease the odds... I don't spend any time around children, so I don't think that's likely to happen to me haha.
I think it is a scam to sell and buy carbon credits while China and India are the biggest polluters in the world and don't even get a slap on the wrist.

I believe climate change is real but political scams take advantage of it.
I prefer to pronounce it Jithub
You are not exactly the first person to say this on this thread. How do I know you yourself are not part of a discredition campaign? Can you substantiate your speculation by pointing out inauthentic popular posts or accounts at least?
In my view, notebooks are the exact opposite of literate programming, and it's a shame some people seem to think it is its pinnacle instead.

The focus on a notebook is the report, not the code. In practice this means that the report structure dictates code structure, not the other way round.

By contrast, the focus of literate programming is the code. Any "reporting" done is strictly to enhance the code, and not the other way round.

I've seen far too many codebases that should have been "code generating a report" reverse that logic and implemented as notebooks instead, in the expectation that the underlying code can simply be exported from the report. Good luck if you need to work on someone's code of that kind. It's its own special kind of hell.
Because npm install has the insane default behavior of adding a fuzzy qualifier to your package.json, for example ^6.0.2 means all of the following versions are accepted: 6.0.2, 6.0.9, 6.7.84
The problem with tree shaking has been twofold:

- JavaScript is a very dynamic language with dynamic property access and a few other features that make it hard to guarantee that the linker won't accidentally remove too much

- historically there was no standardized "module" format until ESM (ES modules) came up (with some time in between with few competing non-standardized proposals), so statically analyzing exports/imports was difficult; in frontend you'd long rely on just creating and reading global variables (i.e. side-effects).

Hence it's been "safer"/easier to create small packages.

But it's not only this. Once you put a mega-package in your repo, it's easy to gradually start relying more and more on the things it gives you. Even if it supported perfect tree shaking, you'd call one method here, one method there, and with each build your bundle size would balloon (which is not good if you could write one line of code while lib method's code is 1000 lines because it supports IE4 and 17 parameters).

Whereas when you rely on small packages, you need to make a conscious choice each time to pick another dependency.

You probably don't care about this on servers written in C++ or Java that much; but on frontend it's a big deal; hell, even when building native apps for Android/iOS you have size limits for the stores submission / limits for the number of methods (tech limitation in Android). Big companies invest crazy money to shrink their native bundle sizes (https://blog.pragmaticengineer.com/uber-app-rewrite-yolo/).
Ask HN: Best stack for ML blog with lots of code snippets, formulae and graphs?
Hey folks!
I want to refurbish my old dusty blog into something new and fancy but without (too many) late nights fighting with yet another static site generator. I want to write more about my experiences working with ML so ideally this would be a tech stack that can easily accommodate maths formulae (nice if it can be a syntax close to LaTeX but I'm not super picky) and interactive graphs (something like a Jupyter notebook widget).
Do you have a setup that works well and that you'd like to share? Thanks in advance!
There are many valid reasons to make code for yourself public, even before discussing the type of license.
This is of course similar to how early human hunters operated - simply chasing down the prey till they fell exhausted. For the average post-doc CS student this will be three to four blocks so the energy trade off is in your favour. However the available calories drops significantly with cryptographers and even though you can drop one after just one block the energy trade off is even.

Fascinating discussion :-)
I posted this earlier, but it got flagged. https://news.ycombinator.com/item?id=29859476
> When it comes to how to store numbers, in English, we read the highest value from the right to the lowest value on the left.

Huh? When I read 24, "twentyfour", the highest value is on the left, followed by less high values on the right, and spoken in that order.

It's actually different in other languages, in dutch for example I would say "vierEnTwintig", or "four and twenty" translated directly, so saying the least high value first. (... However this is only for the two digits, because upwards we'll say "honderdVierEnTwintig", or "hunderd four and twenty")
That's fine, but then the downstream shouldn't complain either when the code breaks, whether intentionally or unintentionally. The contract on paper disclaims all liability after all. There is a social contract and then there is the literal contract. A lot of commenters here seem to be willfully obtuse or simply ignoring the former.
Clickbait has infected astronomy it seems
The author apparently got political, had issues with the law enforcement: https://news.ycombinator.com/item?id=29839786
His twitter post. https://twitter.com/marak/status/1320465599319990272
Note that this would also be the observable effect of simply prioritizing ICMP while dropping other protocols.

Probably a better thing to observe is loss and congestion on normal TCP sockets, using retransmit counters, congestion window collapse, etc.
At my last job we (InfoSec) had the devs fill out "ownership" forms for when they want to include something third-party into the product. Other than forcing the team to do due diligence on the third-party it also made them responsible for keeping it secure and them the people "at fault" if something went wrong due to it.

While it was seen as an unnecessary hurdle set up by us I hope it started some meaningful conversations in the teams and maybe even end up with them "reinventing" the wheel for the better.
That's when you make a case for why you're pinning them, allowing your coworkers to present counterarguments.

If your boss doesn't take your side, at least you can say "I told you" when things go wrong.
Did you use an constraint solver library like Z3 under the hood or roll your own?
> jq does have a learning curve, but just like any query language, including SQL, first you need to learn the basics of the query language in order to get things to work.

SQL is based on solid mathematical theory, relational algebra. I personally learned that (and tuple relational calculus) in college before learning SQL, which made it easier. It helps making it coherant. Is there something like this for jq? Often when people invent languages that are not based on solid theory, they tend to lack coherence. This can make learning them difficult if you're someone that relies on your mental model of how things "should" work, like I am.
The first company I worked for in the 90s used a floppy disk for each version, double floppies if it was a release version sent to the customer. A section of a drawer in a filing cabinet was allocated for each product. Versions were stored and retrieved using SneakerNet.
Github and NPM belong to the same company, Microsoft.
> "Looking further afield: it seems likely that the end of internal combustion engines will be in sight. Some countries are already scheduling a ban on IC engines to come in after 2030—electric cars are now a maturing technology with clear advantages in every respect except recharge time. Once those IC cars are no longer manufactured, we can expect a very rapid ramp-down of extraction and distribution industries for petrol and diesel fuels, leading to a complete phase-out possibly as early as 2040."

At this point the proposed bans are on the sale of new vehicles that run on fossil fuels. As far as I know, no one is planning to outright ban ICE vehicles yet. Headline writers consistently get this wrong, because making the policy sound more extreme than it is attracts ad views.

> "As about half of global shipping is engaged in the transport of petrochemicals or coal at this point, this is goin to have impacts far beyond the obvious."

Huh, that's a lot. If that's correct, it's a lot more than I would have guessed.
How to archive a website that's shutting down soon
> is that having such high fatality rates is a problem for a virus that hopes to become a pandemic

Somebody forgot to tell that to smallpox, which had something like a 25 or 30% IFR before vaccines came around. And there were lots and lots of pandemics of that!
Not OP, but to answer your question: no, not all the time.

If you take it before bedtime, it sedates you in a deep sleep. But 3-4 hours later, if you wake up, it would be like you didn’t take anything.

You may even have trouble going back to sleep if you wake up early.

Of course all this varies greatly for every individual.
It's among the most hated environements because of configuration nightmares, crashes and broken features. Not gonna say I'll miss it.
That depends on how long it takes you between the moment when you are contagious, and the moment that you drop dead.

If you are contagious on day 2, symptomatic on day 17, and drop dead on day 180, such a disease will happily spread through a population, despite having a 100% fatality rate. There will be no evolutionary pressure for that virus to become less lethal, just like how there's no evolutionary pressure for people to live to 200.
I do free work for open source _a lot_. I have a rather controversial opinion on this. I don't think I should be paid for my work because the moment money comes in I have to be responsible for the work I was doing for fun. I enjoy building cool things others can use for free and I want to reserve the right to respond to feature requests with a simple "PRs are welcome! :)".

I get my paycheck from my employer and I have always been successful convincing my employers that I do open source work on the side for my own interest.
*I revoke my comment. Child comment is correct.
Can you really say, with a straight face, that you inspect the diffs of your entire dependency closure every time you deploy an update? With the level of scrutiny required to detect a maliciously-obfuscated security exploit?

If you can, you're an infinitely more diligent developer than I am, that's for sure.
> If NPM gets a DMCA takedown request they will absolutely have to fulfill it.

Assuming the package is released under a Free Software licence, what grounds would there be for a DMCA takedown?

I suppose a developer could include the lyrics to a pop song in their code (possibly encrypted), and then tell the copyright holder about it (since I don't think you can make a DMCA request on behalf of a copyright holder without their permission), but I would hope that such a poison-pill would be caught long before the package became widely depended on.

Perhaps you're thinking someone would risk perjury(?) charges for making a false DMCA request against their package, and NPM would act on the request without questioning it; but remember that NPM is owned by Microsoft and they have previously stood up to frivolous DMCA requests (after a fashion)[0]. That article has the lede: "Software warehouse also pledges to review claims better, $1m defense fund for open-source coders".

[0] https://www.theregister.com/2020/11/16/github_restores_youtu...
Levocetirizine doesn't cross the blood-brain barrier like other antihistamines such as loratadine does.
The g is silent. It's pronounced "if".
Imagine you have a car problem and take it to a mechanic. Mechanic says: "You have to rebuild the engine ASAP, otherwise the engine is going to explode and you lose the whole car". You pay for the engine rebuild, the car is still broken and the mechanic says: "Oh, I did not know what is wrong with your car, don't hindsight me."

What would you do in such a case:

a) agree that you are over the line with your complaints and keep listening to the same mechanic

b) go to someone else with your mechanical issues and sue the mechanic for the engine rebuild

c) something else?
Don’ let that stop you! There are a ton of free assets both for Unity and Unreal. Check out e.g. the free category in the Unreal marketplace.

https://www.unrealengine.com/marketplace/

Search for the RPG category. There are whole RPG systems you can plug into Unreal which you can buy for laughably little money. (No affiliation, I just like what Epic is doing with the engine)
You're using a VCS I presume? Why not just rollback?
Canada resists pressure to drop vaccine mandate for cross-border truckers
Ask HN: Is indie dev more like engineering or research?
I think even philosophy can withstand knowing the speed of light and incorporating it into the framework of 'when things happened' so that it agrees with our understanding of the universe instead of not.
In the 90s, there was no chilling effect (search it) of persistence being known, or the consequences of such being understood.

People treated posting on BBS like yelling into the grand canyon, and a million other beautiful stories from a million other perspectives.
Forgot .45 vs 9mm, and eMacs vs vim
You can't legally retract opening up software source code under most if not all popular open source licenses.
I haven't had issues yet, but it's considered bad practice for a reason. What headaches am I in store for?
And we find out that the internet is mostly wrong. Confirming what we already knew.
They can and they did, but it still feels malicious because they intentionally reverted the maintainer's latest version, which is the author's will on their creation.

It's a bit like me going to my bank to close the account and instead they throw me out and keep my money.

Honestly I don't understand why microsoft did anything at all. Can't people just pin a version?
But.. public keys are public? Its not sending your private keys to anyone.
Ironically, of course, one such label is the adjective "meaningless", which is rather unnecessarily binary in nature.
I don't understand why. It's his code to break if he wants. But I guess when you use a social media service to host your code these are expected and normal results.
Offline cache with Yarn 2+ protects against this and other network failures when building CI, for example.
I believe Giraffe is pronounced Jiraffe?
5-10% is very generous
Upwork is a red herring in this case. As frustrating as it may be that Upwork wasn't more helpful in resolving this case, the current state of affairs is as follows:

1. The author (freelancer) did $12.5k amount of work that he wasn't compensated for

2. The owner of the CC that was "accidentally" charged $12.5k received all their money back through bank dispute

3. Upwork was able to claim their cut for the $12.5k worth of transaction that occurred between the author and Robin

4. Robin received $12.5k amount of work without paying a dime

Robin needs to pay the author back the $12.5k he is owed. If Upwork isn't willing to help reclaim the debt, he needs to sue Robin directly for the amount. It's very strange how much good will the author is willing to show towards Robin given how Robin is the only entity in the story who got away with all the spoils without paying a thing.
Have you considered that the behavior you're describing is far uglier.
No. This is useful against assholes, not fanatics.

Assholes will opportunistically shit on anything that isn't too difficult for them to worm their way into. Crapping up DNS by making all unknown domains resolve to an ad server? Sure. Making unencrypted HTTP unusable by inserting ads and blocking keywords? On it. Blocking any port they haven't heard of? Hey, who needs ports 70 or 23 anyway, am I right? Assholes can be state actors in a state which doesn't go to extremes censoring the Internet, or they can be companies or other institutions with assholes dictating IT policy.

Fanatics will poison BGP to blackhole YouTube and, if it knocks out YouTube for a couple neighboring countries, well, those countries either agree with them or are kiddie-porn-hacker-atheist-terrorists who need to be put in their place by Morally Righteous Leaders anyway. Fanatics will kill anyone who sends or receives encrypted messages the authorities can't read, just on general principles.

HTTPS and maybe some tricks with DNS will protect you from assholes. You need legitimate tradecraft to thwart fanatics, and even then you're rather likely to be killed by a government that really doesn't care enough to even stage a convincing accident.
The question obviously doesn't mean any egg, it is asking about chicken eggs. But the question still always seemed ambiguous to me only because the terms are vague. If you define a chicken egg as an egg that was laid by a chicken, then it is the chicken first. If you define it as an egg that a chicken was hatched from, then it was the egg first. Define your terms and the question is simple to answer.
> Why wouldn't everyone roll their own solution? Doesn't seem to be a huge thing to me, but I could be wrong...

Laziness; and people’s infatuation for dependency trees, especially those in the Node.js & JavaScript ecosystems.
because they're leet haxxxor dickwad
How about using dependencies but pinning the version and only updating if you know what the update contains?

I'm still continually baffled that we ended up in a world where automatically accepting updates from every dev and their dog is not just the norm but recommended practice.
Because of version locks. Normally you install “^X.Y.Z” which means any version at major X with at least minor Y and revision Z. For more conservative codebases you install “~X.Y.Z” which also locks the minor.

npm install will traditionally install the most recent packages that match your constraints. You need “npm ci” to use true version locks
is this good or bad to be honest?
Someone could have added non-free third-party code into the package (intentionally or inadvertently, it doesn't really matter).
I think history (20+ years from now) will prove that for all but the smallest, almost toy, systems, dynamic typing from the 80s and 90s was a mistake.

The maintenance burdens these languages are creating will make Cobol look like a kiddie bike with training wheels next to monster trucks.
No. That funding is right on the NED website.
I also like doing this, but with node, you have a massive tree of thousands of files. It's crazy and gross.
If package A depends on package C at version 1.0 but package B depends on C at version 1.1, what version of C will be pulled in?

Dependency management is not as simple as only upgrading one direct dependency at a time after careful review.

The NPM ecosystem is particularly difficult to work with as it has deep and broad transitive dependency trees, many small packages, and a very high rate of change.

You either freeze everything and hope you don't have an unpatched vulnerability somewhere or update everything and hope you don't introduce a vulnerability somewhere.
> Correct. Jraphics Interchange Format.

You do you, but Graphics having a hard G doesn't force GIF to any more than the Amplification in LASER forces the pronunciation of its A, or Stimulated its S, or Emission its E. Or do you and your friends also say "lasseer" instead of "layzur"? This is an arbitrary choice you've made in one case but not the other.
I assume that GitHub have lifted the ban given that multiple of the comments show in the post is posted after that tweet was made.
Alternatively, GrapheneOS supports them as well. https://grapheneos.org/
I wonder if the laser engraver would have enough resolution for something like this? https://www.4004.com/ (quick&dirty black&white version https://ibb.co/HTCxVMh )

edit: quick google finds advertised resolution to be 1000dpi for the engraver, so that 4004 die could be within the realm of possibility. Anything more complex probably would not work very well though.
I disagree with this. Theres nothing about this system which requires the world to be infinite. As an example, check out https://www.badnorth.com/ which uses wave function collapse to generate the islands.

The worlds are carefully tuned and aspects of them are controlled, but the algorithm is the same and I do think this creates worlds or at least aspects of gameplay with great interest.
How is it not a legal issue to intentionally DOS customers servers? I would send a complaint to the California DA’s office for hacking; the laws against which in CA are very liberal.
Given that Debian (and its descendants...) packages a shitload of npm packages, it's a wide stretch to say there is more QA for these packages from the Debian side than there is from the npm side.

The one thing that Debian provides is that in the case there is a security issue, admins worldwide only need to do "apt update && apt upgrade" and they are safe, without having to check all of the software that runs on their servers (as long as said software comes from Debian, that is!).