skysight-inc/HackerNews huggingface dataset:
It's interesting how this is a story where to a degree, the demands of the power-user (who probably wouldn't want this product to begin with) help make the product not happen at all:

> The trouble is that fingerprint readers struggle with sweat or dirt, and friends in law enforcement advised Stephens that cops often wear gloves. A sensor error in a self-defense situation could prove fatal.

It's absolutely the case that (for example) fingerprint readers are flaky, and cops would not be willing to tolerate anything that could stop them from using a firearm in an emergency. But really, does the technology even matter then? Why would a cop want a smart gun? So from the beginning, looking at what cops think about your smart gun prototype means you're looking at the entirely wrong audience.

Likewise, are hunters the ones who want a smart gun? What about single mothers who need to be able to defend themselves during a home invasion? The right authentication mechanism and tradeoffs depend on each audience, and the things they want definitely don't match with what cops want. If I was picking up a firearm to use on the range or for hunting, being told 'this RFID ensures nobody can use it after stealing it or taking it from you, but it has a 1% chance of not letting you fire it' might be a pretty good pitch - but if I'm a cop, there's no way I want even an 0.1% failure chance, because if I had to draw my gun a lot of stuff has already gone wrong.

Kind of a baffling place for an effort like "let's make smart guns" to end up at.
For me the right way is never to allow non-ff merges and instead require all changes to be integrated into your branch (either via rebase or merge from base into your branch) before merging. GitLab supports this flow nicely and it has been wonderful for ensuring that the resulting product passes tests.
Only if the target wants to pursue a lawsuit, which is obviously very costly. There is no built-in protection and I’ve never seen our government pursue abuse of the DMCA.

It’s a grey area, too. The penalties if I remember only apply for knowingly sending fraudulent takedowns. But these people are likely sending what they believe are valid reports and they will argue as such.

The DMCA was made for copyright holders so they could do whatever they want within that grey area. They have total control to remove content on the web without any real due process or judicial review.
I'm using the React version, I liked how the code is organized
Depends on what you're doing and how patient you are- I know several people that have done similarly with kitchen-grade toaster ovens, thermocouples, and relays / SSR's to manage temperature and get professional-quality results. It's within reason that someone with a laser thermometer or such to be able to manually do the same thing.
Oh, the G4. My favourite Mac ever. It's aesthetics are unprecedented. I still run one in my studio - with dozens of GB of 360p formatted old shows like classic Simpsons and the 1985 Twilight Zone, and tossed a SEGA, GBA and NES emulator on it with a little USB game controller for when I need to unwind.
Embedding Adobe PDF was possible in Chrome and Firefox too. It was a terrible idea because generally you do not want full-blown Acrobat handling untrusted files from the web; for many years PDF + Flash were by far the top exploit vectors for malware.

Chrome's embedded PDF reader didnt support all of the extraneous crap Adobe did, but that's a feature. It was also sandboxed, which IE's implementation was not for many years.
Bionic Reading: read texts with more focus, awareness, and sustainability
Copyright holders want this to work (as a repeal of the directive would be a far, far worse scenario), and will likely be more than willing to work with anyone who aims to make it work.
I've heard that there is a huge need for machinists and that the pay is great, but all the newly graduated college kids want office jobs, so there aren't enough machinists to go around. Not sure if it is true, just heard the rumor, but would be interesting if it is...
Where's the line between technology advancing forward and weeping for buggy whip makers?

Self-checkouts allow several people to check out a few items at once, leaving the cashiers to deal with those with full carts. They are not inherently evil. It's a good technology (when implemented well with functioning machines...)

I'm all for treating employees with fairness and dignity. But expecting employers to not innovate in a competitive marketplace for the sake of keeping employees doing low-skill work makes no sense.

