skysight-inc/HackerNews huggingface dataset:
I am thinking the same now. The OP solution requires a server to do the the processing, but I am not sure this is the case for the Zoom client.

The Zoom client also requires minimal hardware requirements from the processor iirc.
That line about lung problems being the primary cause for heart problems got to be wrong, without context...
Free Admin Dashboards – Coded by Freelancers
Without pre-existing immunity, a much larger fraction of the population would get flu each year. That's one of the primary reasons why people worry about pandemic flu, as opposed to the regular seasonal flu. An entirely new strain has the potential to infect a much larger share of the population than the regular seasonal flu, precisely because there's no pre-existing immunity.

> chances are 15% of us have already had it according to the Gangelt survey.

No, that's a completely unfounded conclusion to draw from that study. Gangelt was chosen precisely because it was an extremely hard-hit town. Researchers wanted wanted good statistics, so they went to the place that has the largest case density. There was an early superspreading event in Gangelt, during Carnival celebrations back in February. Hundreds of people came into close contact with a known infected person. The population of the town is only 12,000 to begin with.
Deploy Stateful Docker Containers with Amazon ECS and Amazon EFS
Germany is NOT at a place where the lockdown is too strong. The spread is still growing exponentially and they will run into issues a few weeks from now if it continues at this rate.

You can’t keep everything open and then shut everything down once you’re at capacity, as it takes three weeks for lockdown measures to show up in the hospitalization rates.
Yes. But the problem is too much Oxygen in the blood. Which there is not, otherwise you wouldn't be thinking about extra oxygen supply...
If nothing else, nuclear-powered cars would have made David Hahn’s nuclear reactor a lot simpler to build!

https://en.m.wikipedia.org/wiki/David_Hahn
> “simply out of scope” (of the protocol)

But it is in-scope for the framework, would you say not? If we want to evaluate the privacy aspects its important to understand the whole system.

First you said it’s a complete non-issue, and now you say actually we need to tweak things here and there in a serious fashion. That’s fine.

> “The protocol does not prescribe who is able to report certain Diagnostic Keys that have tested positive.”

It heavily implies though that it is a decision by the user. It says the keys never leave the phone, it also says that the keys with the users consent gets uploaded. Maybe what they actually meant is that the keys get uploaded alongside a signed cert of the local health authorities. Or that when you get tested the health authorities extract something from your phone and they themselves report using that. But it very much sounds like this is also a very important part of the protocol then.
Well it's not really meant to be used. It's nowhere near ready for everyday use.
Why are people bad at recognizing and interpreting exponential growth?
Never saw cobol in my life before, guess its "evaluate true when" part. not very explicit but readable. maybe it's just a well written example but something to work with
Weir – A System for Making Generative Systems (By Inconvergent)
I suspect that systems that defy understanding demonstrate something that ought to be a corollary of the halting problem, i.e. just as you can't figure out for sure how long an arbitrary system will take to halt, or even figure out for sure whether or not it will, neither can you figure out how long it will take to figure out what's going on when an arbitrary system reaches an erroneous state, or even figure out for sure whether or not you can figure it out.
Super cool -- one challenge will be that in order to live on the hot processors of today, these emitters will need to still work at around 400K -- the good news is that these appear to still work well at around 300K -- but it sounds like these go to nearly no bandgap at higher temperatures and shift into the infrafred. But yea, pretty awesome stuff..
It feels like elements of that split was always there. You have, on the one hand, very practical engineering cybernetics, what's standard control theory now (PID, optimal linear control, impulse responses and transfer functions, and so on). On the other hand, you have the more general (philosophical, "woolly") part that's filled with comparisons to biology, that deals with society and variety, general patterns, etc.

I once gave a friend of mine Medina's "Cybernetic Revolutionaries", and I think he found it hard to get through because of the latter kind of cybernetics, even though he was very familiar with the former kind.
I won't comment on BE because I simply don't know enough about it but I'll try to clarify some things.

