skysight-inc/HackerNews huggingface dataset:
>So now, reading this news about processors and stacking, I wonder about what inconveniences the end users are going to suffer with processors built under these techniques. Whether in computational reliability, vulnerabilities and so on.

Denser logic hasn't got the same issues as dense non-volatile storage as logic doesn't need to have any persistence.

It's what the likes of Micron and Samsung are good at fixing and working around when they launch and scale their Xnm processes for a specific storage technology, and what makes them better than competitors.

Intel, TSMC, GloFo, etc they all can buy the latest gen EUV machines from ASML if they want, but yet TSMC is always one node ahead on logic and Micron and Samsung win at storage, because they're good at ironing out the kinks and challenges that come from shrinking down those specific designs closer and closer to sub-nm level while the others can not (so easily).

If fabbing cutting edge silicone was as easy as just having the latest gen ASML machines, then ASML would just hoard the cutting edge machines for themselves and become vertically integrated in fabbing their own cutting chips as a side hustle before everyone else.
Ah, I use a Framework, so if (when?) a physical port goes bad, I can just replace it for $10 or whatnot. I've never had issues like you mention, though.

The most flaky removable thing I've encountered is microSD cards, and I don't know if it's the card or the reader, but they tend to only work half the time. I even check them for authenticity of space, so I don't know why they're so flaky.
This isn't that hard. Just have your developers train people with your software. In every craft you learn the moment the rubber hits the road. A film director can watch the film in the editing room a thousand times, but the one first time watching it with a real audience will teach them more than those 1000 hours together. A carpenter can work away on a piece of furniture merrily all week long and be happy with themselves, but the moment of truth comes when the furniture is placed into the customers room. The same is true for software. If you want your software engineers to care about users they have to get first hand feedback what works and what sucks, preferably with their own eyes.

Every software engineer worth their salt has a certain degree of pride about doing things well. If this only ever is about the code, the commit history or other abstract concepts, but never about how well it can be used by the actual people it was made for, then how would they even start caring?
I strongly suspect that most companies of that size and age do not have a tested run book to recover from bare metal.
Dokemon: Docker Container Management GUI
I’ve had many similar issues with ports, to be honest. Just recently had to get the I/O board swapped on an M1 MBP—one day it decided that one of the USB ports wouldn’t connect 80% of the time. It was relatively inexpensive to do officially even without the warranty (around US$60 all in all), and took just a couple of days, to be fair.
One can only hope that everyone learned their lesson: If you disregard IT, dinosaurs will eat your investors.
But that's not entirely true, because the mapping alone doesn't give you any ordering relation or comparison options. Translating the natural numbers into bytes doesn't tell you how they should be ordered. We determine the 'form' of the order with our minds.
>but life organizes

Yes, and that's the interesting part. In the right circumstances, more entropy doesn't mean less complexity. Matter can become more complex and less entropy locally if that results in increase of total entropy in the system. This can occur, for example, if we have constant flow of concentrated energy on some local areas of the environment that continuously wants to spread out. Because the system as a whole "wants" to maximize its entropy as fast as it can, and it statistically "searches" for the shortest paths possible. This may result in natural occurrence of more and more complex molecules that dissipate heat more and more efficiently.

It's like the planet's atmospheric processes, for example. Where differences in heat concentration don't just spread out in linear gradients but can form complex structures like vortexes, hurricanes or even stable geometric hexagons (like the famous hexagon storm on Saturn), etc.

>My view has always been that life fights against entropy.

Yes, it "fights" against entropy to exist, but it exists solely by processing low entropy into high entropy. Maybe that's why it even exists in the first place?

This part is better addressed in Jeremy England's work, for more basic explanations you can refer to videos like

this: https://www.youtube.com/watch?v=GcfLZSL7YGw (it's a very good video on this topic by PBS)
It was a defacto standard. Everyone had Flash.

Granted, there were reason to abandon it. But I can understand people being upset with it gone.
For what it's worth there's also this 2016 document, Introduction to Reports and Theses. [0] It's clearly different, but the introductions in particular have a lot in common:

From the IEEE version of A Guide to Technical Report Writing:

> A good report is easy to recognise. Its title is precise and informative, its layout and format are well organised, and the binding is easy to handle and opens flat to reveal both text and diagrams. Reading a well written report is pleasurable: the style is accurate, fluent and concise, with headings to indicate the content of each section. The diagrams, which in this Guide will be taken to include non-verbal material such as tables and graphs, are well presented and clearly labelled. There are no absolute rules about the details of report production, because every report must be totally adapted to the needs of its reader.

(The IET version is slightly different, for instance it does not mention document binding.)

From Introduction to Reports and Theses:

> A report is good when it is easy to recognize, title is precise and informative. The layout and format are well organized. The binding is trouble-free to handle and open. Reading a well written report is pleasurable, if, the style is accurate, fluent and concise, with headings to indicate the content of each section. There are no absolute rules about the details of report production, because every report must be totally adapted to the needs of its reader.

[0] https://papers.ssrn.com/sol3/papers.cfm?abstract_id=2775664 or https://dx.doi.org/10.2139/ssrn.2775664
But then we often have nothing for millions of generations and absurdly large amounts of biomass for species that we know well enough to know where to dig – but nothing was preserved there, and we can't dig in more than a few tiny spots. The crust's top layers are an immensely big volume and very hard to penetrate and not sure there would be a reason to dig right into an oil well that was emptied millions of years ago. Also, there is a strong aversion to sensationalist explantations in the sciences, so such scratches might even be known but attributed to some ill-understood kind of volcanic activity or earthquake scarring just because speculation towards a Silurian civilization isn't conducive to swift career progression.
The guy mentioned he has social anxiety and autism, the likelihood of him being able to improve his soft skills meaningfully without a long (and costly) therapy is unlikely to say the least.
Huh, maybe I'm an outlier. Maybe it's the way you remove your connectors? Some people tend to wiggle them side-to-side, I touch the chassis with my thumb and index finger around the USB, and kind of roll my fingers so they put pressure against the chassis. That leads to the removing force vector pointing strictly straight out of the connector, and I've never had a problem with any port.
> Apollo missions to the Moon, where scientists had to work all through the night on many occasions, battling against fatigue.

I have seen articles saying that the Apollo missions were absolutely not that. They were 9 to 5 jobs and managers made sure it stayed 9 to 5. The idea was that so many things could go wrong and they couldn't afford to have exhausted and overworked people screwing up.
Quantum Crime – and Overview
It's easy to dismiss 'Hack Now Decrypt Later' (HNDL) attacks as viable quantum threats, so this blog explores other ways that nefarious actors can utilize Shor's algorithm to leverage crime.
It is important to note here that SWA is not supported by all models, e.g. Mixtral is not working correctly.
there is a combobox to pick the repository: https://pkgs.chimera-linux.org/packages?name=xserver-xorg*&r...
The article is not talking about solar-mass BHs but ~asteroid-mass ones, with a Schwarzschild radius on the order of nanometers to micrometers.
All roads bring us back to Worldcoin eventually...
I've had that idea for years.

Two versions that I experimented with. One is where the incoming POW hashes contribute to hashing power for some blockchain mining. An alternative "pay as you use the API" system.

The other using hashcash. Just a way to slow down abuse.

Both, however, suffer from the downside that many/all "ASIC resisting crypto mining" suffer from as well: the cheapest CPU power is CPU power from machines/power you don't own. Botnets, viruses, trojans etc.

So such a mechanism to throtthe or protect APIs won't hold back spammers and abusers for long.
My previous laptop had indeed its SD slot borked at some point (part of why I don’t care that my new laptop lacks it—I would just not expect it to work reliably, so why have another dust collection point). My first laptop’s keyboard had very occasionally working keys in the middle (I blame my pianist fingers bashing them too hard)—I count that as physical I/O, though not a port issue.

