skysight-inc/HackerNews huggingface dataset:
Because the incredibly small part of the lgbt community that has internalized the transphobia they receive is fine with being called "trannies" or being judged on whether they pass or not by socially dysfunctional teenagers that makes it OK for every LGBT person to be called derogatory terms? Do you go around calling black people the n-word because your token black friend gave you the n-word pass?

I'm not entirely sure what you are trying to say with the second paragraph. Other communities have identities, so it's their fault that 4chan, an outlier in the social platform space, enables and encourages their users to post derogatory and inflammatory garbage about people? Have you considered the fact that identity is part of why many communities exist in the first place?
That's exactly what I'm using though! And for the most part, it's an awesome tool. But it still can't magically make resulting SQL query faster than it can be without tweaking the database itself.
I just checked a few newsletter emails in my inbox, and they all offer List-Unsubscribe: mailto: based unsubscription. From what I see, it is quite universal and more common than link-based unsubscription. Newsletter providers prefer not to use the url based unsubscription because some email providers will crawl the URLs in emails and automatically unsubscribe people without them knowing.

It's also possible that you're talking about a 'link' (a href) in the email body that goes to the newsletter provider's site and ask them a bunch of questions (why are you unsubscribing etc.). That's a different concept entirely.

From what I've seen, the email-based way is the primary unsubscription method in use today. Even when you use the gmail feature "Mark this as spam", depending on what you click, it will just send an email on your behalf to the to whatever is specified in the List-Unsubscribe: mailto: header.
Is it fear of damage or danger that would keep them from taking it for free?
> I have never seen an easy clearly marked unsubscribe in my life.

Just a few easy to find unsub links from emails on the first page of RGE.

https://reallygoodemails.com/emails/stay-cool-during-summer-...
https://reallygoodemails.com/emails/find-your-perfect-fit
https://reallygoodemails.com/emails/download-the-new-sonos-a...
https://reallygoodemails.com/emails/dad-approved

Not including the list-unsubscribe headers all these will have which are trivial to click in most modern email clients.
Ryzen 3xxx would be the 3rd generation of Zen CPUs. For example, an Ryzen 3200U (U means it has an embedded GPU, basically an APU) would be low-end, Ryzen 3500 would be middle-end, and Ryzen 3700/3900 would be high-end.
Do you also scan when a private repo is changed to public?
Performance as in CPU usage or memory usage or both ?
Thanks for providing some context.

Informative history is great. And the part where she mentions that she ought to get a nobel prize makes me cautious with overall interpretation of said context, since that tends to be a counterindicator. Gives some confirmation of the point i was trying to make though.
I dont disagree with this, but I also see in our case that good tooling is immensely valuable in keeping things consistent and moving forward (in the same direction) without having to discuss every change.
My experience is that giving front-end developers who does not understand databases the ability to do this is a great way of killing performance across the board.

I don't particularly want that to be easy, because I've too many times had to clean up the consequences.

If you have a team where everyone understands the database implications, then awesome. In that case this consideration may not apply.
There's someone who's commented[0] on another thread about benchmarking hardware and shared a link[1]. Might be useful.

- [0]: https://news.ycombinator.com/item?id=25014690

- [1]: https://www.spec.org/benchmarks.html
I work in my basement.
Hi guys, I have also written a post to explain the high level concept of OpenPose, the pose estimation framework I implemented in this project.

Feel free to check out:

https://github.com/chonyy/AI-basketball-analysis

https://towardsdatascience.com/openpose-research-paper-summa...
Vala is much older. And, sure, who need new language, right ? (hint: sarcasm)
Thanks for this! Immediately forwarded it to my team chat, this is incredibly useful. Turns out that they already researched these options and just haven't invested any time in them because it hasn't been a real production issue, so I probably should take my criticism back.
Is this different than dark matter? This is actually just normal matter that we think should exist based on evidence but we can’t see?

