For the best experience on desktop, install the Chrome extension to track your reading on news.ycombinator.com
Hacker Newsnew | past | comments | ask | show | jobs | submit | history | bhouston's commentsregister

I have tried this before:

https://www.dolthub.com/

It was a lot of work and had poor performance with a lot of complications. I am not using it in my latest projects as a result.


Can you be more specific about what complications you ran into? As for performance, Dolt is faster overall than MySQL on sysbench now.

https://docs.dolthub.com/sql-reference/benchmarks/latency


I, too, have used it. It works well and is especially great for data sharing.

makes sense. i can see things getting complex very quickly.

seems most versions would be better managed at application level, zfs/btrs snapshots not withstanding.


Will this affect the water-resistance of current iPhones? I thought that was why the batteries are not easily replaceable by users, because of the seals/gaskets.

https://www.youtube.com/watch?v=4dyL6hMZvWQ


Most wristwatches provide much stronger water resistance while still being very user serviceable with a $20 watch tool kit. Whatever the phone makers are peddling are mostly excuses.

Also the latest pixel watch has a new mechanism without glue that has a rubber gasket and screws.

There are multiple watches, cameras, etc., with a lot of physical buttons even, all with replaceable batteries and weather-resistant (or even better, water proof). This is a bad excuse.

water resistance + easily battery exchange for repairs is very viable (AFIK always had been, too.)

like this law isn't about users causally replacing batteries like on very old phones

but about an repair shop easily and without risk of breaking your phone being able to replace it without only holding on your phone for idk. 10 minutes

So that you can just drop by (once they have the replacement parts) wait a moment and have a new battery.

This means in the worst case something like needing to a add a bit of additional seal/wax/glue or similar to improve sealing is very much fully viable (Id the sealing agent is generally buy able.)

It just is something you have to design in from the get to go. And it's easier to not do so at all. And maybe if you obsess if your phone is 1/10mm smaller or not that gets in your way too. And not doing so is more profitable as people will buy successor products more likely, even if just very slightly more likely.

But in general? That really isn't the problem.

Also even if it where the problem. What is better? Having a less waterproof phone, but not needing to buy a new one for another one or two years or having to buy one now?


Galaxy S5 worked quite well. IP67 and a removable battery.

While I'd be perfectly content with an IP67 iPhone with interchangeable battery, the current iPhones are IP68 which is a significant step up in dust/water ingress protection. IP68 devices generally require a sealant, IP67 normally doesn't, making it easier to do a battery hatch etc.

IP68 doesn't require a sealant if you just use enough pressure. Phones are just too thin to screw on the back plate and use a proper gasket. Which is stupid in the first place because most people then go and put a bulky cover on them.

and applying a sealant isn't per-see the problem either

iff

- it's generally commercially available

- and re-applicable after replacement with just generic tools

- and removing the battery doesn't risk breaking your phone due to physical strong binding glue being used as sealant etc.

As a dump example you can design the phone as a sealed unit with the battery department being "outside" the seal. Then have the battery also sealed and apply a bit of "sealant" (wax?, glue?) on the electrical contacts braking the seal on both sides. As the battery and battery compartment back have to only be waterproof and not "rigid" this probably fits "just fine" into most phones (except the most over the top slim ones).

Which is probably more the actual problem. Thinks like phone makers over-obsessing with making phones slimmer on a sub 1mm standard ... and then people anyway putting "thick" cases on the phone to protect it...


I don't have a better source, but this is sort of a sign of the times.

What are the gps coordinates? I want to look it up on Google Maps.

Generally somewhere around here:

https://maps.app.goo.gl/wy1PNDWcvP7h9d4j7?g_st=ic

I notice that this area isn’t fully imaged. Just around the known existing islands.


From the article: “The team will publish the exact position of the island once the naming process is complete”

Wonder if it'll be close enough to Greenland for the US (or others) to put a base on it? ;)

It is located on antarctic waters.

Thanks, misread that. ;)

> What are the gps coordinates?

You mean the latitude and longitude.

There are many ways of calculating a position beyond one particular GNSS system.


Peak HN comment

They did do one agent per code chunk, yes. But key is that their agent had to identify when there was a vulnerability and when there wasn't. This "small model" test only had to label the known positive cases as positive -- which any function that simply returns "true" can do. This whole test setup is annoying because it proves nothing.

Mythos was clear it was one agent per chunk. But this positive confirming results do not actually disprove anytime with Mythos, because it is only one side of the discriminator challenge - you got positives, but we do not know your false positive rate and your false negative rate.

In TFA they talk a fair bit about how different models perform wrt false positives:

“The results show something close to inverse scaling: small, cheap models outperform large frontier ones.”


These results were based on "a trivial snippet from the OWASP benchmark". In the section "caveats and limitations" they state that sonnet 4.6 and opus 4.6 now pass.

And they decided to base the false positive examination on a single snippet of a publicly known benchmark question (that small models are known to be heavily fine tuned for) instead of the real use case of finding actual vulnerabilities across an entire codebase by using a for loop and checking the false positive rate there.

This is disingenuous at best, or even misleading by omission if the second approach _was_ done but not mentioned because it just confirmed that the false positive rate of small models is enormous. Given how all seven small models identified the FreeBSD Bug when pointed to it, and how how 6/7 small models still identified the "bug" even after the patch was applied, that second outcome seems likely...


This is quite misleading.

If you isolate the positive cases and then ask a tool to label them and it labels them all positive, doesn't prove anything. This is a one-sided test and it is really easy to write a tool that passes it -- just return always true!

