skysight-inc/HackerNews huggingface dataset:
I'm not being clear. The interference appears to be related to how recently you were infected with something else. If lots of people around you are getting COVID, then they aren't getting something else. Once most people are immune to it, they aren't getting infected with it anymore and other viruses can compete again.

> it's still killing at nearly 5x the rate as the flu

The way they define COVID deaths make such numbers incomparable.
That was my understanding too, I don’t understand how this would be seen as dangerous in this context, I’d also view it as a benefit.
debuginfod is infinitely better than nothing, but I think much worse than the binary just pointing to the absolute source path (1). Using debuginfod for this is an example of what I meant by "people standardizing on workarounds" to a problem which I think is more easily solved by "refixing" the binary to the absolute path.

Some issues with debuginfod you won't have with "refixed" binaries:

* If an assert fails, you still don't get an absolute path you can open in an editor in the error message

* This assumes the debug info including the source code was uploaded to the server. This can work for "external releases" but do you want this to happen with every build done by every user? This would be notably slower than refixing the binary. If you don't do this, then for every build you didn't do this for, you still have the problem

* Not all tools consuming DWARF support this. gdb and Valgrind do; does VTune or the sanitizers which emit call stacks with source lines you then want to open in an editor?

* Implementing this reasonably is just much more work than passing 2 flags to gcc and running one post-link pass on every binary coming out of the build system

(1) Well, "much worse" in this specific sense. debuginfod does solve a different problem of distributing debug information to people who have a binary installation without debug info on demand. At this it's infinitely better than refix which doesn't help here at all. However this is not how I'd like to work on my employer's software as a developer.
They didn't add any content, it was a pure removal commit
I've been using Sidebery and this for container specific proxy configuration and it works fine https://addons.mozilla.org/it/firefox/addon/container-proxy/

I had a socks server running in docker that turned Forticlient, the worst corporate vpn solution ever, into socks so then I could use access the internal urls in one container, still have fast internet elsewhere, and not expose my computer's entire network traffic to Forticrap.
Obligatory XKCD: https://xkcd.com/2347/

Also, I'm on the same page with you. Block the malicious actor, continue sipping your coffee.
I meant more in the sense that if you're creating an open source project, especially one with serious security implications, you should be extremely aware that you have a dependency that a single individual can update with minimal oversight. Somewhat idealistic take, maybe, but not something you should just be able to ignore either.
Each project has its own detailed requirements and scenarios, and we cannot demand that each project use same library to implement similar functions
I agree that recovering from VCS is something that never actually happens. Mostly because the code is forgotten.

Still, commented-out code is generally worthless and should be deleted. Unless it is actively being worked on and only commented out to achieve some short-term goal. In which case it should also not be commented out but instead live on a branch.

Occasionally you might have two flows and you're not sure which is best. But in that case keep them in separate functions and one of those will not be used but can still be covered with tests. And all static analysis tools will work on it. Just needs a comment about why this unused code is there.
> Traceability. There's a difference in how easily someone can insert nefarious code without it going through processes that might reveal or stop it.

But both come from the same authors. If you do not trust the tarball because it may have nefarious how would you trust Git to not have nefarious code? The authors have complete control over what goes in Git and what processes might be there.

> Compare...

The grocery store comparison doesn't fit here because grocery stores do not make the things they sell. The equivalent to a grocery store would be the download site (BTW lets not continue with metaphors because IMO instead of making things more clear you are introducing TWO parallel channels to argue about).
If by "source" you mean the project's version controlled repo, it is for a variety of reasons.

One primary one is, sustainability. The build tarballs are kept forever. Try that with a remote repo that could vanish in a mere 10 or 20 years.. or tomorrow!

And tar is the most stable archive format in existence, with at least half a century of use.

note: Companies that care, should ask themselves what do you do, if you have a build system which relies upon externals, and a part of that build goes down?

And you have an urgent fix to PROD required?

Hope you can find all the bits, unvarnished, scattered on dev boxes? Cobble them together and hope they build, while your PROD is currently borked?

Or do you hotpatch PROD?

If your build process breaks due to an external repo going MIA, then you're doing it wrong.
Can I apply if I am based in India and never used Crystal? I believe I will be valuable in the Core ML Team. Looks interesting!
I clicked it in Discord just to get rid of the popup.

Between everything else they're trying I didn't even realize that it was a prank.
Pi Reliability: Reduce writes to your SD card
Cool! This is really helpful.
Let me tell you, vacations are serious things. Makes you live longer, happier, and see places you didn't see before in many cases.

Also, you can do whatever you want on that period of time. Which is marvelous in itself.
SEEKING WORK | REMOTE or India, Jaipur, Gurugram

Working in multiple Time-Zones-US/UK/AUS/NZ and EUR

Technologies: ReactJS, TypeScript, JavaScript, NextJS, NodeJs, Python, Django, gRPC, Full-stack

Freelancer with deep expertise in Frontend and full-stack knowledge. I have build end to end saas applications for clients in privacy-tech, legal-tech fields, looking for new contracts as my current commitments are ending.

Reach out: gnsharma0810@gmail.com or https://www.linkedin.com/in/gnsharma0810/
The path from source code to distributed binary file is known to be a blind spot.

Removing that blind spot is either Harder Than You'd Think or Easier Than You'd Think, depending on your perspective and expectations. You can find some issues listed here:

https://reproducible-builds.org/docs/

Or the homepage of reproducible-builds.org for a general take on the subject. (I am not associated with that website.)
SEEKING WORK | Remote | Worldwide (EU-based) | Lead/Senior iOS Developer

iOS developer with over 14 years of experience developing, releasing and maintaining high quality mobile apps and games (e.g. https://apps.apple.com/app/id1215380527, https://itunes.apple.com/app/id572537866). I can handle a project through its entire lifecycle, keep great communication and make sure we are solving the right problems.

I'm open to flat-race pricing for well-scoped projects.

Tech stack: Expert in iOS, Swift, SwiftUI, UIKit, Objective-C, CI/CD pipelines, Bitrise, Git, GitHub, etc. Proficient with API design, backend, analytics, Crashlytics, JIRA, graphics programming, UX.

LinkedIn: https://www.linkedin.com/in/albertodn/

Contact: albertodenia [at] gmail.com
I don't think Detroit is set up to build small electric cars like the Renault Zoe. It's the perfect city car. I guess the Renault 5 will be similar.
Show HN: Term-Lisp – A Lisp, based on pattern matching and term rewriting
Yes sorry, I didn't realise I'd copied the article link instead of the HN link.
Oops! Sorry.

Maybe I'd best stop apologising before my (thankfully barnyard-acid-resistant) footwear gets covered in it?

It was somewhere west, that country in a land of import yew,
That they formed an institution called the Sa-andgroper U.
They were long and wiry natives of the rugged beach abode,
And the robot never welded that the Boorloos couldn't code;

> ...a system for automated handling and delivery...

After watching the first bit of that video, I had been about to ask about the load/unload story. Why was the sheep upside down? (I'd think letting it nummle on something during the process might relax it more than being flipped, but I have no clue about small animals)

[having grown up where land and especially labour is expensive, my wife is a fan of "McLeod's Daughters", especially: "I was wondering if you could point me to the ladies?" "Sorry, we don't have any of them around here"]
An open-source tracking GitHub repo traffic history longer than 14 days
Djamo | Software Engineer | Remote (EU / Africa timezone), or Hybrid | Full-time | https://careers.djamo.com/

I'm VP of engineering at Djamo and we're looking for talented people at Djamo. We are building the neobank for 210 millions people in Subsaharan Africa.

Our goal is to build seamless and affordable banking solutions to bring millions of people into financial inclusion, where less than 25% of the population is banked. You can find out more about us on https://djamo.com

Here are our open positions:
* Staff Software Engineer, Mobile
* Staff Software Engineer, Backend

If you're not in the roles but feel you can add something to us, feel free to contact me.

Our stack is simple and scalable: Typescript, Flutter, Postgresql, Redis, Kafka. We run our servers on AWS.

You can directly join me at vianney at djamo.io
Happy Scribe | Product Engineer and ML Engineer Roles, different levels | Barcelona, Spain | Hybrid or 80% On Site (can sponsor VISA)

With a team of just 30 people and no investor funding, we’ve built a transcription and subtitling product used and loved by 300k people monthly. We are 100% bootstrapped and profitable since month 1, and immune from the funding shortages and layoffs that are impacting other companies.

We're hiring Product-focused Full Stack Engineers to help us scale our product, and Machine Learning Engineers to take our AI - at the core of our product - to the next level.

In the next year we want to hire 10 engineers; if you don't see anything that fits now, get in touch anyway. We want to learn about your career goals so we can reach out in the future.

This might be a once-in-a-lifetime chance to solve one of the fundamental AI challenges of this decade.

We offer visa sponsorship and relocation packages.

Here is our careers page https://www.happyscribe.com/careers

Here is our product www.happyscribe.com

And here is a blog post from Pau, one of our Software Engineers, about his experience working here https://bit.ly/3y1R6bb

Use this link to apply

Product Engineer: https://jobs.ashbyhq.com/happyscribe.com/cbc6d7f7-156b-4a5e-...
ML Engineer: https://jobs.ashbyhq.com/happyscribe.com/4ad8741a-f007-4b18-...

Compensation info

We are open to considering people from 2+ to 20+ years, which means it's a very wide bracket. We'd start from €50,000 but it could go up to €100,000+ for a very senior engineer. We also offer equity. See our careers page for the full list of benefits and perks.
Yes, but it's slower. Here are the times for running a script that just prints hello.

$ time bun hello.ts
real 0m0.015s
user 0m0.008s
sys 0m0.008s

$ time ts-node hello.ts
real 0m0.727s
user 0m1.534s
sys 0m0.077s
I'm a threat intel analyst and recently started self-learning how to improve my storytelling skills, which is generally lacking in cybersecurity. I've refined my writing skills over the years, starting with Medium, LinkedIn newsletters, and now Substack: https://shorturl.at/jHKLQ
What tooling?

Git is just a filesystem with file versions, anything you can check in a tarball can also be checked in Git. The only thing Git adds is a change history for the contents in the filesystem (a history that can be forged too - Git even has a bunch of commands for that too).

If you cannot trust the authors' tarballs how can you trust their Git repository?
What an exhausting article to read to get to nothing substantive. The only thing I concluded was that shooting yourself in the head or somehow otherwise obliterating your neuronal self is probably the best way to commit suicide.

Here is the paper from the major researcher mentioned in the article:
https://www.pnas.org/doi/full/10.1073/pnas.2216268120
> cleaner energy

Fusion is far from clean and unlikely to ever become economically viable: https://thebulletin.org/2017/04/fusion-reactors-not-what-the...
put it in front of your car and you can end your insurance contract
Interesting part start at 8:35. I think I pasted it in with a timestamp, but obviously not.
It sounds like you have issues with the ultra rich. This is because you can't have ultra rich without the points you mention.

Assume you were to set up solutions to the problems pointed out. The ultra rich would be immediately using their wealth and influence to better their position by working against the guard rails keeping those solutions in place. Why would they not?
It represents a step forward from the 90s for the vast majority of people. E2E in messenger and WhatsApp is still painful for LEO.

The article last week (assuming you're referring to this [1]) involved users consenting for Netflix to see their messages. A user from the 90s could have made the same mistake sharing plaintext emails.

[1] https://news.ycombinator.com/item?id=39858850
IBIS hotel check-in terminal keypad-code leakage
Some IBIS Budget hotels are not staffed 24/4 and use check-in terminals during off-peak hours. The terminals then shows a six-digit code with which you can open the hotel room using a number pad. By playing around with the terminal, we accidentally found out that if you enter the minus sign several times as a booking code, the terminal displays the opening codes of other rooms - in this specific case, this was almost half of all hotel rooms.
A git repo can vanish overnight. Git is often used to snag source, but tarballs are still crafted after even then:

https://news.ycombinator.com/item?id=39903813
I spent a few hours building the smallest kernel that'd boot in Firecracker ( https://blog.davidv.dev/minimizing-linux-boot-times.html ), got it booting in 6ms with network support, which opens up some interesting use-cases.
I'd add a hard limit to the amount of pollution the ultra wealthy are allowed to get away with. You don't need a chopper/plane all the time and for sure that 120m boat is leaving some footprint.
In a controlled environment - where the object to pick up, for example, is always in exactly the same location - you could do that. If there is any variation in the location of the object, you need vision to localize it each time. You need a camera, maybe two, and probably some kind of 3d perception, which is an unsolved problem at the moment (well, not solved in a general way, there are some solutions for specific objects).
Historically, it was done for end-user convenience. Traditionally, each project has two separate sources, one is the actual development repository, strictly for use by developers. The next is the source tarball for end-user installation, pre-generated by developers by preprocessing the source repo - such as autotools script generation, gettext translation file generation, etc. The idea was that the end users were running on many flavor of incompatible Unix systems, so installing the full development tools such as autotools or CVS/SVN could be inconvenient. To avoid those troubles, developers pre-generate tarballs with necessary installation scripts such as ./configure for user-friendliness - so source tarballs are installers in a sense, at the middle way between actual source and pre-complied binary. On the other hand, because these scripts are machine-generated and are extremely sensitive to small chances to Makefiles, they should not pollute the canonical source tree, so they're not included in the source repository. Occasionally, under the strict Cathedral style of software development, the canonical source tree may even be private under exclusive access by the core team, end users only have access to release tarballs.

Nowadays, the repo-tarball split is largely unnecessary, but the practice remains. The xz incident became a wake-up call that the Reproducible Build movement focused on binary reproducibility, but have so far ignored tarball reproducibility. Hopefully, this problem will be addressed by the community in the future.
I was always surprised that Perforce didn't have anything for open source, Git is basically eating their lunch because monorepo's suck so much with git; so people do things in a more fragmented and git-friendly way.

Not that I really want to see a proprietary product succeed, but it's somewhat surprising that:

A) We don't have anything better

B) Perforce isn't trying to gain adoption by giving its software for free to distro maintainers

C) People keep coming up with different paradigms that attempt to solve problems monorepos solve inherently.
April fool aside, what I really want is a Debian git monorepo of submodules, where each submodule points to the upstream git repository.
So this is a random person post on X, with no facts or elements or even anything whatsoever beside describing itself as "contrarian truth" which is up there with "I know I will get downvoted for saying this" in the things you say when you can't handle anyone not blindly agreeing with you.