Any physicist bored and want to do a “explain it like I’m five?”
I agree it can be very meditative. I actually seek these types of jobs nowadays.
I had a good experience with Trazadone. Very easy to get to sleep, eliminated anxiety about going to sleep, and got restful sleep, with only a little grogginess in the morning. No withdrawal when I stopped cold turkey after 2 years. Nowadays I just have valerian tea or magnesium before bed.
Thanks for the link, the Neuro mix is a real banger
>Normal IT politics, I guess.

Lunch driven procurement.

In all seriousness, someone is trying to make an app to benchmark software[0]. You might be interested in that thread. Thanks for the link.

- [0]: https://news.ycombinator.com/item?id=25010373
Take a look at this:
https://mobile.twitter.com/gelbach/status/132476099369259008...
I was asking myself an important question. When you write a Query, what activity are you actually currently involved in? You try to understand the API and want to query it. What's the easiest way to understand an API? Read the documentation? Where is the documentation? It's the schema, hence GraphiQL/Playground. So why would you want to switch back and forth between Documentation and Code when you want to understand an API? On the other hand, if you already use GraphiQL in your workflow, how does this look like? You write a Query in GraphiQL, then copy paste it into your code. Now if you want to add something else you go back to GraphiQL, search for another field and copy paste again. Compare that to WunderGraph: You keep getting back to GrapiQL and extend your Queries. You hit save and the code-generator re-generates the client. You don't even have to change the code if you just extended a query. The function call in the frontend simply returns more data. I wrote a feature page about this: https://wundergraph.com/features/generated_clients I'd really appreciate your feedback on it!
I guess geography is a bigger reason than both tech and policy. Denmark probably have more coast per km2 than any other country in Europe.
Perhaps. But there's an angle here which is there's a VC goldrush of GraphQL ecosystem solutions, many of which (IMO) probably aren't good ideas. So there's a lot of marketing push towards solutions which represent many of the negatives the post I was replying to highlighted.

I think GraphQL actually _is_ the right tool for many of the jobs people are using it for (API layer for 1st party clients), but they're often using it poorly due to many of these tools having slick APIs that let you be productive alarmingly quickly -- you only feel the pain much later.
It's probably a lot simpler than that. They destroy the nice scenery and the money being offered isn't enough to compensate for that.
This is not fair to the British people.

Take-Two gets massive subsidies to make "british games". Namely the "british cultural game" Grand Theft Auto. How!? Yes, how is GTA a british game? Well you see Take-Two bought Rockstar, which itself was a formerly a fully UK owned company.

Now Take-Two has turned around and is buying out one of the UK's few remaining publishers. No doubt the UK will now pay Take-Two yet more generous subsidies to keep Codemasters running.

The UK government is literally taxing domestic industries to subsidize an over seas corporation to further buy out UK industry. This is not a cohesive plan. The last thing the UK needs is to hollow out yet more industry.
We use jsonrpc 2.0 over websockets, typescript + runtime type assertions using functional combinators at the i/o boundary, it's very fast, bi-directional, type safe, pleasure to work with, easy to optimise (rpc call duration is easily captured), we know exactly the number of connected clients, it's easy to inspect outgoing buffer sizes, debounce notifications to do adaptive "throtthling" for people on slower networks etc. Above all, whole communication is uncomplicated and straight forward, lightweight. We tend to maintain client library by b/e team (maybe ~90% of code by b/e devs) for anything non trivial. The best documentation you can get is typed + jsdoc described library that you can just use. It is up to date. It's cheap to add new calls and notifications, it's easy to change apis where typescript guides you through changes required etc.
> they could boast, and they would be right, that they invented the modern tablet and the modern smartphone

Then why didn't they patent them, given that Apple always thoroughly and excessively patents stuff when they get the chance?

Answer: they didn't invent them.
It's whatever you make it about.
That is an interesting point - to be an expert is much more difficult today.

However, I wonder how much of it is survivorship bias? Like the polymaths are generally forgotten because they suck at a lot of things. Every once in a while you get a genius interested in many things... that’s then exceptional and they are capable of learning many things?

