skysight-inc/HackerNews huggingface dataset:
I don't like how dickish I sound in this thread but... they're not fish, they're people.

I've been married for a long time but I've seen enough of today's dating scene from the outside in and heard enough about it from people in it to think it really is worse than when I was dating in the 2000s. I think the reason is the normalization of this PUA meat market mentality, which has come in part from influencers pushing these ideas into the culture and in part from the nature of dating apps (especially Tinder) and how they encourage it.

https://www.engadget.com/2015-05-22-meat-your-match-with-thi...

There's always been a meat market aspect to dating of course, but we've turned it to eleven and taken away the human part entirely. On top of this we've slathered a layer of toxic gender stereotypes received by way of shitty grifter self help gurus.

I feel like my wedding was one of the last flights out of Saigon.
> Further, and once again, rural residency does not significantly predict anti-intellectualism

So this is a perception thing. The guy living in Times Square who views himself as as a "farmer type" is less likely to be "intellectual." This strikes me as society on-the-whole embracing the idea of the country bumpkin than anything else.
The German coast also had notable man-made changes, though far less extreme than what the Dutch did
Unfortunately blue whales are a terrible, archaic measure. There’s too much variability in mass, and then you’ve got the buoyancy problem and different salinity, plus pressure at depth.

Any modern scientific discussion should be done exclusively using standardized measures, like 747’s or 10-story office buildings.
does Rust even support incremental compilation correctly yet? after how many years now?
This document seems to be at a lower level. An actor model would be implemented in terms of these primitives. These primitives are available in many languages.

Immutable is kind of irrelevant in a discussion of multi-threading because immutable data has no problems in this regard. Which, of course, in a way also makes it relevant because one prevents issues. Ultimately one cannot have just immutable data because the computer would not be allowed to do anything. This document would be about data that cannot be immutable.

But the complaint sounds a bit like an article about assembly language getting the complaint that it does not explain how to implement a word processor.
It is DRM, it was just cracked a long time ago and they couldn’t apply a fix since the discs and players aren’t internet-connected or meant to be patched.
Yes the social sciences are where the critical thinkers are. They think so critically that you can't reproduce their work.
Right, most of what you list either hasn't figured out how to live with humans, or is a predator that will kill humans, so humans kill them (illegally!) or otherwise chase them out to protect their children.
I disagree. Frank language is not disrespectful. And here I think the warm opening and closing, the specificity of the critique, and the useful suggestions are not just respectful, but helpful.

Also, I think anybody whose contribution is, "Oh, knock it off," doesn't have a lot of room to complain about somebody bringing the tone down.
What does the Intel Management Engine do? Does it phone home? Can that port be blocked?
Should I introduce you to https://arxiv.org/abs/2403.14064 ?
Economist! /s
How 'Conan the Bacterium' withstands extreme radiation
My argument isn't about if it's advantageous or not. It's that the mechanism (DNA, a long string) may not be well-suited to expressing and adjusting very complex emergent behaviours in the phenotype. There may either not be a way at all to express "show strong maternal instincts but reject all non-related children and surrogate children like pets", or there are too many steps to get there and natural selection would never find it in any reasonable evolutionary timescale.
Environmental collapse due to climate change is way, way more likely than any of those.
What about PDF/A, archive version with restricted features?
Definitely a good use of AI.
When you gave up you started relating to them as people.
What is with the trend of making stupid ass titles to explain some small tech issue?
https://archive.ph/eXVJi
Phi-4 Technical Report
We are looking for a skilled Senior Quality Assurance Engineer (m/f/d) to join our Checkout team onsite in Hamburg or remotely within the EU.

The Checkout team is responsible for the complete order lifecycle, from customers first placing items into their baskets to handling the refund of a returned item weeks later. Between these two points the team interacts with a multitude of internal and external players, spanning from an in-house CRM team to the external marketplace and multiple payment providers in a variety of countries. The applications the Checkout team maintains span from high traffic & fault tolerance API hubs to security-conscious and reliable backend processing engines.

Since we offer through SCAYLE our in-house developed eCommerce infrastructure for online retailers, as a licensed product, a big part of our responsibility is to work on Checkout as a Service.

Our main tasks are to build next-level e-commerce checkout, but also to focus on improving conversation & user flow for our own website.

What you will do

- Perform high-quality manual and automated testing for big-scale e-commerce shops focusing on the checkout part

- Work closely with developers to ensure that testing layers cover the entire project.

- Manage and prioritize bug reports or bug tickets from internal and external stakeholders, always keeping their business value in mind

