skysight-inc/HackerNews huggingface dataset:
That’s all well and good but it seems really unnecessary to paywall it behind what is really an overpriced SSL certificate.

IMHO certificate authorities are a technology looking for validation in their necessity and truthfully the whole business model around CAs is bunk.
I can use DNSSEC to provide a verified chain of trust all the way up to the root (.) signed zone. Regardless of “who signed it” anything I put into the DNS zone should be trusted to have been added there by someone who has control of the domain and access to the private key that can sign the zone.

This whole song and dance of “pay us thousands of dollars each year for us to verify that you’re allowed to use your own trademarked images” is already a solved problem in the copyright system. See someone using your copyrighted images where they aren’t permitted to? You can sue the violating domain owners for copyright infringement. No “trusted third party” CA handwaving required.

Trust me, even the most ambitious of scammers aren’t going to risk that copyright infringement suit when it can potentially result in domain seizure just to spoof BofA’s BIMI image.

I understand people like having this third party system that someone else has done all the work verifying Ts are crossed and Is are dotted but the current system in place (third party CAs) are hardly trustworthy themselves and there are numerous examples of CAs that have “gone rogue” and provided certificates for sites that they should not that you can find out on the web if you go looking which is why I’m a strong advocate for pushing DNSSEC in the first place. The domain itself becomes its own source of truth. If I tell you X subdomain should have Y certificate signed by Z authority and that information is securely verified through DNSSEC I can trust that it came from someone with access to the signing key inside that domain.
Scaling Hadoop on Cloud
Actually I don't get how Apple always gets away with the sh*t they are doing.

All Smartphones on this planet use the same USB-C charging port except iPhones. And as far as I remember, the European Union requires the manufacturers by law to use USB-C, because before the law every phone came with a different power adapter.

Next example, OS and browsers: Every Operating System has to offer the user the choice of which browser they want to use. Except for Apple, they offer a choice of which UI you want to use, but on iOS the browser engine is always Safari (which kills competition hard on iOS devices).

No, I am not a big fan of that Microsoft move, because I think they should respect the users browser choice. But I am even less a fan of Apple doing things nobody else is allowed (for good reason).
SEEKING WORK | FREELANCE | REMOTE

I'm a Product Designer with 3+ years of experience at SaaSPay, where I've been responsible for designing the user interface and experience for the BNPL platform. Initially, I was the only designer working on the MVP, but now our team has grown to include a design head and two other designers. My responsibilities include conducting user research, creating wireframes and prototypes, designing the visual interface, and continuously improving the design based on feedback and data analysis.

You can find my LinkedIn, Behance, and Portfolio Website links, as well as my CV/Resume on Google Drive. My design tools include Figma, Sketch, Adobe XD, Adobe Premiere Pro, and Adobe Photoshop.

