skysight-inc/HackerNews huggingface dataset:
> Also if they ever get locked out from their oauth account they can use the email to create a password and login via the normal way.

This is exactly my point ! You can't recover your account if you don't know the mail used for registration. Even if you remembered it, no check could be made if Apple stopped to proxy the mails for one or another reason.

With other providers, you could always recover an account because your email address would let you prove the ownership of the account.
Frankly, I couldn't care less about whether you trust the app or not

The fact is, I send 0 emails and privacy and security are top priorities. I am passionate about E2E encryption so I have integrated loads of that in the app too

The only purpose an email address serves is password recovery. Period

TBH I am a bit tired of people trusting big tech so much. They are businesses, meant to make money. I make no money and don't intend to cash out because I am passionate about what I do. It's so frustrating to see how people blindly favor big tech
Why did that change in policy take place?
These login methods are the least privacy preserving methods to do a login. The identity provider instantly knows which services you use.
>As a teenager

>I’m not sure what demographic I fitted, but I am glad I have left it.

I think you already got it figured.

The older I get the more every authority figure everywhere leaves me alone. I was probably more 'innocent' as a teenager, though.
Not so sure, the future of the computer is being a client on a corporate controlled network. TPM is necessary to allow or ban clients on such network.
I contend there is no such thing as "weakly-typed" because it suggests it exists in opposition to strongly-typed systems - but instead I feel "weakly-typing" should be considered the absence of type-correctness checking by either the compiler nor the runtime - and that the term "weakly typed" and related should not be used to refer to languages with plenty of implicit conversion between types, because in those languages (like JS) the implicit conversions are very, very, well-defined and predictable ahead of time - TypeScript models JavaScript's implicit type conversions accurately, too.

JavaScript's more forgiving, and often surprising, implicit conversions are still rigidly-defined .

Remember that implicit conversions should never (ostensibly) throw any exception or cause any errors because implicit conversion should always succeed because it should only be used to represent an obvious and safe narrowing-conversion. A narrowing-conversion necessarily involves data-loss, but it's safe because all of the data needed by the rest of the program is being provably retained.
I think more than their own BBC researchers, Bragg uses the notes made by the guests themselves to guide the discussion, sort of like a circusmaster. The role necessarily comes with a bit of ego, actual or incidental.

I get what you mean though - I do IOT in phases, catching up on a few months worth before Bragg gets my back up a wee bit and I let the show lie fallow for a while.
Wow, the hand-drawn sketches they use on that landing page look MUCH better than the Corporate Memphis tripe they're selling, which is quickly becoming ClipArt 2.0 to these weary eyes of mine.
The Author generalized "fewer features lead to less downtime" to "simple systems have less downtime".

A simple system such as a hand-written web server is very likely to crash. It's very likely cannot serve many users if we don't make it serve requests concurrently. What's worse, one tiny exception in one request would bring the whole system down. It stops serving any request to any user.

A relatively complex system with a self-recovery mechanism added goes a long way compared to the former. The Erlang implementation is much more complex than "an Erlang without processes". Kubernetes is complex, and it definitely gives us less downtime than simple scripts we have written before we use Kubernetes.

The real world is chaotic. If a system needs to strive for less downtime, it needs to have some features that mimic biological creatures, instead of being idealistic simple.
LifeHash
After nearly 20 months, Boeing and Starliner have a shot at redemption
Well for starters I could do an MBA in my sleep, it's a total joke and so are most of the people that do them.
Someone has to provide the service, and if private sector is not interested Cuomo will find a friend/cousin/sister willing to run it, like $3000/month homeless shelters

https://www.youtube.com/watch?v=8WGjCeFyr1g
I don't know if it's a standard but both Postgres and MySQL have PREPARE statements, and any sane language driver will implement it correctly
Not a language, but intellij in Java does precisely that (and also has type migrations), but static typing is almost a requirement of that.
What kind of Galactic Federation defines their requirements in terms of time intervals defined by the orbital period of some random planet using numbers that are nice and round but only in some alien base?
This is a very common problem. He could just use an editor/trusted friend who has experience writing for pop audiences.
“Most people” don’t think about updates at all.

