skysight-inc/HackerNews huggingface dataset:
A more better option would be "like Gin or like Ginkgo" because it makes it obvious that the "gift has a hard G, therefore..." people have made a mistake.

So many people come up with so many fake rules for why it should have a hard G, but there are only two real rules for names, and, yes, GIF is a name (of a format). 1) If the named thing can't speak for itself, the people who named it dictate how the name is pronounced. 2) If it can speak for itself, it dictates. Nobody who isn't the named thing or its namer(s) gets to say how its name is pronounced regardless of what they think of the spelling.
The advantage of this kind of tile-set, is the tiles don't have to be some fixed basic size. If you have a 2D Cartesian grid to fill, you could add arbitrary sized tiles (1x2, 2x4, etc) and they don't all have to be rectangles... So you could have variable sized features in your tile-set.

You could also allow the user to "paint" the grid with probability modifiers to adjust what populates.

You could combine... uhh... layer generative methods together. Start with a 2D grid. Adjust land elevation probabilities with underlying shapes (pick your generative method). Let this algorithm generate based on the "continental plates" from the previous step. Then apply a wind/water erosion algorithm.

Permute possible underlying algorithms in each layer...
a special collection at Posnan University, Poland

http://lib.amu.edu.pl/masonic-archives-room-masonic-study-ro...
I would gave said rather that the training happens in the brain and in the whole body (joints, muscles - strength, flexibility, movements, space understanding, all these require more than a brain only).
Had this bouncing around my subconscious, thanks for crystallizing it.
Glad to see this, tying up voting rights with citizenship is a weird hang up, specially in local elections. I'm sating this from a south american country that gets a lot of immigrants, the only people not ok with this here are race nationalists.
It's incredible how far we have come
I know it's bad practice, but I just checkin vendor files/libs to source control. Makes auditing new releases of libraries a bit easier. Assuming they aren't binaries of course.
Wasn't this the literally exact thing NFTs was supposed to prevent?
> now what

Now pin an older version and if you want fork it and develop it yourself. Whooptidoo.
No, the fallacy is "the economic boom is good, so climate change is OK".

Noting the existence of the boom isn't the fallacy. Advocating for it is.
Or, "Do you pronounce 'GIF' like 'giant/ginger/gibbon' or incorrectly?
I get how they feel, but why shaft EVERYONE?
It's a bit wild that the sum total money spent on salaries for engineers handling potential problems stemming from this or defending against the possibility in the future could probably have covered paying the maintainer a living wage many times over.
I don't understand why that matters. If Robin was acting in good faith, he would pay the owed amount. Then the contractor would pay Upwork and everyone would be back where they started—the contractor would be made whole, Upwork would no longer have a 'lien' on the contractor's account, and Robin would be back in good standing.
>He was a hypnotherapist who claimed that in almost all cases they were able to use hypnosis to get information about what happened even if the conscious person was completely unable to recall any details.

There's no guarantee that the information they received was true. I imagine hypnosis is in the same category as lie detectors with respect to its...interpretability.
The island they are eyeing is Nananu-i-cake in Fiji: https://www.privateislandsonline.com/south-pacific/fiji/nana...

It's at least a real island that's really for sale, but Cryptolands renders present it as being freestanding in the ocean rather than right next to the mainland and another island as it is in reality
NPM expects packages to follow semantic versioning. If a package contained a breaking change like that, there would be a major version bump, and you'd have to upgrade manually.

If the maintainers wasn't acting maliciously, they could change this new version to count as a major release, and then it wouldn't be a DoS.
Is it pronounced "gist" or "jist"? "Gem" or "jem"? "Giraffe" or "jiraffe"?
It's an NDRI, not an SNRI.
[dupe] https://news.ycombinator.com/item?id=29857409
I should note that the government does a lot of stuff. If you have a cause you feel strongly about, whichever side, it's worth taking some time to understand which ones you can actually (at least theoretically) have a direct impact over, and that's generally in the regulatory arena, or administrative law arena. Agencies don't make laws, they pass rules and regulations, and those that adds legal obligations to pre-existing ones in a substantive way are subject ot note and commentary under the Administrative Procedures Act. This means you, even if you're not an American citizen but have some sort of interest at stake, can and should voice your concerns. It's in fact one of the only ways the average person can at least reach the decision makers that were not elected and don't owe their jobs to anyone but the president.

