Hacker Newsnew | past | comments | ask | show | jobs | submit | dcomp's commentslogin

I think the algorithm is probably incorrect. A number starting with 0 should be treated lexically not numerically. Otherwise you have a situation where img_1_01.jpg and img_01_1.jpg does not have a complete ordering.


That's not the issue.

The issue here is that one camera appends milliseconds to the seconds without a separator, and the other uses a separator.

So of course the ones that include milliseconds look like bigger numbers and get sorted last.

Leading zeros aren't the issue here.


> Otherwise you have a situation where img_1_01.jpg and img_01_1.jpg does not have a complete ordering.

(Good) "natural sort" implementations generally have ways of handling ties like this. It's similar to the problem of case-insensitive sort over case sensitive sets.


It wouldn't be the first time widely-used software sorted numbers by a function that does not produce a total ordering. For example, Excel: https://gregat.es/excel-numeric-order-transitivity/


there's a setting in the developer options called OEM unlock which allows the bootloader to be unlocked

It is still shipped locked. Unlocking wipes the device.

It also doesn't work if your device is carrier locked.


Correct. And you still have to connect the Pixel to the internet before you can unlock the bootloader.


I think the plan is for each GP's prescribing system/appointment system to export enough data that you can just use the NHS app for your needs. i know I can book appointments through it. Obviously doesn't help when the GP is still sifting through paper records. But those are few and far between.


Hm, I'll check that out. If that is the plan then all GP websites should be required to advertise the NHS app instead of the hundreds different private booking companies.


I'm only slightly familiar with the specific features ACPI provides. But isn't the solution the following

For every "feature" provided by the SMM or bios.

Export a UUID ( eg NVME resume implementation1) Have that feature have an enable and disable function. Have each feature have a dependency on each iorange / firmware device it needs access to.

If the kernel know how to implement the feature it can just disable the feature and then as long as it follows the dependency tree and can see nothing else accesses those ranges. It can know that it has exclusive use. If it doesn't have exclusive use it must use the firmware to access those ranges if possible or fall back to no support

If the firmware has a feature without a disable function. The kernel knows it can never access that hardware directly/safely.

You could even have a "lock device" that if you take you know that SMM won't access those io ranges whilst you have the lock.

Obviously this all requires vendor support


This is actually how things are meant to work! Many ACPI features are gated behind a _DSM call that allows the OS to indicate that it has native support for functionality and the firmware should stop touching it itself. It, uh, basically works to the extent that Windows makes use of it.


I thought there was already common terminology for probability of side effects [0]

Very common = greater than 1 in 10

Common = 1 in 100 to 1 in 10

Uncommon [formerly 'less commonly' in BNF publications] = 1 in 1000 to 1 in 100

Rare = 1 in 10 000 to 1 in 1000

Very rare = less than 1 in 10 000

Frequency not known = frequency is not defined by product literature or the side-effect has been reported from post-marketing surveillance data

[0] https://bnf.nice.org.uk/medicines-guidance/adverse-reactions...


Perhaps, but… How many publications have any such guidelines? Make them public? How well do they follow them?


I'm getting office365 nagging me to change the pdf viewer on android after each download in chrome about 15 minutes after the download. Can't find the setting to stop it.


For those wondering, this is a joke from the LTT WAN Show [0]

[0] https://www.youtube.com/live/CSOF8RFrihM?feature=share&t=982...


If you read the description in the link that's exactly there the idea is from!


I've switched to tailscale because their nat busting is actually hard to do "by hand"


That’s sort of the problem, right. Joining two networks is pretty simple, once you do it a few times. I remember when it was mandatory to know how to set up an email server (for more than one user), configure a secure FTP (+ WebDAV for a little while), and probably other things I’ve totally forgetting about. These things were passed down from senior to junior like we pass down how to write Docker images, and set up our ide while those very simple services of yesterday have been eaten up by monopolies. I’m not saying we shouldn’t have services to make our lives easier… I’m saying we should have more of them. I’m not interested in this space, but someone who is should see this company and go “damn, these guys have validated an idea for me. Maybe I can take some of their pie.” Instead, we just give them more money …

Look at email. It’s basically a “lost technology” in that it is nearly impossible to self-host (though there are people out there doing it, there are very few modern guides from zero to production). Same with file sharing and IRC servers.

Maybe I’m just rambling in my “old” age…


Tailscale has several competitors such as ZeroTier and Nebula. There does appear to be a winner-take-all dynamic where being slightly better lets Tailscale take 10x more mindshare than competitors, but I don't see any way around that.


none of those things are analogous to Tailscale having done loads of hard work to automate NAT busting.


Most likely an early disconnection fee during the minimum term. Nearly everyone has a minimum term with virgin media as they only apply promotional discounts if you have a 12,18 or 24 month minimum term and the price shoots up as soon as you roll over onto the monthly.

[1] https://www.virginmedia.com/legal/fibre-optic-services-terms...


This is it exactly; it's kind of understandable given how they want you subscribe for a long time, and most have an exception that a high-enough ranking person can mark (even if it's just "military exception" misused).


Yep, something like that. I would have had to know if and when Im moving a year in advance, which is ridiculous. I mean it's not like I read the fine print on that, so all the better that they had no problem cancelling the fee.


Technically they could force root nameservers (based in the US) to intercept/proxy the whole gtld.

So all except n (netnod (EU)) and i (WIDE (JP))


>So all except n (netnod (EU)) and i (WIDE (JP))

US could just drop the records for those.


No, the US could not do that and there is multiple reasons for it. The root zone is rather special in that operating system semi-hard code the root servers. The operating system also have full control here and the number of name servers at the root zone changes very slowly. Operating systems developed by people not bound by US courts could just ignore it.

The other reason is political. If they were to cut out eu or asia from the list then the risk of a split would increase massively. It would be suicide. If they did that people might even split internet further by splitting iana (Internet Assigned Numbers Authority), in which case a computer in EU would be unable to communicate with an computer in US, and then the concept of a global internet would no longer exist. A split is a exceedingly dangerous concept.


I think the hardcoded IPs are typically only used as hints to initially resolve the root-servers.net domains.


Hints are used by the bind resolver software. It hard code the A -> M root servers and use those to initialize a cache. Naturally bind developers could change this behavior, and in the case that none of the hints works, the current behavior is to use a static compiled list that the software also include.


Not just bind, unbound also. Unbound uses the hardcoded list of IPs to resolve a-m once and build it's cache, the hardcoded IPs are never used again.


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

Search: