Good reporting
Cheers Liam, an in-depth, and well balanced article.
4275 publicly visible posts • joined 14 Jun 2007
Jon, it doesn't matter how accurate your post is, brexitters will downvote anyone who doesn't claim brexit was amazing. Yes, even at this late stage.
These people think that this: https://www.youtube.com/watch?v=7VxygMpm830 is a documentary.
We used to legally be EU citizens. Now we are not, thanks to brexit.
Your original message I replied to said "It's virtually impossible within the EU to strip someone of their citzenship once granted, unless malice aforethough, fraud, etc. can be demonstrated."
Yet they did strip us of citizenship. Ok, I'm still a UK citizen. but you were talking about the EU. If your comment mentioned the US stripping someones citizenship, no-one would think you were talking about them removing someones Australian citizenship"
And my original reply wasn't being pedantic - I really assumed you thought we had retained our EU citizenship.
"Any person who holds the nationality of an EU country is automatically also an EU citizen. This enables you to enjoy certain additional rights and benefits, including participation in the democratic process."
Oh thanks. I'm glad everything was looked at.
As I said in another post just now, I know some of these would be quite difficult to achieve (like 127.0/16) but my point was just that changing the spec without actually promoting the need for updates would put us in a better position if these things reared their ugly heads again in 20 years time!
That's not the point I was trying to make.
I know loopback is 127/8 , and I know it would be more involved to achieve than the 240/4 change.
My point is that 20 odd years ago, 240/4 was deemed too hard to do. If the spec had changed, without even specifically force-upgrading kit, most stuff would be compatible now.
127.0/16 has been proposed many times. I'm just simply saying if you're going to change the spec, cover all possible use cases. Nothing has to actively promote change to with 127.0 or any of the others, but if in 20 years time, there is a sudden need for it, we'll be in a better position, just like if 20 years ago, the said "define 240/4" as part of the normal address space, and just did nothing else, natural churn would put us in a much better position today.
127.1-255.0.0/16`WTF?
Oh, You mean all of the 127/8 except 127.0/16?
That's a really weird way of writing a network definition, partly because it's a horrible definition...
I dunno. It made sense to me; you understood it; and it was an obvious one-liner rather than your 8 CIDR routes.
I call that a win!
What they should do is cover all the quirky cases, like the 0.0.0.0/8 block, the 127.1-255.0.0/16 blocks and any others.
They don't have to allocate them - just remove their reserved status from the RFC's, so that *IF* this 240/4 plan ever works, they should all be just as clean. The changes to the stack should be simple - the issue is having to change things at all, so may as well clear out ALL the quirks at the same time.
I was just asking a question... Um, did I sleep with your daughter or something?
By the way where are these "people like me", and "my lot"? I'd like to make sure I avoid meeting that unkempt bunch, though fuck knows how the hell you would know what we're like, prick.
Now run along, It was just a question, get over it! Nadella doesn't love you back, you know.
Ahhh, you're too young to remember the free fax service by "the phone company" @ tpc.int !
No. Using .local in as a DNS TLD can cause problems because of precisely the reason you cite - it's officially used by mDNS and as mDNS configurations "own" that TLD, using it in the local DNS will cause issues if you're network also runs mDNS.
For this reason, it's already prohibited from being used in the DNS.
You'll be kicking yourself for this comment when Llanfairpwllgwyngyllgogerychwyrndrobwllllantysiliogogogoch becomes its own country.
Mind you, at 58 letters long, when using the English alphabet, it's already too long to be coded in the Welsh alphabet via punycode, so I propose the limit is raised to 128 characters!
Maybe if you read the link I posted, you'd have your answer?
Also, huh? What do you think the "386" in "386BSD" stands for? It was "unavailable" because of the lawsuits, which was the whole point of my post!
Finally, like many GPL zealots, you don't even know your own license. Companies can quite happily take and use your "free work" if they want to.
It's well established that the legal issues around 386BSD were what thrust Linux into popularity - even Linus has said if it wasn't for the lawsuits, he'd probably never have even created Linux: "In 1993, “If 386BSD had been available when I started on Linux, Linux would probably never had happened.“"
https://klarasystems.com/articles/history-of-freebsd-part-2-bsdi-and-usl-lawsuits/
No, Jumbotron64 is correct.
The Linux you describe is run in a virtual machine that runs on the main chrome OS.
If that counts, then you could also say that Windows runs Linux because of VMWARE, Linux runs FreeBSD because of KVM, FeeeBSD runs Linux because of Bhyve etc..
Next time you startup your chromebook environment, type "uptime". It will not be the same uptime as the host.
In fact, Android Apps are run the same way - the android-tweaked kernel and userland all run in a VM too.
P.S. Not my downvote!
So, the give them a different SKU. That argument is meaningless.
And we're not talking about the difference between a PNG and an MPNG renderer, the OS and the web browser are obviously completely different, as Microsoft found out despite their many protestations.
In fact, attempting to integrate the OS and a browser is a security and reliability disaster, and I'm sure the Apple techs would confirm that this isn't actually the case.
Now, the app store may use HTML rendering, but that would make it a consumer of the browser-component, not tightly coupled to it.
> Like having to buy a full set of bricks for the inside of my wood burner rather than the one that cracked.
a) So what is the technical necessity behind that?
b) 2 of the same thing is not the same as 2 completely different things.
Finally, "everyone else is doing it so why can't we." is fortunately not a valid excuse.
I was surprised to find out that they only stopped printing it in 2019. I'm not sure the quality of their online version is though. Have you tried it? https://business.yell.com/yellow-pages/
I dislike Quora, but it isn't an aggregate site.
<rant>
I deleted my profile there after admin power abuse, After them twice putting me on the naughty step for invalid reasons, I gave them a final warning: "3 strikes, and YOU'RE out." - I'm not providing content to them for free for them to behave all shitty.
I had some quite detailed and well received tutorial posts there too.
Also, their posting rules are so draconian, that you won't find decent discussions there, because everyone is either too scared to be anything other than fluffy - either the non-fluffy posts are deleted, or the non-fluffy posters have left. I'm not even talking about things like swearing or personal abuse, just some of the stuff you need to be allowed to air in a scientific or other forum.. Don't you DARE tell someone they are wrong on a subject. It's not nice, or something.
</rant>
Ignore all of cloudflare? Nice, but I don't see it happening!
Anyway, they must have found a way around things, because I have sites that resolve to multiple addresses (not for nefarious reasons) and google cononicalises them: https://developers.google.com/search/blog/2019/03/how-to-discover-suggest-google-selected