skysight-inc/HackerNews huggingface dataset:
If you have root, HTTP Toolkit will handle most of that for you - it can detect root via ADB, install systems certs automatically, and install Frida & intercept individual app targets with most cert pinning disabled (frida scripts it uses are here: https://github.com/httptoolkit/frida-interception-and-unpinn...).

No manual setup or config, just click a button and done.

Avoiding in-depth detection is left as an exercise for the reader, although there are a small set of existing countermeasures in there. In practice, there is definitely a very long tail of further cases of increasing complexity, with diminishing returns on automated solutions, but it turns out in practice you can automate quite a long way down that path and cover most normal cases.

Flutter is the one awkward case here I've found that doesn't fully work. Very interested to see if there are generalizable automated solutions there, or if the recent fork announcements mean the slow death of flutter anyway...
> We're a ways away from a hand and arm that dexterous

So you are saying it is not possible to stack LEGO pieces by a remotely controlled arm (with a human operator)?

> That's an AI I'd rather not see though - that's the fun part OF LEGOs

AI is already claiming all the fun tasks like writing poems and drawing kittens ;)
Often when Russia does something that appears foolish to the west, it's because it is for internal propaganda purposes. The west is not the intended audience.
China itself is probably a good example of what will happen. Slang will have to continuously evolve to stay one step ahead of the censors.

Dead -> unalive -> ?
Unless you can propose a proper way to locally represent time where a person is currently present in relation to the position of the sun then no, time zones will never go away. I know time zones suck for us as programmers but it's a practical way to separate different regions that will experience different times of day differently. As long as we have clocks and times with "midnight"s and "noon"s, time zones will exist. I assume once we truly become an interplanetary species and colonise multiple planets, we will begin to use different methods of time since 24 hour/365 day clocks are going to be an Earth only thing but that's for future scientists to decide. There were proposals for daylight savings to go away but that seems to have disappeared into the ether for some reason.
Is AI ready to crawl through all open source and find / fix all the potential security bugs or all bugs for that matter? If so will that become a commercial service or a free service?

Will AI be able to detect bugs and back doors that require multiple pieces of code working together rather than being in a single piece of code? Humans have a hard time with this.

- Hypothetical Example: Authentication bugs in sshd that requires a flaw in systemd which then requires a flaw in udev or nss or PAM or some underlying library ... but looking at each individual library or daemon there are no bugs that a professional penetration testing organization such as the NCC group or Google's Project Zero would find. In other words, will AI soon be able to find more complex bugs in a year than Tavis has found in his career and will they start to compete with one another and start finding all the state sponsored complex bugs and then ultimately be able to create a map that suggests a common set of developers that may need to be notified? Will there be a table that logs where AI found things that professional human penetration testers could not?
Some State did
the ideal scenario is like cancellable io provide by monoio, I write an example of this in the blog: https://github.com/ethe/io-uring-is-not-cancellation-safe/bl... . However, it has lots of limitation, and do not have a perfect way to do this at the moment.
API would be the source level. ABI would be that you can mix the binary program and the binary libcurl library. (Curl is attempting to preserve both)
3D printing buildings without cement
> If someone can buy or place a solar panels/plant and it is economically feasible, then it is.

"then it is" what? economically viable? He still needs 100% backup from other sources, so you have to factor that cost in. Possible? Yeah, it's possible, but that wasn't the question.
That's funny :) To be fair my first programming with with a octal display and keypad on the motorolla 6800 D2 evaluation kit (https://forum.vcfed.org/index.php?threads/mek-6800-d2-comple...) I think it was called. Can't seem to get any hits on that or images though.

Make's you wonder if that's were the D2 in R2D2 came from :)

https://www.retrotechnology.com/restore/6800D2.html
Creating an optimized keyboard layout for the next generation of the Datahand
In that case Greenland is accompanied by their 'sister country' The Faroe Islands, that has a similar status wrt. Denmark and EU.
I don't consider Yosh Wuyts's concept of "halt safety" coherent, meaningful or worth engaging with. It's true that linear types would enable the encoding of additional liveness guarantees that Rust's type system as it exists cannot encode, but this doesn't have anything to do with broken io-uring libraries leaking resources.
> Over 20 years of experience, too, but I quit doing that for work. Nobody really really cares, all they care is about time to market and having features they've sold yesterday to customers being done today.

I don't recognise this.

Or at least, I recognise that it can be that way but not always. In places I've worked, I tend to have worked with teams that care deeply about this. But we're not writing CRUD apps or web systems, or inventory management, or whatever. We're writing trading systems. I absolutely want to be working with code that we can understand in a hurry (and I mean, a real hurry) when things go wrong, and that we can change and/or fix in a hurry.

So some of us really do care.
Here is another (Jupyter based) notebook solution supporting LLaMA models: https://raku.land/zef:antononcube/Jupyter::Chatbook .