Why exactly is this shared? This has zero net value.
as if Justice Thomas hasn't had a completely consistent judicial philosophy his entire tenure. but don't let anyone stop you coping
Definitely Harder Than You'd Think and we've known this for a very long time.

https://research.swtch.com/nih
Linear: A design reset (part I)
GNU Make Standard Library v1.2.2 released
> Most of the researchers are specifically in a handful of big labs, most of which in turn are in the USA. As one who has done so, trust me when I say that relocation is harder than it seems on paper.

I think it's a bit short-sighted to assume that the future development of AI models will only come from large corporations or research institutions. At the moment, the training still requires a lot of computing resources and a lot of data - but these are limitations that are not permanent. Since the AI boom that Alex triggered in 2012, the development and optimization of models and training has improved very quickly, to the point that even hackers and enthusiasts can create very good models with a little money. Just because a government heavily regulates AI and possibly bans open weights doesn't mean that people on the fringes of legality will abide by it.
How to enjoy life without school.
Well, how surprised should I be that no prompt response has been forthcoming from the poster?

Here's my original (withheld) comment, prepared right before what I posted above:

I'm sure no expert but I've been known to solder a carbon-film resistor or two hundred, and compared them under laboratory conditions to other kinds of resistors.

IMHO with real deep knowledge of resistors, more to the point could be said with fewer extraneous words.