Is it easy to source replacement I/O boards for Framework?
> Printer manufacturers also don't thing like this

at this point, what are they gonna do? Not provide windows drivers?
I don't see how replacing the "it works on my machine" with "it works in this VM" is much better. It is the same problem.

You just added the overhead of running another whole computer in your computer to solve it.

Also the author states he is locked into using VS Code, which seems like a risky dependency to have.
Section 5.5: "Table 3 contrasts our measured human solving times and accuracy against those of automated bots reported in the literature."

Although it's not clear to me that the humans all really were humans.
ECB explores new means of wholesale central bank money settlement
The Eurosystem is exploring potential solutions for central bank money settlement of wholesale financial transactions recorded on distributed ledger technology (DLT) platforms. The work is part of the Eurosystem’s broader efforts to ensure that central banks keep pace with and contribute to digital innovation in wholesale and retail payments. Learn more about the background and intended purpose of the work.

In this focus session, demos from three European central banks: Deutsche Bundesbank, Banca d'Italia, and Banque de France are displayed in the video. Video link:

https://www.youtube.com/watch?v=m5z3uoMH3Fw

Technical documents about each solution provided by all three central banks, including the architecture, the process description, and the message formats can be found in this page, in the Annexes section:

https://www.ecb.europa.eu/paym/intro/news/html/ecb.mipnews23...

What do you think about these three proposals?
Bot operators can already pay human captcha solvers as the paper mentions. So all this does is potentially replace those humans with AI, driving down prices for bot operators.

As prices for bot operators decrease, website operators will increase the challenge and drive up effort for the intended website audience (humans) who are solving captchas instead of paying bots.

In the end, the website operators will have to stop using captchas as the intended website audience will no longer be willing to solve harder captchas.

Website operators can use alternatives, like asking for micro-payments, high enough to discourage most bot operators.
Words for clothing tend to shift their reference to the wearers of the clothing over time. Perhaps it was so ordinary that it never made it into literary record.
The writer didn't say that.

> The American legal system found a less expensive alternative. Like its medieval predecessor, it substituted confession for trial. The medieval confession was motivated by the threat of torture. The modern version, a plea bargain, is motivated by the threat of a much more severe sentence if the defendant insists on a trial and is convicted.
Yes, but wireless wouldn't have saved you with the latter.
"do the right thing (to maximise profits for the shareholders)".
Provide drivers using the old model and a set of instructions to enable that.

Edit: I guess instructions won't even be necessary, as far as I've understood, there will just be a warning. And users are already trained to just ignore those.
Figjam means Fuck I'm Good Just Ask Me which kind of fits. Figma is convinced you love it enough to pay.
Doesn'tcbo.zero just zero the cache, or am I missing something?
Yes. For instance, I've read the first and last books mentioned in https://www.allthingsdistributed.com/2020/07/the-os-classics... and wholeheartedly recommend them (esp. Gray&Reuter!) to anyone with a systems bent. (I've also read several others mentioned there and based on their quality I'd be willing to pick up the ones I haven't read)

I guess it's a bit of a chicken and egg: you need to skim ruthlessly, ignoring (à la Sturgeon's Law) most of what is proffered, skim what you don't ignore (index, table of contents, and a few random pages within), but when you do find "the good stuff", stop, read it, and probably also read works it refers to. Unfortunately for the initial filter to work, you can't be a complete neophyte, but luckily practice helps a good deal there.

Looked at from the other way around ("reversing all the arrows"): whenever you find a work that is helpful for expertise, stop, soak it up, and explore its neighbours. This will be time intensive, especially the practicing part, so of necessity you will need to leave the vast majority of things unread...

> Ved å studere mesterne, og ikke deres elever — NHA
("read the masters, not the students")
Even though I do not fully agree, I think this project has one of the most mature, nuanced, and balanced takes on systemd I have seen yet [0].

