skysight-inc/HackerNews huggingface dataset:
Maybe misfire is a better term. The DMCA process ends up with a lawsuit if the 2 parties don't agree. This means that the submitter of the complaint has to be ready for an expensive legal battle even if they win, or can drop the whole thing.

The US justice system encourages anyone with deep enough pockets to freely step over the law when their opponent can't outspend them.
defo feel like more work is needed, perhaps some new ideas. async apis are needed too IMHO, some framework that permits consistent apis that can be http or stomp or websockets if those protocols are a better fit.
> Fortunately we already have a cheaper alternative to coal, and are making the factories to deploy this solution as fast as we can.

Are we really?

If coal power suddenly cost five times as much, you don't think we'd be making those factories a lot faster?
> If every member of Congress died, would the Republic cease to exist? Probably not. There's a contingency plan for that.

Those plans assume good faith leadership. This insurrection was encouraged by the lame duck president and supported by members of Congress that now refuse to investigate it. And it wouldn't have been every member of Congress dead, would it? Those supporting the Big Lie would have been around to govern. Not exactly comforting to me, and I think well within the realm of believabilty for at least the possibility of a permanent change to our Republic as we know it.

> The claim can't be made if this can't be answered.

On the contrary: the fact that the question can't be answered confidently supports my point rather than refuting it. We don't know what would have happened. It's conceivable or systems would have endured, contingencies enacted, order restored. But there's good reasons to think that may not have happened as well.
I wonder how much better this would be at capturing information that doesn't translate well into text representations of speech.

Consider how with word2vec there are relationships in the embedding space between semantically related words. I would expect the examples of that for word2vec (e.g. king -> queen being a similar translation as man -> woman) to apply here too, but can it also do things like place regular questions and rhetorical questions in different regions of the embedding space based off of of the inflection in the speech?

It would also be interesting to see what relationships exist between equivalent words in different languages within the embedding space. I suppose something like that is probably already used for text translation neural networks, but maybe some notable differences exist when dealing with speech directly.
This is what GitHub used to do, before they changed it to the squash model.
Why would she not be able to sue for recognition as a living person?
I’ve had three laptops fail in the last five years due to a flash rom chip getting corrupted after saving changes in the BIOS one time too many. Enterprise warranty covered an HP and a Dell service rep to come on site and swap out the motherboard+cpu+gpu combo twice, I swapped out the rom myself the third time.

I’ve also had to do it on a desktop Gigabyte motherboard circa 2009 after a successful BIOS update left the flash rom unstable.
The guy is a Trump supporter. I would not try to reason with him.
https://youtu.be/5NeccdDpO5I

I found this to be a great source on the topic. Your question is a great one, and hints as to why Jean-Francois Champollion is hailed as the genius he was. The key insight was essentially the theory that the Coptic language spoken still as the liturgical language of Coptic Christians in Egypt was a modern form of the ancient Egyptian language encoded by Hieroglyphics. Champollion made a key insight attempting to decipher a cartouche (the hieroglyphic form used to write a name) that a symbol at the beginning of a name looked extremely similar to a sun. The Coptic word for sun was Ra. At the time, they’d already identified the symbol used to writes a ‘ss’ sound, and so Champollion was able to guess at the middle symbols spelling Mes, leading to the deciphering of Rameses. Note that the European world at large obviously already knew the name Rameses, which was key here.

I believe in general names were key to deciphering many of the sounds used in the language, coupled with pronunciations hinted at by Coptic.

I typed this all by memory so I may be off in some details but I believe I have the gist right.
Yeah and after you have a working $30B fab, how many people are going to follow you to build one?

The first one built will get cheaper to run every year - it will pay for itself by the time a second company even tries to compete. The first person to the "final" node will have a natural, insurmountable monopoly.

You could extract rent basically forever after that point.
In that case you are definitely in the right position legally. The DMCA is about as simple as it gets. No lawyer is needed, its just a form letter. Most likely they will just take it down, only if the uploader submitted a counter-notice would you have to take further legal action.
Location: Seattle, WA

Remote: Yes

Willing to relocate: No

Technologies: Javascript, Ruby, Node, React / Redux, HTML, CSS, Express, PostgreSQL, MongoDB, AWS

Resume: https://drive.google.com/file/d/1Y1onP5JejM31O_Mk02v3GaRPlpY...

Email: kevin@counihan.io

Hello! I'm Kevin. I am a software engineer looking for a full-stack or back-end position.

