"if they were the last, then a shit provider would be better than no provider."
If they *were* the last provider, no-one else would have a decent connection either, so who would you be talking to?
8168 publicly visible posts • joined 14 Jun 2007
Shits always did lie. In the past, they often got away with it. These days that is increasingly difficult and we get to hear about it.
In the short term, lying is a good strategy. Eventually people catch up, though. In a large society, it can take quite a while for that to happen, but modern communications are shortening that.
"your laws start and end at Dover "
And here was me thinking that they started at Lands End and ended at John o' Groats, and included any internet facing hardware in between. Now I find that the Westminster parliament is actually just Dover Town Council on vacation. Oh well, at least I found out before the elections tomorrow.
Well if you are going to be picky about words, you can't be summonsed to a hearing if you are outside the jurisdiction of the body doing the summonsing.
Personally, I don't see why the politicians (on either side of the pond) don't *prefer* to speak to a lackey who actually knows rather more about how the business is run. Insisting on speaking to the figurehead is a bit like advertising that the session is all form and no substance. A bit like shouting "Hey! Look at us! We're a bunch of vacuous airheads." and expecting respect in return.
"2 - Don't ask the querent why do they want to do that, why would anyone want to do that, then refuse to answer anything at all because it's stupid to want to do that."
This one is in the wrong list. Asking the wrong question is a sufficiently common mistake that pretty much every *good* respondent should be prepared to ask "Why do you think you need to do that?" and every questioner should be prepared to elaborate on the bigger picture of what they are doing. Furthermore, in the interests of community hygiene it is occasionally the case that anyone daft enough to *want* to do X is exactly the worst possible person to tell *how* to do X. Sooner or later, someone *else* will have to maintain (or worse, *use*) this person's code.
Issues of style are, to a lesser extent, covered by this principle. It is *unkind* not to mention to a noob that their current style makes them look like a twat. Using those exact words is, of course, also unkind but we shouldn't shy away from the sentiment. We should just try harder to find kind words.
That seems quite plausible to me. If they've found something that makes a big difference but which doesn't show up under electron microscopy or similar methods, then they might reason that saying nothing at all will give them a couple of years of protection whereas publishing will give the competition ideas that might bear fruit in less time than that and which aren't covered by the patent.
"E.g. to check on the origins of a suspicious email? "
Given the large numbers of people posting here who report that they've pushed complete crap into the WHOIS database and got away with it because there is exactly zero budget for checking user-submitted data, just exactly how do you use the information to check on anything? Particularly when the only thing you know about what you are checking is that is seems suspicious. It's like asking someone "Are you a crook?" and expecting a useful answer.
"Another thing that's totally absent from this discussion of "APIs for legitimate researchers" is the idea of providing an API that will only supply anonymous data."
And on a related topic, an API that can only be used by legitimate researchers?
Blimey! Have Facebook finally implemented RFC 3514?
Alternatively, you could solve this problem the way we've solved it for the last 60 years and write a subroutine.
I mean, you have a vague requirement to do something with reading from a file, so you invoke an AI engine to hand-wave for you? Really? Then, if it turns out that it wasn't quite right, you waffle a bit more until you can't see the problems anymore. Anyone else who had the same vague requirement is presumably left to do their own additional hand-waving, which may or may not produce the same result as your second effort and which may or may not solve the new problem for them.
Whereas, using a subroutine firstly solves a definite problem (viz, what the routine was designed to do) and secondly if you ever discover a flaw in the solution you can "fix the subroutine" and everyone who has used that subroutine to solve that problem can benefit from this fix.
I would hope that in El Reg forums at least, we are familiar with the short-comings of AI and deep learning in particular. Principally, in the currrent context, those short-comings are that we don't know quite what problem has been solved and we don't know quite how it has been solved or indeed quiet whether it has been solved, but it looks pretty on the outside. Trouble is ... these are not properties that you want in software.
"Being in California, if they've got no European offices then what can the EU do to them? They can fine the various registries that do operate here, so maybe ICANN still think they can get away with it?"
Half right. Being in California, they cannot be touched. However, without *any* legal presence in the EU, they can't touch European registries. ICANN are basically dead in the water. The internet will carry on running on empty for a bit and whilst ICANN sob to their friends (they must have some) in the US government, the rest of the world will develop an ICANN-replacement that they can live with.
It's like a Hard Brexit, but for Internet Governance. Enjoy...
"They have to respond by a deadline if they want to bounce it, and they won't. So it will be paid into your account, and not reversible because it isn't a fraudulent transaction."
So any non-fraudulent (ie, you have the balance in your account) movement of funds out of TSB towards some other bank will clear in the usual time, but TSB might end up with an even bigger mess on their hands as a result.
Hmm ... That sounds like something that a lot of TSB customers ought to know.
It is also an established historical fact (because it happened to some Russian bloke) that the occurence of just one event that looks like a nuclear attack is sufficiently implausible that people go and check before hitting the launch button.
"An existential threat is a threat to the existence of humanity, not merely a threat to the existence of Dave."
On that basis, and bearing in mind that we are already far more advanced than any species of dinosaur or trilobite, there have been no existentially threatening events in the last billion years or so. You don't need NASA to tell you that this makes it pretty unlikely that we are about to be hit by one now. You also shouldn't need an economist to tell you that any cost that probably doesn't need to be paid in the next 100 years or so is better deferred until later.
So whilst all this is interesting and fun, it isn't important.
I *have* upgraded to Win10, but like many other people I know, I found that Edge stopped working (early in the New Year) with a number of sites I expect to use and so I reverted to IE because it still works. (Obviously on a machine that isn't supposed to be "as customers see it", I'd have installed a proper browser and wouldn't bother with either of Microsoft's pieces of polished turd.)
Once Edge is finished, I'll give it another whirl.
"....the ones I meet from other countries" ... have already been subjected to some kind of selection process, since they are meeting you. Maybe they are ones who are smart enough to be in jobs that involve foreign postings, or rich enough to enjoy foreign holidays.
"it seems to me that the mental retention of literary allusions, cultural references etc is something older people do."
Well that's almost obvious. We've been around for longer. I know *far* more than I did when I was a teenager, about a huge variety of stuff that I didn't even realise (back then) was a thing that you could know about. Given the time-spans involved, it would be a bit embarrassing if I didn't.
"To be a (eg) biology teacher, you need at least a degree in the subject, preferably a masters or PhD."
Ah yes, but that is "to be a biology teacher". It's not quite the same thing as "to teach biology". For the latter, you only need a degree in something, followed by particularly bad luck when the real biology teacher drops out of the profession in October and everyone in the staff room has to draw lots for the poison chalice that is "covering for the Year 11s until we can hire a replacement".
"My French teacher never once mentioned the passé composé ..."
If you learn French now, the chances are that you'll never learn the Past Historic. (Possibly not even to the extent of knowing that it exists but you haven't been taught about it, which presumably cuts you off from just about any French text that is older than your parents.)
"But I like going round the house and knowing router is 10.0.0.1. Main PC is 10.0.0.2. 2nd PC is 10.0.0.3 and so on. Can't very well do that with IPv6 can I."
You can: https://www.edge-cloud.net/2013/08/07/ipv6-link-local-addresses-as-default-gateway/amp/.
As a bonus, fe80::1 is only 7 characters.
"We have systems that won't even support SMBv2 (issue at the vendor level, not at the OS) level and I consider that an easier nut to crack."
We had that at my workplace. Our attitude was that EITHER we carry on running SMB1 and it is only a matter of time before something like WannaCry tanks all operations for an indefinite period at unspecified cost to the business OR we switch off the shitty hardware. Put that way, the nut almost cracked itself.
"Hey, can we spend lots of money to give you pretty much what you had before?"
It's called maintenance. If you plan ahead, you can spend the time and money when it suits you. If you keep putting it off, you will wake up one morning and find that today is the day and this large figure is the price.
"Who on earth thought that 128-bit addresses was a good idea?"
A fair question, with a fair answer. The short answer is that you aren't supposed to use all 128 bits. The first few (for some variable value of "few") classifies the address type, the next few up to 48, 56 or 64, tells you the "destination network" and the final 64 is enough space to allow devices to assign their own addresses efficiently without fear of conflicts.
In addition to this separation, address allocation protocols are designed so that devices inside such a "destination network" can be easily re-assigned to a different prefix. This makes large-scale re-organisation of the network possible. IOW, IPv6's designers looked at the Balkanisation of the IPv4 address space in the 1990s, saw that by 2010 or so the major interconnects were going to need billions of entries in their routing tables, and decided to design a system that could "repair itself" from that kind of entropy.
The sheer length is mitigated by header compression strategies (in binary formats) and the various conventions for text formats. In any case, nearly all configuration should use DNS names and so almost the only things you need to know the numerical addresses of are your DNS servers and gateways. Those can be assigned hand-chosen addresses of the form "prefix::small-integer". If even that fails, you can ask a local subnet for its nearest host of a given type by using well-known multicast addresses.
In short, the designers of IPv6 were and are network people who grovel over these long addresses for a living and they designed it that way to make their lives easier. It is deeply puzzling that the greatest opposition to IPv6 appears to come from others in a similar line of work who have simply memorised all the arcane warts in IPv4 and are apparently afraid to learn about a much cleaner system.
"No it's not, but if they had just made the first octet a pair, 0-65535, and added an extra octet at the end for local routing (with a default zero if not specified), "
And just HOW the fucketty fuck do you intend to shoe-horn 6 bytes into existing network protocols that have a 4-byte address field? Do you have any idea how many low-level network protocols have literally 4 bytes in which to pass "the address"? It's not all fucking FTP writing them out in plain text until it hits some fucking whitespace.
"I, for example, want to know if two addresses are the same. "
You are weird. No normal user has ever wanted to do this. Come to think of it, neither have I and I'm happily running IPv6 on my network.
"IPv4 addresses (without CIDR) can be understood by humans in their heads. IPv6 ones can't."
Not sure what you mean by understanding an address, but if you are referring to network prefixes I rather suspect that the IPv6 ones are no more numerous or harder to remember than the IPv4 ones. I also rather suspect that you are over-stating the need to understand an address. You aren't the computer. Even if you are a network admin, if you are in any way competent, you won't spend much time grovelling over packets.
"Relying on your politicians to remain intelligent and competent is really not a good method of governing if the past several thousand years of human history has shown us anything."
Relying on your citizens to let bygones be bygones is not a good method of running a legal system either. That's why your legal system explicitly spells out notions like "spent conviction". There has to be a balance and, in this case, NT1 went one way and NT2 went the other, so it clear that there *is* a balance. It is a happy (and instructive) co-incidence that this judge was asked to decide on two cases at the same time and felt able to decide differently.
"its only got those stats because google favours it in its search results."
If I were writing a search engine algorithm, I'd favour WP too. WP is a search engine. Each article is a search query and the citations are the search results. The algorithm used by WP is "Wait for someone who cares about the subject to do the research for you." and whilst this is open to abuse by those who care but should be ignored, it also delivers excellent results for uncontroversial topics. It is a splendid complement to a machine-driven algorithm.
"down to Wikipedia's search optimisation rather than Google"
I think there are three possibilities:
1 WP is just a demonstrably good source of information on a large number of topics and therefore wins in a fair fight against other sites.
2 The actual algorithms that Google (and other search engines) use give preference to WP because the human authors thought it would improve search results.
3 WP uses sneaky techniques to game all the search engines.
Given that the SEO "rules" are in constant flux as Google try to outwit their opponents and given that WP have next to no control over 99% of their site's content, I think (3) is unlikely. (2) is unfair, in the sense that only WP can benefit from a hard-coded rule for their domain, but fair in the sense that Google presumably only wrote the rule because WP is consistently better than the SEO-driven crud that they fight on a daily basis. (1) is clearly fair and IMHO might actually be true as long as you steer clear of politicised topics.
"If Oracle want their trademark, let them have it. And thus, let it die."
This is what Oracle would like and, strangely enough, I find myself in their camp on this occasion.
Start calling it ECMAScript and people stop confusing Java with JS. Publishers get to re-issue old wine in new skins (yes, I know that's the wrong way round) merely by search and replace on all their JS textbooks. Oracle keeps all references to Java-anything to itself. Oracle's lawyers have to find another way of being annoying.
"Finally, it appears this is all controlled at the kernel level. [...]"
You say that as if it were a problem, but at *any* level it is the case that once the malware is running *at that level* it is game over for the defenders. AFAIK, Intel have added no less than three rings below kernel level and each one has been targetted and overcome by malware.
"You're forever a statistic, worth a few pence to Facebook, and a few quid to everyone else who buys data."
Who is "you" in this context? If FB don't actually have a registered user as an anchor, they must be inferring the existence of non-FB people. It is an open question whether that inference is correct. It is entirely possible that some of "you" is distributed amongst your social near neighbours and "you" don't exist within FB's world model as an entity in your own right. Equally it is possible that "you" are distributed amongst several shadows and FB don't realise they are the same person.
Lastly, and with reference to the earlier comment that FB offer to delete all that they know about you if you use a page on their site to "sign in and hit delete", this would only delete what FB know about the person they think you are when you do that. Since we don't all come with UUIDs stamped on our foreheads, that may not be all they know about you and it may be stuff they know about someone else who they've confused with you.
In this public debate, I think there is a real danger that every just believes the claims FB make about their omniscience. These claims are made by FB to sell their services to advertisers. We can't disprove the and FB can't prove them and FB have no incentive to under-estimate their own cleverness. Therefore, it would be wise to assume that they are probably exaggerated.
"You're forever a statistic, worth a few pence to Facebook, and a few quid to everyone else who buys data."
Umm, no. Your data is worth whatever value can actually be extracted from it. That's not the cost.
FB make money from your data by packaging it up and selling it on to someone who thinks that FB have under-valued it. They then either package it up or use it to guide the placement of ads. In the latter case, they are selling ad-placement to a third party who reckon that the second party has under-valued it. And so on, until it reaches someone who doesn't sell it on.
Like a pyramid scheme, the last person in the chain is basically financing everyone else. The question is, does the last person actually get more value out of the product than they paid for it? Maybe. Can they prove that? In the case of advertising, there are so many uncontrolled variables that the answer is certainly "no".
Yes, and being a company that is just basically a big web-site, they *defininitely* know this and so for them to assert otherwise is "barefaced lying because they think their target audience is stupid".
Their target audience, of course, is not the El Reg readership. It might, however, be a bunch of Congress-critters. Perhaps someone should have a word with them. Point out that FB have basically just called them a bunch of stupid fuckwits who can be lied to with impunity.
You never know, something might happen.
"Oh, sorry. It isn't supported on Azure."
Yet. Obviously, the winning cloud provider will have a scheme whereby third-party suppliers to the DoD can pay them lots of cash to make their product lines compatible with the DoD's preferred cloud.
Ten years on, the cloud provider has the additional advantage during the bidding for renewal that almost every third party's products are compatible with their cloud but (quite possibly) not the opposition (or, at least, not demonstrably so). So they get the renewal. Repeat ad infinitum.
Who pays? Well, the successful cloud provider makes a shed-load of dosh from the third party suppliers. Those suppliers pass on the costs (now anonymised) to the DoD, which forks out using tax-payers cash. So, er, I guess it is US tax-payers who pay.
Initially. Of course, the next stage is for it to become a requirement all across NATO.
Free market economics: it's great. Someone ought to tell the US government about it. At the moment, they appear to believe in the magic money tree.