[0]: https://chimera-linux.org/docs/faq#what-is-the-projects-take...
My single data point is October 2023. I don't know if they're slower than they used to be.
Option 1: Micropayments, high enough to discourage bot operators but not the intended human audience will be better for website operators as soon as it becomes too easy for AI to solve captchas.

If website operators don't explicitly introduce micropayments as a captcha alternative, there will be browser plugins that outsource captcha solving to AI for a micropayment, which has the same effect.

Option 2: Using a means of authentication that can't be obtained cheaply at scale by bots, e.g. Twitter accounts, Gmail accounts, government ID, ...
What can you connect to the iPhone 15 with USB-C?
Perhaps? Soft skills includes stuff like writing though, not just schmoozing.
Some new accounts need another user to 'vouch' first. I clicked that button now.

Your first submission was "Looking for Entry Level Software Engineer Job in India". Job posts, including looking for a job, are not allowed. That's listed in the FAQ (https://news.ycombinator.com/newsfaq.html). Next month you can add yourself (add a comment) to the "Who wants to be hired?" https://news.ycombinator.com/submitted?id=whoishiring list.

Your second submission was "Show HN: What Is Open Source vs Free Software". Show is for something you've build (https://news.ycombinator.com/showhn.html). Quoting a piece of text without source (who is being quoted) wasn't enough for anybody to upvote the submission.
YouTube is trying to block Invidious
> Almost all of our current hydropower is based on damns made of concrete. Creating the cement for that is very energy intensive.

Is that really harder than building hundreds of kilometers of aqueducts? Humans have known how to engineer water flows for thousands of years, if we valued power we would build those dams. That power would be more expensive so it would slow down the industrial revolution but it would still happen.

Also you don't need continuous power for an industrial revolution, that is convenient but factories are still revolutionary even if they just run half the year.
MongoDB says customer data was exposed in a cyberattack
The spammers can already do this with captcha farms. The fact that captchas are still around means that the cost of captcha farms are still high enough to discourage enough spammers to be worth the annoyance that website operators cause for human users.
Among the stuff we can use to proof the hypthesis of such a civilization (from skimming the linked paper):

- evolutionary evidence pointing at the possibility of species with large enough brains to build industrial civilizations

- sedimentary proof of artificial pollution and CO2 levels

- fossils

Any hypothesis has to be proven to be true, proofing it to be wrong is impossible and not things work. What the cambrisge paper did, was pointing towards wayw to proof the existence of an ibdustrial civilization millions of years ago. Now the work is on the people believing that theory to proof it.

Speculating without considering the basic principles behind said claim, concluding it is impossible to proof that theory wrong and finishing all that off with a the claim that such a civilization most definetly did or could have existed is just stupid. It worries me so, that this kind of shit shows up on HN more and more often.
Thank you. The data in that table (for reCAPTCHA, citation 63) is from another paper from 2016 which is focused on solving the actual user-presented problems. It doesn't (directly at least) say they achieved a reliable automation of captcha acceptance, though.

https://ieeexplore.ieee.org/document/7467367

From the abstract:

> Through extensive experimentation, we identify flaws that allow adversaries to effortlessly influence the risk analysis, bypass restrictions, and deploy large-scale attacks. Subsequently, we design a novel low-cost attack that leverages deep learning technologies for the semantic annotation of images.

I'd suspect reCaptcha has been updated in the 7 years since to address shortcomings.

Another entry in the table (citation 45) is from 2020 and talks about using an object detection AI to solve the image tests. This again looks like it's focused on the task, not the primary mechanism (behavioral analytics).
On second guessing checklists.

Many years ago I worked as a sysadmin at a bank. We had an outage -- a lightning strike on our server room caused stuff to fail and shut down all power.

Upon restart, we discovered our main Oracle database supporting everything that is important at the bank was corrupted.