Here is a demo movie: https://youtu.be/zVX-SqRfFPA
The fact that we're reading about this means the words are mainstream enough to get banned or at least context analyzed by AI then banned.
Yeah the article is giving what looks like a bad definition:

According to: https://rust-lang.github.io/rfcs/3128-io-safety.html

Rust’s standard library almost provides I/O safety, a guarantee that if one part of a program holds a raw handle privately, other parts cannot access it.

According to the article:

I/O Safety: Ensuring that accepted TCP streams are properly closed without leaking connections.

These are not the same definition.

As I've mentioned several times [1], in Rust, the word "safety" is being abused to the point of causing confusion, and it looks like this is another instance of that.

[1] https://news.ycombinator.com/item?id=31726723
Flatcar accepted into CNCF at incubating level
No, ORMs abstract away the relational database and present it as if it were some kind of object database. Needing to map query results to structs is just incidental, and is completely missing the point of an ORM.

If copying query results to a list of structs is enough to qualify as an ORM, then the term is so generic as to be entirely useless.
I have a colleague that did it also, moving parts of code and « writing » code quickly with copilot. Because it’s easier to overlook LLM updates he riddled the code with bugs. Subtle things that we undercover later, now that he’s gone.
When you write everything yourself you are more keen to think deeply about changes.
I read today that Google has 25% of their code written by AI. They have an history of trashing huge projects and the quality of their services is getting worse over time. Maybe the industry is going to move to « let’s trash the codebase and ask cGPT 8 to write everything with this new framework »… OP said he’s talking to AI like guiding an other dev. Isn’t he afraid that he will loose the ability to think about solutions for himself ? That’s a trained part of the brain that we can « loose » no ?
Let's have some sympathy, he probably gets advice from gpt and we know it's not that great with numbers yet.
https://archive.is/hyF0u
Voyager is something that I keep thinking every time I see people talking about what great things musk/spacex are doing with their fail often/fail fast approach.

I do get the value of iterating quickly towards a solution but that does not invalidate the conservative engineering approach other people have to take to build something much more stable/reliable where they have to be very cautious and can't just break things until you have a solution.
Dog no they don’t lol. My family has been in both ecosystems over the years and by far the iPhones outlast the Android phones they buy both in quality and in updates.
Apple has a pretty generous return policy. I might have to order one to try it.

The ASUS one is pretty interesting and it's only $800.
His annotated Alice in Wonderland is really nice, too.
Then we're in agreement right?
Hello!
I am one of the editors of the Journal of Geek Studies, where the article posted by the OP is from. There is actually another article in our site that discuss the Dogū presence in multiple japanese media, that I recomend the read!
https://jgeekstudies.org/2018/05/19/dogu-from-prehistoric-fi...
Cheers!
Show HN: I built a AI agent that can help you to talk with you dashboard
My friend was struggling with understanding dashboard insights, so I built an AI agent that helps him talk with his database and get a better understanding of his data. Currently, it not only writes simple queries but also generates end-to-end reports and charts for visual understanding. If there is a problem or an insight that hinders growth, it identifies the issue and reports it instead of simply generating the charts. I built this as my side project. I'm not sure whether people want this solution, so I created a waiting list.
Musk, Bezos, Taylor Swift, Mark Cuban, they all use more carbon as a person than any regular person in the world. Yet it's the people that are demanded to change for climate change, not the wealthy, which I find to be gross hypocrisy.
For how much the standards were referenced, nobody seemed to actually explain the history of the two syntaxes or the reasoning that led to the introduction of a dedicated join statement. If anyone has an article that summarizes the actual history (or even the RFC for introducing the JOIN syntax), I would love to read it.
Most of our emotions are adapted just fine. The things that get in the way are:

- People suppress some of their feelings. Especially people in certain cultures with certain feelings (Californians & Canadians with anger, Australians & Brits with pride, etc). Suppression also means nobody knows how to receive that feeling and they get weird.

- When you suppress certain emotions, they don’t get a chance to “grow up” from a childish expression to an adult expression. Adult anger looks different from child anger.

Ignore things if you want. But I think that’s a lower skill, worse outcome choice in general.
Since io_uring has similar semantics to just about every hardware device ever (e.g. NVMe submission and completion queues), are there any implications of this for Rust in the kernel? Or in SPDK and other user-level I/O frameworks?