So... where's the line? Do we demand no automation in order to protect these workers? Or do we demand additional safety nets for these workers and the opportunity for them to improve their skills if they so choose?
I realized that as I was typing it, but there's not much I can do about it other than vote for politicians who claim to want to do that. I can't help it if half the country votes against their own economic self interest repeatedly.
Hamilton crowned the 1000th race in the history of Formula 1
Flutter has had a lot of performance improvements since that date. It'd be great to see that updated compared to current version
The above technique is a myth . See https://youtu.be/1AcEt073Uds .

Trying to randomly unsolder and put back resistors or other components when you don’t know what the error is is another bad idea.

The author should have tried to actually attempt to fix the logic board first. But before all that he should have inspected the board and use a voltmeter to see what the issue is. But even doing that he might need a replacement part.
Doesn't seem to work for me. Just infinitely stuck on a spinner after typing a word ('travel' in this example)

Lots of error'd requests to 'mainnet.infura.io'
> Anybody who cares about the rights of workers in this country should be absolutely ashamed to use a self-checkout stand.

This position is ludicrous.
I kind of made this https://github.com/hsanjuan/ipfs-lite

May not be ultralight (running a DHT node isn't, but it does remove a lot of crust).
Why is it trendy to use expletives these days? It's not big or clever.
Group nouns (eg "a murder of crows" or "a flobble of jelly") also started out as a differentiation between the aristocrats and uneducated masses:

> Even in their original context of medieval venery, the terms were of the nature of kennings, intended as a mark of erudition of the gentlemen able to use them correctly rather than for practical communication.

https://en.wikipedia.org/wiki/Collective_noun#cite_ref-11
You are an excellent writer, so funny and gripping. I suspect writing is your true calling in life. Lol @ what on Earth is that oven? :)
Haunting images. Please consider tagging for the nsfw elements along the right hand gutter.
How do you stop this? It will just encourage then to create fake accounts .
"A sensor error in a self-defense situation could prove fatal."

I've read stories where a grip safety(a button that is pressed down when you're gripping the handgun properly) has slowed down the person just enough to let the bad guy shoot him a couple of times before he could return fire. Safety systems probably save more innocent lives than the they've hurt, but I bet anything less than perfect in a smart gun is really going to hurt popularity among gun enthusiasts.
The tech industry has long treated scaling as an inherent good and positive goal. And that's money backed, for sure. But I increasingly believe scale is causing problems that technology can't fix. Communities too large to be moderated by groups of humans become problematic, and I'd even argue networks and platforms at large scale become easy to exploit and manipulate from a security standpoint as well.

A small curated app store has quality apps published by humans. A giant app store trends towards being full of malware. The larger a platform becomes, the easier it is taken advantage of by bad actors.
The main point seems to be that photography was made by whites for whites, and thus discriminates against non-whites.

What I don't understand is how the article seems to imply that there's something wrong with that. Consider that

- Photography was invented and for the longest time mostly used in a majority white area.
- It makes a lot of sense that, in predominantly white cultural spaces, lighter skin is preferred, as it historically indicated that a person didn't need to work in the open, which implied some degree of wealth.
- Most importantly, it seems to not understand how light works. Dark surfaces reflect less light, so there's less contrast between strongly lit areas and shadows, meaning it's both harder to make a photo look clear and for an AI to analyze it.
That is very arbitrary. You can claim you're doing as much as you can. Who is going to determine how much you are really able to do? What if the judge decides you could've done more and decides to fine you anyway?
I did something similar to this on an iBook G4, I believe?

It's still working to this day. I feel like I was a lot more careful. The author seems to describe their behaviour as rather reckless and haphazard.

Certainly putting it up to 180 wasn't a great idea. :3
What would be the best way to capitalize from a personal investment standpoint in what I can only imagine will be massive growth in VPN usage? The EU and UK are going to end up cutting off large swaths of the internet from their population but I have no doubt people will still want unfettered internet access.

Are there any publicly traded VPN providers?
The trick is how to provide a feature like that which cannot be used as a vector for malicious hacks, and which can't be used by the authorities to compromise citizen's privacy against their wishes.
This looks relevant:

« In June, 2004, the Supreme Court ruled that Guantánamo detainees could challenge the grounds for their detention. It became fashionable for high-profile corporate-law firms to represent Guantánamo clients, pro bono, but many detainees rejected representation, because they thought it was a ploy to lend legitimacy to an unjust detention. »
Streisand effect all the way.

Everyone (Venn diagram: people who pirate TV shows AND people who watch the specific series) will rush to their torrent-provider-of-choice and get downloading.

Well played! They should also download this material and find the leak and dust up their contracts and call their lawyers. Any other snap decision just makes them look like a spoined kid that dropped their ice-cream.
Theft might be a problem, but it's still probably cheaper than paying people to do a job the customers will do for free. I believe major grocery stores are pretty good about estimating shrinkage and I doubt they'd continue to use self checkout if it wasn't profitable.

I personally love self checkout lines.
The boiling point of lead is 1749°C. You're not going to get lead vapor from the solder at the temperatures of a toaster oven. The smoke is probably from some plastic component or some remaining flux on the board. But yeah, that oven shouldn't be used for food anymore.
This is a good illustration of EU legislative structure:

> The legislation was voted through by a majority of EU ministers just a few minutes ago, despite opposition from Italy, Luxembourg, Netherlands, Poland, Finland, and Sweden.

Nonetheless, those countries will have no choice but to implement national laws to comply with the EU directive: https://en.wikipedia.org/wiki/Francovich_v_Italy

> Francovich v Italy (1991) C-6/90 was a decision of the European Court of Justice which established that European Union member states could be liable to pay compensation to individuals who suffered a loss by reason of the member state's failure to transpose an EU directive into national law. This principle is sometimes known as the principle of state liability or "the rule in Francovich" in European Union law.

Indeed, EU members lack the sovereignty even of U.S. states. The US federal government can pass laws directly binding on the citizens of every state, but cannot compel state governments to pass and enforce particular laws. The EU can do both (the former through regulations, the latter through directives). In the US, the inability of the federal government to hijack state legislative and enforcement machinery to its own ends is seen as an important measure of accountability—you can always blame state legislators for state laws. (You see this in the areas of drug and immigration law. Sanctuary cities can exist because the federal government cannot force state organs to enforce federal law. Likewise, legalized marijuana at the state level.)
There's some serious chemistry, thermodynamics and fluid dynamics involved as well.

I suppose someone is thinking that fluid dynamics is plumbing, but it would be a stretch to make that claim over issues like the size and shape of the combustion chamber, its throat and the bell, which are dependent on the characteristics of transonic and supersonic flow.
I’ve never heard that. Just because the content is hosted on Twitter does not mean it’s up to Twitter. It’s up to the target of the complaint to pursue a lawsuit against the complaining party. I’m not a lawyer but I dealt with this a lot as a service provider. We simply had to follow the law and take the content down or else we would be held liable.

The system we had before — the court system — required processing fees simply by the process of filing lawsuits. The DMCA was specifically made so copyright holders can send them in high volume without any review by a judge. They don’t want to be slowed down. That law is working exactly as they intended, even though I strongly disagree with it.
Haven't read the study myself yet, but that sentence alone makes me not want to waste my time on it.
It's so satisfying a read. That's the great paradox of free speech I think. Somehow by reading this, I am more inclined to endorse the excesses of American exceptionalism than wholeheartedly criticism them. Even if it's all hogwash, the mere sight of this lavish helping of self-directed criticism more than enamors me to their cause, whatever it may be.

Free speech may just be a more effective social control mechanism than democracy.
Reddit and YouTube both do not want the increased liability, and hence want you to think of this like it is the end of the world, because it may cost them money. It's unlikely either business would actually exit the EU over it, because that's a lot of money and users to leave off the table. In addition, exiting the EU makes space in the EU market for new competitors to arise... who might become large enough to venture out into the global stage.

