skysight-inc/HackerNews huggingface dataset:
Look, I understand your concern and for example when Facebook uses your phone number that you provided for two factor authentication as a means to target you, that’s wrong. (google “two factor targeting Facebook” and you’ll see what I am talking about)

Now with that said, I honestly think tracking pixels are fine if they are used in non-nefarious ways. I would much rather get ads that are relevant to me rather than ads that have no significance.

Now, I do have a problem with banner ads (Google display network for example) that follow me around the internet, but then again I should be picking a bone with the website that decides to clutter their side columns with display ads!

The truth of the matter is the internet has always used the ad supported model as a source of revenue. We get free tools like Google sheets, drive and docs because of ads. Entire businesses are built using tools that are supported by google’s suite of tools.

And in regards to Facebook, if you don’t want to be targeted stay off the platform. It’s that easy. Now, I do think Facebook SHOULD offer a payed version that has no ads. That seems like an easy solution.

But the truth of the matter is Facebook has allowed an entire new industry of direct to consumer brands to successfully run e-commerce businesses because of their advertising tools. A net win IMO.

But to blast me on hacker news because I am simply trying to help my wife with her craft business (using the very powerful targeting tools Facebook provides) is childish. Pick a bone with Facebook, not me.

And by the way. You’ll notice I didn’t add anything special to the URL I provided in the post. No parameter such as ?source=hackernews so don’t worry about seeing my wife’s BEAUTIFUL pins on Facebook, although jeez you might need something to brighten up your day and perhaps cute little flower pins might help with that.
Although I'm not sure how that "mounting" of cpus would avoid people hogging resources. I use a HPC system where users submit jobs and there's a whole complicated queuing system going on to make sure that greedy users don't monopolize the system.
I think it has nearly zero to do with cars and 100% to do with growing homelessness and grewing drug activity in homeless camps. Nobody who has become weary in Portland claims car traffic. They're all terrified by the growing homelessness and unsafe drug activity in their hood. Needles in your front yard type of thing.
I'm not in the business of home farming, but the price tag seems pretty high.

Also, why does it have to be a subscription model?
Been using it exclusively on iPhones and iPads. The single tab is actually a feature. I never need to remember to close tabs leader open when repeatedly opening various links from other apps, ie Tweetbot, where it’s set as default, in Firefox Focus/Klar.
Twitter threads feel more focussed (than long form content) to me. People skip fluff and focus on the important parts.
https://realclimatescience.com/arctic-sea-ice-unchanged-from...
Obviously CAP_SYS_ADMIN and root-running containers should be avoided.

But on the occasion that they're necessary, isolating from other pods with a network policy and having no public ingress is enough right?

Assuming of course that you trust the container process(es) - or is that the issue?
Every person you recommend that to is worse of having heard you say that.

Stop telling people to turn off Windows Defender.
most important part is hidden in there:

> with deadlines to meet

the reason the company is there, employing you now, is that deadlines were met.
In a fair system we’d all need to take turns in being homeless and share our homes around.
Maybe email me at alizeebellerose @ icloud .com and we can have a better discussion. I was temporarily banned from HN for conversing about this topic. In any case the discussion would be better by email or elsewhere. I'm agnostic in the sense of purpose but I enjoy neuroscience enough and with physics that I cannot see real control existing in reality. Although, I would love to have someone explain to me how they see otherwise.
Here is the transcript, for those who do not feel like viewing a three hour video ;)

https://www.computerhistory.org/collections/catalog/10265805...

An excerpt:

Feigenbaum: One of the things worth observing -- it’s off the track but as long as we’re talking about
history -- is that our current generation, and generations of students, don’t even know the history of their
own field. They’re constantly reinventing things, or thoughtlessly disregarding things. We’re not just
talking about history going back in time hundreds of years. We’re talking about history going back a
dozen years, or two-dozen years.

Knuth: Yeah, I know. It’s such a common failing. I would say that’s my major disappointment with my
teaching career. I was not able to get this across to any of my students this love for that kind of
scholarship, reading source material. I was a complete failure at passing this on to the people that I
worked with the most closely. I don’t know what I should’ve done. When I came to Stanford from
Caltech, I had been researching Pascal. I couldn’t find much about Pascal’s work in the Caltech library.
At Stanford, I found two shelves devoted to it. I was really impressed by that. Then I came to the
Stanford engineering library, and everything was in storage if it was more than five years old. It was a
basket case at that time, in the 60’s.
For a lot of the server market, I suspect Intel, being a known quantity, will remain where it is. Bringing a new design to market is expensive (tooling, supply chain, warranty, maintenance, product life cycle, etc) and I'd need to know I'd be able to sell at least a certain number of boxes over a given time to make it worth it.