I recently built an open-source framework called Tacklebox (https://tacklebox-webhooks.github.io/), which deploys a centralized webhook service on AWS, and includes client libraries (JavaScript, Ruby, Python, and Go) along with a Management UI website (React / Redux, TailwindCSS). My team and I have additional details and a technical case study available at https://tacklebox-webhooks.github.io/
Machado de Assis’s Afterlives
Emphatic agreement, this is something I've wanted for a while. For the purpose of history management/traversal (reverting, bisecting, or just understanding) you want certain code changes to be atomic, implying that they should all be understood/tested/reverted together. But for the purpose of code review you want something more granular and less monolithic, so that a single reviewer can more easily understand a large change, or so that review can be more easily divvied out among certain code owners. Currently getting all all of these properties requires decomposing the commits during the review phase and then squashing before merge, but this is a bad practice because now no reviewer has actually signed off on the code that's getting merged and you're just hoping that nobody's slipping any last-minute or malicious changes in during the squash.
You can actually sort of just open a file directly by running darktable <filename> which will open the file in the editor (the darkroom in darktable parlance; the file is automatically added to the database).

I suppose if you don't care about the photo library management aspects of darktable, you could use it like this entirely, especially since apparently 3.6 adds an export button in the darkroom.

https://www.darktable.org/usermanual/3.6/en/special-topics/p...
20% reduction in capacity means queues and empty shelves elsewhere. If it’s not resolved quickly there will be a lot of food waste as well.
Is it not standard practice to first merge 'master' into 'feature' before you merge 'feature' into 'master'? If 'master' has changes that are not in 'feature' then 'feature' is out of date, testing probably needs to be redone. It also means any merge conflicts are resolved in the 'feature' branch. If 'feature' is a long lived branch then is should merge 'master' on every release anyway.

If your weakest git user cannot revert easily then you're in trouble. Enjoy being on call 24/7 otherwise. Reverting is more important than committing.

I genuinely don't understand why people care about git history so much. I've never needed to look at it in 8 years of using git.
>I do not get why we keep centralizing ourselves around the Bay Area. I am not an expert in the field so perhaps I am coming from a point of ignorance here

The background: other cities exist and have existed. Companies can locate anywhere.

Centralization exists in many industries. It's not a phenomenon unique to tech, the Bay Area, or the United States.

Desirable cities also exist in China. The government is constantly dreaming up ways to get people to stop moving to Beijing and Shanghai.

This situation cannot be merely wished away. The tendency for an industry to concentrate in a particular city is historically broad and durable.
I have seen the videos of groups (or individuals) just walking out of stores with bags of unpaid merchandise. That’s just insane to me. I think out of all the videos I have seen, police arrested or caught 1 individual. Whether or not that person was taken to the station is unknown as the video just stops there.

I think SF is an example of what not to do when it comes to decriminalizing certain aspects. Stealing at all levels should be prosecuted. This discourages others from doing the same. People from all sides should agree with this.
That’s good too. Let’s rethink transportation.
She had trouble even getting a lawyer to take her as a client. People that don't exist can probably not file lawsuits either.
hypothesis: security failure by a service provider is evidence of winning at externalizing costs.

strategy: find SaaS corps responsible for catastrophic cyber-attacks and buy them on the the dip?
FYI, Apple does have two variants of the M1, with 7 or 8 GPU cores (those have a large area and are likely targets for defects) : https://en.wikipedia.org/wiki/Apple_M1

Defects in CPUs (not GPUs) for segmentation hasn't really been a thing for a while, maybe the Phenom X3, and that was already a bit of a stretch from what I recall as most X3s had a perfectly functional 4th core.

A cheap cellphone SoC is definitely not pennies, <10$ is a better estimate and it's usually without RAM included which is not always accounted for in comparisons.

I vastly agree with rmah and most estimates do too.
Want != need.

There are many people that wants child rapists to get death penalty, a lot of people liked Bush, Trump or Putin, or believe some guy living 2000 years ago did wonderful things against the laws of physics. They are not really thinking about the consequences on society, they don't know how a computer work and what is going to happen if behemoths get in control of their entire life, which is well on its way.

Because a computer is not your regular run off the mill appliance. It drives the way people communicate, think, consume, are informed and monitored.
Keeping it legally dead is absurd. What if she commit a crime?

"Your honor. She has alibi. She was dead when it happened."
Eh, 20% of households in the Bay Area earn under $36k/year. Obviously shooting out bus windows isn't the right approach, but I think you may be underestimating just how much of a divide there is between even average tech workers and lower class people living in the region.
Every AlpineJS article I read has the disclaimer that this framework isn't meant for large applications without ever defining what that actually means.
I might have agreed with you 5 years ago, but when Apple dropped support for 32-bit apps (and later x86 altogether) I had to switch over to Linux.

If they were a little more considerate towards their power-users and developers, I could probably loop a Mac in for ~60% of my daily workflow. Nowadays though, I'd rather just use an OS that lets me do 95% of the stuff I do without compromise.
I will admit I am always afraid to lose my changes if I squash! Maybe I should try making a new temporary branch before squashing to give myself peace of mind.
So when Republicans start denying the existence of electrons, we can't post about computers anymore?
I volunteer to work in the banks freezing the accounts of anyone burning coal. Is that good enough for you?
Technically, yes, but in practice not really; eBPF started as an extension of the packet filtering framework and then got generalized to be a nearly-universal debugging/monitoring/tracing system that's only sometimes used for packets. https://ebpf.io/ is a decent starting point for reading.
Even crazier, my i5 750 (from 2009) was overclocked to 3.5ghz and per core Ryzen 3 isn't even twice as fast.

We're near the end of IPC scaling per core. And it was never that good in the first place. Pentium 3 IPC is only 3-4x worse than the fastest Ryzen. Most of our speed increases came from frequency.

IMO we need to get off silicon substrate so we can frequency scale again.

I wonder if the end of scaling will push everyone into faster languages like Rust. You can't sit around 2 years for your code performance to double anymore. Will this eventually kill slow languages? I think so.
I would appreciate an api framework that can handle email as a transport.
Why, time and time again, do we see results of major studies by career scientists which don't pass a moment's scrutiny by the educated layman?
Interpreters are considered elegant, too. For example, Lua is a great little language and it runs everywhere precisely because it's interpreted.
Water pollution like this is a localized phenomenon. The concentration of CO2 in the atmosphere is not. What the study is saying is that there may be no environmentally safe outdoor spaces anywhere in the world at the end of the century. This has never been the case previously, even when environmental pollution has gotten out of control in certain places.
I've never been a fan of the "only one return" view. I find it far easier to understand when the "preconditions" are checked at the beginning of the function and, if they fail, bail out early (guard clauses). Then there's less mental load in the rest of the function.
This is happening everywhere.
an idiot would eat an ordinary breakfast. I will eat an extraordinary breakfast.
The South still makes its cobbler. :)
I assume packing has to take only seconds.
If you could send us the id/url path of the sandbox demo you were on with the error that'd be super helpful. Thanks in advance! support@napkin.io
I agree and want to add a few thoughts.

