skysight-inc/HackerNews huggingface dataset:
A model where the manufacturer is responsible is also leaving it up to the market. All you're doing is assigning blame where it belongs (the actual driver being the software and not the end-user).

The manufacturer (or their insurer) will find the sweet (market) spot between safety and costs, where costs include not just manufacturing but the legal repercussions.

Putting the onus on the end-user is messy and wasteful from a market efficiency stand point. It may benefit Elon to make the user at fault, but it's just as "socialist" (or more-so) than putting the onus on the manufacturer.

I think the bigger concern is how to assign fault. If you allow the end-user to override the software then you'll need an objective 3rd party to determine blame (not the manufacturer or the end-user).
exactly my sentiment. 120hz is an absolute minimum for any desktop stuff as well.
I think it depends what downstream task you're trying to do... DeepMind tried distilling big language models into smaller ones (think 7B -> 1B) but it didn't work too well... it definitely lost a lot of quality (for general language modeling) relative to the original model.

See the paper here, Figure A28: https://kstatic.googleusercontent.com/files/b068c6c0e64d6f93...

But if your downstream task is simple, like sequence classification, then it may be possible to compress the model without losing much quality.
A competent security response to this would have been "Yes, they compromised one of our support technicians. We've initiated an audit and are sending out e-mails containing all of the actions that support representative performed for each customer to that customer's administrator"
My point wasn't "any difference in outcome is the result of discrimination" it was explicitly "you cannot use the difference in outcome as evidence there should be a difference in outcome."