In those cases, the specific site to follow would be https://www.regulations.gov/ and the api docs are at https://open.gsa.gov/api/regulationsgov/ and at least most administrations (last one excepted, although they didn't seem to have anyone on staff in the executive branch who was familiar with the APA to begin with) are pretty good about at least reading, if not agreeing - sometimes cruelly and sometimes nonsensically - to your comments.

It's good to see what the government is doing, but in a sense if you want change, that's already too late. Focus on the regulatory aspects of things, and you can make a real difference, possibly. The CFR feed on the RSS page shows how regulations are routinely promulgated, and it's not an ideological thing necessarily: DHS/ICE is an agency just like the FDA or EPA. Rules are, after all, rules.
I've never heard of WebSub until you mentioned it. Apparently I was so intrigued by it / your post that I ended up making a little service to provide an alternative to Google's pubsubhubbub. Got it mostly feature complete as of a couple of minutes ago: https://websubhub.com/

Thanks for sharing your struggle!
GPL for students and open source projects, paid license for orgs and companies. GPL itself isn't really a way to get paid for your work.
> gives me the feeling of looking into cryptic Perl or regex

Dunno if you'll see this given how many replies you already got, but rather than just dumping "how do you do that" here's a realization I had a while ago that made it way easier to understand:

jq's language is a series of filters/transformers more akin to bash pipes on a stream of data than anything else.

For example, just "." selects out the current object (and is needed to match the "root" at the start of the query), and jq pretty-prints the results (when to a terminal):

$ echo '[{"k1": "v1", "k2": "v2"}, {"k1": "v3"}]'
[{"k1": "v1", "k2": "v2"}, {"k1": "v3"}]
$ echo '[{"k1": "v1", "k2": "v2"}, {"k1": "v3"}]' | jq '.'
[
{
"k1": "v1",
"k2": "v2"
},
{
"k1": "v3"
}
]

There's only 1 matching element here, the outermost array. We want to go one deeper, so use "[]" to unwrap/flatten it:

$ echo '[{"k1": "v1", "k2": "v2"}, {"k1": "v3"}]' | jq '.[]'
{
"k1": "v1",
"k2": "v2"
}
{
"k1": "v3"
}

jq is now iterating over 2 objects, so the next filter is the one where you select out the key you want. This can be done in two different ways for this example (per sibling replies):

$ echo '[{"k1": "v1", "k2": "v2"}, {"k1": "v3"}]' | jq '.[].k1'
"v1"
"v3"
$ echo '[{"k1": "v1", "k2": "v2"}, {"k1": "v3"}]' | jq '.[] | .k1'
"v1"
"v3"

Note how I broke these up: The atoms are ".", "[]", and ".k1" - ".[]" isn't one of them, despite what it may look like at first glance when compared to ".k1". Some additional examples to show how these combine:

The "unwrap/flatten" [] can be used multiple times when nested arrays are involved, with or without the pipe syntax, but only works on arrays. It errors if given something else:

$ echo '[[1,2,3],[4,[5,6]]]' | jq '.[]'
[
1,
2,
3
]
[
4,
[
5,
6
]
]
$ echo '[[1,2,3],[4,[5,6]]]' | jq '.[][]'
1
2
3
4
[
5,
6
]
$ echo '[[1,2,3],[4,[5,6]]]' | jq '.[][][]'
jq: error (at <stdin>:1): Cannot iterate over number (1)

$ echo '[[1,2,3],[4,[5,6]]]' | jq '.[] | .[]'
1
2
3
4
[
5,
6
]
$ echo '[[1,2,3],[4,[5,6]]]' | jq '.[] | .[] | .[]'
jq: error (at <stdin>:1): Cannot iterate over number (1)