If they’re not automatically installed, they’ll never be installed. They’ll upgrade to Windows 11 when they buy a new computer. The idea of downgrading won’t cross their mind because the operating system and hardware are not distinct, decoupled components—if they don’t like Windows 11 they’ll just learn to live with it because that’s just how new computers are.
You can see Robert Martin's view on this, even for small and personal projects, here: https://blog.cleancoder.com/uncle-bob/2020/05/27/ReplDrivenD...
I would say this is the case even in C++ world. When modern stuff is used correctly (etc. optional, variant, constexpr + static_assert), most of the tests you will ever need are integration tests, basic smoke tests or feature-documenting-tests.
I was hired at Xerox in 1976 to work on the Xerox Star. I spent 43 years in the industry, and that job was by far the best I ever had.

I just published a novel about my experience at Xerox called
Inventing the Future. It’s historical fiction: real situations, fictional characters (except me). There are already histories of the events surrounding the Star, but I felt that a novel was the best way to capture what it was like. In my book no one knows how it's going to turn out.

Some of my former Xerox co-workers were kind enough to share their reflections on the book based on their memories of our experience:

Derry Kabcenell (file system architect, later Executive VP at Oracle): Although I joined after the earliest unformed years of the Star project, I can say that the events portrayed are described in a way that matches my recollection. More importantly, the book captures the feel of the place -- the sense that we were privileged to be doing
something new and important,

Paul McJones (architect of Pilot, the Star's operating system): I worked at Xerox SDD in Palo Alto from late 1976 to spring 1981. The book captures the spirit of a relatively small group within a large established company building a revolutionary new product. Seeing and using the Alto from Xerox PARC was to see and feel the future.
By all means, show me a new car with a list price of 3-5k. Current ICE cars already cost 10x that amount, and EV cars are generally even more expensive. On what basis do you expect new cars to ever cost 3-5k? That's the range of an electric bicycle, not a car.
If you have an Apple ID, you’re already implicitly trusting Apple to use that data appropriately. Apple doesn’t sell its user data.

So anybody who is using Sign In with Apple trusts Apple to do the right thing.

Besides, what monopoly? Apple is perfectly happy with other single sign ons — provided you also offer Sign In With Apple.
Show HN: Talk about modern pseudo random number generation
I was under the impression that the Apple email that you get is not a real email address with an inbox? Is it? How can you verify a user the real owner of the email?

If they are locked out of the oauth account, presumably they can't check their inbox.

edit: Oh, do you mean you ask for an email address after they already flow through the oauth process - because that's the worst of all :)
Yes. It is important that more developers stand up to this kind of bullying. Apple needs to respect developers more and, if it wants them to integrate Apple services they should instead offer incentives rather than threats to them. As both a developer and an Apple user, I don't care about Apple ID and so why would I wish to waste my precious time adding features I am not interested in? (I use Apple products but I never use Apple ID anywhere because I believe it weakens my privacy - why would I want to share more personal data with Apple, a company that was part of PRISM and used to sell user data to the government?)
Agree. Regex literacy is a big skill to have too.
Prominent figures in the biggest winners of the IT boom were toxic. What makes you think other ceo's of smaller companies are not going to look up to the winners.

>A lot of bad behaviour was tolerated in previous decades across many industries.

IS tolerated. Petty, irrational bosses are reality in many sectors not just low level services. You sound like you never worked blue collar job and only heard about it or observed it from afar.
> The key issue is that you have a single event loop that all visual and human interactions need to be handled by because that's the only thread that can interact with the DOM.

Isn't that normal? A single event/drawing loop. Would there be an advantage to two threads drawing? Sounds pretty novel.
> there is no reason for you to act so smug.

I'm not smug. I'm battle-scarred. I'll lay odds that I've had a lot more rejections than you have, and probably gotten a lot more pissed off at Apple.

Being an experienced Apple developer (since 1986), means that I have been incandescent with rage at Apple -many times. All of us have. Apple can be a real pain to work with.

I still develop for Apple, but I am not a "fanboi."

BTW: The rejection reason says that, because it's canned. It covers a lot of areas. I have received many such vaguely-worded rejections, and had to figure out why they bounced the app. In a couple of cases, I have been able to get people on the horn (PROTIP: Don't be calling them "smug," and be polite, even though you want to throttle them), where they have explained the issue.

