skysight-inc/HackerNews huggingface dataset:
> "This is a sad day for San Francisco," Safai said. "We can't continue to let these anchor institutions close that so many people rely on."

This is the conclusion reached by that spokesperson?

I guess the solution is to outlaw closing private stores in areas where they are needed. How outrageous that they should try to turn a profit there while the people need their goods /s

Literally sounds like a chapter from Atlas Shrugged, except in real life
I find the biggest issue is if the QR code is laminated or not. My phone catches glare and takes ages to scan, but on crappy paper (similar to a sticker on a box in a warehouse) it works great.
As a hockey fan what I see is that at least 4 NHL players have had their careers badly harmed or ended by COVID-19, that's not a very big pool of people, of which only some small proportion have been infected - that has changed my perception of the risk dynamics significantly.
> One of my biggest gripes about semver, for instance, is how often supposed non-breaking changes in semver do in fact break client/consumer functionality.

Something I've seen happen – management issues a directive, "Every team must use SemVer it is our standard". Now every team has version numbers 1.x.0. Almost nobody ever bumps the major version above 1 – people just make breaking changes on the minor version. There is no way to enforce the requirement to bump the major version, so no way to tell if people are doing it when they are supposed to (I know there is some tooling to detect backward incompatible API changes, but a lot of places don't use any such tooling, and even if they did, it will always be incomplete, there will always be backward incompatibilities it won't be able to detect.) So long as every team's version numbers look like SemVer, management can be told "Directive implemented, everyone is using SemVer now"
I love my RM2. I don't have a problem w Remarkable wanting to charge for opt-in, value-add services. TLDR the hardware's great, the software's mediocre but steadily improving -- and extremely hackable -- and I'll continue to use and recommend it.
The rank arrogance and stupidity of this project has me halfway convinced it’s a red herring.
I have a Dymo driver that I connect via USB, and have never installed a driver.
I bought a bunch of N95 masks the day after I heard China was locking down Wuhan. There were still plenty of masks at regular prices at the time.
A Happy and Lightweight Python Based Google News API
The bigger problem is the precision-machined hohlraum the pellets sit in for ignition. That costs millions of dollars, is crucial for actually achieving anything, and is destroyed in the process.
More like 'parents won't let kid ride more than block from their house'.

And so we get stuff like this:

https://www.engadget.com/little-tikes-smart-stationary-bike-...
Synchronous vs asynchronous is a choice for the author of the my_operatornotify file. This module just hands the subject + body to your code.

I did some experimenting with async sending and even batching in mine, but decided to remove that and stick with synchronous. The SMTP connection is really fast and most programs send the email at the end of runtime, so it doesn't matter anyway. I prefer the simplicity. I certainly did not want to get into managing an outbound spool, waiting for the server to come back, running a separate daemon for this...

In my_operatornotify I use tenacity to do a couple of retries, then write the message and the fatal exception to a txt file on my desktop or ~/ if there is an error sending the email. I'll notice it eventually. The stuff I'm doing is not important enough to demand more retrying.

Thanks for reading!
I think one important piece that's missing from this conversation is just how essential FB is to many people who don't otherwise have Internet access. In many less fortunate countries, FB has sweetheart deals with telcos to provide access to it's services at lower rates than general internet access, and many people can only afford FB.
"Pathological scapegoating" of the guy that has literally said "No, that’s okay. That’s all right. You got your freedoms".
k3s on single VPS. cert-manager and external-dns for maintenance free LE certs.

nginx ingress (I would probably go Contour+Envoy if I was to set it up now).

Kotlin w/Gradle. Build + Deploy single command `gradle deployStage`.

jib for container images, don't need Docker, reproducible super fast builds.

Prometheus + Grafana for metrics and alerting.

Things I like about it:

- JVM is super low maintenance runtime, tune it once and pretty much good to go. Very easy to diagnose memory or performance problems in production. I even have the debugger agent loaded in prod listen on localhost so I can use kubectl port-forward to access it and diagnose bugs that only occur in production or hung threads etc.