Note that I don't know a lot about Rust, and I'm not familiar with the rules for Rust in the kernel, so it's possible that it's either not a problem or the problematic usages violate the kernel coding rules. (although in the latter case it doesn't help with non-kernel frameworks like SPDK)
What is "NCS music"?
Tesla gave out free trials of their self driving upgrade this month. I didn't buy it initially because of the grandiose claims that never seemed to materialize, but I've actually been pretty impressed with the trial. I still don't think it's worth it, but my Model Y has driven itself (with my close supervision of course) to a number of destinations I've keyed into the navigation, without me having to intervene.

There's also lots of times I have had to intervene, but we're closer than we are far, at this point, I think.

So I think your take here is a bit outdated. It was good a couple years ago, though.
> Starting on January 2, 2025, continuity discounts will no longer apply to new organizational subscriptions. ... This update only impacts new licenses purchased after this date. Your existing licenses and packages will retain their current discount rates.

The title sounds worse than it is. They're only removing the continuity discount for new organizational licenses. Organization license renewals, and new and renewed personal licenses should remain unaffected.
Evaluating OpenAI Whisper's Hallucinations on Different Silences
One big thing to watch out for is structs. You can’t add extra members later.

If you have a struct which might grow, don’t actually make it part of the ABI, don’t give users any way to find it’s size, and write functions to create, destroy and query it.
You could also argue that different languages need to go away. Would make everything easier.
Even the “main instance” on bluesky is a cluster of instances; it’s just not exposed in a way that causes the choice issue. And since you have full account portability, if you ever want to change, it’s at least possible.
Doesn't this close the incoming connection, rather than allowing another pending accept to receive it?
Majority of btc nodes run on Tor network
I'm curious:

Suppose I upload some code to GitHub, but I didn't have the authority to share it with anyone at all. And then it was used to train DL models.

How would various jurisdictions handle that? Would any of them force the deletion of all resulting model weights?

And how might the remedies differ based on the kind of data? E.g., copyright vs. trade secret vs. protected medical info vs. military secrets?
Just because you personally are used to a specific type of clock doesn’t mean you can’t imagine a different kind. Submarines use 24 hour clocks and give no hecks about where the sun is.

The solution is to just use UTC. That’s it. That means in NYC you’d get to work at 13:00 and go home at 21:00, which used to be 9am-5pm. That’s it. Your whole transition has been completed. The rest is just what your calendar says. Niece’s recital on Thursday at 19:00, beers with Greg at 23:00 on Friday, etc. It really isn’t hard to imagine.
I mean, it’s only a problem if your design is based on the Future having exclusive ownership of its read buffer, but io\_uring assumes a kind of shared ownership. The “obvious” solution is to encode that ownership model in the design, which implies some kind of cancellation mechanism. C and C++ programs have to do that too.
> Timezones are 19th century thinking. We can do better.

That's why I only use Swatch™ Internet Beats [1] for timekeeping.

Now if you'll excuse me, I have a @583.32 meeting to get to.

[1] https://en.wikipedia.org/wiki/Swatch_Internet_Time
We aren’t questioning your logic, just your reading comprehension in this case :) OP was correctly describing the case where both lights are blocked from view.
Amusingly, I have made three tries to read that book, and kept giving up (getting a little further each time). Partly it was the peculiar sense of aesthetics (e.g., the idea that of course audience would reject color movies) and partly it was the Looney Tunes solar system, which turned out to be something I could accept in a Daffy Duck cartoon but not in a novel.