I've found the best way out of these kinds of questions, where the asker hasn't put in even the lowest level of effort is to say, "I don't know, but here's what I would do first to figure it out." Most people will be glad to find out there is a path forward and take it themselves. If they're not willing to pick it up there and do the thing you've suggested then you are dealing with someone who doesn't value your time and setting a boundary is the right thing to do. The kind way to respond at that point is simply, "I'm sorry I don't have time to figure this out right now. You can try [the thing I suggested] and come back if you still have questions."

The crux here is there is no kind way to just make people go away. If your role is mentoring, and any of us with experience should be in that role at least a little, then some of your time is going to be spent on this interaction. The most valuable thing you can do for yourself, the other person and the company is lead them toward finding the answer themselves. That's going to require a balance of helping and honestly and kindly saying no to doing their work for them. Not easy.
They have already been pushing this heavily in the Windows 10 installer to either “gauge the reaction”, or more likely, to let everyone know that this is coming and there’s nothing you can do to stop it. The time of “gauging the reaction” is over and now it will be the requirement.
> Why don't I know for sure it's gotta be the one on the left?

Because of fast-forward merges.

It will be the one on the left if you, as expected, were on the master branch and merged the feature branch ("git checkout master; git merge feature"). But if you were on the feature branch, merged the master branch into the feature branch (usually, this is done to resolve conflicts), and then went back to the master branch and merged the resulting feature branch into it ("git checkout feature; git merge master; git checkout master; git merge feature"), it will be a fast-forward merge: no new commit will be created, and master will point to the merge commit which was originally on the feature branch, which is going on the opposite direction as you would expect.

The solution, as others have already mentioned here, is to do all merges to master as non-fast-forward ("git merge --no-ff feature"); that gives a consistent order to all merge commits on the master branch, and the end effect is the most similar to the "grouping" feature OP wants (if everything on master are these non-fast-forward merges, the difference between one merge and the preceding one is that "group").
why is this in wordpress?
"do their job as customers" yeah that totally doesn't sound like bullshit :D
I'm not deep on the weeds of high-performance compilers, but just because ISA evolution hasn't happened doesn't mean compilers can't evolve to use the silicon better.

There always was an "Intel advantage" to compilers for decades (admittedly Intel invested in compilers more than AMD, but they also were sneaky about trying to nerf AMD in compilers), but with AMD being such a clear leader for so many years, I would hope at least GCC has started supporting AMD flavors of compilation better.

Anyone know if this has happened with GCC and AMD silicon? Or at least is there a better body of knowledge of what GCC flags help AMD more?
I’m one of the people who strongly advocates the squash merge. My PRs are also single commits most of the times with the PR body as the commit message. That is a hidden gem of GitHub, if you open a PR with a single commit then GitHub will use the commit message as the description.