I think there always has to be a filter applied with what is possible and what is probable in a individuals life when thinking about making choices for your daily life.
> You'll likely never be in a situation where over-querying via a non-granular REST call will ever be an issue worth optimising around.

While I agree with your beginning sentence, the one I quoted doesn't sit well with me. It would be good to remember that not everybody has 100 Mbits fiber or 5G download speed.

We all saw the data on how milliseconds affect user retention then proceed to completely forget about it once building our apps.

I think we can do better.
Wouldn't it be better if we look at PS4 vs PS5 rather than PS4 Pro which was more like PS4 with 4K.

But in that case it is still only 5.6x.
Let’s build an MP3-decoder (2008)
>I helped many teams move from Java to Go, and came across this so many times. Everyone wanted to find the Spring equivalent for Go (or Django, Ruby on Rails, etc) when it doesn’t actually exist. That’s by design.

I'm not sure how it's "by design". Go, by itself, doesn't give much more than e.g. Java gives with its Servlet base libs, etc. And yet Java has Spring, and some popular framework could very well emerge as the "THE" framework for Go.

Whether that framework would conform to the stdlib interfaces / middleware is another question. It might not, if it's compelling enough (there are lots of popular Java non-servlet API conforming frameworks, e.g. Play, Vert.x, etc).

It's only because of fragmentation (and small still market, with lots of NIH) that one hasn't emerged as such, not some special Go design. Many/most Go-ers like to keep it simple, so they don't adopt any big framework lib (after all, if they didn't keep it simple, they wouldn't be using Go).
How does one invoke a Lambda function via HTTP without an AWS account (ie a public API call)? I think you are not including it in the "most workloads"?
There are simple reasons GraphQL is prefered to REST.

It's a spec and not a architectural approach, which makes all GraphQL APIs more uniform than all REST APIs.

It comes with a type-system that makes code generation really easy and allows for tools like Graphiql, which are orders of magnitude better than what most REST docs deliver.

Can this be done with REST?

Sure, just use something like OpenAPI.

Problem is, most REST APIs don't use such tools/specs, but most GraphQL APIs do.
Private repos need a different approach, but committing secrets to them can still be a problem.

If a secret is committed to a private repo then anyone with read access to that repo could use it. That might give those users more permissions than they're supposed to have. It's particularly a problem in large organisations, where thousands of developers may have access to a private repo, but should not necessarily have direct access to production infrastructure.

That said, the risk tradeoff when a secret is found in a private repo is different to when one is found in a public repo. If it's a personal private repo that no-one else has access to, the risk may be limited. If it's a corporate repo with hundreds of contributors, someone almost certainly wants to be aware of it. Even then, each organisation will want to respond in different ways, perhaps depending on who has access to the repo, and what access the leaked secret granted.

I'd be remiss not to say that GitHub has a beta offering for private repo secret scanning that we launched in May. It's a paid feature, targeted at large, security-conscious organisations, that scans your git history and each new commit for secrets and displays them in the GitHub UI.
Quoting Conan the barbarian.
Former Blitzer here (early 2000s). I went for an interview at codies about 2010, and it had a really strange vibe. People talking in hushed tones in corridors, stuff like that. I completely bombed the interview, but would have declined the offer anyway. I heard bad things about overtime, not sure if it's changed in the last 10 years or not.
GraphQL doesn't exclude hand-crafted database queries. If that is what needed you can perfectly make that fit with GraphQL. And if for some reason it won't fit in GraphQL, you could still create a one-off REST endpoint.
Walking an hour would require a decent amount of fitness. Not sure why you’re saying it’s a non-activity
It can be a very bad thing or an acceptable payment for developer velocity, based on what's your business priorities with the project.

I have a couple of issues that I worked on that started exactly like this: front-end developer implemented a feature based on GraphQL, but when we deployed this feature, we quickly disabled it after receiving alerts from production database, and re-enabled it back only after backend developer (me) went and worked on database indexing.