You need to test your tool on both positive and negative cases and check if it is accurate on both.

If you don't, you could end up with hundreds or thousands of false positives when using this on real-world samples.

The real test is to use it to find new real bugs in the midst of a large code base.



I don't get the point of banning specific pornography niches/fetishes that are otherwise legal.

Are there not much more objectionable fetishes than this one?


> I don't get the point of banning specific pornography niches/fetishes that are otherwise legal.

A typical practice for dictatorships to create a legal system capable of exerting pressure on any opponent.

> Are there not much more objectionable fetishes than this one?

The goal isn't to combat sexual perversions, but to silence anyone the dictatorial regime deems necessary.

You pass a law that's clearly unimplementable, and therefore won't cause much outrage, and then, as expected, the law doesn't work. But when you need to silence someone, a complaint emerges that someone accessed and distributed illegal content (some anonymous on some forum saw their IP-address doing that). In the public consciousness, the violation isn't serious (the law isn't actually implemented), so there's no significant outrage. Meanwhile, you conduct searches of the victim's home, confiscate their computers, laptops, smartphones and other gadgets, and open a criminal case against them.

And then you simply close the case, saying, "Yeah, nothing illegal was found, we are sorry". And the victim (and others) will think twice before going against the dictatorial regime next time. Typical practice, all dictatorships do it


This exactly. I don’t believe the government should be censoring porn, but I have a really hard time arguing that principle against studies that suggest it is normalizing choking and slapping women among the young men exposed to it. Why is this roleplay fetish the beachhead and not something like that?

That's an odd perspective. I have heard of young women demanding to be choked and slapped (with their partners acquiescing) far far more than young men instigating the behaviour.

https://www.theguardian.com/lifeandstyle/2025/jul/07/no-safe...

> Now thought to be the second most common cause of stroke in women under 40, it can also lead to difficulty swallowing, incontinence, seizures, memory problems, depression, anxiety and miscarriage.

Looks like they are going after that too though.


Not that have reached the top twenty in prevalence at major sites, no. Incest porn has grown (in concert with the typical move-out age increasing due to economic pressures*) from a long-tail niche decades ago to, looking through a certain United States site’s category list today, being approximately 4x as prevalent by quantity than category ‘British’ and 2-10x more prevalent than most other categories. I would imagine that British leaders are particularly hostile to that U.S. cultural export (and we are a, if not the, top exporter in that industry!) for various reasons beyond simple disinterest in it. Monarchies tend to disfavor that which diminishes their ‘above’ness relative to commoners, and export of this now-widespread U.S. fetish into British society certainly could be estimated to have that diminishing effect by British leaders.

* For anyone looking for a controversial Econ/Psy dual-major thesis topic, inflation-adjusted wage and job losses for teens reaching their age of maturity resulted in the ‘moving out’ age spiking, which combined with known U.S. repressionist tendencies, resulted in a corresponding spike in the incest fetish export trade. (psych sidebar about how fantasies serve as an escape valve for being trapped in one's circumstances). (citations needed)


If you really want to know, see the 215 page report commissioned by the UK governments Independent Pornography Review

https://www.gov.uk/government/publications/creating-a-safer-...


I'm guessing that incest porn is apparently so popular in the US that it's made finding anything that isn't incest porn on US porn sites much harder for these perfectly upstanding members of the House of Lords.

Wait, am I still allowed to say upstanding members?


The UK government wants to ban porn entirely. Requiring website users to identify themselves (the age verification thing) is the first step. This is another step.

Yeah, this Ghost Murmur thing doesn't seem to hold water. But I figured I'd post it anyways, maybe someone know more than me about this field.

Also, I agreed that there was a failed raid, I tried to post on it yesterday but got no traction:

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


Magnetocardiography is a thing. The NRO has some insane capabilities, so I wouldn’t immediately discredit the idea that a magnetocardiographic scan of a large area is possible.

It’s important to note that the individual was isolated by miles. And that they knew the time and location of the crash to determine the search radius.

It’s also one of the many tools they can use. So they may have used some combination of methods to reduce the search area and to pinpoint the target’s location. To say that they only used magnetocardiography is probably false.


It is. One of the first magnetocardiographs was of my heart, because I happened to be in the basement when my fellow graduate students were looking for a subject (I’m a theorist and wouldn’t be allowed to actually touch anything). They used a SQUID that cancelled out the Earth’s field and its gradient; the sensor was close to my skin but not touching it.

Earth’s geomagnetic noise fluctuations are on the order of nanoteslas (10^-9 T), which is 18 orders of magnitude above the signal they claim to have pulled out.

It’s below the thermal noise floor of any physical measurement system that obeys thermodynamics. You can’t engineer around it because it’s not an instrumentation problem. The signal is smaller than quantum noise limits at that scale. “AI” filtering doesn’t help when there’s no signal to filter. You can’t computationally recover energy that isn’t there.

This is certainly bullshit of the finest, most grassy and odorous caliber.


What if they have a bunch of prerecorded data for the guys heart, then use a lock in amplifier to see if there is a signal in the noise

https://en.wikipedia.org/wiki/Lock-in_amplifier


It could be real. Or it could be a smokescreen for their remote viewing program. But isn’t the most likely explanation that pilots carry a radio/gps device and that’s how rescue found him?

Background noise is pretty random. A cardiac signal is pretty regular.

Could be like astrophotography. Where you focus long enough that the background noise cancels out.

It aligns with this earlier leak this month:

https://www.washingtonpost.com/national-security/2026/04/01/...


Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search:

HN For You