Also notice how the "." is needed after the pipes; these are separate filters/transformations being chained together, so as a new rule it needs the same "." as with the first one.
Unlike all the other questions which are subjective or philosophical, it’s gif with a J for f*s sake. It’s what we called it in the 80s, it’s what the creator called it, it’s Jif goddamnit.
Also found this set useful

==========

How to Read a Scientific Paper Efficiently and Critically
https://youtu.be/lXJeU2dzzWo

How to Use Narrative Structure in a Scientific Paper
https://youtu.be/XW77hpjNTvY

Writing Is Thinking
https://youtu.be/tX9asHdFSv4

How to Write Clearly: Cohesion & Coherence
https://youtu.be/FpOPA3GFeJg

==========
All personal stories on Reddit should be assumed to be lies. I can’t believe there are people out there taking anything on it seriously.
Signing would not have helped at all here - the author decided to nuke their project (and likely their last reputation), they could have signed that commit/package.
I can't agree more! Webhooks are unreliable and requires both parties to do a very serious job to avoid lost events! Having a feed is the most rational decision!
Imagine they introduced something worse. Could any developer explain to a manager why you needed to import this package? "Why do we need colors there?", "Why can't we make that colored ourself?"
It's a tough one. I have a decade in industry and have noticed that even with lots of experience and expertise in things that most candidates don't have, some of the more interesting positions have hard requirements for a master's or doctorate degree, meaning that HR filters you out before even getting to a hiring manager. As a result, I'm doing an online masters (a pain at this point in my life) to keep my options open if I need to change jobs later. I kinda wish I had done a master's sooner before starting my career, but then it would have pushed my career back and I wouldn't be where I'm at now (skill and experience wise). I've talked to several industry contacts that have offered to hire me, so I'm not at a major loss. I just have to use networking for some jobs instead of just going through regular channels. This is fine as long as I know someone at the company I'm interested.

In short, there are advantages to both. A lot of the skills you get in grad school are the same ones you pick up in industry, although grad school will show you how to do published research as well. Having the piece of paper (degree) is nice, but getting a major project done is also good.

If you want to be in academia long term, stay in school. If you're only getting a master's because you don't know what to do with your life, I'd consider taking a break and trying that opportunity. Think about opportunity costs here. You gain and lose either way, but perhaps one choice has a higher benefit overall.

Edit: for robotics in particular, I would think you'd want a master's or doctorate to not be pushed into niche roles, but I'm not really sure. Can you bring up these concerns with those offering the job? Like "Hey, I'm really interested in doing this, but don't want to lose out on future opportunities. What is the typical career progression for someone that works here with only a bachelor's degree?".
Pin all you want, if the repo/vendor/maintainer pulls the release then you're not getting access to your dependencies at all.

If anything, this is the reason you use pull-through proxies. Your proxy will hold the version you depend on, regardless of upstream drama. Keep your proxy backed up and you'll be able to use those dependencies until the end of time, or you finally decide to migrate to an alternative.
https://www.govtrack.us/
The bubonic plague killed a third of the population of Europe. I imagine that felt pretty apocalyptic at the time & it had a long term impact on the entire region.

A plague that killed a third of those infected spread by modern international travel would be catastrophic. Medieval Europe got to spread the impact out over decades. Killing a third of the population in a year or two would be much worse.
The author of this package was caught with 50lbs of Potassium Nitrate (in the middle of NYC) and a bunch of materials on making bombs and booby traps when his apartment caught fire:

https://abc7ny.com/suspicious-package-queens-astoria-fire/64...

https://www.qgazette.com/articles/more-charges-possible-for-...

https://nypost.com/2020/09/16/resident-of-nyc-home-with-susp...

He might have been the unibomber in training.

Don't want to pile on, but dude clearly seems to be going through mental issues.
I've created this automatically generated list as I couldn't find a single source of truth that tells me which custom OS I can install on which device.

Android devices can be identified by their unique codenames. This list is generated by fetching data from multiple sources and collating it in a single (codename, OSes) map.