But for my team, at the current point of the project's development, this scenario is a net positive overall, because we're exactly in "move fast and break things" mentality, which suits our product and our place in the market. If our project would require a lot of 9s, or worked with very confidential data, or had 10s of millions of daily users, we would have completely different internal procedures and development practices: much safer and much slower.

Also, I wrote about this exact problem in another thread under this post: https://news.ycombinator.com/item?id=25014918
When Phones Were Fun: Nokia N95
The truth about exercise (documentary)
No, that's not not why.

If you have secrets, encrypt them.

Private repos can be turned public, intentionally or by mistake. Repos can be exported to give software to third parties. Also, git users clone repos, which means that those secrets are copied every where. Can you make sure those stay private too? Do you make your developers encrypt their laptops or delete repos from them before they leave their house or office?
Spend 20 seconds on the page, couldn't see an unsubscribe button.

Tried to spend another 20 seconds in good faith, still couldn't find it. I honestly don't understand what is the strange layouts of these pages and where is the newsletter even supposed to be.

Spam that is.

P.S. If you're wondering, the news seems to be the left column, then go to the bottom. I don't think having to scroll through 3 screens of texts and pictures to find a button is easy. My not tech savvy parents and friends wouldn't be able to find it.
Exploring the 5 Stages of the Design Thinking Process
Reminds me of the new Spam offering from DoNotPay.com
seems like you could just log in directly at that rate
I am wondering if we are not pushing too far the core count.

Do we need all those cores in a single machine? Do we know how to use them? Beside some scientific workload, how are they used?

I guess the standard answer is virtualized them and sell them in chunk as "cloud" but then why prices are still so high?

I am not complaining, I just feel that something is off, and I don't understand what it is.
Humanity's Largest Art Project
This is more or less the approach I'm taking with WunderGraph. There's just one exception. I'm not using websockets but simply a HTTP2 stream. Browsers have limitations regarding how many tcp connections you can open to the same origin and for each tab/window and websocket connection you have to open a new tcp connection. HTTP2 on the other hand can pipeline, depending on your browser, up to 200 streams over a single tcp connection, regardless of the tab or window. I've written a post on the topic: https://wundergraph.com/blog/deprecate_graphql_subscriptions...
It's like in Germany, Solar got the greatest boost at a time when it was still really inefficient to use but it received government subsidies. After they stopped the subsidies growth stopped despite technical advances. The good news about this is probably that whether to use regenerative energy is an actual choice and mature enough building blocks to make the switch probably already exist.
What’s the consumer application for this?
I would say this is somewhat misleading. It's not like other countries ran out of coast to put wind turbines on and that's the reason Denmark is ahead.
> Note that institutions are shorter lived than one might think. If you have become 25 this year, you'll have lived for more than 10% of the US's entire lifetime. 75, and you'll have lived for a third of its existence.

Note also that the US has one of the longest lived current governments in the world. There are plenty of countries that have been around longer, but most of them have forms of government that came into effect there later than when the US got its current form of government.
The GOP used a Two Santa Clauses tactic to con America for nearly 40 years
China sends world's first 6G test satellite into orbit
> MIT turns volunteering into unpaid labor for some billionaires.

Um... no? The idea behind MIT/ISC and the like is to let other people use your software, which they aren't automatically allowed to do because copyright is broken by default.

There's a lot of software that I would like to use in my day job that I can't touch because it's GPL. This is by design.

> These companies try hard to push the narrative that MIT is "practical" and GPL is "political" - guess why.

I have no sympathy for FAANG, but that happens to be correct. GPL is explicitly political in its intent.
Will hasura also help with the indexes, the most efficient SQL is usually the one which utilizes the indexes properly which still need to be setup to accomodate for each and every client side queries.
Besides hasura would have been great as a library but it's another api server you need to maintain on top of your existing one.
You're right if you're directly exposing your Databse-driven-GraphQL API to the client. If you use GraphQL to power your REST APIs this is less of an issue. On the other hand, tightly coupling your database to a client doesn't always have to be a bad thing. If you outscale a single Postgres Database with Hasura you can add read replicas. If that still doesn't work you can add Yugabyte to the mix to scale further.
From my experience (most with github’s graphql api), graphql is phenomenal for get queries as you can get a big chunk of things in a single request exactly as you want.

