That's all well and good, but the CEO sets a certain culture for the company. That culture effects everyone, especially management. If ALL the managers who ever talked to the CEO were replaced, you might be able to change the culture fairly quickly.
> round after round of additional ethics training to the point we can all quote it by heart.
Again that's probably not a bad thing. In some companies, the reaction to ethics training is "yada yada yada yeah whatever". In other organizations, people hear of ethical breaches mentioned in ethics training and their reaction is "holy shit someone actually did that?! That's soon fucked up!"
It's not easy, but fortunately you wouldn't be the first to do it. Others have done it, documented the process, published tips and tricks, and even scripts for it.
MySQL can even federate to different types of RDMS, so you can migrate one table at a time.
>Just getting the data out of the old database and into the new could take hours and hours and hours.
Just like copying files to a new server, or any bulk data transfer, here's a tip to minimize downtime. Copy over the data while the old system is running. It's okay if that takes hours or days; the old system is up. Then copy over the changes that happened in those hours - that'll take minutes. Then shut off the old system and start copying over the changes that occurred in the last few minutes. That'll take maybe 60 seconds to copy over. Then turn on the new system. All the data is synced up with 60 seconds of down time.
Again, it's a tough problem, but it's a *solved* problem. Others have figured out how to to do it and how NOT to do it, and already scripted a lot of it for you.
I don't know if they would expect me to be complicit in criminal acts, but it's clear their corporate culture doesn't have ethics as a top priority.
I'm kind of in an interesting situation. We provide security services to banks and other large businesses. When you see in the news that someone stole $x million from banks, or read about credit card skimmers or whatever, it's my *job* to know how the bad guys do that. In effect, it's my job to know how to steal millions.
One thing I've learned is that crooks don't normally get caught the first time. Or the second or third time. They keep doing it until they eventually get caught. So I've learned that to avoid getting caught, a criminal should do one big theft, once - at most two or three the same day, then stop. Don't keep stealing $12,000 at a time until you get caught. Someone or two big ones and retire.
So here I know *how* to commit crime electronically. I know better than to commit small crimes. So why haven't I stolen $10 million and retired? Only because I'm not a thief. For that reason, I have to make sure I never become a thief. Once, I accidentally took a 25 cent clove of garlic home from the grocery store without paying for it. I had to drive back to the store and pay the 25 cents, because I have to know I'm not a thief, I stick strictly to my moral principles (the best I can). If not, I'm all too likely to try stealing $10 million.
Ps for a larger application or system, it's likely some logic / rules apply to the subject of the application (roughly, the data) while others are application-specific. If there is a chance other applications may someday operate on the same items, it can make sense to split domain logic from application logic.
An example - "students may not receive a diploma until their bill is paid". That's domain logic, it doesn't matter which application is trying to print or mail the diploma. "No more than two copies of the diploma may be printed" is application logic, it's not inherent to the subject entities, but rather applies only to this application.
Would you hardcode user interface code into your database, things like "radio button color=orange" or "textfield length=16", in your database procedures? Of course not. So why in the world would you hardcode SQL code into your application? That's actually just as crazy, though more common.
For most any moderate to large application, it's a good idea to have at least these layers, which communicate through well-defined interfaces:
UI - Design this as though it will be replaced by a web UI, or an app, or something else. Because it probably will be. This layer is only what's visible on the user's screen.
Business logic - this is where you have code that makes sure you can't sell an item you no longer stock, etc. It defines which operations can and can't happen, under which conditions, and in which order - regardless of which UI is trying to do it. Compliance rules are a sub-module here.
AAA - authorization, authentication, and accounting sits close to the business logic layer, controlling who can do what to what.
Data operations (CRUD) - this layer creates, reads, updates, and deletes items from the database. It doesn't have the business logic. Business logic is the layer above. All this layer does is add, remove, update, and delete operations that have *already* been approved and ordered by the logic layer. This is pretty much just simple INSERT, DELETE, etc statements. It can be implemented as stored procedures. As you mentioned, ANSI SQL should be preferred when it makes sense, to avoid being tied to one specific version of one specific RDBMS.
I write SQL code that is specific to a certain vendor - in my stored procedures. Our company rule is that SQL is not allowed in any application, or anything other than a stored procedure, period. If and when we switch to MariaDB. MySQL, or Postgres, I only have to touch my sprocs, and only those where I had a good reason to not use ANSI SQL. I shouldn't have to look at the business rules or application logic, those are separate layers.
For months Wells Fargo has been trying to hire security professionals in my area. No thanks, I'm not interested in working in that environment. I certainly wouldn't be a customer either.
If you're relying on a service someone is providing you for free, and your project is complex, you should have at least two layers or modules in your project. Whatever the big chunks are, business logic , UI, data - whatever your big chunk of work is, separate that from the vendor. Maybe use a maps library that connects your data and logic to Google maps. Then you can switch to any other mapping system by only updating the library.
If you're using a ridiculously expensive solution from a vendor like Oracle, you should have at least two layers or modules in your project. Whatever the big chunks are, business logic , UI, data - whatever your big chunk of work is, separate that from the vendor. Maybe use a database layer that connects your data and logic to Oracle database. Then you can switch to any other database, including a much cheaper one, by only updating the database layer.
No matter how much you're paying, or not paying, it's a mistake to intertwine a lot of your work with any external project. Even if you control both projects, close coupling is normally a bad idea. One project will eventually become "legacy" and you'll want to use the X code with some new Y. So they should interact only through well-defined interfaces, and preferably that interface should be implemented as a distinct interface layer which can be replaced or rewritten.
A case in point is two products we develop at work. The same company runs both. I work on the internal engine, a different team does the UI. It was decided the UI should call upon not only out engine, but other things too. The interface is being changed from SOAP to REST*. Fortunately, we put all of our SOAP stuff in a dedicated SOAP module, so we can switch and not touch 99% of our code. We just replace the SOAP module with a REST module and we're done.
* Not actual REST, as in RESTful. Really we're just putting the parameters in the query string and calling it REST. People who actually understand REST architecture would laugh at us.
The original purpose of systemd was to replace System V init.
They did replace System V init, in a very non-Unix-like way, with a monolithic blob full of binary interfaces, Windows-style.
They then continued to merge in more and more stuff, like a friggin DNS server. Had they stopped before replacing Network Manager with yet another integrated blob, systemd would just be a poorly thought out init system which is the opposite of the UNIX way of doing things. Since they didn't stop, but rather continue to merge more and more unrelated stuff, it's a real problem.
Yeah the http (web) protocol has changed as follows:
1991 0.9 1990 1.0 1997 1.1 2015 2.0
Yeah, every five years or so you need to run "yum update http" in order to support the latest version of the web protocol.
> The data needs to have search requests and transmissions encrypted because it can be packet sniffed
We charge $15 for a TLS cert and $25 to set it up. We suggest getting a 3-year cert, so that comes to $20/year.
The summary says 200,000 visitors per month. Guesstimate 10 pages deep, so 2 million pages. One VM with 1GB RAM running Apache can serve about 150 requests per second of static content. If your joining database tables, get 2-4GB of RAM and call it 100 rps. 100 requests per second is 260 million pages per month, so about 100 times as much as you need.
The $20 VPS would probably be sufficient for only 200,000 visitors, but let's over-engineer by two orders of magnitude and get a managed dedicated server.
At the bottom of the linked article, the agency says it would cost them "hundreds of thousands of dollars" each year to host even a static archive of the site - some text..
If the agency is telling the truth, they don't know how to have a static site hosted for less than hundreds of thousands of dollars, somebody else should be doing it rather than them. That statement indicates they are either incompetent, dishonest, or both.
Those ratings are voluntary, not legally mandated. Web sites can use the exact same MTA rating system and some do. More use a different rating system. A lot of porn sites use the meta tag, but very few non-porn sites do, so that reduces the usefulness.
Unfortunately I don't have time at the moment to explain WHY the system is voluntary and trying to pass a law about it doesn't work - at all. Perhaps someone else will be kind enough to explain that.
There *is* a US law that in effect says that all porn sites must have "2257" at the bottom of the front page, or the next page if the site uses a splash page. That's a pretty effective item to filter on. The Girls Gone Wild guy, Joe Francis, went to jail for not complying with 2257. The law is a bit more than just having that number on the web page, but the practical effect is that porn sites all put a "2257 disclosure" link at the bottom of the page.
You mentioned the most simple possible approaches, a whitelist, or a blacklist. A comprehensive blacklist is actually too large to install client-side, but there are much more advanced approaches available.
You can of course go to Google and get a list of sites covering any topic, such as perhaps "compare ease of learning different server-side programming languages", even though Google has not made such a list. You know there are far more advanced methods for categorizing content than using a pre-generated list, but you seem to have forgotten that for a moment.
You can use both pre-generated data and dynamic algorithms in concert. You can analyze keywords on the fly, of course, and that includes keywords in other sites that link to the site in question, ala: https://www.google.com/search?...
If PBS.org links to a site, it's probably safe. If pornhub links to a site, that's a red flag. If the site consists primarily of image galleries or video galleries, that's worth a couple points. Have a CCBill signup page or Strongbox login page? Probably porn.
If you use your imagination for two or three minutes you can probably think of ways such a service could use several terabytes of data and a cluster of very fast web proxies. AI even. I don't think it'll take you long to think of how three racks of equipment in a datacenter could do this more effectively than a 20MB app installed on a tablet can do it.
Just the other day on Slashdot, people were telling me how absolutely nobody could ever want a kid-safe internet service, because you can just install filtering software on all of your devices.
I'm curious to see what they think of this study. (Also curious if they were never 12 or 13 years old and showing their parents how to use technology.)
> if I own a small company should I be free to ignore the Clean Water Act, dumping lead in the town's water supply, just because I don't employ 50,000 people like Dow Chemical? The entire line of "reasoning" is asinine on its face.
Dumping lead into the water is harmful. Offering an $8 / phone service for seniors who don't have or want a smartphone isn't harmful. Operating a community wireless mesh network isn't harmful.
The government has a strong interest in preventing lead in the water. They don't have a strong interest in preventing a community network from having rules about fair use of the limited bandwidth available. Your right to network with your neighbors is stronger than the government's legitimate interest in telling you that you can't do that.
> I have never watched much "streaming video" on my phones, other than the occasional YouTube video here and there. And usually on WiFi. Why would anyone give a damn what resolution over ""DVD quality" they are watching on a tiny 5 inch screen?
Sam's here. What TV and movies I watch, I watch at home, using a home connection. Are people using their phone as their *only* connection, with no home internet or TV service? That's a pretty inefficient / silly use the technology - fiber or coax has a lot more bandwidth available.
They say "a picture is worth a thousand words" and that's true in terms of bandwidth. Several thousand words equals one high-resolution photo. Video is a million pictures.
Since I don't use / abuse the cellular spectrum to stream HD video all day, I'm glad I don't have to pay for such usage. I pay $30/month for Boost mobile, which meets my needs fine. Occasionally I listen to YouTube in the car (Bluetooth). Sometimes I remember to set it to low-pressure video while I'm listening.
Once in a while I have a couple days of slower internet when I hit my high-speed limit for the month. Figure maybe two or three days every three months - so about 3% of the time. I wouldn't mind paying another $5/month to increase it a bit so I never hit it.
They advertise $35/month, but it's only $30 after you pay your bill on time for a few months. Apparently that's different from most phone companies - the actual price is lower than the advertised price.
Btw sometimes I make fireworks. In fireworks, the bright colors you see are metals on fire. Orange-yellow is iron, green is copper, magnesium burns bright white, etc. Fireworks are lit with a match, how do they burn all of these metals?
It happens that things which catch fire at fairly low temperatures (such as jet fuel) tend to give a fairly low temperature flame. Things that light at higher temperatures (such as iron) give a higher temperature flame. So to get magnesium to burn, I combine something that catches fire from a match with something else that catches fire at a higher temp, but burns hotter. It's stages.
Stage 1 lights easily, and produces 750 degrees. Stage 2 lights at 700 degrees and produces a flame of 1200 degrees. That 1200 degrees can light magnesium, which produces a 4000 degree flame. By having two other materials present, a match can light a fire that burns metals and produces 4000 degrees.
As it happens, a large office building contains many different kinds of materials. Some light easily, some burn at several thousand degrees Fahrenheit.
I forgot something. You may know steel is mostly iron. You may know that 2,00-3,000 years ago people were smelting (and melting) iron.
You may not know they were making steel in China over 2,000 years ago. Molten steel. Do you think they used C4 in China 2,000 years ago. Of course not. Melting steel just isn't all that hard to do. Especially if you don't mind destroying the container it's in. I've melted various metals to liquid and my problem has always been breaking the container. The melting itself isn't too hard.
Thanks for asking. There are a couple of important effects at play, some of which you can try yourself at home, or may have already seen.
You may have seen an aluminum can or glass bottle melt in a campfire or bonfire. Glass melts at about 2,700F. A wood fire can reach temperatures of 3,590F, especially with a structure providing vertical airflow. About 2,000F is more typical for a campfire, but I've seen glass melt in a wood fire and you may have as well. Iron catches on fire, not just burns, at about 1500, and produces rather hot flame (think lighting 4th of July sparklers - they are made of iron).
So there are a lot of things in a building that can burn, and some of them burn quite hot. The elevator and utilities shafts turn the building into a VERY large blast furnace.
Here are a couple things you can definitely try at home. Go to the garage and get your standard 1 pound hammer. Find a chunk of brick or concrete and bring it to a shaded area, or do this in the evening so you can see sparks. Smash the brick or concrete with your 1 pound hammer a few times and notice you get some sparks. Notice the color. Yellow. If we look it up, we see that yellow corresponds to 1100C, or 2012F. You just made 2,000 degrees with your 1 pound hammer. Now imagine a 5 million pound hammer. That's the weight falling at WTC - 5 million pounds. If a 1 pound hammer generates 2,000 degrees, a 5 million pound hammer generates - really fucking hot.
Not too far from the truth, for the freeways. Spokes to drive into town in the morning and drive out toward the suburbs after work. Then three concentric rings to get from the spoke to your neighborhood.
If your able to select your spoke such that when you get to the ring you're on the opposite side of the road from the majority of traffic, it works pretty well.
Rather the opposite. His dissent said that NN laws can and should apply to Comcast, Time Warner, etc. Those companies are big enough, and have enough "market power" that the government's interest in regulating them thoroughly overrides their right to provide whatever services they want.
In contrast, Kavanaugh wrote, community mesh co-ops, etc should be allowed first amendment freedoms and the government's interest isn't as strong because these entities don't have "market power".
You CAN read his writing for yourself rather than making up shit to hate whoever Bill Maher tells you to hate.
As soon as you started talking about a weird road in Dallas, I knew you were going to say Beltline. I thought it was really weird until I thought about the name. Belts go around. It's a loop, which isn't uncommon at all. Beltline is kind of a messed up loop, though.
The good news is - wherever you are in Dallas, if you're lost you can ask anyone how to get to Beltline. Follow Beltline long enough and you'll eventually get to your neighborhood - no matter where your neighborhood is.
Slashdot Mirror
> the CEO ultimately resigned.
That's all well and good, but the CEO sets a certain culture for the company. That culture effects everyone, especially management. If ALL the managers who ever talked to the CEO were replaced, you might be able to change the culture fairly quickly.
> round after round of additional ethics training to the point we can all quote it by heart.
Again that's probably not a bad thing. In some companies, the reaction to ethics training is "yada yada yada yeah whatever". In other organizations, people hear of ethical breaches mentioned in ethics training and their reaction is "holy shit someone actually did that?! That's soon fucked up!"
It's not easy, but fortunately you wouldn't be the first to do it. Others have done it, documented the process, published tips and tricks, and even scripts for it.
MySQL can even federate to different types of RDMS, so you can migrate one table at a time.
>Just getting the data out of the old database and into the new could take hours and hours and hours.
Just like copying files to a new server, or any bulk data transfer, here's a tip to minimize downtime. Copy over the data while the old system is running. It's okay if that takes hours or days; the old system is up. Then copy over the changes that happened in those hours - that'll take minutes. Then shut off the old system and start copying over the changes that occurred in the last few minutes. That'll take maybe 60 seconds to copy over. Then turn on the new system. All the data is synced up with 60 seconds of down time.
Again, it's a tough problem, but it's a *solved* problem. Others have figured out how to to do it and how NOT to do it, and already scripted a lot of it for you.
I don't know if they would expect me to be complicit in criminal acts, but it's clear their corporate culture doesn't have ethics as a top priority.
I'm kind of in an interesting situation. We provide security services to banks and other large businesses. When you see in the news that someone stole $x million from banks, or read about credit card skimmers or whatever, it's my *job* to know how the bad guys do that. In effect, it's my job to know how to steal millions.
One thing I've learned is that crooks don't normally get caught the first time. Or the second or third time. They keep doing it until they eventually get caught. So I've learned that to avoid getting caught, a criminal should do one big theft, once - at most two or three the same day, then stop. Don't keep stealing $12,000 at a time until you get caught. Someone or two big ones and retire.
So here I know *how* to commit crime electronically. I know better than to commit small crimes. So why haven't I stolen $10 million and retired? Only because I'm not a thief. For that reason, I have to make sure I never become a thief. Once, I accidentally took a 25 cent clove of garlic home from the grocery store without paying for it. I had to drive back to the store and pay the 25 cents, because I have to know I'm not a thief, I stick strictly to my moral principles (the best I can). If not, I'm all too likely to try stealing $10 million.
Ps for a larger application or system, it's likely some logic / rules apply to the subject of the application (roughly, the data) while others are application-specific. If there is a chance other applications may someday operate on the same items, it can make sense to split domain logic from application logic.
An example - "students may not receive a diploma until their bill is paid". That's domain logic, it doesn't matter which application is trying to print or mail the diploma. "No more than two copies of the diploma may be printed" is application logic, it's not inherent to the subject entities, but rather applies only to this application.
Would you hardcode user interface code into your database, things like "radio button color=orange" or "textfield length=16", in your database procedures? Of course not. So why in the world would you hardcode SQL code into your application? That's actually just as crazy, though more common.
For most any moderate to large application, it's a good idea to have at least these layers, which communicate through well-defined interfaces:
UI - Design this as though it will be replaced by a web UI, or an app, or something else. Because it probably will be. This layer is only what's visible on the user's screen.
Business logic - this is where you have code that makes sure you can't sell an item you no longer stock, etc. It defines which operations can and can't happen, under which conditions, and in which order - regardless of which UI is trying to do it. Compliance rules are a sub-module here.
AAA - authorization, authentication, and accounting sits close to the business logic layer, controlling who can do what to what.
Data operations (CRUD) - this layer creates, reads, updates, and deletes items from the database. It doesn't have the business logic. Business logic is the layer above. All this layer does is add, remove, update, and delete operations that have *already* been approved and ordered by the logic layer. This is pretty much just simple INSERT, DELETE, etc statements. It can be implemented as stored procedures. As you mentioned, ANSI SQL should be preferred when it makes sense, to avoid being tied to one specific version of one specific RDBMS.
I write SQL code that is specific to a certain vendor - in my stored procedures. Our company rule is that SQL is not allowed in any application, or anything other than a stored procedure, period. If and when we switch to MariaDB. MySQL, or Postgres, I only have to touch my sprocs, and only those where I had a good reason to not use ANSI SQL. I shouldn't have to look at the business rules or application logic, those are separate layers.
For months Wells Fargo has been trying to hire security professionals in my area. No thanks, I'm not interested in working in that environment. I certainly wouldn't be a customer either.
If you're relying on a service someone is providing you for free, and your project is complex, you should have at least two layers or modules in your project. Whatever the big chunks are, business logic , UI, data - whatever your big chunk of work is, separate that from the vendor. Maybe use a maps library that connects your data and logic to Google maps. Then you can switch to any other mapping system by only updating the library.
If you're using a ridiculously expensive solution from a vendor like Oracle, you should have at least two layers or modules in your project. Whatever the big chunks are, business logic , UI, data - whatever your big chunk of work is, separate that from the vendor. Maybe use a database layer that connects your data and logic to Oracle database. Then you can switch to any other database, including a much cheaper one, by only updating the database layer.
No matter how much you're paying, or not paying, it's a mistake to intertwine a lot of your work with any external project. Even if you control both projects, close coupling is normally a bad idea. One project will eventually become "legacy" and you'll want to use the X code with some new Y. So they should interact only through well-defined interfaces, and preferably that interface should be implemented as a distinct interface layer which can be replaced or rewritten.
A case in point is two products we develop at work. The same company runs both. I work on the internal engine, a different team does the UI. It was decided the UI should call upon not only out engine, but other things too. The interface is being changed from SOAP to REST*. Fortunately, we put all of our SOAP stuff in a dedicated SOAP module, so we can switch and not touch 99% of our code. We just replace the SOAP module with a REST module and we're done.
* Not actual REST, as in RESTful. Really we're just putting the parameters in the query string and calling it REST. People who actually understand REST architecture would laugh at us.
The original purpose of systemd was to replace System V init.
They did replace System V init, in a very non-Unix-like way, with a monolithic blob full of binary interfaces, Windows-style.
They then continued to merge in more and more stuff, like a friggin DNS server. Had they stopped before replacing Network Manager with yet another integrated blob, systemd would just be a poorly thought out init system which is the opposite of the UNIX way of doing things. Since they didn't stop, but rather continue to merge more and more unrelated stuff, it's a real problem.
> The problem is that neoliberal free market capitalism isn't exactly delivering flowers and unicorns
Point of fact: It is delivering flowers and unicorns
https://smile.amazon.com/gp/aw...
Would you like next-day delivery, or free three-day delivery?
> . Web protocols and web browsers change.
Yeah the http (web) protocol has changed as follows:
1991 0.9
1990 1.0
1997 1.1
2015 2.0
Yeah, every five years or so you need to run "yum update http" in order to support the latest version of the web protocol.
> The data needs to have search requests and transmissions encrypted because it can be packet sniffed
We charge $15 for a TLS cert and $25 to set it up. We suggest getting a 3-year cert, so that comes to $20/year.
The summary says 200,000 visitors per month. Guesstimate 10 pages deep, so 2 million pages. One VM with 1GB RAM running Apache can serve about 150 requests per second of static content. If your joining database tables, get 2-4GB of RAM and call it 100 rps. 100 requests per second is 260 million pages per month, so about 100 times as much as you need.
> These "small servers" are not free
Right, they are $120 for managed hosting of a dedicated server.
https://www.hostgator.com/dedi...
The $20 VPS would probably be sufficient for only 200,000 visitors, but let's over-engineer by two orders of magnitude and get a managed dedicated server.
At the bottom of the linked article, the agency says it would cost them "hundreds of thousands of dollars" each year to host even a static archive of the site - some text..
If the agency is telling the truth, they don't know how to have a static site hosted for less than hundreds of thousands of dollars, somebody else should be doing it rather than them. That statement indicates they are either incompetent, dishonest, or both.
Those ratings are voluntary, not legally mandated. Web sites can use the exact same MTA rating system and some do. More use a different rating system. A lot of porn sites use the meta tag, but very few non-porn sites do, so that reduces the usefulness.
Unfortunately I don't have time at the moment to explain WHY the system is voluntary and trying to pass a law about it doesn't work - at all. Perhaps someone else will be kind enough to explain that.
There *is* a US law that in effect says that all porn sites must have "2257" at the bottom of the front page, or the next page if the site uses a splash page. That's a pretty effective item to filter on. The Girls Gone Wild guy, Joe Francis, went to jail for not complying with 2257. The law is a bit more than just having that number on the web page, but the practical effect is that porn sites all put a "2257 disclosure" link at the bottom of the page.
You mentioned the most simple possible approaches, a whitelist, or a blacklist. A comprehensive blacklist is actually too large to install client-side, but there are much more advanced approaches available.
You can of course go to Google and get a list of sites covering any topic, such as perhaps "compare ease of learning different server-side programming languages", even though Google has not made such a list. You know there are far more advanced methods for categorizing content than using a pre-generated list, but you seem to have forgotten that for a moment.
You can use both pre-generated data and dynamic algorithms in concert. You can analyze keywords on the fly, of course, and that includes keywords in other sites that link to the site in question, ala:
https://www.google.com/search?...
If PBS.org links to a site, it's probably safe. If pornhub links to a site, that's a red flag. If the site consists primarily of image galleries or video galleries, that's worth a couple points. Have a CCBill signup page or Strongbox login page? Probably porn.
If you use your imagination for two or three minutes you can probably think of ways such a service could use several terabytes of data and a cluster of very fast web proxies. AI even. I don't think it'll take you long to think of how three racks of equipment in a datacenter could do this more effectively than a 20MB app installed on a tablet can do it.
Just the other day on Slashdot, people were telling me how absolutely nobody could ever want a kid-safe internet service, because you can just install filtering software on all of your devices.
I'm curious to see what they think of this study.
(Also curious if they were never 12 or 13 years old and showing their parents how to use technology.)
> Disclosure: My Citroen burned like a fucking candle
Maybe someone was trying to keep the bugs away and got.confused.
https://www.homedepot.com/b/Ou...
> if I own a small company should I be free to ignore the Clean Water Act, dumping lead in the town's water supply, just because I don't employ 50,000 people like Dow Chemical? The entire line of "reasoning" is asinine on its face.
Dumping lead into the water is harmful. Offering an $8 / phone service for seniors who don't have or want a smartphone isn't harmful. Operating a community wireless mesh network isn't harmful.
The government has a strong interest in preventing lead in the water. They don't have a strong interest in preventing a community network from having rules about fair use of the limited bandwidth available. Your right to network with your neighbors is stronger than the government's legitimate interest in telling you that you can't do that.
> I have never watched much "streaming video" on my phones, other than the occasional YouTube video here and there. And usually on WiFi. Why would anyone give a damn what resolution over ""DVD quality" they are watching on a tiny 5 inch screen?
Sam's here. What TV and movies I watch, I watch at home, using a home connection. Are people using their phone as their *only* connection, with no home internet or TV service? That's a pretty inefficient / silly use the technology - fiber or coax has a lot more bandwidth available.
They say "a picture is worth a thousand words" and that's true in terms of bandwidth. Several thousand words equals one high-resolution photo. Video is a million pictures.
Since I don't use / abuse the cellular spectrum to stream HD video all day, I'm glad I don't have to pay for such usage. I pay $30/month for Boost mobile, which meets my needs fine. Occasionally I listen to YouTube in the car (Bluetooth). Sometimes I remember to set it to low-pressure video while I'm listening.
Once in a while I have a couple days of slower internet when I hit my high-speed limit for the month. Figure maybe two or three days every three months - so about 3% of the time. I wouldn't mind paying another $5/month to increase it a bit so I never hit it.
They advertise $35/month, but it's only $30 after you pay your bill on time for a few months. Apparently that's different from most phone companies - the actual price is lower than the advertised price.
They way they are going, the MacBook Pro will soon just be a really big iPad. The Max iPad, or Maxipad.
Btw sometimes I make fireworks. In fireworks, the bright colors you see are metals on fire. Orange-yellow is iron, green is copper, magnesium burns bright white, etc. Fireworks are lit with a match, how do they burn all of these metals?
It happens that things which catch fire at fairly low temperatures (such as jet fuel) tend to give a fairly low temperature flame. Things that light at higher temperatures (such as iron) give a higher temperature flame. So to get magnesium to burn, I combine something that catches fire from a match with something else that catches fire at a higher temp, but burns hotter. It's stages.
Stage 1 lights easily, and produces 750 degrees. Stage 2 lights at 700 degrees and produces a flame of 1200 degrees. That 1200 degrees can light magnesium, which produces a 4000 degree flame. By having two other materials present, a match can light a fire that burns metals and produces 4000 degrees.
As it happens, a large office building contains many different kinds of materials. Some light easily, some burn at several thousand degrees Fahrenheit.
I forgot something. You may know steel is mostly iron.
You may know that 2,00-3,000 years ago people were smelting (and melting) iron.
You may not know they were making steel in China over 2,000 years ago. Molten steel. Do you think they used C4 in China 2,000 years ago. Of course not. Melting steel just isn't all that hard to do. Especially if you don't mind destroying the container it's in. I've melted various metals to liquid and my problem has always been breaking the container. The melting itself isn't too hard.
Thanks for asking. There are a couple of important effects at play, some of which you can try yourself at home, or may have already seen.
You may have seen an aluminum can or glass bottle melt in a campfire or bonfire. Glass melts at about 2,700F. A wood fire can reach temperatures of 3,590F, especially with a structure providing vertical airflow. About 2,000F is more typical for a campfire, but I've seen glass melt in a wood fire and you may have as well. Iron catches on fire, not just burns, at about 1500, and produces rather hot flame (think lighting 4th of July sparklers - they are made of iron).
So there are a lot of things in a building that can burn, and some of them burn quite hot. The elevator and utilities shafts turn the building into a VERY large blast furnace.
Here are a couple things you can definitely try at home. Go to the garage and get your standard 1 pound hammer. Find a chunk of brick or concrete and bring it to a shaded area, or do this in the evening so you can see sparks. Smash the brick or concrete with your 1 pound hammer a few times and notice you get some sparks. Notice the color. Yellow. If we look it up, we see that yellow corresponds to 1100C, or 2012F. You just made 2,000 degrees with your 1 pound hammer. Now imagine a 5 million pound hammer. That's the weight falling at WTC - 5 million pounds. If a 1 pound hammer generates 2,000 degrees, a 5 million pound hammer generates - really fucking hot.
Not too far from the truth, for the freeways. Spokes to drive into town in the morning and drive out toward the suburbs after work. Then three concentric rings to get from the spoke to your neighborhood.
If your able to select your spoke such that when you get to the ring you're on the opposite side of the road from the majority of traffic, it works pretty well.
Rather the opposite. His dissent said that NN laws can and should apply to Comcast, Time Warner, etc. Those companies are big enough, and have enough "market power" that the government's interest in regulating them thoroughly overrides their right to provide whatever services they want.
In contrast, Kavanaugh wrote, community mesh co-ops, etc should be allowed first amendment freedoms and the government's interest isn't as strong because these entities don't have "market power".
You CAN read his writing for yourself rather than making up shit to hate whoever Bill Maher tells you to hate.
There were 23 changes to building codes based on lessons learned from 9-11.
https://www.buildings.com/arti...
https://www.fireengineering.co...
As soon as you started talking about a weird road in Dallas, I knew you were going to say Beltline. I thought it was really weird until I thought about the name. Belts go around. It's a loop, which isn't uncommon at all. Beltline is kind of a messed up loop, though.
The good news is - wherever you are in Dallas, if you're lost you can ask anyone how to get to Beltline. Follow Beltline long enough and you'll eventually get to your neighborhood - no matter where your neighborhood is.