The reason why I prefer squash commits is not only the linear history but also the fact that I’m simply not interested in the sausage making process. If a PR becomes so big that it would need multiple commits than I request smaller patches. But I also see that this heavily depends on the team size and general setup. But I use squash PR ever since it was introduced in GitHub. Before I manually rebased the feature branches to have a clean merge.
Humans produce about 2tonnes of CO2 annually, and even at an industrial scale, CO2 scrubbing costs about $1,000/tonne:

https://news.stanford.edu/news/2011/december/extracting-carb....

And that's at an industrial scale - residential scale would be even more expensive. Not all of the CO2 in the air has to be removed though and humans are not at home all the time.

It would cost, at the very highest range, $50t to stop climate change over 20 years. That's $2.5t per year, or $2,500 per middle class person for 20 years. Plus, we get a whole lot of benefits from a cleaner environment without oil and coal.

https://www.globalgiving.org/learn/cost-to-end-climate-chang....

Its cheaper and more effective to just... deal with oil and coal usage as a collective, rather than all of these ad-hoc individual amelioration measures.
> A random alien civilization that is more advanced than us is likely to be thousands of years more advanced.

s/thousands/millions/
Thanks for explaining that - I was totally missing the point to be honest.
If they can weld that good, they wouldn't need to steal the converters.
> Current version is actually free.

Oh, I looked at the FAQ which listed the (old) price, the current version is donationware/gratis indeed:

https://www.sagelighteditor.com/purchase3.html

> Reasons to Donate to Sagelight Editor

> Current Version. The current version is the original release version, with some bug fixes and updates. Donations go to updating the current version and adding some functions.

> Next Version 5.0. Version 5 is 75% complete, featuring a complete revamp of the UI, many new functions, and new a new-and-improved noise-reduction. Donations also go to finishing this version.

> Get Version 5 free. If there are enough donations, I can give version 5 away for free. If you donate $5 or more, keep your information and you get Version 5 for free, even if it goes back to a regular purchase.
It would make sense to me if hide my email continued to generate a random iCloud address and it redirected to your custom domain email. I doubt they would create a random email at the custom domain, for exactly this reason.
Corruption hides in a complexity. A true “universal” program with no gatekeepers, no special qualifiers beyond citizenship, has a much smaller attack surface for corruption than the status quo. As soon as you introduce qualifiers and people to police those qualifiers you will get corruption.

The problem is that most universal programs are not truly universal.

Ideally the fed only does unconditional universal (I shouldn’t have to prefix this with unconditional since that’s redundant), and leaves everything else to the state and below.
The Oath Keepers brought arms to DC for this rally they had a major hand in planning. That the FBI only seized one handgun from the riot doesn't by any means indicate or imply there were not other armed rioters, especially given evidence from chat logs and social media that these militia groups did travel with their weapons. And many of the rioters had non-firearm weapons as well (e.g., tasers, bats, crowbars, stunguns, knives, chemical sprays, etc.)

The reality is we'll never know the extent of how armed (guns or otherwise) the rioters were, because almost everyone was allowed to leave unimpeded.
If an action takes you 5 minutes to do correctly and your boss force you to do it in 1 minute, how the hell can you do it right and not lose your job?
I've got a virtual machine with Debian 3 installed... it was the only OS that I could find old enough to deal with the variant of C, and was 32 bit.

I'm a Pascal programmer, so it was news to me that there isn't really a standard C, but rather it changed more than once... the old code doesn't work with the new compiler. A few of the macros just will not work because of the way they assign things.
San Fransisco has already removed (b) as an issue [0].

When SF made that change, you had people saying the same thing “this won’t change anything because you can’t build the housing that’s needed”.

No one is saying that this, by itself, with zero other changes, will resolve the issue. I prefer to applaud individual incremental improvements than belabor the fact that this one change is not enough.

[0] https://www.livablecity.org/time-san-francisco-say-goodbye-m...
That's not the workers problem.
According to petite-vue's readme, it supports the `v-cloak` directive [0], which is how vue recommends you hide the unprocessed template before it is mounted.

For more complicated logic, I think working with the @mounted event might work.

[0] https://v3.vuejs.org/api/directives.html#v-cloak
Yea, I can totally see that happening. Hopefully in a room full of people, somebody will have the gumption to not vote low confidence if there’s concern about this happening.
And eBPF stands for extended Berkeley Packet Filter:

> eBPF is an extended BPF JIT virtual machine in the Linux kernel

It's really quite an amazing tool, especially since you can use it to run sandboxed programs in kernel without changing kernel source or loading a kernel module. These programs can be written using a limited dialect of C.

Some examples of its use can be found here: https://github.com/iovisor/bcc/tree/master/examples
Have career scientists been held accountable for the replication crisis? I know Hanlon's razor says not to, but at this point I can't help but think medical and social science have been more or less taken over to produce propaganda. Not too dissimilar to what the CIA did during the Cold War.