Github’s graphiql explorer was a joy to use and has saved me hours. For fetching a graph of nested data, graphql absolutely shines giving you fast responses of only the data you need.

For mutations though, graphql is a giant pain in the ass. We wrote a bunch of things using graphql mutations and after two months reverted all mutation code back to using REST api. GitHub was flakey, some things didn’t have error responses. Mutations would screw up encoding “ character and it was just painful.

REST api was much more deterministic and easier to work with. POST/PATCH/PUT/DELETE map well.

I wish graphql didn’t invent its own quirky language and stuck to good ol json.

In my experience graphql wasn’t worth the hype. There is a lot of over complication. We’ve got a lot more production success sticking to the basics.

NOTE: we were interfacing with github’s graphql api from python. Outside of js, graphql tooling is sparse and sometimes non-existent.
Prices are so high because cloud vendors have no incentive to lower them. It’s even worse with bandwidth. Cloud bandwidth prices are rape.
> From what I've seen, the email-based way is the primary unsubscription method in use today.

It's not. Most people unsubscribe by clicking a link in the email.

What you're referring to is the list-unsub header which is again a different concept to what the person above you is saying regarding replying to an email and asking to be opted out.
In the snow. Uphill. Both ways.
To the people in this thread advocating antipsychotic medication for anything other than treating psychosis and as an adjunct for severe depression, don't. These medications are serious things for serious situations and can have unexpected effects on you mentally.

I went on them in my early twenties due to a nervous breakdown, and while they stopped the endless loops of thought and insomnia (I ended up sleeping ten hours a night without breaking a sweat), they reduced my libido, made me gain weight, and worst of all, robbed me of my natural sharpness and creativity. It was as if my brain had been wrapped in a layer of bubble wrap, and my ability to come up with those sparks of inspiration that you need to do intellectual work was almost extinguished. I'm 100% now, fully recovered, but it took me about 3-4 years to get back where I was before it all happened. If your doctor thinks you're right for them, go for it, but only as a last resort.

They do work, but they're the last tool in the box that you only want to use when everything else has failed.
It is not just about the scenery, there is noise and light pollution as well.
Ask HN: What is the current state of GUI in WSL2?
I read this blog[0] about running emacs within WSL2, and I was curious if there's official support for GUI in WSL2.

[0]: https://emacsredux.com/blog/2020/09/23/using-emacs-on-windows-with-wsl2/
U.S. Military Responsible for Widespread PFAS Pollution in Japan
Do you have ideas on how we can make mutations work better? What's missing? What could have helped in your situation? Would really appreciate your input.
Well, the lasers currently in use are approx. 2 mW at 905 nm. They become Class 1 due to the continuous scanning. If a laser beam were to become stuck pointing in one direction, as GP mentions, it becomes Class 3R.

And with the current limitations to stay in Class 1, range is 100m or less, so basically useless on a highway. There is a lot of work going on to find good tradeoffs in power and wavelength to give useful range while staying in Class 1.
Seems like the closer you get to retirement age, the less likely you are to feel burnt out. Maybe this has something to do with how much you need the job. The job will be much less stressful if you know you have the financial means to retire or quit soon.
I believe AWS secrets are 240 bits. That is a pretty massive space. I don't know how many active secrets are out there, but I think someone would need to get very lucky to collide before the attack was noticed and stopped.

Other partner's secrets may be more susceptible.

Edit: I did not consider the paired access key which is another 70 or so bits. I think you'd need to collide on both to make someone have a bad day.
How is that not equivalent to "they were so much cheaper that you could get more of them"? Hardly what I'd call architectural success.