Instead of storing bug state, git-bug store intent of the users in a chain of commit. When read, those intents are interpreted and compiled into the state of the bug at that point. When a concurrent edition happen and a merge is needed, the concurrent operations are reordered as well as possible and a new state is computed. This state might not be the perfect state but:
- it is guaranteed that the bug is in a legal state (no actual merge conflict making the data unreadable)
- even if the reorder is not the one you would have wanted, the intent of user is preserved. It is clear who did what and you can "fix" the state manually by adding more operations if needed.

I'm not 100% sure that it's the optimal solution but it works. It might break in some full P2P scenario. To be honest, I'd like to eventually move over a full DAG of operation instead of this purely linear way so the conflicts can be merged in a more optimal way. See [1] and [2] for details.

What I'm sure though is that storing the state directly in git and especially alongside the code is the bad way to do it. It does lead to have unreadable state and badly merged state, and has been stated as a reason for failure by at least one similar project.

> The entire point being that as you make a change to the code in a branch, when finished you can also close the bug in that branch. When merged, that bug is now closed.

It's a nice feature but implementing that way implies the shortcoming described above. I believe the best way to implement that is to have git-bug "aware" of branches and have it react to those changes to either change the state or recompute it on the fly so the conflict resolution characteristics can be preserved. See [3].

[1]: https://github.com/MichaelMure/git-bug/issues/212
[2]: https://github.com/matrix-org/matrix-doc/blob/erikj/state_re...
[3]: https://github.com/MichaelMure/git-bug/issues/16#issuecommen...
Oh, this is literally your job. There are different takes on this, and the detail is hard, but the broad strokes are:

* Follow your vision for the product - i.e. form a feature-set that combines the greatest compatible combination of requested features and your understanding of what the future of the product post those features will look like

