Wait, I'm getting confused. Is it a truck, or a tube? Are you saying we need an information hyperloop?
What I do know is, eventually we're going to need to install kitten housing in the towers to keep it from getting plugged. Voice data might be able to wiggle through on its own, but everybody knows internet needs kittens.
But that's experience with killing terrestrial organisms. That's what I meant about a narrow view.
That's one difference; a mathematician won't care that the job description is about killing terrestrial organisms to keep them from infecting other planets, instead they'll take the list of words in the job description, list the Latin and Greek roots, and then define their own whole system of what they should really be doing based on a careful study of etymology.
Right, but the actual word is "nexus," and "presence" is just how the media describes it. It means having stores or major offices in most cases.
Also, the rules isn't that you have to collect taxes for sales in a State if you have a nexus there. It is actually at the other end; the State is not allowed to demand that you collect the tax unless you have a nexus there. If there is a requirement, it is up to local State law to say so. Not all States bother, and they don't have the same rules for what is a "nexus."
That is how collecting sales tax actually works. There is no single set of rules, and how many sets of rules you have to follow depends on the laws of every State that you have enough of a presence in for that State's laws to touch you. And in many cases that will actually mean hundreds of additional sets of rules you have to follow depending on the city or county that the buyer is in.
But none of that matters to the context that you replied to; even in tax law, a nexus is defined differently for the purpose of collecting sales tax than it is for collecting income tax! And we were talking about something totally unrelated to taxation, consumer rights. So all the rules are different, and you can't crib an understanding from a completely different area of law. But states don't try as hard to enforce consumer rights as they do to collect taxes, so you'll find even less portability of protections. If you have a protection locally, and they also have it in Washington State, then you could sue them over it. But expect to have to hire lawyers in both your own State and also Washington State, and expect to fight for a year or two in court over venue before you even start negotiating over an actual case.
Oregon, and many other US States, have the same 14 day refund period for most items. There are exclusions.
The thing is, I'm not buying any of it in Oregon. I don't know if when you buy from Amazon, where you legally make the purchase. But when I buy, I'm buying stuff from Washington State, where Amazon is.
Generally, to get local protections you have to buy it from a local retailer. When people talk about Amazon being bad for local retailers, now you know one of the reasons why that matters to some people.
It already works almost the same way; current system is, buyer requests return, seller says no, buyer makes complaint to Amazon, refund approved and the customer is stuck recycling the junk item.
I'd actually rather force them to accept the returned item, but this is at least some sort of progress.
They're Republicans and they can't complete a project that is regulated because they hate hippies so badly, they can't follow a rule. So they try to ignore every rule, and all those attempted shortcuts cost money because the government engineers are going to expect you to have followed the actual rule. Making a nasty joke about hippies and spotted owls is fine to deflect questions in a company meeting, but it doesn't weigh anything at all to an engineer.
I see this all the time with small businesses, too. These utilities are the same situation as a small business, where some boneheaded idiot has complete control of decisions, and so is able to attempt to cut lots of corners; even ones that can't be cut.
Why would anybody want to pay double for lighting just to use this technology?
You may not be able to comprehend numbers or use cases, but perhaps if you studied some Home Economics even you could learn how to compare prices and make basic purchasing decisions.
The standard for refusing a properly submitted extradition request is somewhat more specific than vague "humanitarian concerns." And hilariously, that link doesn't even cite any humanitarian concerns; or any claims of innocence. All it actually contains is some whining about American prison sentences being longer than British ones, and typical media misrepresentation about the maximum sentence possible under actual American sentencing guidelines.
That isn't a big problem, and it isn't something where bureaucrats need to be particularly smart.
This is only about devices sold to the US government; this means that if the government thinks the device you sold them continues to have known security problems, they have a code to write down that means no agency can buy that device from you anymore, until they're happier with your response.
This just gives the government the needed purchasing responsiveness to deal with this, without relying on each purchasing clerk to know which devices are secure are which are not. This way they'll end up with a list.
There are lots and lots of different ways to screw up your water, if you don't manage it well. 1930 the river that runs through my town was colored red and all the resident fish died. People didn't like it, they made rules, the water recovered. Now it is fairly clean and there are lots of fish and wildlife.
Florida has worse problems, like that you're going to be in the ocean in less than 200 years.
lol, no, I'm saying that the future will contain the day where few of these bugs are being found in it. It receives resources from RedHat. Bugs will be fixed. Bugs will be reported. Bugs will be fixed. Bugs will be reported. Bugs will be fixed.
The rate starts out bad, and gets better later. Because RedHat makes money and isn't going away.
You have to install 27 different libraries that don't come with *BSD. Only a small package of code is included. It is all the stuff needed by the other packages that are included. If you're trying to compile something outside of what is included, it is expected that you first compiled the entire list of dependencies.
Basically, all of your software is compiled by the user, other than the basic tools. Welcome to *NIX.
(Often you're going to need a newer version of autotools, too, before you can even really think about trying to compile)
It is true that neckbeards snarl worse than a grue, but they're not capable of physical attacks. They also can't remain outdoors for extended periods of time, so they can't stalk anybody.
The real point that professionals can read between the lines is that this code has been gone over by a gazillion haters already, and a huge number of real and potential bugs have been fixed without having been first used in exploits. This is a huge victory for systemd, and it is a strong sign that is going to be rock solid in the future.
It is the same as when we were talking about bug rates on windows 15+ years ago on here. It is exactly the same. When people focus on a system they will find its bugs. And software starts out with bugs. Any new feature starts out with bugs. And design flaws. And the features that go largely unchanged over time, but receive bugfixes, will be very solid and reliable. It doesn't matter what the starting condition was.
In the 1990s there was a thing called "Matt's Scripts," and while it was very kind and generous of Matt to write these scripts and give them away for free online, the problem was that they all contained huge security flaws. So you use this script so that people can email you from your home page, and now spammers are using your website to send spams in your name. All the scripts had these problems. He was panned all around the world, magazines wrote articles warning people not to use it, etc., etc. But Matt was undeterred. And he understood, spammers are bad. So he just listened to all the complaints, looked at their teardowns of his code, and fixed his code. It took years, really, because each fix introduced new bugs. But he wasn't adding features, he was just fixing bugs, and so even with a high bug rate, his scripts eventually became rock-solid and there were no more open bugs.
Hate cannot destroy bad code, and the virtue of Stubbornness is an absolute shield for hated code.
A central processor, memory, data storage, and at least one external I/O interface (user, network, serial, whatever) combined, will make something a computer. A CPU by itself is just a CPU.
(and yes, a smartphone obviously qualifies as a computer)/pedant mode off
You're an awful pedant, sorry.
First of all, the processor doesn't have to be central. That makes it easier to program, but it is not necessary.
Second, you said memory twice. You don't need multiple memory, you don't have to have auxiliary memory at all.
Third, you don't need "one external I/O interface," you in fact need at least one input, and also at least one output. They don't have to be combined, and in fact they rarely are at the hardware level. Also, "I/O" covers anything that is an input or an output; a read-only interface is still an "I/O interface." If you only have "one external I/O interface" then I can simulate the entire system with a single resistor because all you did is convert electricity to heat. It has to either be bi-directional (rare), or you need at least two.
And you only need the memory if it is a digital computer, to store your digits. An analog computer can often leave that out if it is calculating continuously, and memory is only needed if you want temporal isolation. Digital computing of course requires temporal isolation for the values to have consistent meaning.
Slashdot Mirror
Wait, I'm getting confused. Is it a truck, or a tube? Are you saying we need an information hyperloop?
What I do know is, eventually we're going to need to install kitten housing in the towers to keep it from getting plugged. Voice data might be able to wiggle through on its own, but everybody knows internet needs kittens.
But that's experience with killing terrestrial organisms. That's what I meant about a narrow view.
That's one difference; a mathematician won't care that the job description is about killing terrestrial organisms to keep them from infecting other planets, instead they'll take the list of words in the job description, list the Latin and Greek roots, and then define their own whole system of what they should really be doing based on a careful study of etymology.
As long as you know not to click the link, it won't really matter what the story was.
"Whatever the problem, solve it with fire!"
That's how they do it on the planet Flame.
pewpewpewpewpewpewpewpewpewpewpewpewpew!
Oh no, missed.
Right, but the actual word is "nexus," and "presence" is just how the media describes it. It means having stores or major offices in most cases.
Also, the rules isn't that you have to collect taxes for sales in a State if you have a nexus there. It is actually at the other end; the State is not allowed to demand that you collect the tax unless you have a nexus there. If there is a requirement, it is up to local State law to say so. Not all States bother, and they don't have the same rules for what is a "nexus."
That is how collecting sales tax actually works. There is no single set of rules, and how many sets of rules you have to follow depends on the laws of every State that you have enough of a presence in for that State's laws to touch you. And in many cases that will actually mean hundreds of additional sets of rules you have to follow depending on the city or county that the buyer is in.
But none of that matters to the context that you replied to; even in tax law, a nexus is defined differently for the purpose of collecting sales tax than it is for collecting income tax! And we were talking about something totally unrelated to taxation, consumer rights. So all the rules are different, and you can't crib an understanding from a completely different area of law. But states don't try as hard to enforce consumer rights as they do to collect taxes, so you'll find even less portability of protections. If you have a protection locally, and they also have it in Washington State, then you could sue them over it. But expect to have to hire lawyers in both your own State and also Washington State, and expect to fight for a year or two in court over venue before you even start negotiating over an actual case.
Oregon, and many other US States, have the same 14 day refund period for most items. There are exclusions.
The thing is, I'm not buying any of it in Oregon. I don't know if when you buy from Amazon, where you legally make the purchase. But when I buy, I'm buying stuff from Washington State, where Amazon is.
Generally, to get local protections you have to buy it from a local retailer. When people talk about Amazon being bad for local retailers, now you know one of the reasons why that matters to some people.
It already works almost the same way; current system is, buyer requests return, seller says no, buyer makes complaint to Amazon, refund approved and the customer is stuck recycling the junk item.
I'd actually rather force them to accept the returned item, but this is at least some sort of progress.
You came from the soil, is there anything wrong with putting you back?
Local concentrations often matter.
They're Republicans and they can't complete a project that is regulated because they hate hippies so badly, they can't follow a rule. So they try to ignore every rule, and all those attempted shortcuts cost money because the government engineers are going to expect you to have followed the actual rule. Making a nasty joke about hippies and spotted owls is fine to deflect questions in a company meeting, but it doesn't weigh anything at all to an engineer.
I see this all the time with small businesses, too. These utilities are the same situation as a small business, where some boneheaded idiot has complete control of decisions, and so is able to attempt to cut lots of corners; even ones that can't be cut.
Forget words, you can't even read numbers!
Why would anybody want to pay double for lighting just to use this technology?
You may not be able to comprehend numbers or use cases, but perhaps if you studied some Home Economics even you could learn how to compare prices and make basic purchasing decisions.
The standard for refusing a properly submitted extradition request is somewhat more specific than vague "humanitarian concerns." And hilariously, that link doesn't even cite any humanitarian concerns; or any claims of innocence. All it actually contains is some whining about American prison sentences being longer than British ones, and typical media misrepresentation about the maximum sentence possible under actual American sentencing guidelines.
For example, define "vulnerability".
That isn't a big problem, and it isn't something where bureaucrats need to be particularly smart.
This is only about devices sold to the US government; this means that if the government thinks the device you sold them continues to have known security problems, they have a code to write down that means no agency can buy that device from you anymore, until they're happier with your response.
This just gives the government the needed purchasing responsiveness to deal with this, without relying on each purchasing clerk to know which devices are secure are which are not. This way they'll end up with a list.
This is about devices sold to the US Government, so it has nothing to do with jailbreaking consumer devices.
You could always check that, if you can find a dictionary.
If the only work you can think of that uses software outside of ports is smoking pot, that says a lot about you and nothing about the subject at hand.
If everything they needed is in ports, are you sure they even needed a computer?
There are lots and lots of different ways to screw up your water, if you don't manage it well. 1930 the river that runs through my town was colored red and all the resident fish died. People didn't like it, they made rules, the water recovered. Now it is fairly clean and there are lots of fish and wildlife.
Florida has worse problems, like that you're going to be in the ocean in less than 200 years.
lol, no, I'm saying that the future will contain the day where few of these bugs are being found in it. It receives resources from RedHat. Bugs will be fixed. Bugs will be reported. Bugs will be fixed. Bugs will be reported. Bugs will be fixed.
The rate starts out bad, and gets better later. Because RedHat makes money and isn't going away.
No, this story was about, only apps can app you up the app.
I've used them both and IMO they are exactly the same as a desktop because you're going to have to compile everything anyways.
You have to install 27 different libraries that don't come with *BSD. Only a small package of code is included. It is all the stuff needed by the other packages that are included. If you're trying to compile something outside of what is included, it is expected that you first compiled the entire list of dependencies.
Basically, all of your software is compiled by the user, other than the basic tools. Welcome to *NIX.
(Often you're going to need a newer version of autotools, too, before you can even really think about trying to compile)
It is true that neckbeards snarl worse than a grue, but they're not capable of physical attacks. They also can't remain outdoors for extended periods of time, so they can't stalk anybody.
The real point that professionals can read between the lines is that this code has been gone over by a gazillion haters already, and a huge number of real and potential bugs have been fixed without having been first used in exploits. This is a huge victory for systemd, and it is a strong sign that is going to be rock solid in the future.
It is the same as when we were talking about bug rates on windows 15+ years ago on here. It is exactly the same. When people focus on a system they will find its bugs. And software starts out with bugs. Any new feature starts out with bugs. And design flaws. And the features that go largely unchanged over time, but receive bugfixes, will be very solid and reliable. It doesn't matter what the starting condition was.
In the 1990s there was a thing called "Matt's Scripts," and while it was very kind and generous of Matt to write these scripts and give them away for free online, the problem was that they all contained huge security flaws. So you use this script so that people can email you from your home page, and now spammers are using your website to send spams in your name. All the scripts had these problems. He was panned all around the world, magazines wrote articles warning people not to use it, etc., etc. But Matt was undeterred. And he understood, spammers are bad. So he just listened to all the complaints, looked at their teardowns of his code, and fixed his code. It took years, really, because each fix introduced new bugs. But he wasn't adding features, he was just fixing bugs, and so even with a high bug rate, his scripts eventually became rock-solid and there were no more open bugs.
Hate cannot destroy bad code, and the virtue of Stubbornness is an absolute shield for hated code.
/pedant mode on
A central processor, memory, data storage, and at least one external I/O interface (user, network, serial, whatever) combined, will make something a computer. A CPU by itself is just a CPU.
(and yes, a smartphone obviously qualifies as a computer) /pedant mode off
You're an awful pedant, sorry.
First of all, the processor doesn't have to be central. That makes it easier to program, but it is not necessary.
Second, you said memory twice. You don't need multiple memory, you don't have to have auxiliary memory at all.
Third, you don't need "one external I/O interface," you in fact need at least one input, and also at least one output. They don't have to be combined, and in fact they rarely are at the hardware level. Also, "I/O" covers anything that is an input or an output; a read-only interface is still an "I/O interface." If you only have "one external I/O interface" then I can simulate the entire system with a single resistor because all you did is convert electricity to heat. It has to either be bi-directional (rare), or you need at least two.
And you only need the memory if it is a digital computer, to store your digits. An analog computer can often leave that out if it is calculating continuously, and memory is only needed if you want temporal isolation. Digital computing of course requires temporal isolation for the values to have consistent meaning.