skysight-inc/HackerNews huggingface dataset:
Genuinely curious -- is there a reason not to exploit someone who voluntarily enters into that relationship? I always assumed 'exploitation' meant forcing people to do things they didn't want to do.
I don't know if older macs are intentionally crippled or they're just ignored during QA,

More likely neither. Software just becomes larger and more complex and thus slower on older hardware.

(My 2021 MacBook Pro 14" is still lightning-fast though, I never wait for anything.)
I just want a safe-ish language that doesn't nerd-snipe 95% of software engineers into creating glorious and incomprehensible syntactic monstrosities that go nuts with allocations and hidden function calls. Really hoping Zig getting some more traction.
*System* or Method and Mechanism for Asynchronously Pushing People’s Buttons on a Packet-Switched Mobile Network
"People are welcome to not pay Bank of Japan 0.1% to look after their money"

And how do they do that in aggregate?
You need to do a systematic study if you want to say "does not make it better". One example of one product is too particular of a case.
My intel MacBook lags in such a predictable and constant way, as if a process is running constantly at 99% CPU. Makes me a bit suspicious

How much have they /really/ added to the OS (which is enabled on my hardware) and consuming extra resources?
If you can make your dataset fit on a single 24tb disk (or less if you want cheaper disks), that simplifies the setup. I’d use a set of 3 copies:

* One main disk that you use for collecting and organizing all of the data

* One backup disk in the system with the main disk

* One backup disk kept off-site in a safe deposit box or similar

Every few months, swap the onsite and offsite backup disks to keep the offsite one fresh. When you do that, verify the integrity of the data on the disk that just came back.

Automate verifying the integrity of the main and onsite backup monthly.

My preference for filesystem would be single-disk ZFS “arrays”. That allows you to run a scrub to verify integrity easily.

For copying the data, use either zfs send or rsync. zfs send copies the filesystem directly so it preserves everything about the file (for example sparse files) but rsync is less complex.

For getting the data from your various disks, I tend to use dd to create a raw image of the disk, then use other tools like losetup to mount the image as a loop device. Then if there’s data that I want more convenient access to, I’ll rsync it out of the mounted FS. That way, you’ll never lose data from a misconfigured/faulty copy since you can always do it again from the raw disk image.
My experience on HN for the last 15 years is that the tangential, loosely correlated, comments tend to not only be the most interesting but lead to the most interesting threads.
I haven’t read the manuscript yet, and am not sure that I will. However I don’t agree with the question. Gradient descent, the properties of the loss function are the “how”. It seems like you want to know how some properties of the data are manifested in the network itself during/after training (what these properties are doesn’t seem to be something that people know they are looking for). Maybe that’s what the authors are interested in as well. If I could bet money in Vegas on the answer to that question, my bet would be in most cases that structures we may probe in the network and see in them correlations to aspects of the problem or task that we (as humans) can recognize, well very likely this will boil down to approximations of fundamental and eminently useful quantities like, say, approximate singular value decompositions of regions in the data manifold, or approximate eigenfunctions etc. I could see how these kind of empirical investigations are interesting, but what would their impact be? Another guess, that these investigations may lead to insights that help engineers design better architectures or incrementally improve training methods. But I think that’s about it - this type of research strikes me as engineering and application.
I am not talking about wound up springs. This is a simple spring you usually see in pairs, one on each side of the garage door.
The threat model isn't "someone will install stuff on our servers". The threat model is "some user will look at the network traffic and see all the personal data we're hoovering from their phone".

Sometimes also "some user will look at the network traffic and notice that we have 0 server-side security".
Thanks for surfacing the story about Backblaze.

I had the same type of thing happen to me with the LastPass leak, which made me very wary of closed-source supposed-e2e encrypted services.

Looking at Borg, it doesn't seem to have native support for the actual transfer of the remote backup. It seems like if I used Borg it would be for a local backup, and then I would need an additional layer to sync the backup to remote storage.

It looks like rclone does, mentioned in other comments here, any others?
Another interesting way to headline this is, Madagascar was the last place on earth to be settled, despite being right next to the first
Maybe get a proper certificate designed for such things instead of using what amounts to a corporate-funded public service.
They're quite regular - look at the Wikipedia page for Irish orthography to get a good set of rules.
It's important to note that this is preventing pinning /intermediates/ which are re-issued about annually. It is usually a mistake to do that. It is possible that due to a large-scale incident, we'd have to revoke an intermediate immediately and switch to a backup.

While we don't recommend key pinning, there's nothing to prevent pinning Let's Encrypt's root CAs.

(I work for Let's Encrypt)
I’m curious how quickly the data would be used up if only using it for the intended forms/jobs/welfare. I wouldn’t be surprised if the data lasted barely any longuer due to bloat.
They're supposed to help small innovators get protection from the big guys when they invent something new, and then they're supposed to expire expediently so that they don't stifle innovation.

... but ...

Seems like that isn't their main use anymore.
Astronauts in the 1960s were required to be perfectly healthy before their mission, not even minor anomalies in bloodwork etc. were tolerated. No surprise that a third of the moonwalkers is still alive at approximately 90.

Nowadays the tolerance is somewhat bigger.
I generally agree, but with the caveat that you are more speaking to "Agile" and agile project management (eg: Scrum).

To that extent, I find it really useful to draw a distinction between agile development and agile project management. The former I think has some good ideas, namely :

- don't go off into a cave for days, weeks or even many months before merging or showing any work; show & release your work often.

- ask users frequently: "here this is, what do you think?"

- assume you are probably on the wrong track, a good way to get back on track is to talk to the users. The more often you talk to users, the less likely you are to spend time on the wrong track

- deliver in small increments. Gall's law - don't do big-bang deliver-the-world style projects, they often fail.

On the other hand, agile project management (IMO) is almost trivial when agile development is done well and should not be prescriptive. If someone is building a tool for someone sitting next to them, does it make sense to do a demo every two weeks? I find what's more that Scrum is not even coherent, it's not internally consistent with itself. It's ironic as Scrum says nothing about going "fast", yet it's all about "fast" development - and second a framework that says "we will be changing our mind every two weeks" is somehow supposed to be more predictable and a better fit for long-range project timelines??

ON THE OTHER HAND... in the defense of Scrum, having a framework to prioritize work and emphasize delivery can still be valuable. Dev's can have a tendency to only want to work on cleaning up code. It can be a bit like Starcraft, where a player spends too long building economy and workers and never actually builds the army that wins the game. Though, frameworks have a bit too often become shorthand for actual thought, too much cargo-culting.

[edits: cut out some ranting]
Google it. They released female mosquitos with a bad gene and they almost immediately got selected out.
I disagree from a conceptual/philosophical perspective (broken accessibility is bad delivery, not just occasional mishap/edge case for some small set of customer) and from a practical perspective. It's not an occasional customer, it's a huge chunk of the marketplace. Here are some stats: https://themeisle.com/blog/web-accessibility-statistics/

I don't think software shop owners that are ignorant of or ignoring accessibility are necessarily jerks. Before being informed, they are transgressive to good sense; after being informed, immoral. How they act directly towards someone is what defines whether they are a jerk or not, and that, in my mind, is not really connected to the conversation.
The sweatshop is typically there in the first place due to international economic policies that blatantly benefit the more powerful nations, and provide a source of cheap labor for said nations.

The exploitation is baked into policy. Paying people near slave-wages is merely using the exploitative policy as it was designed.

https://pluralistic.net/2024/02/07/farewell-mr-chips/
> There’s a good chance some or all 7 will see people walk on the moon reasonably soon.

Yes. And SpaceX was supposed to fly the japanese entrepreneur around the moon in 2023.

https://www.cbsnews.com/news/spacex-moon-announcement-elon-m...

Considering that just a fly-by to the moon is being delayed, I'd imagine that actually landing men on the moon is going to be delayed as well.
To write safe C++ you need moral discipline, rather than intellectual/cognitive. The language has the tooling.

Moral discipline means rejecting the use of unsafe constructs for the sake of speed or convenience, and doing the safer, slower, sometimes more clumsy thing.

For instance, to skip thinking like "oh, we can just retain a direct pointer into here, and then we don't need to make a copy ...".

And, of course, while that is all well, you can only practice this advice only applies to small team or solo greenfield projects.
I'm not an expert by any means but there are some papers exploring this using category theory.
Their websites look so similar....
It also prevents your employer from snooping on you if you open Signal/WhatsApp/Facebook/... on your work computer.

Of course, you might consider that a legitimate employer thing to do.
Dinner Like Obama
Imagine that you graduate university with some cool tech ideas. You develop a prototype and want to start building a business around it. You file a patent, hoping it will protect you long enough to get your company off the ground -- often a 7 year mission. Does it? Not necessarily, but it is nice, in theory anyway, to think that big tech can't just rip off your idea at scale the first time somebody sees it

In practice, my understanding is that you can't really afford to enforce your patent without a big legal team, and even then, the cost can sink your fledgling company

I think the real problem is the cost of accessing and navigating the legal system (including: the cost of invalidating bogus patents)
What if the mutation is the result of some crude logic? Like the choice of things to eat is limited by what you can catch or find. You not just randomly happened to prefer eating chickens over eagles. Then when used to eating chickens you run into dodo's and the choice is obvious. Running into dodo's wasn't a random event. We deliberately went looking for something like them.
I believe the interaction with asbestos is material, not chemical. It breaks into tiny shards that are light enough to breathe, and sharp enough to cut up your lungs.

Which is why a single exposure will damage your lungs, but it takes lots of cycles of damage and repair to chance into getting cancer.
Or to move on to a new opportunity!
> TV streaming is a luxury good

I don't agree. For many people, it's the only way to access TV. Wide access to broadcast media is a basic right, not a luxury. Some would say (me, for example) that it's neccesary for the proper functioning of civic society.

Meanwhile I note that free-to-air TV has been in decline for over a decade, at least in the UK. Cable and satellite services have been stealing the broadcasters' lunch. BBC News has an ever-shrinking circle of reporters (which they nowadays refer to as "editors").

I have no use for a streaming "package"; I don't watch sports and athletics, vintage sitcoms or new-release movies. I have a Sky dish and DVR, with the basic package. I gather Sky want to move me over to streaming, which would mean I'd have to upgrade my internet service.
Doubts Grow About the Biosignature Approach to Alien-Hunting
We could let the market set interest rates but they would be much higher. Banks would be very unhappy since they have loaded up on the rock bottom rates. You'd see many banks go under similar to SV bank. This is a world economy and they are all somewhat aligned on their interest rate policies. Those that don't fall in line will see a currency repricing (and some like Japan want that to some extent).
Does this not simply mean they want people to pin "ISRG Root X1" instead of pinning "Let’s Encrypt R10" because they want the ability to rotate the latter?

Although IMHO saying "don't pin this cert which expires in 2027, instead pin this cert which expires in 2035" is kinda a weird distinction to make as those are both too short.
> Some of these problems could be a de-emphasis on the Intel experience.

Unlikely since several of the issues seem to happen only on Apple Silicon.
I also remember coming away from my studies with the simple but effective heuristic to never, ever eat a foraged all-white mushroom. Seems like those ones have particularly high risk of melting your guts (literally)

I personally never could get into foraging not because of fear of poisoning, but rather because I learned that many mushrooms are super-accumulators of metals, similar to fish.
patents have a pretty short lifespan compared to copyright, so patent trolls can't leverage them for very long.

The alternative would be a gold rush every time a good idea is had. It would be chaos.

Patents could be shorter though. Ten years?
Tastes like chicken? Think again–edible ants have distinctive flavor profiles
It's specifically to discourage intermediate key pinning. If folks want to pin their own end-entity public key (and always re-use the same key when renewing their cert), go for it -- dealing with compromise of their own key is their own problem to solve. Or if they want to pin a root public key to ensure some other CA doesn't issue a MITM certificate, go for it (although that doesn't prevent a bad actor from getting the same CA to issue a MITM certificate; there are other mechanisms to prevent that).

Just please don't pin intermediate CA keys, which should be opaque to the end-user and need to be able to change quickly without breaking a bunch of apps.
IMO, the ALL CAPS words interspersed throughout have the opposite of the intended effect. Rather than underscoring his desires in a persuasive manner it appears he is screaming and childish.
> We think the way you win in CRM in 2024 is by keeping the flexibility of SObjects, and then tacking on modern UX. That first part takes engineering discipline, but the second part is much easier than Salesforce had it 25 years ago. Just about every part of a modern SaaS product has dozens of vendors that do most of the work for you.

It sounds like your business strategy is 'remove legacy code.' I don't hear anything about how you will address network effects or inertia, or which niche user are you solving a problem for.

Good luck.
You are missing one important point.

Your network can learn some dataset very well. However, that doesn't say anything about how well it generalizes, and thus how useful your network is.
Steam Families opens up game libraries for sharing, with a few caveats
Java has worked great on Apple Silicon since release and it’s still working great now for most users. The linked post explains that Java is already using the W^X modes but there’s an edge case involving page faults while the JIT is updating pages, which to me seems suspiciously like an attempted security improvement which needed better testing:

https://bugs.java.com/bugdatabase/view_bug?bug_id=8327860
That is definitively not the way to test mushrooms.

Yes, there are mushrooms that can kill you that way, and a lot more that can seriously harm you. False morels, funeral bells, deadly webcaps, a bunch of different amanitas... in the case of deadly webcaps, you won't notice until a few days. But then you're going to need new kidneys.

Basically every webcap is suspected of being carcinogenous too, and look up Julius Schäffer if you think there can't possibly be long-term effects of eating mushrooms that "seem fine" after 20 minutes.
It is telling that you have to use a throwaway to post a link from an Israeli news org investigating an influence operation by Israel.
That's the same level I had when I got very ill, it's near the bottom half of the insufficiency range, you should definitely consider supplementing and monitoring it.

Per your question, the latter, the theory is autoimmunity is exacerbated in a certain genetic makeup, and to compensate for it by megadosing.
Not at all. The way you gain trust is by making clear commitments and either meeting them or updating them as necessary.

I'm not saying that the engineering troubleshooting a problem should be narrating moment by moment. I'm saying they should say, at the outset, something like:

"I'm going to go try flushing the cache and restarting the app servers. I expect this to take about fifteen minutes, and if it works I would expect to see the database load normalize."

That's all I need as an incident manager. Otherwise I'm sitting there not knowing what to say in my status updates, my stakeholders are asking questions about estimated duration that I can't answer, and so on.
The degree of reduction is nice considering the countless times in the past where I wrote my own file cache logic using if/else statements, temporary files, pickle, and bespoke sqlite databases.

Why give myself the headache of maintaining so much extra code when someone already wrote it.
Perhaps I phrased this badly. I don't think the entire article boils down to inheritance vs composition. But in discussing these patterns elsewhere, some of the pushback has been that many Ruby devs prefer to decompose problems via sub-classing instead of composition of command objects, so I tried to cater to that objection with that line.

Pipeline steps are command objects (a pretty standard OO pattern), so they have a single entry point / public method. But they can still fully leverage any other OO pattern in their implementation. The more complex ones I use may instantiate other objects, pass messages between them, etc.

But the single-method #call API is what makes composition easy. See Rack, or any number of middleware-style designs, for other common uses of this in Ruby.
its obviously just an abstraction over an IQ test.

Id argue its probably quite hard to find a 'top talent' that has an IQ thats substantially outside their desired range. Obviously theres variance and there's other factors that contribute to someones success in their career, but their raw intelligence is certainly a large input thats worth considering.

Its nearly impossible to train someone with an IQ of 80 to be a senior software engineer.

and please dont respond to this comment claiming IQ is a useless metric. its not, and thats been very clear for decades.
Another problem is that many packages have been sitting waiting for critical bug fixes for months. I'm not sure what their focus is, but they really aren't particularly suitable for use as a desktop or server OS.

A third problem is that the quality of the .deb's they package is low and decreasing rapidly. For instance, they don't seem to understand how to properly configure update-alternatives anymore.

I'm guessing all the above can be explained by establishing hiring bars that aren't good predictors of job performance, and then letting it play out for a decade or so.
You could make an outlook/excel add in. Sales people live in those two apps. Without that you are battling to be that “second screen” as you mentioned and sales folks aren’t generally tech savvy enough to “go it alone” on your solution vs the status quo. Looks nice though good luck!
of unknown origin or type

Very few people end up in hospital because they are randomly eating mushrooms of unknown origin or type. They end up in hospital because they 'know' the type of mushroom they are eating, and just happen to be wrong.
Guerrilla Filmmaking at Xerox
1M is the target today. What does that have to do with 50 years from now?
> When you're investing for retirement in your 20s or 30s you can wait out a 5 or 10 year downturn in your index funds.

Sure, I know all that.

But the point, or rather the question, remains ... what are you investing ?

Which brings us back to "don't invest what you can't afford to loose", because by definition you can't afford to loose that for days or weeks, let alone 10 years !

You should really have 6–12 months worth of salary in hard cash in bank accounts. Then you only start "investing" whatever spare you have after that.

Why 6–12 months ? Because bad things have a habit of coming in pairs. You have an emergency that needs ca$h, you have a problem with your house that needs ca$h, you need to pay your mortgage with ca$h ..... and then your boss comes along and tells you that there's no job for you anymore.

6–12 months might sounds like an unreasonable amount, but if you lost your job tomorrow, nobody is going to be generous and wait for you to find another job, the bills will keep on coming.

Most people also don't have an ability to walk from one job to another. Realistically it will take (at least !) a couple of months to find another job if your departure from your previous one was unplanned.

Cash-in-the-bank provides you with a safe number that is a close to guaranteed as you can get. Meanwhile you cannot rely on selling off your passive index holdings to support you because the markets could drop 40% tomorrow without warning just because some dictator on the other side of the world got out the wrong side of bed and invaded the country next door.