* Solve the immediate next problem that will bring you most money fastest. Apply debouncing. i.e. the next blocker to money is feature A in the shape of a customer saying "we're ready to sign if you have A". Rank all amount of money, likelihood of customer actually executing (if you aren't able to sign on to a pilot w/ "we'll have it next week"), and divide by time. Do that. Do not re-evaluate for some duration of time.

* Find what you're selling. Sometimes this can be very different from what you're making. And the customer may be asking for a feature because they think that feature in the thing they're being sold will solve the problem they're having.

Honestly, no one here can help you with this. I suspect not even a course could help you with this. This you're going to learn by attempting to constraint solve here. Just learn from the pain fast and do what's necessary to keep the trust of your team (primary!) and your customer (secondary because there's more of them than the team).
There always needs to be a balance between external forces changing your priorities and your internal vision and strategy.

This being said, if the roadmap changes mostly based on new customer asks.. then you're not building a product, but doing custom development / professional services work.
The source paper[1], "Single-chip microprocessor that communicates directly using light" may be closer to your preferred level.

[1] - https://www.nature.com/articles/nature16454.epdf
Coronavirus found in air samples up to 4 metres from patients: Study
Currently the R0 in Germany has gone below 1, according to some models.

I don't think the measures will be softened before May, but according to the authorities, the ICU capacity will not be overburdened. Stressed to the maximum, yes, but not (or not much) over capacity.

Another issue is that with an R0 this low there will be a much lower rate of immunity. Which in turn means the restrictions can't be lifted because then the whole mess starts up again.
I agree, this is anecdote but a dysfunctional company I have seen had engineering stick on their own roadmap disconnected from customers. The end result was a product that failed to evolve to the market, no features were added for years because the engineering roadmap was always to migrate to a new exciting technologies, or improve fun features to work on but that no customers were using.
It might be good for the overall market in the long term. But it’s not good for the stock investments of the politicians making the decisions.
Do not overprotect them. Teach them that life will throw you curve balls, but they can get back on their feet. You can only learn to keep your balance if you have fallen a lot.

Teach them not to blame others - or circumstances - for bad things that happen to them. Teach them to take responsibility for their actions and not to ask for handouts.

By the way we were strict when they were little, so we had enough slack to give them space when they rebelled in their teens.

(3 kids, 2 have great jobs in IT, one is a high school math teacher, all three are successful and valued members of society).
Oh yes. And, thanks to that wonderful hardware, they are really fast ones.

Still, unless you are running a Unix like OS directly on an LPAR, you can't completely ignore the z/OS personality.
That's probably because they work in isolation from newer technologies which are constantly adding business rules. Most of the mainframe work I see involves maintaining old code bases and handling batch processing.
SUPDUP and EMACS supported "line saving", so Emacs could send a control code to tell a SUPDUP terminal to save lines of text in off-screen buffers, and restore them to the screen, so EMACS only had to send each line one time, and the SUPDUP terminal could quickly repaint the screen as you scrolled up and down through a buffer.

Here's my Apple ][ FORTH implementation of SUPDUP with line saving (%TDSAV, %TDRES), which saved lines in the expansion ram card.

https://donhopkins.com/home/archive/forth/supdup.f
No one example only proves it is POSSIBLE for paid sick time to not be abused.

It does not ELIMINATE the possibility or even imply it is unlikely.

And in a plague where working puts healthy employee and their families at risk, there is an enormous incentive to not go to work, regardless hazard pay incentives.

BUT I agree:

Paying workers hazard pay is a fair thing to do, assuming the company is capable of doing so.

And paid sick leave for sick people will save lives, again assuming the company is able to.

We can assume Amazon is capable of both.

To eliminate the incentives to abuse that system I would explain to all employees:

(1) You think they deserve hazard pay for staying
(2) You will conditionally offer it to them (or be up front why the business can't)
(3) You think they deserve paid sick leave
(4) You will conditionally offer it to them (or be up front why the business can't)
(5) If you are offering either/both hazard pay and paid sick leave, make it conditional:

Each employee signs a form noting they understand the benefits but also understand they can only work if healthy employees show up, and commit to showing up if healthy.

People tend to act honorably when they feel respected, they have given their word, and see the company is doing everything it can for them.

Despite all that, the incentive for healthy workers to avoid a plague are huge and legitimate, so the hazard and sick pay could still muck everything up. But there is not risk free solution.
Costs are within a family's control. There's just more communication involved.

And costs are just one side of the equation. Income is the other side. People can learn new skills. People can change jobs.
> The real solution is to think long term and rewrite all of these antiquated systems so that the next time there is an emergency it will be much simpler to find qualified developers.

Assuming the 're-written' version isn't similarly out of date by that point in time, the real solution is for business/government to finally understand that if your org depends on software then it's infrastructure that requires constant maintenance and scheduled replacement.

Getting them to understand that is an exercise for the reader.
Really impressed they stuck at it, by the sounds of it there's still a lot of work to do. Hopefully it won't be another 50 years before we see it adopted at scale.
Those controllers are still designed prioritizing cost over performance most of the time.
> The technique is limited in time, after the pandemic I'm hoping usage will drop to zero.

Do you think it's likely that, if successful, this same technique would be proposed to reduce the negative economic impact from the traditional seasonal flu in future?
Jekyll only adds that if you use their “SEO” plugin: https://github.com/jekyll/jekyll-seo-tag/blob/0943563d0aac60.... (I don’t use that plugin, so I add it manually to mine.)
Ask HN: Product Customer Disco
People have all the tools to invest but IMO sometimes lack the basic knowledge to invest and all the resources are scattered.

Prop: A platform that creates short learning paths for each side of investing, mutual funds, hedge funds, and possible errors in decision science, bias, randomness.

Deliver curated content, get guest speakers(profs, industry veterans) and complete a 2 month 4 month course on each learning path, project based where we use real historic data and grade them based on how they performed from lets say if they invested in stocks in 1990’s and what their returns were in 2010 or similar time frames

Once they receive a passing grade on their stock pickings, we unlock the final platform to start trading with their own accounts
Spain's plan to introduce a basic income to fight the economic crisis
It's not mentioned in the blog, but we are actively working with other providers to bring them on board. Hopefully we will have Digital Ocean soon, and I am hoping for Packet after them
Your post doesn't mean anything; but even the most charitable meaning I can assign to it is pretty bad.

Stuff like this is no better than "php bad!!1".
You can have the solution fast, cheap or good. Pick two.
We didn’t need different CCP numbers to have taken more effective action in the UK, we just needed to listen to public health experts rather than statistical epidemiologists and motivated thinkers in government. Germany, Austria, S Korea are all just as, if not more, connected to China than the UK and Spain but are faring much better because they have competent govt, distributed and robustly funded public health systems. This is not a black swan event because it has long been predicted by mainstream epidemiologists.
does it really? I am in the middle of reading it The Elephant in the Brain and I agree with the parts I read.

I strongly disagree with Weinstein and think he's spreading conspiracy theories
I found the link you are probably referring to, but the article doesn't give any clear conclusion, other that it is known, that ventilation is a very harmful procedure.
I would assume, for that reason, doctors wouldn't use ventilators until there is no other option to keep people breathing. Do you have a source for ventilators being used much earlier? If so, than this is certainly something which should be reconsidered. Is there any other treatment than ventilation, once the oxygene level in the blood drops beyond a certain level?
I think I can spot my blog in the Analytics section, I guess I'm the only one using Gauges as analytics.
You could still have geo sharding if the device also saved the location locally and shared the diagnosis for every zone it’s been in / downloaded the data for all zones. Ofc that would mean more data to process for travelers but it should still be way less than the data of the entire globe.
Hi, I'm also in the industry and in the same situation. The best life changing advice I can give is to introduce a one week delay between finishing features and releasing them. Adjust your software versioning so that you only release what was done a week ago. You have to stick to that one week delay as much as humanly possible. This gives a lot of confidence and room to breathe so you can enjoy work again.
while not specific to postgres, for general DB internals the CMU courses are top-notch.
intro: https://15445.courses.cs.cmu.edu/fall2019/
advanced: https://15721.courses.cs.cmu.edu/spring2020/
Being record aware comes from the punched cards that were the most popular way to keep data when they started evolving. They were born before ASCII (they use EBCDIC and, while ASCII was supported in one early IBM 360 model, it was dropped almost immediately)

Unix was born after magnetic storage, both disk and tape, were common. A file looks a lot like a tape.
It did cause massive inflation - in asset prices.

But when property prices, rents, and stocks go up, that's labelled a good thing, even though it's just as much inflation as a hike in the price of bread.

2008 was basically a hand-out to the 1% who caused the crisis in the first place. [1] There was a bit of political nudging and winking about how it would trickle down to ordinary workers, but what it actually did was keep wages low and create an even bigger shitpile of unserviceable debt at virtually all economic levels - which was just starting to fall over before CV-19 happened.

Our economic system is perfectly capable of imploding and destroying trillions in value on its own, and does so regularly. CV-19 showed that it's also fundamentally unable to deal with any kind of significant external shock.

With any luck this may raise questions about whether the system really is fit for purpose.

It may finally become clear that you can't solve a problem that requires cooperation and solid support for key front line staff with economic dogma based on cut-throat piratical competition and contempt for "disposable and low-value" front line workers.

CV-19 may not be enough to make the point, but there are other threats coming down the road - expected and not - and the choice is rapidly going to become evolve-or-die, in very stark terms.

[1] And some economic commentators had the gall to call the bail-out Keynesian, when in fact it was plain old corporate welfare which did nothing to repair crumbling infrastructure or provide key services or any form of social investment.
(5) Pay trained professionals to do chainsaw work. If you don’t have the time to learn how to use a chainsaw professionally, don’t use it.
Something doesn’t stack up here. If China’s response is such a shit show why don’t they have widespread transmission around the country? The US and Europe have had more warning than Chinese regions, but have been far less effective at managing the disease.
> Given that hospitals are running out of PPE

They aren't. You're being fed fake news. Hospital admissions and ICU admissions in NY are _way_ down. Nobody is running out of PPE. If you're going to dispute this, please provide a credible source familiar with the situation on the ground. My source is governor Cuomo: https://www.washingtonexaminer.com/news/were-ok-andrew-cuomo.... Don't bother pasting that teary eyed nurse who was "forced to work without PPE". That's fake news. Look it up. She's not a nurse, she's an Instagram "influencer".

> regular movements of going over speed bumps and potholes become potentially life threatening

Yes. Move them ahead of time, before they need intubation. Seems like people are in some kind of a stupor there. These are pretty obvious things.
I spent the better part of last night comparing e-readers. I really want something that is large enough to comfortably read a magazine (PDF), but everything seems to be 7" or so.

I'm with you. I can't wait until we have a proper A4 / letter sized e-reader -- or better yet 2x A5 that could close.

I haven't kept tabs on the e-ink scene outside of a little digging twice a year. Outside of refresh rates, it doesn't seem like a lot has changed. The price is still up there and the screens are still roughly half of what they should be.

I fell in love with the general idea of e-ink with the Pebble watches (Sharp's Memory LCD.) Having a device that just works and doesn't require frequent charging is such a pleasure.

What I really don't understand is why e-ink hasn't consumed the mobile market (like the Yotaphone.)

edit: proper paper sizing
Distributed Work’s Five Levels of Autonomy
It's kind of fitting that this was done in Eindhoven, a city that formed around the Philips light bulb factory.

It's a place that celebrates a history of making stuff glow.
Coronavirus Song – In Our Hands
His argument is self-defeating. If you have rapid exponential growth and would have to publish hundreds of megabytes of keys per day, this approach of contact tracing is useless and you must instead get the entire population under lockdown. If everybody is sheltering at home, nobody needs notifications of possible contacts, because everybody is doing what would be the response to such a notification already.

This approach, just like the manual approach of tracking potential contacts via paper and phone, is only of use in a scenario with a very limited number of transmissions and an R (reproduction rate) of around or below 1. Its purpose is not to reach such a situation, but to aid in keeping that situation in effect without severe measures. But severe lockdowns must first suppress the infection counts to such levels before any contact tracing may work at all.
Weird question, how do sysadmins normally administer windows? Rdp? Psexec? Something else?
Ask HN: Play Store removed our app, but allows WhatsApp
We are a FinTech startup in India. We give unserved people a credit card. To ensure recovery we collect user's contacts and use them to remind people of their bill if they don't pay. All of this is covered in our TnC, and we warn users of the actions we will take before we do so.

About two weeks ago, Google Play banned updates to our app from the Play Store citing this section of their Policy, here: https://play.google.com/about/privacy-security-deception/use...

We complied. This is how the screen looked before the change: https://imgur.com/a/o4Cvh7F

Here's how it looked after the change: https://imgur.com/a/gHP8BDR

We were approved after the change. However 3 days later, we were removed from the Play Store. So now no one can download our app, or update their app if they have a buggy outdated version.

Despite regular appeals, Google keeps redirecting us to the policy above.

Today I checked how WhatsApp handled user uploads, as it's the same thing we do; sync contacts on each launch(we don't sync when the app is not being used though). Here's how WhatsApp looks: https://vimeo.com/user112475576/review/406480240/9ca7c4e2c1

Can anyone help us with what should we do? With the COVID crisis our users are unable to depend on us for their daily spends. We're are the primary credit card for a lot of them, and not being able to service them now, is making us look bad.