If all my tooling and supply chain is geared towards Intel on the server lines, it'll take a much better value proposal, volume guarantees, and the threat my competition will do it first to make me add a new line geared towards AMD.

OTOH, for cloud powerhouses that design their own hardware, even a marginal improvement in TCO/performance will tip the scales.
A direct tissue-grafting approach to increasing endogenous brown fat
Could start with regression testing, each time you break something, write a test so that you do not break the same thing again. After a time you will have a decent test suit. Also write tests for all new stuff. And also write tests for everything you change. Would also be an idea to start using version control, so that each change is documented in the commit message. Both tests and SCM you can start with on any stage eg. even on legacy code. Another strategy would be to move some functionality into a micro service. For example instead implement new feature X, make it a standalone service that not only is decoupled from the monolith, it should not even share the same db, it should be completely standalone.
I'm not sure I understand the title or introduction to this article. The paper being referenced is about a constant time single iteration quantum algorithm/circuit(perhaps single gate? I didn't read too closely) that performs the Kravchuk transform.

The QFT is already used all the time in quantum information processing. Many algorithms makes extensive use of it (including foundational algorithms like Shor's). And if we paint with broader strokes, a Hadamard is a just 2x2 qft matrix, so all problems in BQP that are solved by exploiting quantum parallelism use it.
Here's the thing: when I see people spend all their time on design discussions and documents, their work isn't any better for it. Usually it's worse. The documents are not clear or helpful. The designs encoded therein are not better than the first pass knee-jerk thought. The points raised in reviews are just bikeshedding. The process encourages explosion of complexity, making mountains of molehills, and sometimes can be a refuge for people who don't actually have the skills to hide out in. I do very much respect when someone can plop down some working code this afternoon vs. organize an 8-person kickoff meeting next week.

If it's a genuinely large project, the working code is a skeleton POC, and we can run a design process using what we learned from it. But most of the time it's not, and that engineer has saved us collectively hundreds of hours of waste talking to death something that just isn't that hard.

I think one of the critical senior engineer skills is having correct intuitions about how much time and energy should be sunk on a particular task. Sometimes that means asking people to slow down, collaborate, and think. Equally often, it means asking them to put down the calendar invites, make a choice, and bang something out. We have this bizarre cost model where code is expensive and meetings are free; nothing could be further from the truth.
...Wow. This article changed my opinions dramatically. Really thankful to see an article like this. It puts the emphasis on irresponsible (whether it's intended or not) journalism as a huge problem here in the US, as opposed to all the dystopian news stories that come out these days.

Of course there are real exceptions, like stories that turn out to be true about really bad working conditions in some places. But it particularly struck me to see this example, of John Oliver and his team grasping at straws to put together a damning narrative about Amazon, only for one guy with firsthand warehouse experience to come out and tell a much more positive and convincing story about his job.

We definitely live in a time where social media and the news tend to make us think the world is a hellscape of things like big tech and AI, corrupt politics, and corporate greed, all coming together to destroy our world as we know it. I don't think the world is perfect, there's still tons of problems that really suck (homelessness, poverty, actual corruption and greed, ...) but I feel like we're gonna be totally fine and this is pretty manageable overall. We'll figure it all out.
that is a little funny you're right. It reminds me of something interesting I read, don't know if it's true or not. I heard that in the "middle ages" (or dark ages) it was taken for granted that the ancients -- meaning the Greeks and maybe even the Romans, not sure -- had been way wiser and more knowledgeable than them. (You know, as they read Euclid's elements and Socrates and stuff.) As I remember it, all the way through the Renaissance that was the thinking, that the ancients had known way more.

Imagine thinking that the ancients knew more than we ever will, and trying to study their works to get at just some of the wisdom they had held. I think few if any people read ancient authors that way today.

however my memory on this subject may be shaky.
For example LXC containers are unprivileged by default. If you escape the container you end up as a normal user on host, not root.

LXC main dev is on HN. I'm sure he can explain this much better.
I'd say "that depends"

For example if you're running Kubernetes, then if you have a user who has RBAC rights to exec into a privileged pod, but doesn't have rights to create new privileged pods, then this could be a privesc risk, as they can use something like this to escalate to the underlying node after exec'ing into the privileged pod.

It (as with all things security) depends on your threat model :)
I don't think an analogy that focuses on "capacity" alone is a great one. You want an analogy with both stocks and flows. It's worth checking out Donella Meadows' book "Thinking in Systems: A Primer".

here's a rough disk space analogy with stocks and flows:

Suppose you have a disk with free space X. What rate do you consume free disk space? What rate do you produce more free disk space? if flow out (of disk space) is larger than flow in (of disk space) then after some finite time you will always run out of disk, no matter how much free space X you started with. More capacity (a larger initial value of X) just buys you more time until the emergency. Which is useful, but you still haven't solved the actual problem in terms of the delta between the two flow rates. Now if you have your flow rates under control, and you produce at least as much free disk space as you consume, what if the flow rates aren't always steady, but have variability? Then having some spare capacity can help to provide slack or buffer to deal with temporary periods where disk is consumed much quicker than usual. But there are diminishing marginal returns to having lots of excess capacity.

> Annual income twenty pounds, annual expenditure nineteen six, result happiness. Annual income twenty pounds, annual expenditure twenty pound ought and six, result misery. --Charles Dickens
I mention this because some, if not all, of the code links are dead.
Sear: An always-encrypted tar-like file archive format
On the other side of things, my favorite demo for people new to docker who aren't yet aware that sudoless docker ~~ root access is:

docker run -itv /:/host ubuntu chroot /host
It's typically not the case that we can't make things as well as we use to. It's just that we've found ways to make them that are cheaper by an order of magnitude and last just long enough to do their job.

Roman concrete wasn't disruptive. It was disrupted.
> They are well structured blocks of rocks that distributes the load well basically

So is a building like the Burj Dubai, but this is an incredible understatement of the technology involved. The reason Roman concrete is interesting is that until ~50 years ago we had no idea what made it so durable. Dams are being built using these discoveries, sounds quite useful to me.
Anecdotally I know several people whose 'main' desktop PCs are now right around 3 years old. Mostly stuff from one or two intel generations prior to the introduction of the Ryzen 1xxx series several years ago. After going through all of the reviews for the Ryzen 3xxx (3700, 3800X, etc) and X570 chipset motherboards, they've upgraded and are really pleased with the performance.

It's fun seeing something that can chew through kdenlive video editing of 2160p, 60fps video and encode a project into HEVC like a hot knife going through butter.
Submitting this re: the recent discussion about PGP alternatives. It seems right in line with the types of tools that were being suggested for replacing specific use cases of PGP. Written by Tony Arcieri, who is well-regarded in the cryptography community.
I picked mine up at abebooks.co.uk – it seems to have been quite popular in the UK at the time.

Regarding copyright: It was published in the UK. So for the moment EU copyright regulations, 70 years from the death of the author (I guess).
Zoom – Conceptual Design and Analysis of Rockets and Their Missions
I wonder if that figure will hold though. The progressive strategy may well be to get any sort of limit passed now, and lower it later.
Can confirm. The name will have to be changed.

And to the app's creators: Don't change the name to InDesign.
Bachelor’s degree in geography? I wonder if she went to school with Buster Bluth.
Not really news, but maybe timely on the 50th anniversary of Apollo 11's lunar landing.
True, but my point was how much they charged developers for being there, not how many were available.
No set time limits, they eventually get tired of the stuff that is garbage and move on to more interesting content.

Under the age of 7 we let our children watch educational videos, pixar movies, and play the Wii and Wii U in the main living room (large projection screen) from sun up until sun down.

Ipads are crack for very young children and I think it's best that kids learn how to read and write before getting their hands on one. After a certain age (~10?) they kind of lose interest in ipads since they are rather limited (we don't install apps on our tablets or phones).

I think Minecraft is actually a very good technology for engaging their creative interests and drives children toward educational content on YouTube. Obviously they watch a lot of junk along with the educational stuff, but the junk is also more social oriented so has its own merits.
I suppose it depends on whether expected future debt is considered ‘debt’.

If you have no savings, then it’s very likely you’ll still go into crippling debt eventually; at best, you’re staving it off until retirement. At that point, cheap credit is probably not going to be as readily available.

But I get your meaning. Yes, there is definitely an in-between where people can spend their entire income without accumulating immediate debt (social debt and future debt not withstanding).
Out of curiosity, what did you happen to move to (and why)? Back to ext4/xfs, or to Btrfs or something else more involved?
Lateral movement of an attacker within your cluster would also be a problem.
Also:

Lobste.rs

Subreddits - find the most appropriate ones and check their submission rules

IndieHackers.com if it’s a revenue making project

Producthunt.com

Echojs if it’s js related

Medium, dev.to, hacker noon etc

Some will give you instant traffic. Some might give you traffic if lucky and people clap you (or whatever).

Also try talking at a tech meetup near where you live.

Then put the video on YouTube, dailymotion, etc.

Be a guest on a podcast.

Guest blogging.

Google about internet marketing, seo etc. there are endless things you can do.
I'm not sure I follow you here.