And the content overall would be more sensible and meaningful.

Either way "delicacy" is not a feature, not positive nor negative, just not remotely related. And the most "colorful" effect that would be widely recognized is the multicolored banding of the components to identify their value according to the standard resistor color codes. The circuit board looks colorful regardless of whether it is operational.

Seems "almost" like the author has no first-hand knowledge nor a native language.

Abecedarian or not.
That'd be the case with any update, not just the one that removes Denuvo though.
'Artificial sun' sets record for time at 100M degrees-advance for nuclear fusion
Bun is run by a little prince
You request it, we make it!

Please open an issue and let's discuss it further. With any luck, we can make it available in just a few weeks.
I wish that half the executive initiatives I've seen ended the same way as this post.
Do you mean if they built from a git hash? The tarball contains "Source code" which is what they are building.
Sample size: 21

For all we know, they removed the subjects off of their highly-processed food and reverted back to Keto (another form of non-highly-processed food diet).

Have they ruled out highly-processed food yet?

I did, and seem better for it. Of course, I am only a sample of 1: YMMV.
I didn't quite understand this post. Seems to be a series of contradicting factoids on banana prices. The writing is a bit too incoherent.
Only when you screw up as a developer do games run below 144 fps on modern hardware. And yet most don't. This isn't a valid argument. Most games do not implement denuvo in a way that performance is magically unaffected
"A load of more failure modes" - which? This has been used for more than a year by more than 1000 developers and there were never complains about corrupted binaries or corrupted debug information (except when for some reason "refixing" didn't actually happen for some of binaries), or build speed issues. This, in a code base producing a binary that crashed debugedit after 30 seconds of processing. So empirically it's fine and I think also fine on theoretical grounds; if you disagree it'd be interesting to hear the details.

Regarding replacing the paths "properly": it's not accidentally quadratic, it's predictably linear but with large constants because there's a lot of data to move and a lot of offsets to update. An example of such a problem (linear complexity, large constants) is the linker. It took more than 40 years for C++ linkers to get fast; mold is the linker that I always said was possible (a very fast one) but that I didn't actually implement. Now it's implemented and it takes 5-10 seconds to link that large binary. This is roughly the speed that you can hope for if you not only postulate the possibility of fast DWARF editing like I used to do with fast linking but actually implement it; this will still be an order of magnitude at least slower than refix but it will match the speed of sed. Of course since we had to wait for more than 40 years for a fast linker and a linker is something nobody can do without and everyone wants to be fast, we will have to wait for more like 400 years for anyone to actually optimize debugedit to that level. And I much prefer the small annoyance of having leading ////// in the file paths to waiting for 400 years for a less buggy and faster debugedit and then waiting 5-10 seconds per rebuild.

I agree that it would have been great if the DWARF format as well the actual DWARF producer made it easier to change path prefixes, and it'd be especially great if it worked with compressed debug sections without having to uncompress and recompress them.
Currently working on refining my storytelling skills (threat intelligence). The goal is to present all the technical findings I come across every now and then in a more relatable manner: https://shorturl.at/dwyNX