I think it's unlikely either site would leave the EU, but if it did, I'd be glad for the increased competition it might give rise to.
The self checkout machines are great(ish) for small purchases, but I would hate to do a real grocery run on one. All of the ones I've used insist on me keeping the products in the 'bagging area' during the transaction, and there wouldn't be any room. You also can't get any sort of speed going, because it gets grumpy when you scan more items while it's announcing your items and their prices and the savings. No way to tell it you have 6 of whatever either.
Big Companies Thought Insurance Covered a Cyberattack
It's still there in the Code of Conduct: https://abc.xyz/investor/other/google-code-of-conduct/

Scroll all the way to the bottom. It's the closing thought, one of the key places to emphasize something.
There is a book about the development of Windows NT called show stopper. In the book they talk about this. C++ was pretty new in 1989 so Dave Cutler decided to stay with C to reduce risk.

Except for the graphics team, as they were managed by someone else. They decided to go with C++, and they were pretty much always late because everyone was learning and building the tooling around C++.
It's a question of effort, really. The bad guys get infinite tries; support only needs one person to fuck up once.

My hope would be their training largely prevents "oops I can't remember" getting through, but I suspect you'd eventually get someone quitting tomorrow who doesn't care, or someone having an off day.
I have to admit I skimmed this article, but the aristocrats had a purpose for the rules and regulations. If you're at a very long table in a very long hall with 20 other people, it's difficult to see, much less hear or join in with the conversation of the other guests. Making a bunch of noise, getting in people's way, spilling things all over the table, mixing up whose drinking glass or knife this is, etc could cause annoying disruptions, not to mention made dining less gross.
I'm somewhat glad to hear I'm not the only one who has been subjected to extremely excessive recaptcha tests according to these comments. Especially when I'm filling these out just to login to websites of which I'm a customer. I get it for ordering, but if you put this on your customers logging in, it's like you're begging for cancelations. Google is the one determining your paying customer's user experience.

And if I pass your captcha, can you not cookie me with a signed token indicating that I already proved I was human for 30 days? It's like these lazy people can't handle bot login spam, so they just throw recaptcha on their login form and call it a day.

If your login form requires paying customers to fill in recaptcha each time, you're doing it wrong. Please stop. Or go out of business faster.
I am a friend of a famous Apple products repair person and one of the things I've learned through our friendship is just how fragile repairs can be. As this individual quickly learned, putting a MacBook Air logic board into an oven is a terrible idea. Do not under any circumstances do it with your computers. It is one of the worst fallacies of DIY repair out there.

What you're trying to do (as he stated in the article) is that you're trying to reflow the poorly adherent solder beads in the hopes that you'll fix the faulty connection. But the way you're doing it introduces the risk of damaging the PCB and the ICs themselves through thermal stresses and gaseous expansion by any trapped ambient moisture. This will irreparably damage your board and it will lead to the phenomena he experienced here. ("popcorning")

The right way to do it involves a directed hot air gun and proper equipment so that you aren't imposing excessive thermal stresses onto the board as a whole. If you don't know how to do that, then please send it to someone who does. There are several good repair outfits out there right now who specialize in this and can help you out.

Do not repeat this person's mistake. This DIY method is like doing cardiac surgery with a chainsaw. It's a terrible idea for your data and wallet.

Edit: Here's a guide that outlines these issues and offers ways to do it properly with the right equipment. The "popcorning" is called board delamination. https://www.latticesemi.com/-/media/LatticeSemi/Documents/Ap...
> competition can give us even cheaper groceries

If only it were so competitive. But that's spot on, automation will remain a constant at any rate. Whatever the solution to structural unemployment it won't involve hampering innovation.
Well the article says:
To ensure its success, the Information Commissioner's Office (ICO) says that online services must also adopt "robust" age-verification systems.