[EDIT]: Also, branding is something that a lot of geeks don't understand, but it is very important (and valuable). Many of the seemingly insane moves by Apple are because they are building and/or protecting their brand. That "smugness" is actually a deliberate part of their brand. I don't think that it's a good idea for their fans to reflect it.

In terms of branding, a corrupted branding element is exactly the same as no branding element (except it's legally actionable).

Speaking of which, did anyone see this week's John Oliver show? I get the feeling that HBO is a bit peeved with Disney.
Cities supercharge innovation. Can an online community ever compete?
> You may as well argue not signup to anything using gmail because, heck, google might go out of business.

I personally avoid to do it, but that's not the point.

Every other third party allows account recovery by mail : if you want to stop using FB or Google's SSO, you can ask the website to send you a mail to prove the account ownership.

If Apple's SSO stopped working (because Apple stopped it, banned you, because you dont have Apple devices anymore so you are locked out of their proprietary 2FA), none of those websites could send you a recovery email.

> That is pure BS.

I don't feel like I've been insulting, so please don't be either.
That wouldn't fly past App Review
I meant the US and Europe. And by extension places of that nature. Slower growing aging populations and the realization that low density single family both burdens local government with costly infrastructure that generates low revenue. Like a sewer main with 100 customers per mile. Only sustainable when growing fast.

There is a lot of multifamily being built despite fairly intense NIMBYism. And despite that you're seeing cities getting rid of R1 zoning.
Ahh, so one continuous block of wood following the grain vs sliced together chunks that will bring to mind Frankenstein's monster.

Hmm, I wonder if you can feel the difference when you rub your hand over it if it's just polished, probably not if painted. So perhaps people who want polished wood for their staircase might go for the older style even if it's more expensive?

Yea, flubbed on the screenshots bit, was just thinking images of stairs and as I expected them to come from your computer my brain clearly went to screenshots instead of pictures =)...
Common Sense by Thomas Paine: https://en.m.wikipedia.org/wiki/Common_Sense
NASA science chief says it’s OK to be “worried” or “terrified” about Webb
Show HN: Till – Unblock and scale your web scrapers, with minimal code changes
It is a great question, but it's like jumping on refactoring: you'll solve all the problems that were obvious with the old solution, but introduce new ones that you didn't think of that were already solved by the old one.

Basically, "thermal blocks", which is mostly what's used in construction in areas where they are used (Europe, rather than filled-in bricks) need to be modified to accommodate imperfections: you need half bricks, third-bricks, and they are easy to make on the spot.

For automated construction, you'd have to have a bunch of these pre-made, and the larger the block you are building with, the more types of those smaller ones you'll need.

