skysight-inc/HackerNews huggingface dataset:
In the past a Cloudflare representative typically appears in these threads, and if that's happened, I missed it. Not to mention the MVP's comment in the locked Cloudflare thread that

"You should use an up to date major browser. Old Firefox forks are not supported and expected to have problems."

It's all incredibly telling, that they've given up trying to be impartial. When "they" start picking browser winners and losers, are OS's next?

In a way Cloudflare missed an opportunity, because a try()/catch() around the bit of failing JavaScript would have been perfect fingerprinting. Having said that, I don't expect it will take the Pale Moon team very long to patch the problem.

But where to go from here? Is there anybody besides the ACLU and EFF with enough resources to mount a "public nuisance" lawsuit? And what would constitute winning? A court-appointed overseer to make sure Cloudflare is regularly educating its staff on the variety of browsers in use today, and providing near 24–hour turnaround times when issues like this occur? It would be a start.

Personally I wonder if this whole style of security is a fool's errand and any blocking should be server-based and look at behavior, not at arbitrary support of this or that feature. I think it would also be helpful if anybody who finds themselves blocked would be given at least a sliver of why they were blocked, so they could try rectifying the problem with their ISP (bad IP), some blocklist, etc.
There are a lot of wealthy retirees in South Florida who make great marks. Beyond that it’s probably to some extent driven by talent agglomeration effects; if you’re someone who makes their money promoting scammy penny stocks, you might want to learn from other people who promote scammy penny stocks, so if they’re in Boca, you’ll go to Boca. Coincidentally(?) Boca Raton was founded by the Mizner brothers, Addison and Wilson; Wilson Mizner was himself a notorious con man.
Show HN: Surgeon – surgically modify a Git fork
I built this fun little tool to help me make automated modifications to a fork.
Original source (33 points, 2 days ago, 6 comments) https://news.ycombinator.com/item?id=42955009
I thought OV still bypassed smart screen and virus false positives from Windows defender?

Although I think even OV require HSM now for local, with some options for hosted services like Azure Trusted Signing.

But I really don't know. I read details only to end up not certain.
Show HN: ExpenseOwl – Simple, self-hosted expense tracker
>> How do you know? Every interview you conduct is for your team?

My apologies. I should have been more careful in making the claim. You are right in challenging me**.

>> What do you ask? If you want to challenge the status quo you have to offer a replicable alternative

I cannot share the specific problems publicly as then those become available for candidates to practice out, whereas the idea is to give them a fresh problem to think about. Further, the list of interviewers is often made available to the candidates ahead of the time, which can create a loophole as interviewers tend to have a relatively small set of problems they keep repeating for different candidates***.

In general however, I always use real-life problems. Similar examples from text books may perhaps be: (a) Find the day of the week for a given date, (b) Output a given number in textual form (e.g., 14630 -> Fourteen thousand, six hundred and thirty), (c) etc. Most of the problems I pose are motivated from actual use cases, while the remaining are taken from my own prior interviews as a candidate. As I noted before, each one is at best Big-O[N] in time complexity, just like the Fizz Buzz problem. I have brought in more complex ones only when testing for specialized skills for specialized positions.

I also focus a lot on fundamentals. There have been candidates hired for my own teams which could not fully solve the problem I posed, but who however were unambiguously going in the right direction and would not say anything wrong or stupid during their reasoning towards it. I chose to go ahead with them with some risks in my mind, however, these people proved to be stellar in performance. When fundamentals are understood well, gaps can be picked up on the job as well.

I still do stand by my original assertion that proxy problems can be avoided for interviewing. In general, the best method to solve a problem is to solve that problem itself and not another.

** Appendix: Here're the actual data points:

- For interviews within my own team where I have been an interviewer, my claim likely holds. However, this is a small number of hires (say around six-eight) so the error margins would be large. Also, I would not have information about false-rejects, hence '100% accuracy' cannot be claimed even in theory.

