It did and still does affect heterosexuals in larger numbers than is reported. The problem is that heterosexuals don't really get reported on because lower testing rates and due to the taboo on extramarital affairs. HIV is still not in many standard test and can also lay dormant and never emerge as AIDS.
There are plenty of stds that affect a lot of people yearly, the more sexually free communities tend to be vocal about it, but for many "sleeping around" is still taboo even though a high percentage of people does it with or without a dedicated partner.
Even straight men and women are "sluts". It's just improper to talk about in the US but it doesn't mean it isn't happening.
People that don't dwell in basements have sex, lots of sex with lots of people and although a longer term relationship usually constrains that somewhat, it's not unheard of that people still seek out other mates or even consent to their partners having other partners.
If it were only gay people that were sluts, STDs would've not only just been contained in that community but most STDs would never have the chance to spread, there are just not enough gay people to sustain an epidemic.
It's pretty hard. I only have experience with a metropolitan area network but I suppose home fiber will have a similar cost. For a ~1 mile stretch consider the following:
a) You have to engineer the way the cables will go where they will terminate, what equipment you'll be using, where you'll be tapping off (fiber to each house or to a central unit). b) You have to survey for existing cabling and make sure your installation doesn't encroach upon private property. This could be as easy as dialing a number and getting some plans or as expensive as having a ground radar and doing land surveys. c) You usually have to notify and have permits for digging up. Sometimes the city will take it upon themselves, other times you have to do it. Cost of permits and notices to 100 houses d) Install tubing, lay cables, 8 people, a backhoe and a dump truck will take a good week or two if all the surveys have been done correctly. Off course if you manage to hit a thing with the backhoe, you could be delayed for a day or two. You still have to pay the construction workers. e) Fill the holes and repair side walks, lawns and streets you have broken open. Again, 4-6 people with equipment will take about a week doing that. f) Fielding complaints, law suits, talking to locals why you didn't re-plant their lawn Kentucky Blue Grass etc
And then we haven't talked yet about material cost of lines, piping etc. Our estimates average about $500k/mile with a mix of overhead and underground cabling which isn't expensive since you can easily service 200 houses on a mile stretch. Underground is about 5 times as expensive as overhead. Obviously most of these costs are eventually fully funded by the tax payer (operators pretty much get paid for laying Internet lines) but it's a huge upfront cost and a player like Google won't benefit from grants since it's not really a local political player.
Last week we had a backhoe operator hit a line twice, the second time he literally ran off and went missing for 3 hours without notifying anyone. Obviously he doesn't work there anymore but it caused a delay of 2 days between fixing the line and finding a new licensed operator and bringing them on site.
Please try to link to a site that does not obtrusively ask for money when you want to see the story. I'm sure there are other sites that have the same coverage without ruining my experience.
Why wouldn't it have helped? If Dyn is down, the other provider would still be up and resolve your domain. Amazon stayed up even though they were using Dyn, they also use PowerDNS.
That's not how DNS works, most machines do not directly resolve against a domain's DNS server. They resolve against an ISP's DNS server. An ISP's DNS could easily stream thousands of requests per second to a provider like DynDNS. And usually that's not a problem since in a well-architected DNS system, you have a TTL of 3600-86400 and so your ISP caches requests from all their clients for a specific server.
The problem with the way Twitter 'fixes' issues is to set TTL on the order of seconds and continuously update their DNS with 'working servers'. That means for every request an ISP's DNS gets, it has to immediately request a new DNS entry, because in the cloud, instead of fixing an issue or properly setting up failure models or scaling a service, you just throw more single-sourced hardware at it and let an actual working protocol route around your issues.
If your TTL is high enough, attacking a DNS service wouldn't deny service. The RFC says at least 1800s. Most of these sites have such poor uptime/architecture that their TTL is set to 120 or less.
Please enlighten us. Amazon stayed up thanks to having multiple DNS providers as did many other systems. It was only DynDNS that was out, nothing else.
The main problem was the incompetence of those sites' sysadmins. A TTL under 3600 and all your authoritative nameservers not just with the same provider but on the same platform with the lowest of low, cheap, scum of DNS providers (DynDNS)
Someone tripping over a cable or typing in the wrong command could've caused this. And it's not like Dyn hasn't just unplugged their customers before.
Every device already has that. Luckily for us this ID isn't routable. Your proposal still wouldn't work, we know the IP's these attacks are coming from after all, the problem is getting providers like Verizon or ChinaNet to cooperate.
Dyn seems very quiet about a lot. They and their customers got their ass handed to them. This was pure incompetence on the hands of Dyn and many sites and services.
DNS TTL 3600s or even 86400 (the gold standard back in the day) - because the cloud prides itself on individual machine uptime of 80% or less Single DNS provider - because the cloud prides itself on a single vendor being world-scale just by spreading out
Twitter and co (still) has a TTL of 130s, way lower than RFC 6781 suggests and still has all their name servers at Dyn meaning they haven't learned anything yet.
Motives can only be determined when someone has the full story and is not the only part of legal process either.
Either way, we are talking about things that are part of public record. Just because someone (HRC) doesn't/didn't want them to be part of public record and used a personal account to hide them doesn't mean they shouldn't be.
If HRC wouldn't have cheated; these records could've been obtained by FOIA request and would've happened in a real election or the stonewalling of the FOIA by the administration would've been a big talking point.
From what it reads, it only works when someone cuts the lock with an angle grinder, meaning it may be something that is ignited by heat in order to work, plenty of circumstances where such ignition could be severely delayed (eg. in cold climates). If it's just compressed gas, any sort of metal issues (fatigue, bad welds or rust) or impact could release it (eg. if the biker gets hit by a car).
Terrorism charge is the first thing that springs to mind what you'd get charged with if this gas either intentionally or accidentally gets released in a public area (such as a bike stand).
Is it even legal to use this in any developed country? Any sort of problem (a delay in the mechanism, failure or bystanders) and you got a terrorism charge.
No, just DNS the way it was intended. DNS and all early Internet services were designed to withstand nuclear war and attacks by state-sized actors, actually specifically designed to withstand an attack from Russia.
The problem is the cloud has aggregated all that diversity of everyone running their own services into a handful of really big corporations. Today's just a reminder that any one of those corporations has a significant amount of control if it were a truly bad actor. Imagine Dyn intentionally pointing all the Twitter etc DNS records elsewhere, they did it for their "free" accounts a decade ago just to make them pay.
It seems no one at those big corporations remembers the true history of DynDNS, and how they screwed their customers over. I was surprised they were still in business at all.
Not how the Internet works. Yes that's true on the edges but once you enter into the public Internet, packets could be routed from anywhere to anywhere. The only solution here is to shut down ISPs that are participants but you're talking about getting participation from people that often are themselves involved in the criminal enterprise (that's true for US, Europese, Chinese etc providers) and are profiting from these attacks through overage fees etc.
You wouldn't imagine but even providers like Verizon won't shut off mobile connections because they are often charging their customers per GB consumer. A lot of sleazy hosting provider (the cheap $5/mo.VPS) simply delays intentionally or unintentionally because they don't have the staff to keep up and they are often paid for by the criminals.
A) Avoid a single point of failure (the cause of downtime across all these providers) B) avoid using a single point of failure C) stop using public DNS (or DNS at all) for self-configuration and discovery of your hosted servers D) stop using a single provider for all your stuff
I think EasyDNS has a product but it's as simple as maintaining two sets of DNS records and pointing your domain to two different providers (e.g. powerDns and easydns).
This "attack" could've been easily prevented if they had a single SysAdmin with 15-20y experience in Internet hosting. Having multiple DNS providers used to be standard practice for any medium to large organization.
Imagine dyndns CEO or disgruntled employees simply pulling the plug out. Same result and a reason to avoid SPOF even if you're "in the cloud"
Proper practice is to have multiple DNS providers. All of the sites that are currently 'down' have failed best practice we had 20 years ago. The great "cloud" has finally come down to this: https://xkcd.com/908/
The problem is the 'premium' has been largely debunked in enterprise settings. If you ever get to price out a Dell or HP machine with the same features as a Mac, you're ending up paying more than a Mac. Sure you can get a 5 year old CPU in a brand new Dell and pay $500 but if you care about 3 year hardware support and somewhat modern hardware, you're paying a good chunk more to Dell than to Apple.
Slashdot Mirror
It did and still does affect heterosexuals in larger numbers than is reported. The problem is that heterosexuals don't really get reported on because lower testing rates and due to the taboo on extramarital affairs. HIV is still not in many standard test and can also lay dormant and never emerge as AIDS.
There are plenty of stds that affect a lot of people yearly, the more sexually free communities tend to be vocal about it, but for many "sleeping around" is still taboo even though a high percentage of people does it with or without a dedicated partner.
Even straight men and women are "sluts". It's just improper to talk about in the US but it doesn't mean it isn't happening.
People that don't dwell in basements have sex, lots of sex with lots of people and although a longer term relationship usually constrains that somewhat, it's not unheard of that people still seek out other mates or even consent to their partners having other partners.
If it were only gay people that were sluts, STDs would've not only just been contained in that community but most STDs would never have the chance to spread, there are just not enough gay people to sustain an epidemic.
It's pretty hard. I only have experience with a metropolitan area network but I suppose home fiber will have a similar cost. For a ~1 mile stretch consider the following:
a) You have to engineer the way the cables will go where they will terminate, what equipment you'll be using, where you'll be tapping off (fiber to each house or to a central unit).
b) You have to survey for existing cabling and make sure your installation doesn't encroach upon private property. This could be as easy as dialing a number and getting some plans or as expensive as having a ground radar and doing land surveys.
c) You usually have to notify and have permits for digging up. Sometimes the city will take it upon themselves, other times you have to do it. Cost of permits and notices to 100 houses
d) Install tubing, lay cables, 8 people, a backhoe and a dump truck will take a good week or two if all the surveys have been done correctly. Off course if you manage to hit a thing with the backhoe, you could be delayed for a day or two. You still have to pay the construction workers.
e) Fill the holes and repair side walks, lawns and streets you have broken open. Again, 4-6 people with equipment will take about a week doing that.
f) Fielding complaints, law suits, talking to locals why you didn't re-plant their lawn Kentucky Blue Grass etc
And then we haven't talked yet about material cost of lines, piping etc. Our estimates average about $500k/mile with a mix of overhead and underground cabling which isn't expensive since you can easily service 200 houses on a mile stretch. Underground is about 5 times as expensive as overhead. Obviously most of these costs are eventually fully funded by the tax payer (operators pretty much get paid for laying Internet lines) but it's a huge upfront cost and a player like Google won't benefit from grants since it's not really a local political player.
Last week we had a backhoe operator hit a line twice, the second time he literally ran off and went missing for 3 hours without notifying anyone. Obviously he doesn't work there anymore but it caused a delay of 2 days between fixing the line and finding a new licensed operator and bringing them on site.
Please try to link to a site that does not obtrusively ask for money when you want to see the story. I'm sure there are other sites that have the same coverage without ruining my experience.
There is actually a TTL and an expiration time on DNS requests, I usually set my TTL to 86400 and expire to 2 weeks.
Additionally using multiple name services would help as well and a high TTL gives you time to respond by pointing to other caching nameservers. l
Why wouldn't it have helped? If Dyn is down, the other provider would still be up and resolve your domain. Amazon stayed up even though they were using Dyn, they also use PowerDNS.
That's not how DNS works, most machines do not directly resolve against a domain's DNS server. They resolve against an ISP's DNS server. An ISP's DNS could easily stream thousands of requests per second to a provider like DynDNS. And usually that's not a problem since in a well-architected DNS system, you have a TTL of 3600-86400 and so your ISP caches requests from all their clients for a specific server.
The problem with the way Twitter 'fixes' issues is to set TTL on the order of seconds and continuously update their DNS with 'working servers'. That means for every request an ISP's DNS gets, it has to immediately request a new DNS entry, because in the cloud, instead of fixing an issue or properly setting up failure models or scaling a service, you just throw more single-sourced hardware at it and let an actual working protocol route around your issues.
If your TTL is high enough, attacking a DNS service wouldn't deny service. The RFC says at least 1800s. Most of these sites have such poor uptime/architecture that their TTL is set to 120 or less.
Please enlighten us. Amazon stayed up thanks to having multiple DNS providers as did many other systems. It was only DynDNS that was out, nothing else.
The main problem was the incompetence of those sites' sysadmins. A TTL under 3600 and all your authoritative nameservers not just with the same provider but on the same platform with the lowest of low, cheap, scum of DNS providers (DynDNS)
Someone tripping over a cable or typing in the wrong command could've caused this. And it's not like Dyn hasn't just unplugged their customers before.
Weather in the UK is pretty simple to predict: foggy or rain
Every device already has that. Luckily for us this ID isn't routable. Your proposal still wouldn't work, we know the IP's these attacks are coming from after all, the problem is getting providers like Verizon or ChinaNet to cooperate.
Dyn seems very quiet about a lot. They and their customers got their ass handed to them. This was pure incompetence on the hands of Dyn and many sites and services.
DNS TTL 3600s or even 86400 (the gold standard back in the day) - because the cloud prides itself on individual machine uptime of 80% or less
Single DNS provider - because the cloud prides itself on a single vendor being world-scale just by spreading out
Twitter and co (still) has a TTL of 130s, way lower than RFC 6781 suggests and still has all their name servers at Dyn meaning they haven't learned anything yet.
Motives can only be determined when someone has the full story and is not the only part of legal process either.
Either way, we are talking about things that are part of public record. Just because someone (HRC) doesn't/didn't want them to be part of public record and used a personal account to hide them doesn't mean they shouldn't be.
If HRC wouldn't have cheated; these records could've been obtained by FOIA request and would've happened in a real election or the stonewalling of the FOIA by the administration would've been a big talking point.
From what it reads, it only works when someone cuts the lock with an angle grinder, meaning it may be something that is ignited by heat in order to work, plenty of circumstances where such ignition could be severely delayed (eg. in cold climates). If it's just compressed gas, any sort of metal issues (fatigue, bad welds or rust) or impact could release it (eg. if the biker gets hit by a car).
Terrorism charge is the first thing that springs to mind what you'd get charged with if this gas either intentionally or accidentally gets released in a public area (such as a bike stand).
Yes, except all those big name sites were using exactly that (crappy) provider.
Is it even legal to use this in any developed country? Any sort of problem (a delay in the mechanism, failure or bystanders) and you got a terrorism charge.
No, just DNS the way it was intended. DNS and all early Internet services were designed to withstand nuclear war and attacks by state-sized actors, actually specifically designed to withstand an attack from Russia.
The problem is the cloud has aggregated all that diversity of everyone running their own services into a handful of really big corporations. Today's just a reminder that any one of those corporations has a significant amount of control if it were a truly bad actor. Imagine Dyn intentionally pointing all the Twitter etc DNS records elsewhere, they did it for their "free" accounts a decade ago just to make them pay.
It seems no one at those big corporations remembers the true history of DynDNS, and how they screwed their customers over. I was surprised they were still in business at all.
Not how the Internet works. Yes that's true on the edges but once you enter into the public Internet, packets could be routed from anywhere to anywhere. The only solution here is to shut down ISPs that are participants but you're talking about getting participation from people that often are themselves involved in the criminal enterprise (that's true for US, Europese, Chinese etc providers) and are profiting from these attacks through overage fees etc.
You wouldn't imagine but even providers like Verizon won't shut off mobile connections because they are often charging their customers per GB consumer. A lot of sleazy hosting provider (the cheap $5/mo.VPS) simply delays intentionally or unintentionally because they don't have the staff to keep up and they are often paid for by the criminals.
A) Avoid a single point of failure (the cause of downtime across all these providers)
B) avoid using a single point of failure
C) stop using public DNS (or DNS at all) for self-configuration and discovery of your hosted servers
D) stop using a single provider for all your stuff
I think EasyDNS has a product but it's as simple as maintaining two sets of DNS records and pointing your domain to two different providers (e.g. powerDns and easydns).
This "attack" could've been easily prevented if they had a single SysAdmin with 15-20y experience in Internet hosting. Having multiple DNS providers used to be standard practice for any medium to large organization.
Imagine dyndns CEO or disgruntled employees simply pulling the plug out. Same result and a reason to avoid SPOF even if you're "in the cloud"
Proper practice is to have multiple DNS providers. All of the sites that are currently 'down' have failed best practice we had 20 years ago. The great "cloud" has finally come down to this: https://xkcd.com/908/
PowerBooks had G4's never G5's (sadly) and depending on your usage, the G4/G5's were way more powerful than contemporary Intel's.
If that were true, why did you not simply return it for a replacement under the warranty?
The problem is the 'premium' has been largely debunked in enterprise settings. If you ever get to price out a Dell or HP machine with the same features as a Mac, you're ending up paying more than a Mac. Sure you can get a 5 year old CPU in a brand new Dell and pay $500 but if you care about 3 year hardware support and somewhat modern hardware, you're paying a good chunk more to Dell than to Apple.