This is why these differences are studied.
Isn't that the Mark I perceptron? https://en.wikipedia.org/wiki/Perceptron
with some exceptions (it's single-layer, and the entire dataset is a single batch input).
How to Store a Permutation Compactly
Factory of lies: Russia's disinformation playbook exposed (2018)
Any sound can have musical use, and some music doesn't aim for pleasantness. I would make recordings of this, then chop out the most interesting bits, rearrange them into patterns, play them back at different speeds, time stretch them, put effects over them, etc. There is a lot here to work with.
Is it strange but as a product guy my first thought when I saw this is how I could use it to replace my sales team... Well 80% of them at least.
In this case at least the neighboring buildings are both from OVH as well and the only thing realistically at risk from spreading fire is a rail yard.

Of course that doesn't excuse the design at all. Putting employees and firefighters at risk isn't ok, and I'm kind of baffled that they were allowed to operate like that.

https://www.google.de/maps/@48.5848973,7.7971161,3a,75y,26.0...
Nobody wants to ship Chromium with their pdf library or application. How do I get a print preview? If I do convince myself to lug around chromium, do I invoke Chromium each time for 1000 PDFs in a batch? Do I want to pay to invoke chromium on a EC2 instance or lambda?

Every document production library that handles HTML (a very popular feature) has had to implement HTML/CSS parsing.

I and many others are using HTML and CSS to declaratively lay out complex , dynamic documents (or trying to at least). Seems to make sense but we have ten more years to go before it's fully solved. Right now it costs serious coin to do it (unless you are releasing FOSS) and it ain't fun.
So happy to hear. We'll keep making it better :)
If you want to start making value judgements about who is worthy to purchase your product, wouldn't it be better to enforce that by directly verifying the identity/worthiness of each individual customer rather than relying on crude proxies like "didn't use a bot to make the purchase"?
Ask HN: Google has locked me out of the account
I forgot the password to my account and I have been trying to reset the password. To reset the password, Google keeps sending a verification code to the same email of the account that I'm trying to reset the password for.

I really do not get the point, I do not have the account logged in on any of my devices. I have tried all the previously used devices to reset the password from. It still keeps sending the code to the same email.

It's an account I use for AdSense and I have unpaid revenue in there. I have literally tried 5 different devices that I have used the account on, I can verify the phone number but then it keeps asking me to verify a code that's sent on the same email.

Now that I'm trying potential passwords, it asks me to solve a captcha everytime and I've tried so many times that it says I've entered the captcha wrong even though it's correct. We're 3 people literally looking at that and solving it and it's done that 10s of times.
Presumably the cards they tested have that?
Posting a key in Slack is obviously not good opsec, but whether this is a big problem depends whether those keys allowed access to anything sensitive.
They could be keys allowing access to random test data, or public data, etc.
They could have been revoked immediately they were posted.
Looks like I need to check out F#! Thanks!
Bush is an interesting person (I built a desk-sized Memex "reproduction" and am currently building 20 tiny Memex!) but I wonder about using him as a role model. The era of Big Science that he helped create after WWII was wildly one-sided, with most of the money going to the large firms that built the war machine.

Many excellent inventions and innovations resulted but all from within ~one worldview and that's not a productive way to run greenfield research today.
In the keynote, Jensen made a sly remark about how they themselves could benefit a lot from one of their cyberthreat AI solutions.
Can't say I'm working at scale but one of my product is latency sensitive and we stripped docker because it was slowing down each request.

I never really got to the bottom of it, someone linked me a bug in the interaction of docker / linux kernel (now fixed) which could have caused it, but I don't have time to waste chasing docker performance.

Ours is a fairly simple setup: one postgres db per machine, one python app per machine on $cheapVPSProvider; number of instances goes up and down based on traffic (basically cloning one of the machines); a load balancer in front; data gets updated once per day and replicated; auth / subscription status data is stored in redis
What any sensible company wants is that their changes get upstreamed, but changes that they don't care about from other sources (such as other such companies) do not.

Someone who can work with toxic and unfriendly upstream anyway has an advantage; they are able to get stuff into a project that is stable because it loudly rejects crap and fluff.

A corporation doesn't care about toxic and unfriendly; that just describes their world, pretty much.

If I'm dealing with some external project as part of company work, that's the situation in which I least care about people's personalities. I represent a company, not some individual and his fragile ego. I might be in charge of upstreaming something that doesn't even have my own name on it.

In business you have cutthroat competitors who unfairly bad-mouth your product.

You have irate, rude customers.

You may have suppliers to whom you are a low priority because their volume is elsewhere.

Your HR doesn't control any of those external people. You have to be cool as a cucumber, or it behooves you to be so.
It almost is. https://en.wikipedia.org/wiki/Tachyon#History:

The term tachyon was coined by Gerald Feinberg in a 1967 paper titled "Possibility of faster-than-light particles". He had been inspired by the science-fiction story "Beep" by James Blish.“

I don’t think “Beep” introduced the word, though (https://archive.org/details/galaxymagazine-1954-02)
Yeah Nix is why "choose boring" is a bit of a misnomer.

The truth is tautologically unhelpful: choose good technologies.

Most people have trouble separating snake oil and fads from good things, so old/boring is a safe heuristic.

Nix is not boring, but it is honest. It's hard because it doesn't take half measures. It's not an easy learning curve gaslighting to you to a dead end.

But taste in choosing good technologies is hard to teach, especially when people's minds are warped by a shitty baseline.
Engagement statistics basically.

The first cause is that in general users use more their phone than their computer.

The second cause is a corollary of the first cause and the existence of tools such as push notifications.
The article doesn't establish Thiel knew the guy was a white nationalist. Guilt by association is weak by itself, but if the two just attended the same party unbeknownst to Thiel and then Thiel spammed a list-serve of attendees with "THANKS EVERYONE I ENJOYED ALL YOUR COMPANY"--that's not association. The article is so threadbare its impossible to know whether that happened or whether Thiel purposely hosted a dinner specifically for the white supremacist. Or something in between.
Yeah that's fair! As a candidate I've enjoyed takehomes in the past because I was able to dip out easily if the project was clearly not doable in the alloted time. It's a bit harder to pull that off in an in-person interview.

Re: the takehomes that never take two hours, I think (but I'm a little biased) that Fairlane solves that – given there's a hard limit on how long the repo is available, a company that makes a takehome that takes way too much time would notice because very few of their candidates would complete it.
No, my argument is that outcomes are worse for some subsets of black people because they are more likely to make decisions which put them in conflict with the legal system. Which is an objective, statistically supported fact, and even if you want to shift to poverty as a scapegoat, that still is primarily expressed through culture and ultimately up to the individual to change.

"Deserve" is a loaded term, a moral judgement and has no actual bearing on this argument. And let's also acknowledge that not all blacks in the US have these problems, Nigerian immigrants are one of the most successful demographics in the country by all measures, despite the supposed abundance of racism holding all other African Americans back.
That's it, I'm getting a PulsOx sensor and breaking out my Raspi and getting to the bottom of this! :-)
Your edit is basically "You're arguing what CRT actually is and means but I wanna argue about what I think CRT is based on the narrow set of sources I personally interact with."

That's not a debate worth having.
Not uncommon at all.

I was recently brought back to do a weekend's worth of consulting for a former employer and help them bid on a new project, with the offer for a lead position on that project should they get it.
Don't believe for a moment that this misdirection is unintentional. It's one big reason you might have contract workers instead of employees in this role, actually.
Of all the things to be the worried about being released by a fire...?!

No. Lead is way down on the list. I'd be far more concerned about the other carcinogens from stuff burning.
Last year, we released our first prototype, AirClick. It was a note-taking app for developers. Since we released it, we collected many valuable feedbacks.

Today, we pivoted our product to include task management, and rename our product to Collow. It saves your time engaging with your customers, and it also reduces your time managing tasks by automating the scheduling and task status.

1. With our sharing feature, you can easily share a roadmap with just one click. You don’t need a second app to do that. We use our product to build our roadmap https://collow.io/site/brdbuwkqvn2kajs4et

2. With automatic scheduling, we help you schedule tasks and sync time based on fewer inputs and task dependencies. So whenever a time estimation changed on a task, all the tasks(parent tasks, subtasks, predecessors, and successors) will recompute the time. It will help you identify a potential project delay without the need to hold weekly sync meetings, and action on it right away.

3. With the auto status feature, we help you block and unblock tasks based on task dependencies. So, you don’t need to manually block/unblock tasks.

Our goal is to provide an all-in-one solution like ClickUp but optimized for software teams. Our chat feature is coming soon. Messages, tasks, and notes will be easily convertible in Collow.

Give Collow a try, we would like to know your thought and we would like to save your time on your daily work.
I think "obtain" here is specifically meant to mean "get existing passwords in plaintext", not "get a valid password via resetting it to a known one".
> If we force manufactures to be responsible, then they are going to find a way to reduce payouts. No country is going to destroy their automotive industry because of self-driving cars. And Too Big To Fail companies are never held responsible for their actions.

No country would "destroy their automotive industry because of self-driving cars," by making manufactures liable for their products. Worst case is the shareholders would get wiped out in a bankruptcy, but the manufactures themselves would survive.

> I'm in the camp of owner-responsibility. Insurance rates for self-driving cars will set a price for the safety of the system. It will happen rather quickly and will be largely accurate. Are you going to even use a self-driving system if it elevates your insurance premiums to $10k a month? Even a person who prefers convenience over personal safety is going to think twice about paying all that money to insure themselves.

That's a ridiculous, Rube-Goldbergian idea. Lets simplify it: the manufacturer has the liability, buys the insurance, and includes the cost into the price of the self-driving feature. Instead of waiting for your insurance bill after you buy the car to find out if you can afford self-driving, it's there in the sticker price.
Seeing the increased bandwidth is super exciting for a lot of business analytics cases we get into for IT/security/fraud/finance teams: imagine correlating across lots of event data from transactions, logs, ... . Every year, it just goes up!

The big welcome surprise for us the secure virtualization. Outside of some limited 24/7 ML teams, we mostly see bursty multi-tenant scenarios for achieving cost-effective utilization. MiG etc static physical partitioning was interesting -- I can imagine cloud providers giving that -- but more dynamic & logical isolation, with more of a focus on namespace isolation, is more relevant to what we see. Once we get into federated learning, and further disintermediations around that, even more cool. Imagine bursting on 0.1-100 GPUs every 30s-20min. Amazing times!
> The main difference with Auth0 and WorkOS is that BoxyHQ is being built on an open source ethos. Our focus is to be a developer-first security platform, putting developers at the centre of our holistic approach and help them close the gap between compliance and security.

Not to detract from this project, but I'm familiar with Auth0 and WorkOS both, and I think both would say the same thing about themselves.
I did this by accident. Best bit of advice you can give, honestly. Most people don’t know that if you actually make friends with they guy/gal setting up your account (and not doing it online), you can literally choose your phone number. My phone number spells my (very popular) first name and is from an obscure part of the US. Any phone calls from there is spam. That being said, bots tend to use that prefix for spam, in general and for a few years there, I got a lot texts and calls: “missed call from this number, who dis” and “I don’t want your warranty” type of things. That was annoying.
We currently run a Java Monolith that is build on every push to master on Gitlab pipeline, when successful the fat JAR is copied to S3 (including all resources) and then a config file is pushed to S3 to ask DEV servers to run it.
The machines are pure EC2 instances with the service registered in systemd with auto-restart after 5s. A simple shell script downloads the config file, the fat JAR and runs it. We detect the environment and machine we're at using the EC2 meta- and user-data, which is set when the EC2 instance is launched. All of this is basically simple plain batch script using JQ and other standard tools.
It is a little more complicated, because we have graceful restart by first asking a specific instance in each cluster to update itself and when it reports that is is updated, the next instance will be asked to update.
All the EC2 instances in a cluster are behind a simple Global Accelerator and are in multiple regions. The service has an API that is invoked by Gitlab with a token to ask for graceful restart, then it will report back to GA that it is unhealthy for some time, so it can finish pending requests (close sockets) and then it simply terminates, the rest is back up to bash script and systemd.
To deploy or redeploy to an environment is as well a simply click in Gitlab UI and especially important for On-Call, so you can see which version was deployed to which environment when by whom. Additionally some JIRA tickets are automatically created.
Eventually this only needs Gitlab, EC2 instances, Global Accelerator and Bash scripts, while allow us to be multi-region and have stateful connections, we can even ask clients to directly connect to specific instances or ask GA to redirect certain ports to specific instances. Basically GA is our load balancer, router, edge location. It is stable, fast and easy with the smallest amount of pieces involved. We can remove individual instances, update one instances in a specific region for testing to a new version and so on.
Given the nature of what Okta does, is this going to kill them? It's like the business version of a headshot.
> If one studies the history of European countries you'll find bending over is the outlier.

Before or after 1945?

Before 1945(and especially before 1918), I agree. After 1945, the experiences of losing a generation in the crucibles of WWI and WWII seems to have broken the European martial spirit. Europe has done a lot of bending over since 1945 (decolonization was not because of some moral enlightenment, but mainly because they did not have the resources to continue with it). See Soviet domination of Eastern Europe. See Suez Canal. See Bosnia where Europe could not intervene to stop a genocide in its own backyard.
Oh please, Buzzfeed does not have a good reputation, yes some articles were pretty good, but it's far from something people would be willing to defend as a good news source.

Investors don't have to shoulder costs for a service that no one cares about. You want a "what flavour of jelly bean are you" quiz you go to Buzzfeed. You want serious news you read one of the countless other site that covers world news. Yes it's cynical, but if I had money in Buzzfeed I would have pressured the CEO too.
Do you know what nations they mint coins for? I can’t seem to find that information.
Booking has competent perl ops people - including people who contribute to the language core and toolchain - and keeps very much up to date.

Sane application scale perl is pretty much a different language to old school scripting perl - the two just happen to share a parser and a VM.

(not everything about Booking's code is necessarily sane, when you've got a codebase that's been running that long making heaps of money there's inevitably stuff people wish they could replace, but your 'most likely' simply isn't descriptive of most companies running OO perl application stacks in 2022 - the ones that wrote crap perl mostly already blamed perl and are now writing hopefully slightly less crap something else)
There are a lot of people who want to play arbitrage with rare goods, if you have enough money you can do it with just about anything. It is perfectly fair to want your market segment to be to deliver cheap rare goods to people without many resources.

Sometimes arbitrage helps make efficient markets, other times it is just a drag on the economy. It is perfectly fair for a provider to not want to only provide goods to people with many resources or scalpers.

RPi is also just not a good deal if it is significantly more expensive, there are lots of more expensive options out there for small computers which have better specs and are more readily available.
These tech demos usually are for developers, so that makes sense.

IME they tend to show off how tech will look 4-5 years down the line, about the time a modern AAA game needs to from production to release.
I wonder if Apple also intends to introduce ECC LPDDR5 on the Mac Pro. Other than additional expansion, I’m struggling to see what else they can add to distinguish it from the Mac Studio.
Thanks! It's absurd how they make us pay in cookies to view their marketing PR posts.
> These breaches of Government policies, and of the duty under the Public Records Act to make arrangements for the selection and safe-keeping of records which ought to be permanently preserved, are unlawful.

Unlawful, but I'm guessing not criminal, because governments rarely seem to write laws which include penalties for ministers who break those laws. Perhaps the public are intended to rely on the expectation that ministers who act unlawfully will resign...
I'm sorry but I don't think people need to cite sources in every sentence for every word. You are not going to ask them to cite the dictionary for each word, would you? So there is a balance, and I think we are just conflicted on where the balance should land. I think this problem is pretty apparent and you don't. What I can't figure out is are you just rules lawyering at this point or do you actually believe its not a problem.
That's just your moral crusade clouding your judgement so you can't appreciate the technology.

You're crusading for the kings of Web2, so they don't lose control.

Humanity will be fine, calm down.
I can see a Slack breach being far more damaging than policy should effectively permit it to be because plenty of people use it to share things they technically should not.
Yeah but you don't ever really see Google or Amazon or Facebook or Netflix or Spotify on here,

In the words of a limbo competition judge, "that's not a high bar".
> Now for a company that starts today I don't think I'd recommend that

Any reason why? It sounds pretty good.
It runs some kind of A13, so similar to an iPhone 11. But it may not be a fully capable version of that chip. All retail 'Apple Silicon' Macs use a version of M1, which is more of an enhanced A14.

It might be similar to the Apple Developer Transition Kit from two years ago, which was an A12 with extra GPU power. But until someone can get software actually running on it, will be hard to know.
Here is the funny thing. People want to throw shade at the investors, but Buzzfeed staff themselves frothed when they couldn't sell off their stake in the company.
https://www.newyorker.com/news/annals-of-communications/how-...

"As it turned out, for many former employees, it was all too good to be true. This past Monday, as BuzzFeed went public, many of them learned something alarming: they weren’t able to trade the stock that they had waited years to exercise."

When you have skin in the game it aligns interests.
Some old things really are better, or at least not worse and already familiar.
I'll edit the post to reflect it, but it will definitely only be within normal work hours and voluntary.
That lines up with what I saw.
A Manifesto Against Sex Positivity
More cores and more RAM is really kind of it. I guess PCIe but I’m kind of wondering if they’ll do that.
Not putting secrets and sensitive data in bug reports / tickets has been a thing for at least 20 years, so you worked at some crappy run places.