These blocks are also relatively simple to put electrical and plumbing installations in (it's a lot more demanding to make "channels" in concrete than bricks).

Anyway, block construction is way cheaper than eg. gypsum board construction for interior walls in Serbia, and other than taking a lot more space, being heavier, and requiring curing time, it has a bunch of better properties (acoustic, thermal,...). The price not being high is actually the reason this is not further improved.

Filled-in bricks are mostly used for decoration of outside walls these days (and usually as plasterboards these days), and as far as paying for things go, humans will happily pay the most for good looks!
> For anyone suggesting giving a de-googled lineage phone to anybody who isn’t a technologist or doesn’t have days and days to spend tweaking a poorly-supported-outside-certain-jurisdictions device, just, please, don't.

ftfy. I get a bit fed up with seeing these things promoted. I’m from New Zealand, not the US or Europe. Where do I get one? Who fixes it when it buggers up? Why does it cost so dang much? Why is it such a slow piece of crap compared to my iPhone 11? etc.
A Hollywood scriptwriter federation.
I think the nginx that members of the public can get from their package manager does not have this feature, and will force each client other than the first to either wait for the entire body to be downloaded or wait for a timeout and hit the origin in a non-cacheable request.
Request coalescing in a shared cache does not solve thundering herd, it just reduces propagation to backend services. Your cache is still subject to a thundering herd, and may be unable to keep up.

The only way to solve thundering herd - which is that a load of all requests arrive within a short timespan - is to distribute requests over larger timespan.

Reducing your herd size by having fewer requests does not solve thundering herd, but may make it bearable.
(published fatalities, the same way a jammed tunnel with thousands of cars recently flooded and the official death toll in all of China was 53.)
Is there any guide on how to make a Linux-based print server which would be autodetectable by all the major OSes? I feel like we need a dedicated print server for our office (where there are many computers running Ubuntu, Windows and MacOS) because the printer doesn't work reliably enough. I have never actually seen such a scenario in the wild - people seem to always connect to network printers directly (they also used LPT and USB printers shared via the standard means of Windows in the past).
It isn’t that mind-boggling to me, it’s Microsoft’s way.

Release a phone platform. Then another, incompatible phone platform that looks and behaves practically identically.

Reminds me of Windows 11. Three different kinds of control panel, two different kinds of context menu, infinite different kinds of window frame.

MS competes with itself!
> MS to burry the Meltdown/Spectre vulnerable family
> Once you view the product requirements through that lens, it makes a lot more sense.

No it doesn't. You can disable these mitigations in kernel right now and there is no guarantee that intel won't have any vulnerabilities in future micro-architectures. So you need the support to enable/disable future mitigations in kernel anyway.
Tech is automating away a lot of the work being done by people currently called lawyers. Whether you think that work is "secretarial" or "actual legal work" is a matter of opinion.
Apple's SSO may not be eternal but it's also very unlikely to disappear overnight. If it is indeed going to be phased out you will have advance notice of this and a transition period.

I agree that in a perfect world you'd provide your real email address and solve this problem. But developers and companies have repeatedly proven themselves to not be trustworthy and the majority will misuse any contact details for spam which users do not want. In fact there wouldn't be a business case (nor appeal to end-users) for Sign in with Apple if this wasn't a real problem.
REPL and expression-based are not limited to dynamic languages. REPL-oriented programming as it's understood by Lisp/Clojure users might be, I'm not sure.
I think anything that is growing and is new has a tendency to become complex. Simplicity is a constant balance. You have to allow end endure the complexity to get anywhere new and then re-integrate it by creating order. Such is coding and such is life haha.
No Apple cell phone required.

https://firebase.google.com/docs/auth/android/apple
Nah, the message itself could be justified, the messaging isn’t. Especially the hostility the writer has decided to show to their users.

I don’t care how upset you are with Fruit Co., you don’t take it out on Fruit Co.’s users. Who does one think one is, Epic?
As a teenager I realized that I could get away with anything because of how I looked. I could effortlessly shoplift whatever I wanted and did so for many years. Later on I got away with selling drugs for a long time, including being pulled over but not searched with a quarter brick in the trunk of my car! I did get raided later but got very lucky as I had mostly cleared house and they did not find the several sheets of LSD in my freezer.
The Apple-provided e-mail address forwards to their real email, so you can still use it for e-mail verification and communications. It just means the user can deactivate the alias at any time and stop further spam.
Retries tend to amplify it, but a more common cause is scheduled tasks in clients/end user devices.

E.g. all clients checking for an update at 10:00 UTC every day, all clients polling for new data at fixed times, etc.
I think the tasty addition was lead acetate.

https://en.m.wikipedia.org/wiki/Lead(II)_acetate
Why the drama? Why not use a web app instead of a native app?
> Don’t use apple SSO because apple might not exist one day?

Yes. And more to the point, because that Apple service may not exist in the future. Or Apple may determine that a particular app or service can no longer use its service for whatever reason, and you as a user will not have any choice in that manner. It's all been done before.
Maybe not the smartest idea to post this on a public forum :)
Considering the exact sequence of events to trigger it, I feel sorry that I found the bug. Seems like a really hard one to trace and debug. Almost feel like I should be apologising, rather than thanking you for taking a look!
> that Foo decided to disclose your email to.