- I have been a interview 'bar raiser' at Amazon. Bar Raisers at Amazon are people highly trusted for interview outcome decisions and process control.

*** I have even had cases where (a) someone interviewed a candidate for a second time after a time gap and posed exactly the same problem, (b) a recruiter leaked out questions an interviewer asked frequently to the candidate.
Good point, but there are probably plenty of formulas that can be derived with simple integrals, as a backup for if those formulas are forgotten.
"R4L dies" is hyperbolic nonsense. There are many ways/places to integrate Rust in the kernel, even for wrappers. It's not like "I think this code should be someone else" automatically means the death of Rust.

Marcan goes full nuclear every other time someone disagrees with him. He's very much the "if it's not my preferred way then we might as well not do it at all"-type of engineer (many of us have worked with those people).
> In terms of "good enough", a Canadian postal code, broadly equivalent to a zip code, is much more granular and can often identify an individual apartment building, or single city block.

To the point that StatCan and other agencies have rules on the number of characters that are collected/disseminated with other data to make sure it's not too identifying:

* https://www.canada.ca/en/government/system/digital-governmen...

* https://www12.statcan.gc.ca/nhs-enm/2011/ref/DQ-QD/guide_2-e...
It's not exactly a single ultra-specific 1.1000000... degree value only, just values approximately close to that. As to what the connection is: that's what the research is trying to unearth more about.
Ethics and cybernetics: the ethical groundlessness of cybernetics
Optimus Player – The best app for playing audiovisual content on the Mac
that was not their original announcement
I do agree. I had edited my original topic post as I didn't like how I had phased my sentence.
For sentence coherency; I do that.

Is this a problem?
> Let's recap the past: Taxis were borderline unusable in almost all American cities before Uber (except for NYC)

My experience was very different and "almost all" doesn't feel correct. It's certainly fun hyperbole. NYC the systems worked more than they didn't. In part because of spot lights from famous TV shows and 70s corruption documentaries/news exposes. Most smaller cities the taxis quietly worked with little corruption and a lot of trustworthiness. In the early oughts I had good experiences hailing cabs in cities a lot smaller than NYC that people didn't believe you could even hail cabs in.

Because Taxi regulations were so wildly different from cities, it's hard to generalize what the experience used to be. It varied a lot from city to city and was a massive spectrum, with a few national certainties like some of the big Franchises to help smooth things a bit.

> I certainly didn't love their ruthless business practices, but let's not delude ourselves and admit that Uber or Lyft wouldn't exist if they didn't break the laws around taxi medallions.

In the early oughts, a few cities like Seattle were pressuring the big national Franchise companies like Yellow Cab through a mixture of regulatory body pressure (but not actual laws) and bottom up consumer messaging/volume customer requirements to move to "Computer Dispatch". There was a growing competition in that space, and a bunch of innovation happening between the competitors, including some of the things Uber and Lyft take credit for today because Yellow Cab mostly broke apart in the onslaught of VC subsidization and rule breaking.