The Docker daemon runs as root (which is kind of inevitable, if you don't then you end up needing hacks like slirp4netns to hook up networking)

However, there's nothing innately inside Docker that requires contained processes to run as root.

Indeed it's a standard part of recommended Docker security guidance not to run your contained processes as the root user.

Docker also provide the facility to enable user namespaces at the daemon level, so that root inside the container != root on the host.
Within the capitalist system, of course - that's how it works. The capitalist fights to increase the working day (either in time- or piece-wages) while workers fight to decrease the working day. It's an endless tug of war between capital and labour. Ultimately, though, I don't think it solves much. The whole logical system and ideological analysis goes beyond simple adjustments to various quantities.
They do have a very special kind of leverage that directly affects their users' genitals though.
Largely a result of NIMBYism keeping home construction figures near economic centers low, resulting in a huge demand-supply imbalance, forcing renters into a bidding war for access to those markets, causing much of the surplus to go to landlords.

Also, the treatment and legislation of housing as an investment asset class rather than as a life necessity.

And then there's the healthcare industry, swallowing much of the real wage gains in recent decades in the form of rapidly rising insurance costs (cleverly decoupled from peoples' paycheck, so they feel like it doesn't cost them anything).

And, of course, designing most of our cities to require that people maintain enormously expensive personal cars, or waste hours per day navigating sub-par mass transit systems.

There are myriad other causes (advertising, consumer culture, extremely expensive infrastructure, government writing blank checks to universities, etc etc), but I think these are the majors.
Hence why it is way cheaper than it used to be back then.

When Apple announced 30% cut, mobile devs where cheering, because many providers were charging way above 50%.
Does it have the seven shells and a lake of boiling blood instead of the kernel?
You could make the same argument about mounting disks.

You revoke the permissions of the people who abuse those resources, and you don’t expose them to the outside world at large completely unprotected.
I'm not an expert, but from what I understand, the hard part wouldn't be the cutting edge rocket science (choice of fuels, valve design, etc) but the fabrication techniques.

The 1960s had a generation of highly skilled welders, machinists, and sheet metal workers that had honed their craft in the factories of the second world war. The USA today doesn't seem to have the same quantity of skilled workers and NASA has to design parts differently to allow automated tools to do the work.

But those fabrication techniques probably would have been considered routine at the time, although maybe above-average in complexity. So even a routine technology can be, in a sense, lost if it falls out of demand.
The best software I ever worked on - software in which the customer never reported a single bug, and every requirement was met - could not have been done without the documentation. The documentation was part of the process of creating the software - the larger part, really.

Requirements, design, implementation, testing; all documented thoroughly, all reviewed and checked, each stage linked clearly to the previous and the next. One could literally trace a requirement from the requirements documentation, through the design, into implementation (which was done using literal programming, producing beautiful PDFs for humans to read - there was very little need for anyone to ever actually look at the actual pure Objective-C code that was fed to the compiler), and then onwards to testing, such that each individual test was linked to proving given requirement(s) that had been written down at the start; sometimes years previously.

The customer was so impressed that they asked us to take over from another supplier whom they were busy suing for lack of delivery of a piece of the same system. Our software was delivered on time, exactly to spec, fully documented from requirements to design to implementation to testing. The whole project ran for most of a decade.

It certainly wasn't easy. It required rigor and discipline and review panels and, I gather, somewhere between ten and twenty years' experience of creating software like that. It worked; the only software I've ever worked on in which the customer never reported so much as a single bug. The entire system could be completely understood down to the level of the code by reading the documentation, and when changes were required, the software engineer would begin by reading the documentation and upon opening the literal style source file, would find it just as expected from the design. I've never seen anything like it before or since.

They went all in, though, and took years to get there. One couldn't just take a modern, agile-style software shop and start doing this. It was culturally ingrained.

I certainly agree that in other places, I've seen some truly awful documentation that hindered more than it helped. I've seen system diagrams literally consisting of a square box with "server" written in it. Protocol documents that contradict themselves on the same page. I once was double-checking the wiring diagram for a cradle for a processor board, and disagreed with the voltage of a single pin; it turned out I and the other chap read the exact same line of text from the board manufacturer and interpreted it in completely opposite ways - one of us interpreted it as meaning the pin should be grounded, the other that it should be connected to the live rail. The documentation was so bad we ended up having to go back to the manufacturer and get a human on the line willing to go on record with the correct value.
I'd love to find this community too.

Apart from technical forums like this, one thing 'Id add that I'm seeking, personally, is all of what you said + a willingness to enjoy life and not obsess over work. A community where people find enjoyment in talking with others as opposed to just bragging about what they did when they weren't at work would be a plus.
AFAIK, that's the only what to run Chrome unless you disable Chrome's sandboxing.
> Most people want convenience, and will trade almost anything for it.

No, this is what indoctrinated "UX" people think.

I hear it every day from ordinary office workers how sick they are from dysfunctional, progressively dumbed down UIs.

Ask just how many people keep MS Office 2003 just because they can't use the "ribbon" UI.