- Prometheus seems like overkill but it's just so much less effort because everything already has a prom exporter.

- Using k8s API saves a bunch of time again. No need to screw around with docker-compose or some godawful config management from the 2000s like Ansible (ick).

Things I don't like:

- It's not HA. The DB pods push their WALs to S3 and I have script to spawn a new PG from S3 using PITR. This is how I test new code so it's known working but it still means that if my server goes down it's down until I do something about it.

- The box is a bit snowflaky. I didn't set it up using a script, it was hand configured up until the k8s level.

- I rarely upgrade k3s because I have to do it manually. If I was using EKS or GKE I would probably press the upgrade button more often.

- Grafana is a chore. grafonnet helps (I also use Tanka w/jsonnet for k8s manifests).
> I don't see how a biotech revolution would bring great change.

For example, vastly more efficient food production. Imagine meat being grown in a petri dish. It would use far, far less resources. The nutritional value could be enhanced. It could taste like the best beef.
I was days away from ordering a Remarkable 2, despite the high price.

I could see it being amazing, with screen-share, in diagraming and sharing visually with webex/zoom colleagues.

Now it looks like I'll need to pay them $7.99/month for the privilege ? Instant hell-no.
Most Walgreens don’t have dedicated security guards. If these stores had guards working all operating hours (2-3 shifts per day, every day) and some stores might have employed multiple security guards, the multiple is there.
> Berkeley is actually even more liberal on many issues so your explanation doesn’t really make sense

This isn’t a single-dimensional system.
You are suggesting we mislead people to get them to be vaccinated because they are too dumb to understand. The whole point of this post and comment thread is that it doesn't work.
Does SPA stand for Single Page Application?
> Interesting article. How much requests can you support for 20/month before losing money with this stack?

Ha, I haven't profiled it yet. I'm not too sure. But, I think a decent amount. If a slack team with 10000+ physicists signs up, I may need to talk to them offline.

I do plan on doing some stress testing in the future for fun, I'll try to remember to reply here.

> partner frontend

Yep, to repeat what steve_adams_86 said, she did the frontend completely. Usually I'm forced to do the frontend, it was very nice having someone else just do the whole thing without me.
Sadly I’m watching one of the companies I consult with go this way prioritizing process over productivity, while at the same time basing requirements on the deals they’ve signed lately rather than a clear plan. I’ve seen it before and it is painful to watch.
Did you see the picture and get the impression that the rock was traveling at supersonic velocities? Really?
> city, however, is still incredibly hostile to new people who haven't bought a house or found generational success

It’s also quite hostile to those who have. The only people it coddles, paradoxically, are those who inherited property rights.
The author appears to be JCR Licklider's son. JCR Licklider was the ARPAnet funder whose vision and backing gave us modern computing. See Waldrop's excellent "The Dream Machine" (published on Stripe Press) for more on JCR's achievements. <https://press.stripe.com/the-dream-machine>
"sue" suggests civil action and a decision by the wronged party.

They're lucky a prosecutor didn't prosecute them for criminal activity. The school would not have any say about whether or not this happens.
> I am not surprised at all that PostgreSQL now seems to be taking over everywhere

To a large extent, Postgres didn't out-compete Mysql in mind-share by being a better database. Arguably it was a better DB in the Web 1.x LAMP days and everyone knew it - it just was SO hard to setup replication, which is where it still hurts (not for RDS though, which is another part of the story).

Mysql went out of its way to lose free users which was compounded when it was bought out by Oracle.

The death-blow of sorts for Mysql+Java was the GPL licensing of the jdbc binaries. This made Mysql a very sticky backend to use with a Spring or similar JVM based framework in general, because you had to convince someone that GPL is okay for a product that never leaves your building.