- Contribute to the shaping and constant improvement of SCAYLE`s long-term automated testing strategy

- Advocate for product quality within a cross-functional development team

- Coordinate testing efforts to ensure the delivery of quality features

Who you are

- You have at least 5 years of experience in quality assurance, testing, and debugging of the backend in big-scale projects

- You have very good coding skills in JavaScript/TypeScript and have proven automation experience using them

- You are experienced in manual testing (explorative and destructive) as well as automated testing (e.g. with cypress.io, playwright, and chai.js)

- You are able to get a quick grasp of complex technical systems

- You focus on the details but always keep the business value of the software in mind

- You are experienced with agile methodologies and understand what it means to have a quality mindset in an agile environment

- You possess very good communication skills and the ability to handle different stakeholders
You speak and write English fluently

YOU ARE THE CORE OF ABOUT YOU.
We take responsibility for creating an inclusive and exceptional environment where all genders, nationalities and ethnicities feel welcomed and accepted exactly as they are. We believe that a diverse workforce essentially contributes to the ABOUT YOU culture. In order to maintain talent and diversity, we emphasize the care for physical health, mental health and overall well-being. Our values and work ethics essentially contribute to our brand mission: empower acceptance and shape an inclusive, fair and circular fashion culture.
Even before the crisis you had lead times of over a year.
The namespace on Twitter is not property owned by the user. It's just namespace which is owned by Twitter. The use of it is at the sole discretion of Twitter. If Twitter doesn't think that it's appropriate that this group be able to represent themselves as "Alex Jones" or "Infowars" in their namespace then they don't have to. It doesn't matter if it's a voluntary sale or a court ordered transfer.

My default action would be to just take all the handles away. I wouldn't tolerate allowing courts to redefine my namespace into other people's property. Especially if I just paid $44 billion to purchase it!

I'd definitely not allow the new owners of Infowars to have Alex Jones personal Twitter handle(s) because they are not Alex Jones and doing so would be an admission that my namespace is not my private property, but that of someone else.
Did Star Trek not already warn us about this one?
Controversial EU ad campaign on X broke bloc's own privacy rules
One might be the author of such a page …
> Some people might say that it’s cool to open to open up a home appliance and expose yourself to high voltage AC components, but at the end of the day, it’s also pretty fun.

Ok you got me.
RISC-V International CEO Calista Redmond Resigns
Majjit LSP
A lot of time and money was wasted over the years on communications concepts. It wasn't until the mainstream collaborative editing tools and PC-based video conferencing (as accelerated by COVID) that, for now at least, everything sort of came together.
Someone put a reply and then deleted it while I wrote a response, and it irks me that it might have been a waste so here's the gist of it:

"Is it just that people are more comfortable with blue-green deploys, or are blue-green deploys actually better?"

It depends. If you can do a blue-green shift where you gradually add 'fresh' servers/VM:s/processes and drain the old, that's likely to be most convenient and robust in many organisations. On the other hand, if you rely on long running processes in a way where changing their PID:s break the system, then you pretty much need to update them with this kind of hot patching.

"Does Erlang offer any features to minimize damage here?"

The BEAM allows a lot of things in this area, on pretty much every level of abstraction. If you know what you're doing and you've designed your system to fit well into the provided mechanisms the platform provides a lot of support for hot patching without sacrificing robustness and uptime. But it's like another layer of possible bugs and risks, it's not just your usual network and application logic that might cause a failure, your handling of updates might itself be a source of catastrophe.

In practice you need to think long and hard about how to deploy, and test thoroughly under very production like conditions. It helps that you can know for sure what production looks like at any given time, the BEAM VM can tell you exactly what processes it runs, what the application and supervisor trees look like, hardware resource consumption and so on. You can use this information to stage fairly realistic tests with regards to load and whatnot, so if your update for example has an effect on performance and unexpected bottlenecks show up you might catch it before it reaches your users.

And as anyone can tell you who has updated a profitable, non-trivial production system directly, like a lot of PHP devs of ye olden times, it takes a rather strong stomach even when it works out fine. When it doesn't, you get scars that might never fade.
The ability for very rich people to make butt-loads of money from the few non-failures.

From 14 years ago, https://www.inc.com/eric-markowitz/brilliant-failures/why-si...

> The first, and most obvious, answer, is that failure has become inexpensive.

> "failure is almost synonymous with learning experience"

> not punishing failure leads to stronger long-term growth.

> funds are leveraged with the expectation of failure; failure is baked into VC firms' business models. Start-ups are encouraged to swing for the fences, because one or two big exits in a cycle will guarantee profitability for a firm.

From 24 years ago, https://archive.org/details/understandingsil0000unse/page/24... :

> Many have remarked that in Silicon Valley there is little stigma attached to failure. Most have attributed this to a "cultural" trait; few have considered that it is in the interest of the venture capitalists to lower the cost of failure. It is critical for the entire system that entrepreneurs continue to venture. Discouragement and punishment increases the cost of failure and offers little economic return to the venture capitalists. Also, it should never be forgotten that success is valued far more highly than failure!
My number one recommendation is to wear good shoes / boots. My first year at FOSDEM it snowed and I only had some old tennis shoes which means I spent a lot of time with freezing soaked feet. It gets cold and talks are in different venues, so prepare accordingly.

Rooms can fill up and some are quite small, so if there’s a talk you really want to see it pays to get there on the previous talk, even if you don’t care too much about it, to save a good seat. Don’t stress too much about it, though. Talks are recorded and it’s common that something you thought was going to be awesome turns out to be boring and something you didn’t care for at all is fascinating.

You shouldn’t have much trouble with public transportation, especially because you’ll probably see other attendees making the same trip. But I do prefer walking and in all my visits I didn’t mind walking thirty minutes or more each way. It’s only two days and it’s my preferred way to visit a city.

There are going to be booths too so you can visit them for some stickers and to strike up a conversation with people if you want.
An example is when you have a shared data structure that is written by one or more writers and to which one or more readers want read-only access.

In this case, the readers can use optimistic access to the shared data structure, also known as lock-free access (a very inappropriate name in my opinion).

Thus all the readers access the shared resource concurrently, but they must be able to detect when an update is in progress or an update has overlapped in time their read access, in order to stall or retry their reading of the shared data structure.

To implement this, a version counter is used, which is incremented after each update by a writer of the shared data. The version counter must be updated twice, both before and after the rest of the shared data is updated. The first update must provide an invalid version number, to enable the detection of an update being in progress.

There are two simple ways to achieve this. The version counter can be complemented before data update and negated after data update. Complement followed by negate is equal to increment, and negative version numbers would indicate an update in progress. The alternative is to increment the version counter both before and after the data update, when odd numbers would indicate an update in progress and even numbers would be valid version numbers.

A reader must read the version number both before and after reading the shared data. An invalid version number before reading will stall the reading, while after the reading an invalid version number or one that is different from the first version number will cause a retry of the reading.

The two version counter stores by a writer and the two version counter loads by a reader have different ordering requirements.

The version counter store before data update must be an "initial store" (as defined in the previously posted message).

The version counter store after data update must be a release store.

The version counter load before data reading must be an acquire load.

The version counter load after data reading must be a "final load" (as defined in the previously posted message).

There are also other frequently used algorithms, e.g. for queuing locks, which need "initial stores".

The explicit memory barriers are a mistake in ISA design. They have stronger ordering properties than the various kinds of ordered loads and stores that can replace them, and these stronger ordering properties are never needed.

Moreover, explicit memory barriers increase the code size and they occupy instruction decode slots and various locations in the internal structures of a CPU core without providing any benefit.

Explicit memory barriers are absolutely necessary for Arm Aarch64 and for Intel/AMD x86-64 (for the latter only when accessing memory regions with weakly-ordered accesses), but only because these ISAs do not include all the kinds of ordered loads and stores that are needed.
I didn't think about that. It makes sense, I was talking about flavoring specifically
Mirror life would have no interoperability with normal life, in biochemical terms. Say, if a predator attacked a mirror bacteria, and ate it, it would be just like eating an inedible microplastic particle. A technological analogue would be to change tensions in electric outlets at random, between 115V and 230V standards, with no indication of which outlet has which tension. People would start blowing equipment left and right.
This is incredibly well-executed. If I were a Shopify user, I could easily see myself spending hours exploring all the channels. The nostalgic Sunday morning TV vibe is spot on! The 3D remote adds a wonderfully tactile, "chunky" feel to the experience.

I did encounter an issue with the phone QR code control where I couldn't get it to work (possibly due to an adblocker interfering?). While exploring the developer tools, I noticed a file named `ozempic-CmQHzXBW.css`. Out of curiosity, is this built using Remix?
Yes! This is exactly my point. Also, not sure why we treat our kids like such weak snowflakes. This “kid” is 17. That’s damn near being an adult and able to be sent off to die in wars. Scissors are great tools, don’t sue the scissor company because you can’t teach your kids to walk with them, the parent has the primary role in everything.
This is a bit like the two children who asked a parent to divide a cookie.

First child says the cookie should be divided in half. That's fair.

The second child says he deserves all the cookie.

The parent split the difference, giving the first child a quarter of the cookie, and the second child three quarters of the cookie.
I've dreamed about making this for years, so glad someone did.
It's a bit silly to claim that any debugger comes with zero performance "overheads".

And somehow they failed to think of any drawbacks for the debugger they ship in their paid software...

I use nvim-dap with nvim-dap-ruby; it's excellent.

Every benefit the post ascribes to RM's debugger applies to nvim-dap (modulo the user's ability to do basic neovim customization), with the added points that:

- nvim-dap is protocol-based, so you can use the same configuration with many languages

- it's completely free

https://github.com/mfussenegger/nvim-dap

https://github.com/suketa/nvim-dap-ruby
SEO spam is the façade you get to see as a user. The gold is all that you don’t see. Just because they don’t show it on page one doesn’t mean it won’t be useful for training.
I did that once as well. My recommendation for that is the Janson room.
I haven't personally verified this, but I'm fairly positive all the enterprise versions of these tools (ChatGPT, Gemini, Claude) not only are oblivious to document contents but also respect things like RBAC on documents for any integration.
I’m sure it would attack it, and it likely would even succeed.

The problem is the chiral molecules would be difficult to clean up. You’d have this anti-life bacteria torn to pieces, yes, but then the pieces get stuck everywhere and potentially jam things.

Personally—not a biologist—it doesn’t feel like a huge risk, given we accept threats such as microplastics which do much the same thing. However, it’s a completely unnecessary threat with essentially no upsides, and it wouldn’t be possible to undo once created.
Bitframes – a generative artwork and film crowdfund
“What else is there to research about disease? They’re bad, but people get infected.”

These are things which shape our world, it’s worth understanding them at a level which doesn’t fit on a bumper sticker – and, right-wing mythology aside, the cost is not very high. Academics are cheap and their work almost always has spin-off benefits, even if that’s just providing a place for people to learn general research skills they take on to the workplace.
The Principles for Reliable, Safe and Fast AI Agents
Building AI agents is hard. Most attempts end up with brittle systems that break in production, cost too much to run, or worse - make costly mistakes that could have been prevented.

Fortunately, there are several core principles that I’ve learned while building agents that actually work. Hope you find it useful!
It seems like it would be a neat, happening place to be. But how dangerous would it be to live and work there? Is there the potential for the rockets to blow up and destroy the city or anything like that?

Working at SpaceX that may just be a hazard of the job, but if they want the location to be a real city with a post office and school and cafes and shopping and all that, it probably wouldn't work. But I'm not too familiar with how likely or how big adjacent city affecting disasters could be.
This guy Mysts.
Scientists transform skin bacterium into a topical vaccine
You’re right. They can actually do RLHF just using their users. Showing each of them slightly different generations and watching their behavior.
does torch.compile support intel arc? I have trained my model for the past few days using this intel's GPU.
I believe the term is armchair grandmasters.
being 100 bps off target is not a "high inflation environment"
How much achiral food would be available for these bacteria anyways in nature? They'd have to compete for it with all other life.
I’m really not sure how many more Literature papers we need on Proust, Shakespeare, Beowulf, and on and on. They have to continue to pump out papers and books, exclusively read by other people in the same subjects. “Invaluable” this is not
> Our Solution: Use Redis and Postgres Database Polling + leader election using RedLock

To me this seems one of the worst architectural choices they could have made. I'm assuming they had some constraints that were not mentioned in the article to justify this decision. But for a simple distributed circuit breaker this seems far from a reasonable solution.

Besides that, there is one implicit assumption that was made that I'm not sure is true. By having a 'leader' you are basically saying that your network connections never fail or that they always fail at the same time. Sure, under normal conditions this assumption doesn't seem that bad. But as soon as things start to degrade you may have a pretty bad outage in your hands.

If I had to implement this feature I would probably use raft[0] to communicate between pods. And would also keep track of 2 values for each host. One is the local failure rate and the second one is the global failure rate. This way I can change my behavior according to current network conditions.

[0] - https://github.com/hashicorp/raft
All I see this really doing is increasing the Brain Drain. This assumes NZ has a Brain Drain and I am open to being corrected. But I am pretty sure it does have one based upon some of the comments here.
Can mobile medicine solve the health crisis in Morocco's remote villages?
I recommend you send samples to coffee machine reviewers on youtube and have them review it and offer their opinion. I feel this is the kind of product that needs consistent marketing efforts to maintain stream.
And after all this when you finally get to work continually dismiss every window / popup notification that is somehow allowed to steal the focus from the window you’re working in.
That comment takes all facts and context out of the discussion and does not inform. Do you know what Title 1 is? 504? IDEA? I'm not going to defend garbage laws like No Child Left Behind, mind you, ask any teacher how terrible that law is. But both my kids, one autistic, one ADHD, have heavily depended on section 504 for their education. As for any decline in education, I would look instead at the anti-intellectual so-called 'family values' that have been on the rise since 1980.
I replaced my son's school timetable app with an e-paper
good, there is no need for a nation to have an abundance of social "scientists".
NZ$15/person still seems like a drop in the bucket out of a $3.2B budget, especially since it’s boosting the local economy rather than going out of the country.