skysight-inc/HackerNews huggingface dataset:
Previous discussion when this story originally broke:

“They introduce kernel bugs on purpose” - https://news.ycombinator.com/item?id=26887670 - April 2021 (1954 comments)
Nice! Howabout adding a way to link to a meal?
It's true, I still run relatively old Unifi nanoHD APs (3x) and considered their newer U6 Pro AP for my house. However, the small benefits that would result from this are not worth the price to me, especially since everything works great with the older gear. We also don't have that many wifi6 clients in the family yet, so I discarded the idea.
I love the idea of Wifi 7 and I'm looking forward to upgrading from 5/6/6E, for a couple of reasons:

- Yes, I actually do feel limited by the speed of 5 and 6 (not 6E), not least of which because it gets worse with distance. The 6GHz network works great but doesn't get nearly enough range, and I'd love to supplement that by simultaneously talking on 5GHz and 2.4GHz, while using as much 6GHz bandwidth as is getting through from a given location. And I don't want to have to change which network I'm connected to, or even if it's the same ESSID I don't want my device to have to "switch" networks.

- No more dealing with 2.4GHz vs 5GHz vs 6GHz channels, or worrying which channels are clear, or which devices should be on which frequency. The premise of WiFi 7 seems to be to use all the bandwidth that nothing else is using, while avoiding anything that another device is interfering with. "What channel is your router using?" "Yes."
In contrast to the system of wifi access points in apartment buildings, which is more cells AND more power!
Solid analysis.

A word of warning from personal experience:

I am part of a medium-sized software company (2k employees). A few years ago, we wanted to improve dev productivity. Instead of going with new laptops, we decided to explore offloading the dev stack over to AWS boxes.

This turned out to be a multi-year project with a whole team of devs (~4) working on it full-time.

In hindsight, the tradeoff wasn't worth it. It's still way too difficult to remap a fully-local dev experience with one that's running in the cloud.

So yeah, upgrade your laptops instead.
I'm not the person you asked, but I think they meant: changes that are not shared with others. You can back up your own stuff as you please, but once you share it with someone else, it's best to treat that bit of repo history as immutable from that point onward (because they may have made their own copies, shared it with other people, etc).

So I think what people are saying (and I largely agree with them) is that it's fine to rewrite history as long as you never share the ugly mess that existed before the rewrite with others.

A typical example of this is having un-shared ("local" - but could be backed up) streams of "tweak a comment, fix a semicolon, xxx" changesets that aren't really going to be useful to other people. Before you share with others, you squash them down to a single (or few) "implement feature X" kind of changes, often with linear history.

Having that less-branchy and less-noisy linear history available is useful in the future when you want to examine the history of the repo. Future people don't need to know that you fixed a comment, added a semicolon, etc. They want to know the big coherent logical changes that were applied to the repo.

Squasing/rebasing/fixing history before you share it allows you to have your cake and eat it too, more or less.

----

EDIT: Here's a decent email from Torvalds on the subject (not that I agree w/him about everything, but in this case): https://www.mail-archive.com/dri-devel@lists.sourceforge.net...
Local in the sense that every developer has a full history, and can edit their own history after the fact before pushing changes.

Basically it's the equivalent of bringing patches up to date before upstreaming them. Upstream isn't going to apply a patch that no longer applies cleanly.
Why use Chrome when Brave is pretty much the same but with better privacy?
In my opinion, this is a misrepresentation of the Vietnam war. The country was not "bombed back into the stone age". The U.S. merely used extremely despicable tactics like Agent Orange, My Lai etc.

