skysight-inc/HackerNews huggingface dataset:
Some of the quotes here kind of cause cognitive dissonance with those who actually saw the crisis unfold from the ground, like myself.

1. The Italian government and many experts downplayed the issue at first: on January 31st, Giuseppe Conte declared "we're fully prepared", but it wasn't so: he was far more worried about his unstable coalition.

2. The ban on China flights was so only for direct flights: passengers coming from China through other Schengen areas were not screened at all.

3. Testing policy was inconsistent: at first, test everyone, then only those with symptoms, and it took months to increase testing capacity (also privately-owned labs were forbidden from performing tests)

4. Forbidding autopsies and thus delaying findings that were found to be useful later on (when first thrombosis was found in dead patients' lungs and use of heparin suggested, some experts called the finding "colossal idiocy")

5. Procurement of PPE and ventilators was done in the most inefficient, over-bureaucratic way possible. Disclaimer: it would've been objectively difficult given the shortages, but one could've done better. The appointed person to handle the job went through all the complex bureaucratic steps to do the calls to procure tests and masks, failing to get them in time. Then, when some companies converted themselves to producing masks, the price was arbitrarily fixed at lower-than-cost (and subsequently raised for obvious reasons). The first shipments of masks to some of the hardest-hit regions weren't even close to being PPE (they looked like dust towels). The way the government also paid, 30 days after invoice, made it slower than others who were willing to pay cash immediately. In short, a lot of initiatives were delayed for, to be frank, fear of being then accused of "corruption".

6. The coordination of the emergency response teams was, for a good while, largely inefficient. Some donated masks took a while to go to the hospitals due to bureaucratic reasons.

7. Lockdown was unnecessarily harsh, shutting down stuff that could've been kept running (some factories), and totally blanket, locking both regions with lots of positive cases and regions without significant signs of community spread

8. Inconsistent mask policy (granted, there aren't clear cut data even now)

9. At first reopening, a "secret" (and not signed by anyone) report full of epidemiological errors was leaked, warning of "150,000 Italians needing ICU care" by June if activity would resume (it was then torn apart by other experts)

10. There wasn't even a clear plan of reopening. No one even mentioned it, until a politician from the majority raised the issue and then the debate started.

11. Little to no financial aid to the sectors impacted by the lockdown, and extreme delays in providing it. OTOH, massive promises were and are still being made with plenty of numbers.
> Health insurance is not 100% free (e.g., you go to the
> doctor and he prescribes you some pills. You have to
> pay for those pills yourself. Sure the doctor
> doesn't charge you for the hour).

Just to be clear, the pills are still often subsidized and very cheap where they are not. It is uncommon to have medical expenses of more than 30€ per visit even for cosmetic concerns.

Also important to note that most of the fee of 300€ per semester of university pays for a public transport ticket which allows you to take busses and trams in the city where your university is located and usually also trains within your Bundesland.
At its core, Funes is not really about memory - I've always felt that is a convenient hook to hang a piece of metaphysics. I prefer to regard it as a parable about identity and what it means that a thing is a particular thing.

Maybe it helps to regard it as an elaborate variation on The Ship of Theseus: https://en.wikipedia.org/wiki/Ship_of_Theseus

Note that it's many years since I read it and I tended to read Borges to avoid having to read actual books on philosophy. ;)
The joy of writing and designing multiplayer games is the constant tension between cleverly hiding latency and trying to keep the view of the game somewhat coherent between players.

Probably the most relatable example is “peekers advantage”. A static player looking at a corner will always be at a disadvantage to someone coming round it if there is client side simulation of the local player. This is caused by the moving player getting round the corner and seeing the static player before the server is even aware of it (as they are locally ‘ahead’), the static player won’t see them until the movement makes it through the server to them. As such the advantage gets bigger as the round trip time between the players increases.

For the static player this manifests as seeing someone coming round the corner and having them dead to rights. Clicking the fire button, seeing the shot hit (in their local ‘ahead’ view) and then getting shot and killed by the moving player. Fast FPS games with short time-to-kill weapons are particularly affected by this which is why competitive games try to reduce the time the server spends sitting on updates by running at high tick rates.

If both players have a fast connection to the server (20-40ms) and the server is running at 60Hz (~16ms tick) peekers advantage still exists but is much less exploitable (~56ms best case). Versus the bad case where both players have a slow connection to the server (100-150ms) and the server is running at 10Hz (100ms tick) so best case becomes 300ms and the moving player enjoys an enormous advantage.
Swift, Rust nor Go provide support for exotic targets. If you want code to work in actually "weird architectures and little known operating systems", then your only option is C (or weird dialects of "C" in some cases).

At least that was how things were around >10 years ago, not sure about the current state of things. Anyone can chime in? Do embedded vendors etc. provide proper forks of newish, modern compilers?
How long did you try? Of course learning to touch type on a different layout will take some time but that doesn't make using brackets in programming languages unreasonable.

Using a German layout is very much a choice you have made and is no reason for you to demand that programming languages should make everyone else's life harder to acomodate those choices. Even for German text input, umlauts and sz are rare enough that it is not much of a hindrance to have to enter those via dead keys or compose sequences on a layout that doesn't make {} and [] a pain to type.
CJEU Judgement – First Statement
It's important to note here that the 4 seconds of latency here is a pretty recent development. 30 seconds used te be the norm.
The numbers are hard to trivially analyze, because there is no source that tracks "deaths caused by tesla cars" - NHTSA tracks deaths in cars and pedestrians, but e.g. not in other cars involved in the accident, even if potentially there car without the fatality was a contributing factor (fault is kind of irrelevant).

But the numbers we do have make Tesla's look pretty dangerous. Tesla's overall fatality rate may be low, but that's true in general of luxury cars (perhaps because they're driven in safer areas, by safer drivers, have fewer safety related faults, or protect their occupants better). Compared to similarly priced cars, tesla does poorly (https://medium.com/@MidwesternHedgi/teslas-driver-fatality-r...).

https://translate.google.com/translate?hl=&sl=no&tl=en&u=htt... - norwegian safety authority also concluding Tesla's are more dangerous.

Finally, specifically the autopilot is often compared incorrectly - autopilot isn't used on busy city streets or chaotic traffic situations (it's not capable of that yet) - but those are where most traffic fatalities occur. On the highway, fatalities are comparitively rare, even in "normal" cars. On interstates, in 2012 (I can't find more recent numbers), the fatality rate was 3.38 per billion miles travelled (source: http://www.bast.de/EN/Publications/Media/Unfallkarten-intern...) - and in some countries, much lower even than that (e.g. 0.72 in denmark). Since that includes old & cheap cars, you'd expect luxury cars to do better than that - that's the baseline autopilot should be compared against.

Comparing https://en.wikipedia.org/wiki/List_of_self-driving_car_fatal... with https://cleantechnica.com/2019/10/14/lex-fridmans-tesla-auto... I'd say a lower bound on autopilot's record is around 2 per billion miles - that's OK, but not very good. We may be missing autopilot related fatalities; if we missed even a single one, that would make these numbers look outright poor. That's a very rough estimate; but if we want any kind of reliable estimate on autopilot safety, you'd need much more data that we have (also more data on competitors!) Of course the very fact that we can't tell because data is so sparse is good! It means there are few deaths in this category; while driving in general may be dangerous, driving a luxury sedan on an interstate is fairly safe - exactly how safe doesn't really matter.

----

All in all - Tesla's safety record looks good compared to the average car, but not very convincing compared to similarly aged similarly priced cars - i.e. Tesla's competition. If you were to base your buying choice on safety, you probably should not buy a Tesla; but definitely should not buy the marketing nonsense. On the upside; it simply doesn't matter much, driving on autopilot-enabled roads is fairly safe anyhow, regardless of whether autopilot helps or harms safety.
Anyone might take offense, that's the point. Offense is taken, not given.
... as I said ‘where appropriate’.

However I don’t think for one minute that you’re going to get that super fast data everywhere. :-)
Very happy too work done on an a phone with open boot loader. That you can run Linux on Pinephone. A smart phone is just a smaller sized computer. Computers should be allowed to boot any operating system to be promoting computational freedom. Further consumer competition laws should Be changed to mandate open boot loaders and hardware specifications. With open source software hardware devices can be used longer and its thus better for the planet and environment. Closed source is not so environmentally friendly in that it will more often lead to hardware not getting software updates.

Great work Pinephone team!
Ive tried doing a 3D Game of life a week ago in Blender https://youtu.be/xEu-YKq91-A
It's pretty common amongst my geeky social circles in Paris, much less (for obvious reasons) amongst the musicians/partyers social circles, unfortunately.

What's very annoying is the social pressure: feeling compelled to say something, anything, when somebody say they won't have that drink in a social gathering. Just shut the hell up! (Saying that to myself too!)
Robot Barber – get an haircut during quarantine
and I'm learning ML to try make some awesome new game mechanics. Still a noob, progress here: https://twitter.com/GamesWithML
Unless you are looking for a "senior developer with x years of experience". I have a live, hobbies and family. I don't care to spend most of my free time fixing code in some obscure library I'm not ever going to use only to stand a chance to get a different job in the future.

How in the world did current developers EVER get ANY job? Who gives developers the chance to grow these days?
rip ath9k. it was too good for us <3
Project Ideas
Any cool ideas for python applications!
Well, looks like we found one of those truths that goes against the orthodoxy.
> We have a pretty solid roadmap to fusion power plants. ITER and DEMO don't have tremendous risks attached to them.

The costs of ITER have grown to be more than 4x as much as what was planned (and it is still in early stages so that's probably not the end of the story). I would not call that "solid".
The context implies it’s macOS on Apple silicon.
If you read the published report, you'll see that only one of the issues are actually related to scalability in any way (and most newly created projects learned their lesson of not using auto-incrementing IDs for many reasons). The same goes for many companies, the downtime is not because of any scaling issues but rather maintenance, code deploys or other things where humans are involved.

So while the reward of you promoting your product on HN can be high, unless it's very specific and actually solves their need, it just looks spammy.
The comments on this thread are gems. Thank you all. :)
Maybe that's a tempting thought, but it's clearly, how should I put this delicately… bullshit?
Do you mean Chaos-Mesh or TiDB?
For Chaos-Mesh, it is not a suitable tool for deterministic unit test case (like inserting an overflow value and expect to get an error).
For TiDB, it is easy to use `Alter Table` statement to enlarge the length of a integer column with zero impact on the online business.
can you elaborate or attach some source why LPP is not credible?
What do they actually look like? I'm struggling to understand what two gestures are 180 degrees to each other.
Nah, it's because this is the process for phone, not video, interviews, which are somewhat more accessible. And you need the ability to record the code at the end anyway (which docs provides and a video doesn't).
That's fantastic!! Great link. Thanks!
To the author: This site has major scrolling issues on Mac Safari in certain dimensions. For example, my window width is at 1347px and when I scroll quickly the layout goes crazy and everything flashes in different locations until the scrolling or overscroll stops. Occurs on any page on this site and in many other dimensions. Doesn't happen in Chrome though.
We make use of OpenResty and LuaJIT although we are moving away from them and more and more towards code written in Rust and other languages.
It's curious that Rust performed as node did. I thought surely it would be better
Finage Beta – New Way to Access Financial Data
We just released a new kind of financial data API and more service You can join free beta test today!
Finally someone who turns the "think of the kids" argument around and uses it for good!
Yeah, I think most people who touch/interact with backend/database code, even if not actually backend/DB developers, have a reaction nowadays to seeing auto-incremental IDs because it's famously hard to scale to any distributed architecture + introduces issues when you hit the limit.

Projects started in the last three years that I've collaborated/been part of have all ditched the auto incremental IDs.
> > In any case the fault is most certainly not merely marketing, it's a fundamental design flaw.

> I was actually referring to the ruling. The court did not take issue with the autopilot system, just with the way it's marketed.

I meant the parent post you were replying to, i.e. what I think MereInterest meant when he said "If there is a human in the control loop, then it needs to take into account human limitations", to which you replied "I am honestly not sure how to interpret your comment but I'll try to respond. The fault is not with the AP."

I did not mean to imply you thought it was a fundamental design flaw - sorry!
This looks really sweet, hopefully they succeed, but

>Device Warranty: 30 Days

that's not legal in the EU right? minimum is 1 year for businesses and 2 years for consumers?
Doesn't that tell you that the method of hiring is flawed in the first place?

If you care to weed out bad candiates, what help are 100% perfectly fine take-home exercises? The only thing that tells you is, that all of your candidates are viable in the first place. Just go into an interview with THAT assumption and ask the right questions.

Why do so many companies assume that people who try to get hired for a certain job don't meet the basic requirements? That gotta be the rule not the exception? That's just a bad faith assumption.

Just make sure your hire fits into your culture and give them sufficient probation time to grow into your codebase.
I think you're a bit starry eyed about Google.

I had a fairly high level of Gmail and Gaia administrator access for a while when I worked there, including the post Snowden era. Resetting the password on an account would indeed trigger an audit event, and I'd be asked what was going on. I could provide any plausible sounding reason and that was sufficient, it wasn't really investigated. And that was the right level of oversight because as far as I know nobody with that kind of access ever abused it by making up a plausible sounding reason.

Stopping bad insiders is really hard. Attempting to do it makes most organisations totally dysfunctional. There is one very famous kind of company that combats bad insiders regularly and with huge quantities of systems - a bank. Investment banks in particular. Whenever you read about 'rogue traders' they inevitably had to do a lot of stuff to disable all the various security systems trying to catch rogue traders.

Institutionally distrusting your own employees can lead to seriously messed up IT systems. It's one of the reasons that bank employees are notoriously unable to access so many ordinary external websites, or services like Slack. It's how you can get "administrators" that can't read the logs of the service they supposedly administer. Encrypted messaging services in particular are poison to an org that's trying to stop employees exfiltrating valuable data. Google can just about do a good job of it because it has an essentially unlimited budget, which it spends on rolling its own tools for absolutely everything and integrating it all into one uber-architecture. From an economics perspective this makes no sense - comparative advantage etc - and thus basically no other company can do it that way. They have to buy or deploy open source tools that use a wide array of threat models and security systems but 95% of them will assume a trusted admin. Then try and hack things on top to restrict what rogue admins can do. It's deeply unpleasant.
I think it died the moment Chris Latterner left.
Shameless plug: All the companies(Google, Microsoft...) are telling trust us. But, I believe that we should trust us instead of relying on third parties. They always change when businesses interest changes. This is where web3 is coming to play. Technologies like IFFS, safe network are coming. Looking at the scale issue, I guess this web3 takes at least 5 more years. But, this kind p2p technology is possible with small-scaled mesh. Mesh networks within our devices or families. From the beginning, I hate the idea of storing passwords in the third-party password manager. Later, I fell into the same trap because a managing lot of passwords is difficult. So, I building an open-source p2p password manger. Replicates the passwords within your devices, instead of storing everything at the vendor's cloud. It's half-way for the closed beta release. I would like to hear everyone's feedback on this idea.

Thanks
These articles always make me feel two conflicting emotions at the same time: "I feel so inadequate because I couldn't do this reverse engineering myself" and "it feels good knowing that I'd do a better job than Charlie even though I don't even work in that industry". Poor Charlie.
Where do you see a shadowban option on that screenshot?
You don't need a line of credit to start a business. You just need desire to work and ingenuity. People are more than happy to give you money if you are willing to do the work. There are countless rags-to-riches stories from all over the world.

But first you need to change your mind set. With self-limiting beliefs like those, you'll never get anywhere. Not only are they patently false, they don't help you in any way.

Get out of your echo chamber, hang out on same entrepreneurial forums (like this one!), read some inspirational books, learn how much is possible if you're just willing to try.
why does everything with a negative valence attract this criticism? surely there are plenty of times in one's life where he or she says negative things about something (a coworker, a boss, a partner, an acquaintance) without any intent to foster a "productive discussion". as though that is something owed to products / services / people / experiences / whatever that we hate for whatever reason. as though those things would somehow magically improve with any amount of "productive discussion". how about not everyone take it personally when someone dislikes something purely because of the experience that they have had with it? given the comments section, the only way for this "discussion" (some call it a post) to have engendered this tone of discussion while still being on the front page is either (1) everyone disagrees with the post, but hate-upvotes it anyway or (2) the points being made strike a chord with people. and regardless of which it is, this whatever the opposite of saber rattling is that causes this kind of reaction clearly misses the point.
The Life Ideas and Legacy of Pieter Hintjens (2018)
> You can run your own private island, but if you want to be "part of the fediverse" then you need to peer with servers in the main network, right? Which means tyranny-of-structurelessness organisational politics, because each admin gets to make their own rules about who they peer with, and so if there are disagreements in the network then you have to pick a side.

Sounds like normal human interaction to me. This is a feature, not a bug as far as I'm concerned.
I actually started to measure pockets with my phone and buy based on that. (5.5' OP3, but the PinePhone usually fits in the same pockets)
Not sure if you're purposefully missing the question here.

ithkuil is not asking if you can change the length of the integer column but rather if you somehow would have prevented the issue GitHub saw here with hitting the limit. So something like automatically updating the length, or giving the developers warnings, or alerts of some sort.

My guess would be no, as I haven't seen this in the wild.

And if the answer is indeed "no", your comment seems again to plug something that wouldn't actually solve the problem GitHub saw here.
Imagine buying puts on TSLA and tweeting this from @elonmusk:

> Stepping down from TSLA effectively immediately. Focusing 100% on SpaceX. Life's short.

This could easily be worth $100m's
Urbit, lol. Yeah.

If anything, Xanadu[^1], but that's a thought, a philosophy, and it'll probably never happen.

[^1]: https://en.wikipedia.org/wiki/Project_Xanadu
I like Swift a lot but Apple seems to be focusing on cross-platform within their ecosystem only, the fact that it runs elsewhere almost feels like a side effect. If your goal is sharing some cross platform code then I feel like you're better served by Rust / Go / Kotlin Native / C++ as these languages are making / have made and effort in that space.
Using the adulterated marijuana cartridges as a way to push anti-vaping campaigns was the same sort of disingenuous technique use to get people to not wear masks to save them for health care professionals at the beginning of the COVID epidemic. The authorities think the public are too stupid to understand or react to facts, so they lie to them and it ends up backfiring.
Nudge Theory Examples to Reach Your Life, Career, and Savings Goals
It was a figure of speech. Influence is what gives you control, of course.
If you can exploit it to make economic damage, would that count as a security bug?
> such as `go generate`--which already allow you to implement a crappy version of generics

The design document for "go generate" listed many motivating use cases, and not one of them was generics. The raison d'être for "go generate" is not to simulate generics. Some people just saw the character sequence "gener..." and made it about generics.
I'm curious about how Github generates 32 bit IDs in a distributed system.
ITER alone "is expected to be in excess of €20 billion" says Wikipedia, so fusion has gotten more funding than those $23b.
Except of course the Ipswich Mall, Brunswick St in Fortitude Valley, and the Queen Street Mall in Brisbane CBD. That's that I know of.
Wasn't BTC supposed to stop centralised authorities from controlling who can send money to whom?
"detail what is more complicated"...