No biggie, we had a backup database. The backup was constantly being updated from the primary and was essentially just couple minutes away from being current with it.

But the Disaster Recover Plan which was prepared the previous year clearly stated that in case of a disaster like that, the first step is to make a backup of the secondary database. This would take about 6 hours which our management didn't want to do. This would mean the bank would not be open the next day and nobody wanted to make that decision.

So they decided, we will skip this step, copy the rest of redo logs to the backup, apply them to the database and then turn on the database.

We did this only to find the secondary is also corrupted.

To summarise, when the lighting hit the server room, some garbage was written to the redo logs on the primary server. We had perfectly good secondary but when we copied the logs from primary and applied to the secondary, we also corrupted it.

Now we have no primary and secondary... let's check if we have a tape backup!

As it happened, we were in transition from an old DDS backup method which was taking too much time during the night to a new shiny DLT tape library. Only the tape library came blocked to just couple slots (demo mode!) and would use same 5 tapes all over again. It was impossible to fix this remotely and we were waiting for a technician to come and unblock the library.

In the meantime, somebody decided we don't have enough time to do both DLT and DDS backup, so they figured out we will only do the new, untested backup method.

So when we tried to recover data from DLT tape we found ... it is also corrupted. Same tapes were written over again and again without ever testing the recovery and now the only backup we had was also corrupted.

At this point, to our horror, we found that we have no single consistent backup of our main database.

In the end, I ended up spending two or three days almost NON-STOP on a transatlantic call (that was extremely expensive back then) with an Oracle guru who was telling me how to edit the large data files in a hexadecimal editor to manually fix the mess.

In essence, we would locate everything that would point to the extents that contained garbage and would edit it to no longer point to the garbage.

Overall, the bank was shut down for 6 days and lost 20% of its market cap.

All that for not following the procedure.

Somebody made that procedure with a clear head to analyse all pros and cons and all possibilities. The time to ask "Why do we need to make a backup of the backup before we can use the backup?" was when that procedure was made, not when the actual thing happened...
Your using terminology in non standard ways.

Read the first paragraph on eventual consistency on wikipedia, it describes the agreed upon definition.

"Eventual consistency is a consistency model used in distributed computing to achieve high availability that informally guarantees that, if no new updates are made to a given data item, eventually all accesses to that item will return the last updated value"
musl is just a mandatory choice; the toolchain configuration doesn't really allow running anything else (glibc doesn't go together with clang+compiler-rt, they only very recently made it build with clang and that's still assuming a gcc-centric runtime as glibc actually dlopens libgcc_s, and every other libc is going to be much worse in terms of support)

i think you overstate how much trouble it is to port software to it; most software does not involve any porting in the first place, upstreams are not that reluctant, and as for firefox having a specific crash, have you reported it?

slowness is typically a default allocator issue and that does not apply to us (in fact, it may sometimes be faster)
also strangely missing from this discussion about the supposed outrages of pricing when you round, and losing 0.1 or 0.2% in cash payments, is that credit card companies will charge that gas station is a bit over 2%. So no matter what coin you abolish, the gas station comes out on top on the cash payment, even if it's the quarter. It'd still come out on top if it was the dollar bill/coin for bills under $200, so, pretty much always.
And yet it exists anyway.
Didn't really take long for replacements like https://ruffle.rs/ to emerge, though.
I wish I had USB-C charged cats. Imagine savings on food...
It has a very high polish and seems to work well for the mock retro board I created. 3 likes might be a bit small of a default value IMO. Good job on the project, it looks better than whatever we use at work.

I am confused with the header nav links, particularly how the "Planning Poker" and "Retrospectives" items swap positions on click - but don't actually navigate to the page itself (just to a landing page?) When I click "Start Reflecting" on the "Retrospectives" page it directs to Planning Poker creation.

On the "Start Reflecting" nav item it appears only the "Start" text contains a click handler - clicking the "Reflecting" text doesn't do anything.

Cheers and good luck