(But then I'm an astronomer, so I'm primed to get annoyed by random mistakes and carelessness that other people wouldn't notice or care about. I mean, I could kind of momentarily accept the silliness of a habitable solid surface for Uranus, but when you describe the Sun as fainter than Jupiter seen from that location... and then we're told that wheat can't tolerate cold climates the way rice can, and I realize the botany is just as nonsensical as the astronomy...)

I've read most of one of her short-story collections and really liked it, so it's not a generic problem with her writing.
If you move fields around in a struct that is passed between a library and library-consumer it will cause ABI breakage

typedef struct {
char name[50];
int age;
} Person;

vs

typedef struct {
int age;
char name[50];
} Person;

Basically anything that moves bytes around in memory for data structures that are passed around. Of course any API breakage is also an ABI breakage.
If the product is the result of compiling all the open source code out in the wild into a LLM, it can be argued that the derived product, the LLM itself, must follow the licensing requirements of the used source code.

The AI companies don't care much about this. When the time comes, they will open their models or stop using sources that don't meet the appropriate licensing. Their current concern is learning how to build the best models, and win the race to become the dominant AI provider - who cares if they need to use polluted sources to reach their goal. They will fix it later.
Thanks for the feedback! I'm Syrus, from Wasmer. We are currently working on redesigning the homepage so its easier to know what we do and what is our business value. Stay tuned :)
Same set up here - specifically went for OLED to minimize eye strain.
The action comes after years of mounting scientific evidence of the dangers posed by exposure to the chemical dimethyl tetrachloroterephthalate, also known as DCPA or Dacthal.

Great, now do Glyphosate.
Access to energy is a huge part of it. Fuel, to this day, is the easiest way to distribute energy. Industry is still heavily dependent on fossils.

We have not managed to decouple from fossils: heavy industry, shipping, airports, ... There could be a scenario where the energy source is not fossils: but so far it's not in sight.
They also want to get rid of most civil service employees and change their positions to political appointees. Not just the top management positions, but also the people that actually do the day to day work.

E.g., the scientists at the FDA who check the science on safety and effectiveness when processing approvals for new drugs would be political appointees who were vetted for loyalty to the President.
Ray tracing algorithms are quite simple - it’s essentially just checking line intersections with geometry and doing bounce calculations - but a VAST number of rays are needed and a GPU that can do ray tracing needs to keep much more information about the scene geometry in memory. In older generations you wouldn’t store detailed collision information in GPU memory.

A GPU that can handle ray tracing, however, can do a lot of the techniques mentioned in the article (and others) more efficiently without doing what you’d consider full scene ray tracing, because the fundamental path tracing algorithms are very versatile.
It is much harder to do. We all speak the same 24 hour clock and it is not a culturally significant thing. It would be nice if everyone could understand everyone but there is something to be lost by losing languages. There is absolutely nothing to be lost by doing away with timezones.
That's Anti-Amazon behavior. Whatever is going on with their Alibaba-like store is not about finding good products.
> it also makes it easier for compilers/query planners to understand what you're trying to do

Hopefully that's not true. SQL's a declarative language, where you describe what you want and the system figures out how to do it. If you describe exactly the same thing using two different syntaxes, the system shouldn't really do anything different. That just makes the programmer's job harder.
I find LLM’s to be much worse than the junior engineers I work with. I have tried copilot and I always end up disabling it because it’s often wrong and annoying. Just read the docs for the things you are using folks. We don’t need to burn the rainforest for autocomplete.
See my reply to a parallel comment.
I found one in a thrift store and I was so excited until I realized that they wanted $150 for it... even local thrift stores know what they have now
You're right. Looking at my actual code, instead I stored the accept to be yielded next time you call accept and only cancel an accept call if you drop the entire listener object mid-accept.

The solution proposed in this post doesn't work, though: if the accept completes before the SQE for the cancellation is submitted, the FD will still be leaked. io-uring's async cancellation mechanism is just an optimization opportunity and doesn't synchronize anything, so it can't be relied on for correctness here. My library could have submitted a cancellation when the future drops as such an optimization, but couldn't have relied on it to ensure the accept does not complete.
I think this story is that Facebook, for years, has synthesized local or regional organizations based on user “interest”. So there’s nothing organic or spontaneous about The Michigan III%. It almost certainly matches the moderation regex for militia. If someone were to emerge as it leader, well that’s a very interesting result of what appears to be inexpensive surveillance.
I dont usually buy the argument "make this code no longer state the intent that would normally be understood by people who know the programming language, so that it's more readable for people who don't know the programming language"
This kinda thing is so rough, and I can really relate to the questioning of your own sanity part when everyone around you is insisting something works in a particular way that is just factually incorrect.

I got hired into a pretty old small technology company that has over a decade of tech debt, and "how the whole system works" is different depending on which engineer you're talking to. You have to do a context shift to a different engineering reality just to do basic improvements to the system. Lots and lots of built up confusion over years of incremental changes, some of which under pressure no doubt, some well intentioned half-refactors, some almost dead code...imagine your well established corporate morass and then give it a shoestring budget.

It's scrappy in its own way, but the threads where people advocate "don't worry about the tech debt, if the company succeeds they will have the budget to fix it" don't account for the middle ground of not having huge success but having enough success to continue indefinitely. I guess that could mean you could fix the problem over longer time spans, but people do t stay at orgs like this long enough for that to happen, because the job of fixing it is no fun and you can't just throw huge amounts of money at the problem.
No. R2D2 came from film editors' shorthand for a specific piece of film. George Lucas literally got asked by a coworker to "Hand me R2D2", meaning Roll 2 and something-else 2 (I forget what the D was). Lucas did, but also wrote down in his notebook "R2D2. Cool name."
Right, I would assume we'd render multiple 2D images from different angles, and train on that.

But as I'm writing this, why can't we do ML directly with the 3D models...
> Sure, right now the democrat policy is letting migrants in so that they vote for democrats.

> As a Hungarian…

Where are you getting your news from in Hungary that is both reporting on US politics but also is so confused about the basics of how voting in the US works?
Have you ever assembled a Lego set rated 8+ or older? It's not about stacking bricks, it's about applying just enough pressure at exactly the right angle, whilst supporting the assembly in the right places. (Something humans can do remarkably well.)

This is something you can probably program an expensive assembly robot to do if it has to repeat that same procedure thousands of times, but doing it for a whole set human operated? That only makes sense if you haven't got a set of nimble appendices and opposable thumbs, and you have the time to spare and inclination to train with the remotely controlled arm. Having an LLM do it seems fruitless at this point — and why bother?