I don't think it would have taken "20 years" to implement it "correctly". We don't know because the whole thing got disrupted so sideways by the gig economy. (Which also really didn't care about making the taxi business better, but about making the labor market worse. We should also not forget that breaking the worst parts of taxi medallion laws also broke the good ones that helped build useful labor-side things like taxi driver unions and paid for things like healthcare.)

All I'm saying is that there was a path that this could have all been done under the old regulations, legally. It's a path not taken here, and probably to our detriment. Though I can't prove that just as much as you can't prove that innovations like smarter apps would have taken "20 years" in that other timeline.
The linux kernel project specifically cares about the labor pool of maintainers.

My assumption is that it's easier to train someone on rust then to train someone to be a kernel subsystem maintainer
> It's not exactly fair to treat those rural residents as burdens to the urban areas when they provide the means for the urban areas to exist.

There's a difference between people that are in farming/ranching and industry vs. people that are rural to afford a more lavish home in the woods or on the hills.

Even still, a system that doesn't appropriately price and apportion risk will always be under pressure.
Bad examples of DEI do not invalidate DEI, they invalidate bad implementation of policy

Having a workforce the is purely white men is sub optimal and needs to be addressed. But it needs to be addressed carefully and with good management.

It does not need to be addressed like this

If you want to see a good example of DEI in action look to New Zealand. Forty years ago there were almost no Māori lawyers in New Zealand.

The deans of the law schools got together and decided to do something about it.

It worked, now there are many. Now it is much much harder for the state to accomplish the systematic impoverishment of Māori people and things are turning around

It takes decades done properly, but creates huge improvements in society

This story is a story of doing it catastrophically wrong
I disagree. The behavior of the person who complains about decorum is relevant because it may indicate a double standard in the community. If a community (such as the Linux kernel maintainer community) is ganging up on an outsider using arguments of decorum, it's highly relevant that the already-accepted members of that community themselves act in a way which would've been deemed unacceptable if they were outsiders.
I'm not affiliated I just really like it, the only player that supports spatial audio and HDR content.
Shipping it in its current state does seem premature. The spec still hasn't addressed a major concern from rendering library authors, which was that an explicit check to see if a node is connected is now required to branch between using moveBefore or insertBefore, since moveBefore throws if used to place a disconnected node.
> The Rust drama is an uncommon failure of leadership for Torvalds. Instead of decisively saying "no, never" or "yes, make it so," he has consistently equivocated on the Rust issue. Given the crisis of confidence among a sizeable (and very vocal) contingent of the Linux community, that decision has backfired horribly.

Efficiently collaborating on large distributed open source projects like Linux is as much social activity as technical. For people like Kent Overstreet or marcan and many before them this is apparently a hard thing to grasp and they have been failing badly at following the process, building consensus, earning respect and trust of people from other subsystems, that kind of things. To me it looks like that for Linux big part of R4L experiment is to specifically understand whether Rust people can convince key stakeholders that R4L is good idea and get their buy-in and that is why he doesn't attempt to force it. Also, what is he gonna do to the reluctant but key maintainers? Refuse to accept anything from them until each of them shows him a repo with all Rustlings exercises solved to ensure they are ready for Rust or what?

> And it's quite out of character for Linus not to have a blazingly clear opinion.

Linus tends to have clear opinions on things he is world class in. He is technically brilliant and very knowledgeable in most of the low level systems things but likely not in Rust, so it is understandable for him to just keep being open minded about it and let the chips fall where they may.

> As a pilot program, R4L should have graduated or ended a long time ago. After several years of active development, its status remains unclear.

Which is absolutely normal for the kernel. You can have a driver spending years in staging or RTLinux taking 20 years to get there. It is totally expected for such a disruptive change as introducing new (and quite complicated) programming language to take a few more years to reach maturity.

> Arguably his reprimand of Martin is a clear signal that he will never show Rust any favor, but he hasn't said anything explicitly.

Not it isn't.

> decision has backfired horribly

> place responsibility for the drama on Martin's shoulders

> Imagine how much time and energy (even just Martin's alone) could have been saved if Linus had just said "no, keep it downstream".

HN crowd and random JavaScript-kids on Reddit are only hotly debating this because the "drama" has the word "Rust" in the title. For Linux maintainers it is just another day at the office, nothing much to see here honestly.
"Celebrity" in colloquial use implies someone "famous for being famous", like Kim Kardashian.

To use such word with regard to one of the most talented and innovative physicists of the 20th century debases the entire conversation.
Just so we are clear that’s now in just the past couple of weeks:

- Musk doing a Nazi salute

- Two different of these little DOGE dweebs who forgot to scrub Nazi references from their social media profiles.

I get this is an uncomfortable realisation for a lot of people but I don’t think it’s something you can just wave away as a coincidence at this point.
Hey Julien, long time! We should catch up!
Don't I know it. It's why trade secrets are protected by law, while smart TVs spying on users, with or without revealing it somewhere deep in their EULA, does not get even a slap on the wrist. And why the government bullies other countries into adopting restrictive, maximalist IP laws, but is wholly unbothered by consumer rights getting trampled by DRM and EULAs, or ridiculous patents getting granted.

We're racing to a corporate dystopia, and this is the reason why.
I refuse to take public transit with a checked bag until the NYC subway has 99.9% escalator uptime and escalators at every station, realistically possible with redundant escalators. We will never have nice things as long as we let the trade unions bend us over
> I also disagree that NARA and LoC is subject to whims of the electorate.

National Archives Workers Unsure If Marco Rubio Has Secretly Been Their Boss for Weeks - https://www.404media.co/national-archives-workers-unsure-if-... - February 6th, 2025
Zep AI (YC W24) is hiring engineers to build SOTA agent memory
https://www.cnbc.com/2024/06/06/supreme-court-justices-milli...
> It's the same and worse over there, the drama just isn't public.

At least you’re getting paid. What’s the point of spending one’s free time arguing with strangers on the internet over some code that will be refactored anyway ten years from now..? Life is short, have fun, enjoy it. If you’re spending time or money on something that sucks, walk away.
No, the entirety of the Rust for Linux kernel development community didn't just quit. One guy quit. There are plenty of other kernel developers who are trying to push Rust 4 Linux forwards and make it viable for more kinds of drivers.
> The one that probably got people killed

Got any more info on this? Seems like an absurd exaggeration.
It's legal in the same way this UK thing is legal - because there's a law justifying it. It may make more moral sense, depending on your political persuasion.
Ultrahigh Specific Strength by Bayesian Optimization of Carbon Nanolattices
I watched how it works, but it seems the rotation is just an animation and a fake. There are two requests: /flip and /info. When you click mouse button, the /flip request is GET immediately and it returns a result of 1(eagle) or 0. After that the coin animation begins with requests to /info which always returns the same response for no clear reason. After several /info requests the coin eventually stops without receiving any new results.

$ curl https://quantum.orgsoft.org/info

{"status":"ok","message":"Connected to IBM Eagle r3 (127 qubits)","display_name":"Eagle r3 (127 qubits)","alias":"ibm_kyiv","version":"1.20.22","num_qubits":127,"processor":"Eagle r3","url":"https://quantum.ibm.com/services/resources?system=ibm_kyiv"}

$ curl https://quantum.orgsoft.org/flip

1
In any big project your going to have disagreements.

I need to get paid to deal with stuff like that. No one is going to tell me how to write code without writing me a check.

Even at work I have my limits, although now that I'm older I'm much more inclined to just go with the flow. But if I'm not getting paid what's the point.

I do enjoy game jams though. We only need to work together for a weekend. Plus at least in my circle we only care if the code works.
Even as a maths professional (20 years ago), I had trouble programming the same abstract algorithms to be fast and generally usable. It is ... non-intuitive for me.

That is why I always admired work of people like Peter Montgomery or Donald Knuth.
No. The person who quit upstream kernel work is Marcan, the head of the Asahi Linux project. The person who developed the kernel driver for M-series GPUs is Lina.
If the ITER timelines stop slipping, we're generating electricity from fusion in 25 years.

If there is a major breakthrough, or one of the 'fusion startups' bears fruit, we're generating electricity in every major city within 10 years.

One must have some hope.
They also only have one type of neighbor. Square grids have 2 neighbor types. Triangular grids have 3.
I have paid special attention to these threads, and I have not seen this. And [flagged] comments don't count: any asshole can create an account and post any ol' bollocks. These posts are not "the community": these are posts "the community" has explicitly flagged and rejected.
Last time I used curb, the cabbie told me that the curb payment wasn’t working and I had to Zelle him, ended up needing to report the driver to Curb to get my money back. Shoulda taken an uber!
The animation reminds me me of https://en.wikipedia.org/wiki/Devs_(TV_series)
As a follower of him on Mastodon this makes me sad. Hector posted a lot of valuable, very informative toots that I learned a lot from.
I know this article is more a buisness case presentation than a full demonstration of the field but the TR also misses some points.

Why remove the refrences in the TR to frama-C, cbmc, etc. from the opinion report? They are easier to adopt than the heavier tooling of coq, etc. I'm always suprised to see those tools ignored or downplayed, when it comes to these discussions. I do agree with the TR's sentiment that we need to improve accessibility and understanding of these tools, but this is not a great showing for that sentiment.

Additionally, both articles miss that compiler modified languages/builds are a path, such as fbounds-safety. They will be part of the solution, and frankly, likely the biggest part at the rate we are going. Eg. current stack defenses for C/C++/Rust, unaddressed in safe language design, are compiler based. The compiler extension path is not particularly different than cheri, which requires a recompile with some modifications, and the goal of both approaches is to allow maintainers to band aid dependencies with minimal effort.

The TR handwaves away the question of the complexity of the development of formal method tools for Rust/Unsafe Rust and C++. Ie. rust really only has two tools at the moment: miri and kani (which is a cbmc wrapper). Heavier tools are in various states of atrophying/development. And C++ support from the c family of formal tools such as frama-C, is mostly experimental. It's not assured, that with the continued language development rate of both languages and the complexity of the analysis, that the tools for these languages will come forth to cover this gap anytime soon.

I do not think the claim in the TR that the current unsafe/safe seperation will result in only requiring formal analysis of the unsafe sections is true, as logical errors, which are normal in safe rust, can cross the boundries to unsafe and cause errors, thus nessecitating whole program analysis to resolve if an unsafe section could result in errors. Perhaps it will decrease the constants, but not the complexity. If rust does further restricts perhaps more of the space could be covered to help create that senario, but the costs might be high in both usability and so on.
Ya, webauthn with hardware requirement would kill it too. Gotta physically touch it. It’ll be gross when someone starts to automate that too.
I disagree. "Slowed decline by 30%" to me means an absolute reduction of 30% in some rate expressed as unit X over unit time, and that's what I thought you meant until another commenter pointed out that it was a relative reduction. IMHO it's not an explicit callout unless you are using the words 'relative' and or 'absolute'
> The blocking of links from HN was 100% about silencing discussion _happening on HN_.

How does blocking HN from linking to a site silence discussion on HN? Because, as you say, "100% of the discussion was happening on HN" which seems to imply that blocking HN from linking didn't actually silence the discussion.

> Both of these mean that if you can't link to Asahi Linux content, it can't be the topic of discussion

You can link to it - you just get the "HN referer" block page just as other people get other block pages (eg. [0], [1]. Haven't noticed people moaning about how those sites are silencing discussion on HN, mind.)

Copy and paste the URL and you can read the link perfectly happily[2].

[0] Much like many of us in Europe get block pages for sites in the US who can't be bothered with GDPR or the cookie law.

[1] Or those of us who aren't subscribed to the various news sites which show a paragraph before putting up a blocker.

[2] Or someone pastes an archive.ph link.
I agree! That said, they won't turn down the money through affiliate systems and resellers either.

The economic incentives, the brand control needs, etc. are important dynamics and I don't think it's all in their court alone. It's a combination of where the market goes (the platforms and systems they prefer) and the capabilities unlocked by those platforms.

With that, this evolution will follow the propagation of agent usage. So we will see a lot more initial adoption of AX principles and patterns from developer tools because the software industry has be the most infiltrated by the rise of agentic workflows. As that expands, the nature of markets and meeting user needs will drive adoption of AX.
They still haven’t properly digitized, curb sucks ass, I had to report a driver to curb when he made me Zelle him because “curb payment wasn’t working”
As opposed to the discussion 2 days ago with 400+ comments:

Ingesting PDFs and why Gemini 2.0 changes everything

https://news.ycombinator.com/item?id=42952605