The postgres community on the other hand reaps the rewards of being very very friendly towards people who want to embrace its client protocols or even outright cut-pasting their code into a proprietary system which offers postgres compat but nothing else under the hood.
The paper was selected at random, it's not really relevant here, so I haven't read it. The point was that it's an example of levels of comparisons we see studied.

It can't be an ad hominem since I never said anything about you. Your post was FUD because you stated it very loosely and asked for hard data to refute it. You're quite likely right on infection providing better protection, but we neither have a hard confirmation of that (or you'd link it, right?) nor did you provide any support for "But beware saying that outloud." Not only there's ongoing research on differences (as we both provided), many people do say that outloud.
Just to nitpick, I don't think that formula is valid. We're primarily interested in "unrelated" wolf attacks, but it counts the total fatalities, not the total number of fatal incidents. If we count each fatal attack as only one incident, regardless of the casualties, we get 2^-258 instead.

But of course we also need to take into account where the 6-member team lives. If they all live in West Bengal, India, the consideration is much different than if our developers live in Atlanta. Atlanta doesn't have any wild wolves. There is a Wolf's guenon in the zoo, but that probably doesn't count as a risk because they mostly eat small animals and also are monkeys.
If the lead solder is actually functional in some way then they may have to attempt to find an exception under RoHS. They could attempt to define the usage so as to have an application not covered by RoHS for example.

This analogy is kind of confusing because RoHS is an imposed standard. A user of SHA1 is expected to make their own decision about appropriate usage. They might reasonably continue the usage of SHA1 for their specific use case. The real world is full of such compromises.
Berkeley is part of Alameda County, but San Francisco has its own county.
Try mining the assholes of Twitter slacktivists. Plenty of sand there. Might find some worms and Fremen, too, though.
The great executive-employee disconnect
This spring my org experienced heavy turnover (including me) from the director down. Not sure how they are doing now but it can't be great considering how many experienced senior devs left.
Total Recall Technologies vs. Palmer Luckey, et al.
Already factored in.

I can't find my original reference, but here's once that doesn't factor in the difference: https://www.energy.gov/ne/articles/infographic-how-much-powe...
Mexico is more overweight than the US and tops your list of reported working hours.
> The bulk of the projects were migrated around August 2020. This was achieved by filing a GitHub support ticket. This also required an admin user in the org to confirm the changes, for which the dnfadmin user account was used.

Wow. They filed a ticket and then secretly used an admin bot user to accept the change? That sounds incredibly dishonest - not just an oops situation there.
"They did a trial, https://www.medrxiv.org/content/10.1101/2021.05.10.21256982v..., and it worked very well."

Only 25 patients, not double-blind, no controls.
Hah! I have vague memories of this. I think this might have inspired it, yes.
This is a good example of how to apologize when you didn't have bad intentions but just made a mistake. Lead with the apology, explain clearly why you did that, and follow with lessons learned and the next steps.
I would just host in Iceland, Greenland, or somewhere FBI-takedown-proof and avoid noxious, invasive EU/US regulations.
> I was surprise that no one suggested truncating SHA-256 to 160 bits...

To do that, you have to stop generating commit hashes with SHA-1, breaking compatibility with existing git clients.

And if you're going to do that, you might as well just use the whole SHA-256 hash, since compatibility is out the window already.
wouldn't it be easy for a competent government to identify and control maks suppliers? btw, here in Canada, most notable ppe hoarders were shipping it to China
Except you don't, because lots of people are faking vaccination status. In fact it's probably less reliable than a positive PCR test. It's extremely common to fake vaccination cards among the anti-vaxx community.
They just lowered it in Paris to 30km/h. Lower speed is directly correlated with less crashes. The other benefit is less noise, which is very important in an urban area. In most urban areas now the loudest most constant noise is from vehicles.
Surprised how far out those stores are - only the 300 Gough St one is really close to the Tenderloin.
> Your children will not be alive in 100-200 years so your point is also moot.

Wow, you really love attacking strawmen don't you? No wonder you're such an optimist.
> But the US would not have invested so heavily in its Navy; it would not have ended the war with more than 100 aircraft carriers, about 20 of which were full size fleet carriers.

The Two-Ocean Navy Act was passed in 1940. The Essex class of carriers was designed around 1939, and Essex herself laid down before Pearl Harbor. Before Midway, the USN had already ordered 13 Essex-class carriers, although another 19 would be ordered subsequent to Midway.

In other words, the great naval buildup was already underway well before even Japan attacked the US at Pearl Harbor. Actually, the US had plans to build even more ships that were cancelled because they realized they had already sunk everybody else's navy.

> because the terms of any truce with Japan would have stipulated a freeze of the naval buildup.

Why would a loss at Midway have necessitated that Japan win the war? By the time of the Battle of Midway, the US has a dozen Essex-class carriers on the slipways. By mid-1943, the US is launching a carrier a month. The Japanese could only manage to start 6 carriers for the rest of the war, and completed half of them.

Japan didn't have the industrial base to compete against the US's production. Furthermore, the Japanese never had the capability to meaningfully strike at the US. Even reaching Hawaii took the logistic capabilities of the IJN to its stretching point; there was never any meaningful risk to any US West Coast (or Panama Canal) assets. Japan's only hope was that the US would tire of the war and give up, but they kind of blew that chance with their strike on Pearl Harbor.
Linux Security Quick Reference Guide (2000) [pdf]
I run a multi-tenant SaaS where every tenant can define custom properties on every entity. PG allows us to dump everything into a single jsonb column, and still have superb performance for filtering / analytics / searching etc. The backend codebase remains mostly agnostic to the data shape, and we rarely have to change the database during new releases.
Yea or projects that are forever on 0.x.x pre release so any change can be breaking according the spec (as it is considered experimental) even after having many adopters. I can think of at least a few OSS projects like this.
This wasn't supported for years.

https://services.google.com/fb/forms/googleassistantforgsuit...

was where you could try to get into a beta.

Google Home, Home Mini Home Mox Home Hum Nest Mini etc did not support gsuite accounts during launch as far as I can tell.
Google Colab available in GCP marketplace
FWIW the shipping minimum applies to the whole order, not just the products that are shipping. So $10 of items to be shipped along with $40 of items for in store pickup is fine. "Scheduled delivery" is the same inventory/process as store pickup, but paying someone to pick it up for you. "Ship to store" is the same process as ship to home, but might be handy in some rare situations.

The two options represent two parallel logistics chains, and are quite similar to other brick and mortar stores. Once you know this, it's actually beneficial because you can choose whether to get the items soon by picking up, or choose from a much larger selection that can be shipped (possibly drop shipped). Although as you mention, it would be nice if they had a middleground option that would bring a medium selection to your local store for pickup within a fixed day or two, especially from other local stores.
Yeap. Mandatory doxing is a terrible idea when attackers, stalkers, and other threats remain perfectly anonymous.
> This move was a mistake. The board deeply regrets that this happened.

This post makes the _action_ sound like a mistake when in fact it seems that the _decision_ was a mistake (loosely defined).

The board made the decision and followed through with it (i.e. did not make a mistake) and now “regrets the mistake happened”. So not only are they not actually apologizing for their actions but they are not even taking any real responsibility for them.

Like someone slipped on a damn banana peel and fell on the “take over all projects” button. Sploops!
Starting with the idea that Sergey has anything to do with how Google is run these days established how much credibility this article deserves right off the bat.
The entire workforce of the United States will be deployed with a vegan toothbrush in hand to scrub the Earth of all the hydrocarbons
Back in the days I was maintaining the driver support for Cyanogen for the MSM7227 based models and I found some builds on xda dev that came preinstalled with some RATs.

I only found out by coincidence of another dev asking me to verify the build. The nature of how Android is built (with all its hundreds of repositories) isn't made for verifiable builds, so it's really hard to prove or audit.

From what I've found usually the builds with custom UIs or skins on top are infected with stuff either the person packaging it doesn't know about (benefit of the doubt) or do, but it comes out a year later when someone skeptical checks for it.

Verification is especially hard because everybody on xda dev is using some paid adfly links or some google storage or dropbox links that will change in intervals (depending on how much traffic they produce they'll get blocked quickly).

So yeah, I think the need for a hash based end to end verification tool is kind of there.

But honestly I have no idea how to build it because even the partition setup of old flash storage using devices is so messed up that there can be side effects when an apk is put in /emulated storage folders.

I think the only future proof way to do this is going mainline like the postmarketOS devs try to do. But until we're there I'm probably dead of old age already. I don't believe in the Android ecosystem anymore, because this is a governance coordination problem that's not easily fixable. Hosting all outdated kernels alone with all the custom drivers is way too much traffic for any open source project to pay for.
The fear is that the nuclear weapons sitting in storage are assumed to be functional, but might turn out not to be. This could have dangerous geopolitical consequences. We can study how the materials age, but have to use simulation to understand the effects on the detonation given the test ban. This research helps calibrate the simulations.

The civilian applications of the facility are secondary, as others have pointed out.
This sounds more like they’re burned out. Subordinates going from great to terrible usually means the business is failing them, not they suddenly “started smoking a lot of weed”. I would take a hard look at your job as a manager.
It's not his most artful turn of phrase, but if you read the context of the remarks, I think Safai is saying "we can't continue to let them close" as in "we can't continue to allow these conditions which are forcing them to close," not as in "government should mandate that they stay open."
A good buddy of mine did the same, but with the message "DOOM!"

His punishment was community service, and the service was having to be basically an intern for the school IT guy. Smart administration, really.
I come from a family with Alzheimer's running through it like clockwork. I have some uncles who tried to live the right lifestyle.

It didn't help. If anything in my observations it made things worse. Though it's a meaningless sample size.
Taking another automated step with the account before getting permission would just be the same thing all over again, no? i get your point, but they're acknowledging that making unrequested changes was bad. doing it again would contradict that, I'd think.
Easy, don't excuse people who don't have a verifiable record or from a test with a known high false positive rate. What's so hard about that? Airlines have figured it out, limiting which tests you can use. Why can't public health officials?
Call me nuts but I run my own startup's DevOps in an extremely minimal, low-tooling fashion:

- Linode VPS

- Nginx

- SSH to deploy code

- Google Cloud hosted (& backed up) DB

Why would I need K8 and some crazy architecture when I'm just trying to get my product to my customers in the fastest / most efficient way possible? I'm not FB or Amazon and if I do get that size, I'll have plenty of time to adapt on the way there

Finally I was going to quote the Pieter levels case but someone else beat me to it
Get vaccinated. This isn't a political two-sided issue.
Deciphering the Philosophers Stone how we cracked 400-year-old alchemical cipher
I don't have a crystal ball, but there is nothing written in stone that says the Bay Area will retain its desirability or economic weight.

I think of New Jersey which not that long ago used to have an amazingly robust economy - plenty of manufacturing, high tech (most pharmaceutical companies were HQ there). Now NJ is known for its bloated, inefficient government, crazy high taxes (including property taxes) and isn't really much of a desirable destination anymore.

Not saying that will happen to the Bay Area, but it's not impossible either. The more dysfunctional the government becomes and quality of life suffers, the less people will be willing to accept them just for a chance at a high salary and Google on their resume. Especially when other offices open up.
Oh no. Those crazy right wingers. They destroyed SF
There's plenty of workflows where untrusted people have their proposed changes audited and then written to a git repo
Twitter: 'no signs of account compromise' after Maxine Waters claims hacked
Ping me if you don't mind. :)
This comment started out quite well and I really wanted to understand everything written after mentioning a lost laptop
> They were part of PRISM.

Isn't that still a thing?
Apple may cut iPhone13 production by millions as US warns of Christmas shortages