The code is open source and available here: https://github.com/olaki-android/olaki

If you're thinking of reusing an old phone or trying out a different OS, I hope you find this list useful.
> Both your examples mention single digits hours, ie very small amount of money. The problems tend to happen if there's larger amounts of money involved.

I've had lots of 100+ hour month contracts, some of which have spanned for years.

At some point you have to use your judgment to figure out what to do. If an individual with no registered business emails you asking you to put in 150 hours worth of work in a month, has a lot of grammar mistakes, seems weirdly aggressive over video calls or won't do video calls and tries to haggle down your prices then yeah it wouldn't be a good idea to wait until the end of the month to bill them.

But usually you'll have a chat or 2 with someone, get a good feel for them, propose a single page contract with a clear set of deliverables and compensation, then do the work and collect your money.

If you're doing project based billing with a new client it wouldn't hurt to ask for a decent chunk (33-50%) up front or at least earlier than your usual billing cycle for the first time.
No, they cut out the internet entirely.
Time and time again I'll keep saying this: This problem is only solved with package repositories that require review by a maintainer to publish. Linux distributions solved this ages ago.
It's both technical and cultural.

Javascript is used on the front end. Front end devs obsess (or at least used to obsess) over download sized. So you'd have crazy stuff like custom builds of Underscore (https://underscorejs.org/) with just the functions you wanted. Think manual sandboxing, if that makes any sense. You could get a package of Underscore with just map, filter and reduceRight, if you wanted to.

Now, when Node came around, people wanted as much as possible to have the same libraries available on the front end, so the same obsession with size was carried over.

Ergo the micro-milli-nano-packages they make.

Now, about the technical solution to this. We have this, for well defined programming languages (read: statically typed ones, or dynamically typed ones with a clear structure).

It's a linker. Tech from the 1950s.

Link (include) just the stuff you want, "tree shake"/"remote dead code" whatever you don't.

https://www.joelonsoftware.com/2004/01/28/please-sir-may-i-h...

Java's largely to blame for this, Sun REALLY, REALLY hated stuff that could be hooked into any OS and wasn't portable, so they didn't provide a linker. Everything was supposed to be on their JVM and you were going to install their JVM everywhere (2 billion devices!!!) and to hell with small stuff or heaven forbid, including native libraries. Javascript followed (on top of the Java restrictions they added: dynamic, poorly defined language, that would have made linking with tree shaking really hard, anyway). .Net also followed.

Almost 3 decades later we're trying to undo that damage.
The genetic tests use genotypes to make statistical inferences about efficacy and metabolism for certain drugs. Wellbutrin is a common medicine, and the testing company probably had it as part of their panel.
The Lockheed Elektra was infamous for its wings mysteriously coming off. Much research finally revealed that dynamic instability (flutter) was the cause. A great deal has been learned about how to prevent this, and a lot of effort goes into designing a wing that isn't susceptible to flutter.

I did the calculations for the 757 elevators to show it wouldn't flutter. And yes, it was also verified on the test stand.
> This is true for npm. After the incident with leftpad, you can't unpublish anymore. You can, however, publish a new patch update that completely breaks everything.

You absolutely can unpublish, it just requires more steps. If NPM gets a DMCA takedown request they will absolutely have to fulfill it.
That's what .lock files do though.
>if everyone had this power images would quickly become untrusted, if only a few have this power they could exploit trust in images longer.

You just answered your question
> now what

stop trying to save a couple of bucks by reusing functionality that's not that hard to just develop in-house maybe?
Not your mom, not your milk.
Not your platform, not your problem.
> proper marketing

CVE are the proper marketing. The perspective of having a package with a vulnerability and no-one to provide a fix is frightening to any software maintainer.

I think I could be extorted dozens of thousands for a single upgrade. Heck, when the electrician auditor says our office is not certified for 2022, I pay $700 for a professional to fix it. Software will be the same very soon.
Perhaps if there is a large reflector in space somewhere, that light could be passing back by us today! If we had a large enough collector, we could create an image.
The Cryptoland Twitter account also endorsed pedophilic grooming: https://twitter.com/widesauce/status/1478816782966136832

Transcript:

> Q: what will the age of consent be in Cryptoland?

> A: Mental maturity should be more than enough! :)

Cryptoland is either tasteless performance art or a disaster waiting to happen.
This change introduced an infinite loop upon import. It is nothing like changing an identifier which would've provided an error message about where the issue occurred.
I mentioned a feature phone in my post that currently supports WhatsApp.

Back in the early years, it used to support Nokia feature phones (not anymore of course) running their S40 operating system (https://en.wikipedia.org/wiki/Series_40).

Accessing WhatsApp from the web is also of course always a possibility.
The Stanford professor who I saw on a recent lex Friedman podcast confirmed what many people already suspected: the death count is exaggerated because the criteria for a Covid death is that a person is dead and also tests positive for Covid regardless of how the person really died. And also that cases were massively undercounted because of the fact that many people never have symptoms bad enough to justify any concern, testing or a hospital visit. That’s what he’s asserting and it’s true.

He said when you sample randomly and follow positive testers to their conclusion, the lethality rate is something like 0.02%. I’m sorry that it upsets you to hear something you don’t already agree with
Isn’t that the exact promise of El Salvador’s Bitcoin City, except for the island part.
> pilots followed that procedure

Were these pilots trained with the new procedure and the other pilots who died not trained?
i would pay for a service that runs an NPM mirror of a "last known good" version of packages to avoid this kind of thing. just keep all my dependencies a few weeks behind NPM to give things like this a chance to get caught, and let me continue blindly updating.

every time something like this happens, the reaction in the comments is the same: well you should test your dependencies. and yeah, i do that before release, but running an npm update on my dev branch and finding one of my dependencies has broken something is a bunch of work i could do without, and seems like work that is being duplicated by a ton of developers.
Packing is most of the point of a distro. They are specifically taking on that responsibility. They also have a better perspective to handle overall compatibility.

In a sense you've pointed out the alternative to having the programmer handling the packaging -- having some third party package and distribute. And this separation of responsibility turns out be almost always be a better solution. Distribution and coding are, after all, two full jobs (without 100% skill overlap). Plus, hopefully it indicates that at least two sets of eyeballs have at least glanced at the code (not the full desired many-eyeball outcome, but as good as we can expect sometimes).
Yes, and my question is: why didn't they have them from day 1???

Or at least day 1000? Npm was launched in 2010, 11 years ago, and I'm quite sure immutable packages were implemented about 3 years ago.

Again, this is not rocket science, we knew the attack angles.
You used Upwork as your credit card processor. Then the processor told you that your customer was basically using a stolen credit card. It’s completely reasonable for Upwork to take these funds back from you. And it’s completely reasonable for you to call “Robin” and demand he pay you back directly.
It's true that the creator pronounces it with a J, but take a look at the slide he used to announce his thoughts on the matter https://www.chicagonow.com/lists-that-actually-matter/files/...

(what letters are used to describe how the word "gif" should not be pronounced?)
Gingko or jingko? Given our jiven? Give or jive? Gill or Jill? Giddy or jiddy?

Both patterns exist in the language.
Taking off the mask to squirt the spray seems risky anywhere in the hospital. I doubt crowded hospitals will adopt this protocol especially with a more transmissible variant.
Immutability feels like the best approach here. Go's module system is pretty good in this respect: "proxy" is just a proxy that serves module code, and "sum" is an append-only transparency log of the hashes of all published versions. You can't "unpublish" from the log, but you can get code hosted on proxy removed for various reasons... which users can protect themselves against by running their own proxy. Go's module version resolution strategy means that the chosen module version never changes without explicit input from the user so no "publish a new version that breaks everyone's CI" issue.

All together I don't see how GP's "email php files around" is as any better than this system in any way.
Why does a new version break projects without action by the project owners? In Go you would have to explicitly update to the broken version.
I don't know what's happening, people are paying tons of money for hashes of jpegs, honestly can't tell it's 50/50 from my pov.