I'm also not aware of the existing Vietnamese government falling (depends on which one you consider the existing one but it was not the government the U.S. wanted to fall that fell). The country resisted a superior invader like it did in the past (China) and I'm pretty sure most people would consider Vietnam the winner of the war (if there's a winner in war).
Try it like this, see what you think:

Commits serve two needs: saving your work and publishing it. Adopting an "early and often, explain what you did" approach is effective for saving, but when it comes to publication a "refine before release, explain why you did it" strategy is more valuable.

The commit history is an artifact of the development process, just like documentation, tickets, or even code. I'm sure you wouldn't complain about people taking the time to write better comments, and a commit message is like a super-comment, because it can apply across multiple files.

Honestly, do a maintenance programmer a favour - fix up your commits before publishing them. A linear history makes tools like bisect easier to work with.
I think I see what you mean now. Thanks.
I’m confused. Is the workflow to rebase branches and squash merge into main? Because that’s what I do at work and it works quite well. You get atomic PR merges so reverts are easy and you get the clean history for a PR so people can in theory review commit by commit. Although if you want to use merge commits in your own branch, I don’t care because it all gets squashed. I don’t fully get using rebase to merge PRs cause then it’s exposing the commits of the PR, when in fact the PR should be considered atomic code changes. But I suppose for workflows where PRs are not considered atomic code changes, rebasing could make sense.

Really, what this boils down to is a confusion between commits as a save point and commits as an atomic code change. With my aforementioned process, commits inside a PR are save points, I.e. I need to just save my code before leaving work, while commits on main are atomic code changes (and therefore should correspond to a single pull request). In the rebase-everything approach all commits are atomic code changes, which I find a little too obsessive since you need to make sure your code is always working when you commit or rewrite your history so that is true.
> the increase in activity seems to have come from just two trades.

its interesting how nobody not even a bot was interested in copy-trading that, most likely due to the incredibly low volume, kept everyone else far far away from that ticker

only 15,000 shares traded today. paltry.

curious if they, were they able to cover that short
Yeah that is a horrible example.
Just an anecdote, but I once reported (by phone to the local gas company) a smelly local gas pipeline/junction that I noticed after cycling by on the road the next to it, so the leak could not have been all that small. I then reported it some weeks later because the smell was still just as strong (but still "faint" at the distance to the road).

Apparently no one cares about the little leaks everywhere (or they cannot be fixed cheaply). Later on I noticed that other gas pipeline junctions -- the type that are scattered around subdivisions -- often smelled faintly of gas. I wonder if these small leaks can be avoided with better engineering or if perfectly sealed pipe fittings in the outdoors are impractical.
Doesn’t work for homes.
> people rewrite their history because theyre irresponsible with pushes. it's got nothing to do with the source control system. You're supposed to push small isolated encapsulated commits with a good names. I never do that while developing.

Its a good ideal but not realistic.
> A laptop compromises performance in order to be lightweight, portable, and stylish.

I'd agree with this ~2 years ago. Then I bought a MBP with a M1 Max and honestly I don't see many compromises with this machine. Coming from a 2019 Macbook Pro, it was a night and day difference. Ports, performance, efficiency, heat, battery life, etc.

Now, of course this laptop doesn't have the fastest CPU or GPU available, but it's so fast that it's no longer a compromise for me. It's actually faster than the desktop I upgraded a few months before buying this laptop, and since then Apple has released faster machines.
lol ethernet to everything please. soooo may helldesk calls. "uoooh internet... bad..." okay plug dat shiiiii in
Why should I readjust my moral compass? Because people could not forget their feuds and started to kill? The system held together by terror was pushed out of equilibrium. They had a change to find a better one but they chose not to. If anything then US has done not enough by letting sociopaths in Syria and Iran still run the show - a huge part of the deaths (I'm not going to dispute your claimed numbers) could have been averted and not only in Middle East.
To save anyone the trouble, the article does not identify anyone specifically, only that "the most plausible account is that whoever made the trades was familiar with Hamas’s secrets."
Local == not published (on the trunk or whatever you call the main branch).

Local != not pushed to a remote. You can totally push to a per-developer remote, or to branches under a per-developer namespace.
Nvidia's China customers who buy a hobbled chip will be the last of the Nvidia Chinese customers.

Say goodbye to Nvidia. They need lots of Chinese customers to survive. They won't.

Those Chinese customers who might've bought Nvidia will buy Chinese chips instead. And yet another US company will bite the dust.
When is the slider not at the bottom when you want fine-seeking? In cases when its not fullscreen, I don't ever need fine seeking.

It's not really "slide up" its just a very tiny motion, maybe less than 1cm of travel to enable it.

We already have long press and 3D Touch events via the "hold longer" action, which might work, but I've had no real issues with the YT solution.
> people rewrite their history because theyre irresponsible with pushes. it's got nothing to do with the source control system.

Corporate policy often is to push at the end of the day, so in the event you spill some coffee over your laptop, all you'll lose is a day of lost work and a day to set up a new laptop.
Me too, friend. Me too.
I have a 65sqm apartment with 3 APs, 5GHz set to low power. I'm pretty happy with the performance.
What did they do that makes you think they valued creating social change more?
I've never understood that. If someone were to hand you a glass of yellow milk, I'm guessing you wouldn't be too eager to drink it. I get that chocolate milk comes from brown cows, but I ain't ever seen a yellow cow.

As an american with enough laps around the sun to have some experience, I'm constantly aghast with what we've allowed to happen to food.
You really need to learn what a"pejorative" is before using the term publicly.
Thx for your reply!

>> As for the distinction between random JPEG files and the Photos app, I think that's actually quite good.

Please don't take this personally, but that always terrifies me. It's like modern apple owner "sour grapes" fable - "I actually love this random limits tion, it makes my life much easier " and I hear it a lot! If I right click and save photo in some apps or websites it is in photos app, but in random other apps that same file is no longer a photo. How's that good? There are a million ways to "not clutter" that are better. Folder might be one but if that's anathema, then albums or tags. It's a completely random subset of things that end up being photos vs not, seemingly based on location or tags that arr neither visible or accessible to me as a user. I get that this is "good" for some people, I am clearly not in that group though.

Re ease of copying files, does any of that work if you don't have a Mac? Context of conversation here is iPhone / iPad as independent working devices and ability to transfer files without a Mac OS device. I am readily convinced that if I bought whole heartedly into apple ecosystem and only apple,my life would be easier along some axis, but that's not a life I lead - I have the black box of iphone and I cannot for example delete all photos on it in any way that I could find including in the app, in the settings, via apple support or apple store creepily smiling people :-/.
Just turn off javascript and it'll bypass their paywall
>Big corps could just pick things that are trending up, rip them off instantly and scale their ripoff much better thanks to their great workforce and marketing reach.

Except that they are already doing this, and since money == "justice" in this country and most of the rest of the world, their big bag of money means that you have zero realistic chance in winning any attempt at suing them for doing so.

Copyright is a great conversation to have, but it's a bit like sitting around talking about how to best dry off a plate in the Titanic dining room.
Title should be: "What gives cheddar cheese its flavor?" I doubt most people would agree that it tastes 'so good' and nothing is said about why a fan would find that flavor good.
There's a lot of value in a short iteration loop when debugging unexpected behavior. Often you end up needing to keep trying different variations until you understand what's going on.
Then I think that the complexity is kind of inherent.

Firstly it's only a codebase I have never seen before because I am not keeping up with the changes. Ideally i will pause during rebase carefully read the commits which will include long thoughtful messages laying out important implications, and my tooling will make clear where the conflicts lie, and how test coverage is affected.

We won't ever just grep for <<<<<< and try and remember which HEAD means - is that mine or yours?

I am making changes against an evolving codebase. Either I am talking with people editing that codebase and we are in sympathy or we are hoping a VCS will solve our political and organisational problems.

I honestly think having time to argue about the best way to solve a problem amoung a team is the best solution - let the team talk argue and decide and they will barely need a VCS. If you cannot "spare the time we must deliver" you got other problems

Edit: Look honestly it's all patches. That's the atomic level. And to my mind, having you gather the freshest version of the codebase then apply your chnage son top is the sanest cleanest approach.

The same merge conflict resolution applies - I agree. (basically line conflicts). But what's the option? Anything else gets weirder faster (seen some trying to understand conflicts in functions, etc)
Pijul VCS – A Theory of Patches
Where the data taye requires it. No point in putting a gigabit adapter in a network speaker. TV, maybe, for 4K and beyond.
I keep hearing artists are not happy with their earnings from spotify. But Netflix does not have to seem that problem. Even though the subscription fees are about the same (for me at least). And making movies is also expensive.

So what is the difference?
"tests on the airbags of Daihatsu Move/Subaru Stella, Daihatsu Cast/Toyota Pixis Joy, Daihatsu Gran Max/Toyota Town Ace/Mazda Bongo revealed the irregularity that the “airbags deployment computer (ECU)” was not the same as that of mass-produced products."

https://www.daihatsu.com/news/2023/20231220-4.html
This sounds like a good direction: even very infrequent, very brief stutters can be a dealbreaker for hardcore gamers, and make them chose wired over wifi.
The article does not provide any direct evidence that trades were made with knowledge of the attacks. Also see a refutal at https://www.bbc.com/news/business-67628380
> You could also do without the disparaging comments.

You're right.
YES. I've been saying that for years. The fact that it doesn't work this way is really pretty braindead.
They really aren't struggling. But yeah, China will soon outstrip our naval numbers by a large amount within the end out of the decade. We still have better tech but what do we do when they launch, at the same time, 200 "good enough" cruise missiles at each aircraft carrier sitting in the Taiwan Straight?
It's very sus but $1M isn't a huge profit by trading standards. If they knew what was coming why didn't they bet more?
> Manually intervening and re-writing history should be completely antithetical to a good source control system.

The way I use git, it's not "history" until it's in main. Up until that point, branches are mutable sequences of patches that may or may not ever get merged in.

These patches bear little resemblance to the actual sequence in which I developed the code: as often as not, I'll amend a commit rather than creating a new one, because the point of the version control system for me isn't to faithfully log what I did, it's to represent my change as a discrete sequence of steps to get from main to main+feature.

Viewed that way, rebase is obviously the preferred way to integrate main->feature branch. Main has changed under me in some way that causes a conflict, so I need to reevaluate my sequence of patches in light of the new information.

When it comes to integrating feature->main, I don't have a strong opinion, except that squash is terrible because I specifically designed the commits to make sense as distinct steps.
"people only use about 2% of the volume of their house at any given time"
Sorry. Has to be 'Vintage' so that it's "Strong and Bitey".
Grafana Dashboards: A PoC Implementing the PostgreSQL Extension Pg_stat_monitor
The government of North Korea did not fall or surrender. You can argue that it was a political win if the goal was defending South Korea, but militarily, it was a stalemate.

North Vietnam conquered South Vietnam after we withdrew. It was in no way a victory for the United States. Afghanistan was arguably pretty similar, although we did install a new government while we were there.

Germany and Japan, on the other hand, surrendered unconditionally. Saying that Germany and Japan were “bombed back into the Stone Age” is a wild exaggeration, though — strategic bombing famously failed to cripple Germany’s wartime industrial production. (Strategic bombing in general is overrated.)

Your number for US deaths in Iraq is low by at least a factor of four.

You may wish to learn the actual histories of these wars before trying to draw big conclusions.
Please explain why there needs to be an upgrade.

There's no business case. Even a full blu-ray 4k rip is only ~60ish Mbit/sec encoded as HEVC. Netflix and co have been pushing streaming bitrates down to sub 10 mbit.
There are only a few bigger companies than the ones I’ve been at.

I only do the sourcing, and the HR side I leave to recruiting. The bottleneck in the process is the sourcing, and I have no desire to do HRs job.

On statistics, they only care about the statistics for their own sourcers and processes. There is no regulatory reason for collecting such stats.

Another thing to remember is HR is the weakest organization in any company, and recruiting the weakest in HR. Any manager worth their salt pushes recruiting around, not the other way around.
I'm not a proponent of it, but some people would say: including all the messy history is a more honest representation of what actually happened.

By that school of thought, a repo should be recording what happened, not what you want to look like happened.

I haven't found it to be terribly useful though. IME, it adds noise for future code archeologists.

In very rare cases, having the messy long history can be slightly more useful for bisecting to find precisely where bugs were introduced, simply because it's more fine-grained.
This is the strangest debate and it's not really clear from the blog post what the benefit of picking one gets you. Why does it matter what happens on a devs branch? just do a squash and merge when merging a branch to trunk.
I really don't think the commenter you're replying to was implying we haven't had targeted advertising for a while, but rather that the issue is how targeted it's getting.
Interesting.

The map seems buggy for Canada. The "Country" map for Canada seems to be wrong, as it looks like it's subdivided into several pieces (as if it was the "Zone" view).
> “The question that we posed ourselves was, ‘What do we do now?’” says Carlos Cordeiro, [...]

Uh, Wi-Fi security still sucks. Can we fix that?
Why do you need to squash & merge literally every PR? Why not use squash & merge when appropriate and rebase & merge otherwise? That's what I do for my projects. Most contributions coming from others tend to get squashed & merged, where as I'll rebase & merge my commits. But I'll sometimes rebase & merge PRs from other contributors who have broken their change down into thoughtful commits.
Ferry* and maybe plane i understand, but especially the later is changing with many flights offering (complimentary) internet service afaik, but your aunt i don't.
The alternative, to me normal setup would be using a workstation at the office and then remoting into it via SSH (behind a VPN, VSCode supports this great). This allows for a thinner client (eg Macbooks Air) which need less replacement and where battery runtime/portability can be weighed more.
Sure now connectivity is a concern but to me that's mostly a non issue where i travel/the work spots i choose, but i guess it can become more of a problem in other (less developed) parts of the world...

* this will probably also change with naval Starlink becoming deployed more...
Sounds like a good plot for a (short) sci-fi story.
Long time firefox user, absolutely love it. My only grudge is that on Android some tab will just randomly go black and blank. This problem has been there for at least 1 year, I think it has something to do with os memory collection but I can't prove anything.

And I still use chrome, because of the Chromecast.
You don't lose it long term if you're using GitHub PRs — GitHub keeps the "reflog" (quoted because I imagine their implementation may not actually use reflog) of the branch indefinitely, even after force pushes. Graphite (built to replicate the Phabricator workflow) enables viewing and diffing these versions. (disclaimer, I helped build this)
I LOVED watching The Secret City as a kid.
L'Oréal heiress first woman to amass $100B fortune
This suggests Israel should have been paying attention to the stocks to figure out when it was going to be attacked. Whomever did this had the distinct possibility of blowing Hamas's opsec if the IDF were slightly more alert about this sort of thing.
Ask HN: Why Does Wikipedia Portray TP-Link as Singaporean, Not Chinese?
I was in the market for a new switch for my home network and started researching different brands, which led me to TP-Link. To my surprise, I discovered that although TP-Link was founded in China and is headquartered there, its English Wikipedia page describes it as a Singaporean company, with no mention of its Chinese origins. What's going on?
Yes but it seems like the treatment is addressing the symptoms and not the outstanding source of them as you say. We are slapping band-aids on an open wound
> Transitioning from one station to another, or worse back to call service

The former is clearly in scope for Wi-Fi protocols. The latter is clearly out of scope for Wi-Fi protocols, as it really involves work at the IP layer (or higher even).
It doesn't really fit the modern collapse. Democracies seem to decline when oligarchs extract so much wealth that the entire economy suffers and common people flock to strong political figures to bring back order and prosperity.

> citizens realize they can vote themselves money

Although this certainly sounds true if you consider just the richest citizens and by "vote" you mean inflence the votes.