- LinkedIn: [https://www.linkedin.com/in/krishna-agarwal11/]
- Behance: [https://www.behance.net/krishn_agarwal]
- Portfolio Website: [https://krishna-designs.webflow.io/]
- CV/Resume: (https://drive.google.com/file/d/1zoSQycezOKJoSrKdYCrf04KQ3k2...)
- Email: krishna.agrwlx@gmail.com
Since we’re being pedantic… Wait’ll you find out what happens after they do the drawings.
GitHub: https://github.com/selefra/selefra
Here is the decision:

https://curia.europa.eu/juris/document/document.jsf?text=&do...

Via a DeepL translation, the relevant passage is:

"Indeed, Article 82(2) of the GDPR, which specifies the liability regime whose principle is laid down in paragraph 1 of that article, adopts the three conditions for the claim for damages to arise, namely a processing of personal data in breach of the provisions of the GDPR, damage suffered by the data subject and a causal link between the unlawful processing and that damage."

Thus, the interpretation seems to align quite closely with those for product safety liability. In both cases, providing the proof is probably the difficult part, although there are some blatant cases that would be easy enough to pursue (e.g., a data breach that has led to identity theft that has caused economic and other harms to a data subject).
Firefox and Chrome accounted for a third of browser marker share when the iPhone came out. It came out with no App Store, and there was no guarantee MS would develop IE for iOS.
Don’t merge. Rebase only. Keep a linear history.

When committing, do a ff-only of ‘main’ to your branch. Yes, this forces everyone to rebase before “merging” but in practice, this results in the least amount of failures, tests being run after you resolved any conflicts, etc.

If you can use GitHub merge queues, that solves a ton of this, and you can run tests on the final merge before actually merging instead of relying on rebasing.
It's not even an argument. It's just stupid denialism. It reminds me of the people insisting on the cusp of abolishing slavery, that African Americans are not technically people, so they can't really think, and so on. And providing lots and lots of pseudo-scientific, but plausibly sounding (at the time) and partially technically correct reasons why this is so. An example of this is the phrenology scene in Django Unchained.

You can always dress your bullshit in half-truths.

In this case, this person's description of AI is not wrong, but... it also described human intelligence. There's absolutely no difference.
It seems like another case of the road to hell being paved with good intentions, most places want/need redundancy and some managed devops and so a few ec2 instances and managed RDS is affordable enough and checks a lot of boxes, but after people start down this path it seems almost irresistible to start drilling down into managed kubernetes, spark jobs, to start ingesting some events we'll just introduce glue, and that plugs right into S3, and look how easy it is to plug in athena, add some quick alerting with cloudwatch, and the next thing you know you're vendor locked and having to hire a full time devops person with AWS experience to configure, manage and keep on top of it all.
When they say k8s is "easy" they mean "for developers", not people/automation running it.

Like, compared to implementing hitless rollback over bare metal services k8s way is "easy", just set some stuff in YAML and have proper healtchecks in your app.
"We built a video stream processor by splitting every 1080p+, multi hour long, 30-60fps video into individual images and copying them across networks multiple times."

Not surprising that didn't go will. This strikes me as a punching bag example.

Anyone who has worked with images, video, 3d models, or even just really large blocks of text or numbers before (any kind of actually "big data") knows how much work goes into NOT copying the frames/files around unnecessarily, even in memory. Copying them across network is just a completely naive first pass at implementing something like this.

Video processing is very definitely a job you want to bring the functions to the data for. That is why graphics card APIs are built the way they are. You don't see OpenGL offering a ton of functions to copy the framebuffers into ram so you can work on them there only to copy them back to the video card. And if you did do that, you will quickly find out that you can be 10x to 100x more efficient by just learning compute shaders or OpenCL.

You could do this in a distributed fashion though, but it would have to look more like Hadoop jobs. I predict the final answer here, if they want to be reasonably fast as well, is going to be sending the videos to G4 instances and switching the detectors over to a shader language.

In general, if the data is much bigger than the code in bytes, move the code, not the data.

IO is almost always the most expensive part of any data processing job. If you're going to do highly scalable data processing, you need to be measuring how much time you spend on IO versus actually running your processing job, per record. That will make it dead obvious where you should spend your optimization efforts.
Microsoft Authenticator is the app that would literally refuse to work unless you first consented to data sharing and telemetrics. No fucking go. Thankfully, F-Droid has a useful alternative (Android only, of course):

https://github.com/beemdevelopment/Aegis
I think Roblox’s business model is similar to that of sweatshops’ in a sense that they’re enabling minors to earn money when there are no better alternatives. Is that truly a bad thing? From westerner’s perspective, a sweatshop might be an exploitation but for the workers’ perspective it’s the best opportunity available to them.
Mention of Chandler triggered a memory of a book.

"Dreaming in Code" by Scott Rosenberg. Dives into the history of the Chandler project. ISBN 978-1-4000-8247-6. I don't know if I agree with the blurb on the back that it's a successor to Tracy Kidder's "Soul of a New Machine", but I remember it being an interesting read.

Sorry, doesn't help with your Agenda problem.
Russian Offensive Campaign Assessment, May 3, 2023
- "According to the U.S. Centers for Disease Control and Prevention, each year in the U.S., RSV leads to approximately 60,000-120,000 hospitalizations and 6,000-10,000 deaths among adults 65 years of age and older."

Those are respectively 0.1 – 0.2%, and 0.01% – 0.02%, annual risks for this subgroup (55 million persons).

The OP discusses three studies, with a combined N of about 17,500 (12,500 + 2,500 + 2,500) (the non-placebo groups). They apparently attribute one death to this vaccine (in combination with an influenza vaccine), which is 0.006% of the participants of the three studies.

I don't know how to interpret this. The FDA's endpoints are "RSV-associated [lower respiratory-tract disease]" and "severe RSV-associated LRTD". Okay. I guess they're ignoring mortality because its small-number statistics aren't meaningful to interpret. But then why endorse a vaccine at all, if the mortality rate is so low? You'd need a vastly larger study to answer the question "does this therapy increase or decrease the risk of death", because the probabilities are microscopic on both sides.
I feel like it's a semantics thing. To me the meaning of microservices has undergone semantic drift to the antipattern in the article where every little component or database table is its own service with an associated "pizza team".

It's fine to just have plain "services" to do things like this where you need to leverage another OS/framework/whatever and just hive off something like PDF conversion while your core application remains a monolith.
Humans, animals, plants, microbes, etc are that technology. Life is self-replicating nanotechnology machines. If synthetic biology works - and we know it does, we have already created a synthetic cell - it's perfectly possible. Not to mention it could evolve on its own. Humans are Von Neumann probes in our environment.
Not yesterday. Been a few days
Oliver Cromwell
Sorry but this just sounds like victim blaming. If a guy threatens you with a stick, and you take his stick away and he pulls out a gun and goes “look at what banning my stick led to!”, it’s not the banning that’s the problem.
I finally realised after using Lambda for almost a decade (started to use it when it was released 9 years ago) that instead of think about apps that you map to lambda functions you should think about features instead.

A simple example: I have a SPA that has the following features: auth(login, logout), dashboard, feature a, feature b. I can write a few very simple lambda functions and deploy these the same way (IaC). What do we (my team) win? We can implement each function in a language we want. You have a feature that is too slow? Rewrite it in Rust. You have an amazing Python lib for feature a? Use Python. What else? We almost never touch auth, so if a feature has a bug it does not impact the entire application. Security is better because we can allow individual functions to access part of the infra they really need to access. Lambda functions can call other lambda functions as well.

Downside is that we cannot use a shared cache that is easy with a monolith. People need to design the boxes well which functionality goes to which lambda function. We have to use distributed trace ids to track requests.
That is probably the best use case for microservices (althought I'd just call them "services" at that part).

That assuming they are big enough to warrant that in the first place.

IMO if it is a dozen unrelated endpoints but all of that still takes less than dev/month to manage it's probably entirely wasted effort to "fix it"

And if any of them grows to warrant dev/month or more.... separate that one and only that one out of that.
Official SDK for macOS (make sure to pick the right one, arm64 or x64): https://dotnet.microsoft.com/en-us/download/dotnet/7.0

Then, an IDE of your preference:

- VS Code: install C# extension and Roslynator (it adds useful analyzers)

- Rider: provides everything out of box, is more user-friendly (especially for people who used to big and fully-fledged solution) and has much superior debugging capabilities but is paid and has higher memory and battery consumption
Ask HN: Details on 04/2021 DigitalOcean data breach?
In April 2021, DigitalOcean suffered a data breach [1], exposing some billing details. They informed affected customers by mail and offered to answer any further questions via their privacy@digitalocean.com address.

Since then, I have regularly asked for updates on how this breach happened and if they would publish a postmortem for this event. They assured me that they would share more information once their investigation is complete.
In September of that year, they started ignoring my requests for an update, and I haven't heard back from them since.

While this is a relatively minor event in the grand scheme of things, it left a bad taste in my mouth. Did anyone dig deeper into this and got more information on what actually was the cause for this leak? Maybe there's a DigitalOcean employee around who can shed light on this?

[1] https://www.securityweek.com/digitalocean-discloses-breach-involving-billing-information/
The Running Novelist (2008)
A lot of that is in the article. Nice little graphs of it too.
But why is it more fair to punish someone more because they're poor? Matching the fine to income/wealth is the best way to ensure the impact to the recipient of the fine is similar, regardless of personal wealth. A poor repeat offender may be bankrupted after just a handful of fines. A rich repeat offdner may be able to continue doing it hundreds of times afterwards without much issue.
Yep. It’s called the market place.
Yeah, the most WTF thing I've seen React do is to mess with console.log by silencing them (WTF #1), which was particularly appalling since React did it only because it run the rendering twice under StrictMode (WTF #2), and only during development so you're not sure what the real behavior will be until you run it on production mode (WTF #3).

Messing with the console is such a no-go that I'm appalled it even passed the drawing board, making the "React isn't a framework, it's a library" argument even more bonkers than it already is.
Every time someone says "stress test", I will point out that the stress tests did not model for interest rates rising like they did, which triggered the current problems we're having (or, really, interest rates being so low for so long was the actual problem IMO, but that's a whole separate conversation). Stress tests as currently implemented would not resolve the issue, and even if they were so wise to reactively throw in more aggressive changes to interest rates to these stress tests, would that be enough to catch the next problem?

https://www.federalreserve.gov/supervisionreg/dfa-stress-tes...

See Tables 2.A and 3.A in 2022 Stress Test Scenarios (PDF), covering a 3-year period starting in Q1 2022. Look at the 3-month Treasury rate. In 2.A, rates go up to 1.5 by Q1 2024 and sit there. In 3.A, rates sit at 0.1 for three years.

Rates are not the only variables, but the point remains that the interest rate changes that triggered these problems do not appear in the stress tests.
In my state, if you get caught speeding too many times, the fines increase until they finally take away your driver's license.
No, hold on. That's not what I implied.

My understanding is that the private key is stored on your own device, unless you decide to use something like iCloud Keychain (which should be encrypted).

The public key, on the other hand, is stored on the service providers' servers. That is used to create a "challenge", which I guess on your phone you will need to "decrypt/sign" with the private key to prove that "it's really you".

That's how I understand it.
There's a middle ground between cloud and on-prem

You don't need to go all in on buying racks and other hardware, when you can rent servers at Hetzner at a cheaper cost than aws.
Have you tried `async` pipe and `takeUntilDestroyed`? I only ever `subscribe` if I need to trigger side effects, like setting a form validator based or a value (probably can be replaced by async validators) or modify DOM outside of the app root.
Sun Tzu wouldn’t like the cybersecurity industry
I really liked South of the Border, West of the Sun - it's a rather short novel and IMO pretty focused thematically. And then, of course, Norwegian Wood is a must-read.
The UX/UI debate and how we should be doing UX research
How can you calculate someone’s income in a way that makes this feasible? Wealthy people 1) dont have most stuff to their name directly, 2) have capital gains which make income ‘spike-y’, 3) make money on many jurisdictions, many which may not be visible to the country fining the person

Just curious how this works in practice
AWS Step Functions are bad for so many reasons. Scaling, pricing, developer experience, etc.

It is clearly made by people who don't really understand (or does not care) how distributed workflows work.

And pricing are prohibiting to run it at scale. In my opinion it should be free to use, provided you glue together other AWS services with it.
Counter-argument: The current system actually punishes them _less_, because the marginal value of money is lower for them.

A $50 fine will punish someone with $20 in their bank account a lot more than someone with $20 million.
Yes. Or rather, you should pay an amount that makes you likely to stop doing whatever it is regardless of wealth/income.
That is how you get to the current state of car dependence in the US.

Parking costs a lot. It should not be subsidized.
“…and finally the work will be done completely by AI.”

How will the AI be trained on novel patterns of interaction, for example new products or previously unknown problems?

It seems to me that (as the article suggests) high level human support capabilities will be more valuable in this scenario rather than less - rather different from a complete AI solution
Ripples in Time
No, it appears half the people here did not read the article nor even look at the graphs.
Then you gotta charge for parking the same way
We should encourage less driving for many reasons, which is why municipalities should have fewer, not more parking spaces. If there aren’t enough available parking spaces, that’s a failure of pricing. Increase the price of parking to a level where there is always an acceptable number of available parking spots.
I think so. A person who already lives paycheque to paycheque can be put into a really bad position by a fine but that same fine isn't even the tiniest deterrent to somebody well off.
Aurora Postgres supports bog standard native Postgres logical replication.
I guess as soon as a kit is available for this purpose that doesn't require advanced knowledge (say, `aisupport4 my-repo/`) and runs on mainstream-ish hardware and doesn't require a centralized service (even running in the browser via eg transformers.js), things will change considerably.
Burst translates C# to to LLVM IR (and first to some simplified C#, etc).
> GitLab plans to improve its customers' DevSecOps workflow efficiency by 10x, by applying AI-assisted workflows

How about GitLab fix the most elemental mistakes they have made with the k8s operator for GitLab runner instead of... whatever the hell this is?
> The only downside is that C++'s moves leave the moved-from object accessible but invalid while the Rust compiler will not let you access them.

"Except for the whole damn point, it's the same." Oh, ok.
This is the kind of sarcasm I'd like to see more often on Hacker News.
How does this compare to Erlang/Elixir? Is any gain of using a strictly typed language or the benefits are mostly related to Rust's CPU efficiency?
Have you not updated your priors given the difference in infection rate and severity between vaccinated and unvaccinated populations? It seems odd to be so fixated on a control study that was abandoned for ethical reasons when so much evidence amassed regardless.
Afaik HN is built around the idea of being as hard to use as possible, to avoid becoming Reddit.
Tons of the pieces you mentioned are probably not that expensive to run for a small use case, given you're only charged on demand. The cost is really in the dev ops time and expertise to orchestrate the whole affair, and in the new ways it can break.
Not parking fines, they are fixed amount by municipality.

Parking fines, is bit more complicated. Maybe the tax rate of the car or some current price... Then again rich could get cheap car and just use that.
Based off tax return and make tax fraud hurt. Sure some people will still optimize for tax avoidance but will be far fewer than the totality of those wealthy enough to disregard rules at present.
Yes.

Simple penalties create classes of crime; wealthy folks just ignore the penalty on double parking some poor schmuck because who cares about a $100 fine when you're making $1M?

These regulations are written to discourage unfair acts or behavior that exploites the social contract. It tells folks that the municipality thinks it's right for less-wealthy people to be burdened with providing comforts for more-wealthy people.

Means-tested fines actually get to the point of it: dissuade all people from doing something dangerous, indefensibly rude, et cetera, and not just poor folks.

For some additional discussion: https://www.theatlantic.com/business/archive/2015/03/finland...
GitLab team member here. Thanks for your feedback!

I have added your suggestion with MR/PR to remediate security vulnerabilities to the feedback issue [0] for the explain this vulnerability feature. The issue is linked from the blog post that provides more details [1].

[0] https://gitlab.com/gitlab-org/gitlab/-/issues/407295#note_13...

[1] https://about.gitlab.com/blog/2023/05/02/explain-this-vulner...
> GitLab is working with Google Cloud because of its strong commitment to privacy

Right. I guess they'll also deal with Qualcomm for their strong commitment to openness, and Russia for its strong commitment to democracy.
Omicron covid for young people (under 50) has similar stats iirc
you replace it?
Seems to require both Edge and Microsoft Account. No thanks. (By implication, I am not sure whether this strategy will increase their market share in search.)
I think Kafka and Wind Up Bird are pretty representative. If you've given them a shot, it's probable you just don't like his writing. I agree that Norwegian Wood is different enough that you could try it, or Wild Sheep Chase, but I don't see particularly why you'd like them if you don't like the others. I'm a big Murakami fan, but I think he's a little like Rush, either you really like him or you dont understand why people like him. You're not the first person I've heard say this.