Or, just as often, anyone that has picked up my address from lists originally obtained via a hack of some sort because one of those entities has had lax security.
I agree, right now the home page is too specific about elm and types.
Thanks. There likely are relative advantages to HTTP/3 QUIC. Here's this from Wikipedia:

> Both HTTP/1.1 and HTTP/2 use TCP as their transport. HTTP/3 uses QUIC, a transport layer network protocol which uses user space congestion control over the User Datagram Protocol (UDP). The switch to QUIC aims to fix a major problem of HTTP/2 called "head-of-line blocking": because the parallel nature of HTTP/2's multiplexing is not visible to TCP's loss recovery mechanisms, a lost or reordered packet causes all active transactions to experience a stall regardless of whether that transaction was impacted by the lost packet. Because QUIC provides native multiplexing, lost packets only impact the streams where data has been lost.

And HTTP Pipelining / Multiplexing isn't specified by just UDP or QUIC:

> HTTP/1.1 specification requires servers to respond to pipelined requests correctly, sending back non-pipelined but valid responses even if server does not support HTTP pipelining. Despite this requirement, many legacy HTTP/1.1 servers do not support pipelining correctly, forcing most HTTP clients to not use HTTP pipelining in practice.

> Time diagram of non-pipelined vs. pipelined connection
The technique was superseded by multiplexing via HTTP/2,[2] which is supported by most modern browsers.[3]

> In HTTP/3, the multiplexing is accomplished through the new underlying QUIC transport protocol, which replaces TCP. This further reduces loading time, as there is no head-of-line blocking anymore https://en.wikipedia.org/wiki/HTTP_pipelining
Many comments here assume that going to law school == becoming a lawyer. This is not always true. Many go to law school since it a degree that you can use in many other business fields even without practicing law.
What's your solution to the systemic problems they raise?
> perhaps it happened this way and jobs was overly caustic, but zooming out from that emotionality, the designated outcome was not necessarily a bad one.

You walk down the street and someone you know in passing tells you:

"Hey, you gain a lot of weight. You look fat and ugly. Nobody will love you so loose weight."

don't get offended they are just trying to help you. Humans are emotional creatures, treating them as if they are robots is reserved for psychopaths.

Besides if you are the boss and team fails to deliver, guess who is to blame first. Its the fucking boss who failed to access the task and oversee the progress.
> we use the email address as a fraud signal for some payment providers

This is not in the interest of the user. As a user I do not want yet another company getting my details and assembling a profile on me under the excuse of fraud prevention, especially when my bank offers 3D-Secure which shifts all fraud liability back to the bank.

> all the sorts of emails that users tell us again and again are very important to them

According to every company every single one of their spams is important. It's not up to you to decide. If the users want your notifications they will find a way to receive them (as far as I know the Apple relay email address does just forward emails, so unless you're breaking a - presumably reasonable - rate limit it shouldn't be a problem).
Fulfillment by Shiprocket
What does this mean for the security of FaceID? Anyone with deeper knowledge? I am not very knowledgable in this field.
I've yet to see something in the wild that starts simple. Usually it starts too complicated and just gets worse over time.
What if my email address stops getting mail for one or another reason?
In particular, similarly to Smalltalk and differently for example from C++, Objective-C does method dispatching from empty interfaces and has does-not-understand functionality.

Everything Is An Object in Smalltalk, and of course this can't be true in Objective-C due to its mixed heritage.