My guess is they'll ask for a valid credit card before allowing users to access the interface for likes and such. Which, IMO anyway, means many less people will be liking things in the UK, not just under-18's. Then some clever kid will find a way to get around it and before you know it the only people liking anything will be kids under 18.
China Spying on Undersea Internet Cables
Rage Against the Codebase: Programmers and Negativity
Yes you are right, ours too are for protection, not fighting off an invasion. I should have made that more clear.
wow thanks a lot for sharing. +1 on my bucket list for sure.
That was an enjoyable read! One of these days I’m going to make it to a Vandenberg launch.
It’s semantics really. Yes, Twitter can stick their neck out and ignore it, but it almost never happens. The end result is that Twitter understandably doesn’t want to have their legal team review every single DMCA request for validity.

The law is clearly broken but service providers like Twitter are caught in the middle.

As someone that had to deal with these reports, and we were tiny, the volume is insane. I cannot imagine the number of complaints Twitter receives.
That was a fun read - I'd hazard a guess that the load from memory is not cached and will get started, then the compare is speculatively executed, but then the conditional jump and whatever follows won't fit into the cpu pipeline and will cause it to wait for the fetch to complete.

One thing you might try is to add a superfluous fetch of the same memory location a few hundred instructions before to get it going before you hit the jump, so it's cached already by that time.
If you wanted to look up, you wouldn't be quoting yourself, writing poetry, or and navel-gazing at your emotional response to mystery. You'd be studying the world as it is, not as the story you want to tell about yourself.
Nobody really uses lead in electronics anymore unless it's absolutely necessary. RoHS (regulation concerning lead use in electronics in the EU) really worked.

Lead-free solder has it's peculiarities but the industry long ago got used to it and leaded solder is now mostly seen by hobbyists. I've made the move to lead-free and while it's not quite as easy to work with, the peace of mind knowing I've eliminated at least one nasty heavy metal from my hobby is worth it.
You're conflating ramp up time of business domain knowledge with skill level. Yes, a sr. dev will come up quicker than an entry because they have the wisdom and experience of past companies, but all devs need some sort of ramp up in an environment like that. You don't hold back pay from your sr. staff until they've ramped up, right? Of course not, they would take a better offer elsewhere. As would your entry levels that have now risen to mid-levels once they get the chance.

But all the same, any company should be able to make any dev useful from pretty much the very beginning. Whether it's rote refactoring work, research tasks that are too time consuming for more sr. folks, tasks that are in the domain of data entry that can be automated with simple scripts, low-hanging fruit bugs, etc. It's a failure of the org not to properly utilize the abilities of a smart person who knows how to program.
My hunch tells me this will be used as a tactical weapon by rights holders and PR companies to bury negative publicity in lawyer fees.

You can argue that you are using some content fairly and you did your best to prevent it in court while paying 500$/hr to your layer, or you can simply remove it.

But yeah, that won't be a problem for 95% of companies and startups - but it will be for some.
I'd say your best bet is probably waiting for CloudFlare to IPO. They're teasing a 1.1.1.1 branded VPN just recently.
I think that one’s called vandalism.
Poor reliability is a theme in IoT, self-driving cars, and here.

We are all accustomed to the fact that computers are flakey. Our computers and phones sometimes need rebooting to fix weird behavior. My printer just forgot how to connect to WiFi for no apparent reason. Everyone has stories like these.

What's tolerable for many popular products is not tolerable for others, though. Leaving aside whether having a gun actually protects you, people own guns for that reason. If your gun won't fire when your life is in danger, or if your car won't swerve when a truck is in the road, or if your thermostat won't turn on when it's bitterly cold, that's unacceptable.

Clearly there exists highly reliable technology: plane and spaceship controls, for example. My understanding is that an extreme focus and expenditure on reliability is required to achieve that.

I think that some of these consumer product categories where it's critical that the thing actually work will require the same kind of rigor before people can trust them.