The FCC is currently trying to end 3rd-party wifi router firmware (think Tomato, DD-WRT, OpenWRT, etc.), by requiring manufacturers to build devices that only accept firmware updates signed with the manufacturer's keys.
This is incorrect.
What the FCC is wanting to require is that the SDR chips in these devices only accept radio firmware loads that are signed.
This is because they license the radios, and the radios are licensed as a combination of hardware and software, Loading different firmware into the radio part makes it an unlicensed radio, and permits it to receive signals in prohibited ranges, as well as transmit signals to interfere with the allowed signals in those prohibited ranges, or in bands which require a license for you to transmit.
The FCC does not give a flying crap about the *router* firmware... "(think Tomato, DD-WRT, OpenWRT, etc.)", what they care about is the radio, in the same way they care about the baseband firmware in mobile phones.
So the only thing the FCC wants is to control the air waves (which is what they, as an organization, were created to do).
Several router vendors would prefer you not replace their firmware, and cable companies which are now deploying WiFi hot spots in their service areas using your house and the router they sold you in order to do it, are objecting to you loading your own firmware, since it means they can't offer paid hot spot service out of your house because you happen to have a router that does WiFi from them.
But that's not the FCC, that's the people who want to use *your* equipment in *your* house in order to further *their* business model at the expense of *your* total available bandwidth (particularly, upstream bandwidth).
And this is why we have an environmental problem. If people would fix what they have instead of constantly replacing it, lots of environmental damage caused by manufacturing and transport could be avoided.
But I notice no "Green" group ever mentions this.
You could get the same net effect by the green groups offering repair services that were cheaper than a new purchase, or by the green groups offering to haul the old stuff away, and refurbish it, and sell it to other people so that they *don't* buy new stuff.
Of course, the problem with that is that the equipment is till going to take energy to operate, and the green groups would generally prefer we live in caves or trees, after at least 90% of the human population is "unfortunately" killed off by something.
If there were children, I would have a life insurance for if they are young. If they are older, they would have to fend for themselves and I hope that they have the same attitude as Ãmy sister and myself have towards our parents
One of the best things you can do for a new baby is be prepared to immediately get a permanent or whole life policy for them, which they can later borrow against, and pay themselves back with interest. If you fully fund it, which takes 11-12 years, if you pay in as much as you legally can, they can borrow from it to pay for college, borrow from it for their wedding, borrow from it to buy their first home, and so on.
There are only about 6 companies in the U.S. which offer policies where you can set your own interest rate on cash value funds borrowed (which then becomes a tax deduction, but adds to the cash value on top of the term value.
The best part is you don't have to depend on your kid being a star athlete, magic minority (e.g. "Irish boys named Humphries"), or be a stellar academician (although I expect most of us here would expect that last of our kids...) and get a scholarship, or not go to college except on daddy or mommy's checkbook.
It's more worthwhile than a trust fund, in most cases, because they *have* to pay themselves back.
Uncapped 4G is pretty nifty. However... I had an uncapped 4G hotspot from one vendor, and it worked pretty great. Then Sprint bought them, and capped it. Then I had uncapped 4G from Clear. Sprint has bought them, and they start capping it, too, as of November 1st. I expect anyone who offers this service can expect to be purchased by Sprint (hey, built in exit strategy for your new startup!) so they can cap it, and charge metered rates for the inevitable overage (particularly now that Windows 10 does peer-to-peer sharing of Windows images and updates, and eats tons of upstream in the process).
If the city implements the infrastructure, then it's possible for it to be competitive, assuming the fiber bandwidth is either intentionally constrained, or effectively constrained by number of links into a single upstream at the head end (same thing that tends to make cable slow at "get up in the morning before work" and "people just got home from school/work" times.
Actually, if we keep having 3 cat4 hurricanes churning the Pacific garbage patch, you could easily argue that it's going to be one and the same problem.
Pretty sure that cat5 hurricanes is the minimum...assuming you want a good signal.
It's bound to go up, but to being "wealthy" means $2-4M in investments to get to that after taxes. Depending on how.
Everything after that is either "invest in the investments" or "pay off the house loan against the line of credit".
Any way you look at it, if you do not want to work, or you do not want to work on something other than "facebook++" for some asshole who thinks he has a magic "get rich quick" scheme, you are at a minimum looking at $4M.
Re the last paragraph. That is not entirely true, as Intel appear to be able to integrate new chipsets during the time they are released (but only to next tier manufacture) before the public can buy anything using it.
What kind of "peeing on it" has been done to the Intel drivers to get them integrated ?
Exactly the same kind. It's possible to do for anything, it just takes time.
The reason Intel is able to do this ahead of general release, when other vendors aren't, is that it does not lose them a competitive advantage.
First, there is no issue of another manufacturer producing "pin and register compatible devices", and undercutting Intel, because Intel's graphics are integrated into the CPU; you'd have to build an entire Intel compatible CPU as well, and you'd have to do it competitively in terms of price point.
Second, no one really wants to emulate Intel Integrated Graphics in silicon, since there's really no advantage to doing so, since the chips have inferior performance relative to the competition.
So there's really nothing lost by Intel pre-announcing all of the information needed to make a driver, or even publishing source code for the driver, since doing so will sell more Intel chips, not less. For other GPU vendors, this is simply not the case, and there's no economic value in such pre-disclosure.
"the R9 Fury isn't yet in good shape on the open-source driver"
The card won't be changing to fix this; the driver will have to change to accommodate the card; therefore it is more correct to say "The Open Source driver is not yet in good shape on the R9 Fury". In other words, it's not the hardware's fault that the driver doesn't support it yet.
"AMD's open-source developers haven't yet found the time to implement power management / re-clocking support"
The power management model in Linux is Linux's responsibility, not AMD's. The authors of the Open Source driver are accountable *only* for writing callbacks for the device power management component, and populating the structure. It's my understanding that Linux lacks a uniform model for use by all graphics drivers, in this regard. his is a Linux issue, not an AMD issue.
Also:
In general, in a hardware world, you either NDA people, or the Open Source is going to lag the closed source, period. This is because openly manipulating code related to an unreleased hardware product in a publicly accessible source repository, instead of a privately held repository, is tantamount to preannouncing your hardware to competitors. You might as well have the CEO call a press conference, and then shoot themselves in the head in public.
Open Source projects have a secondary problem in that, even if the driver source was developed entirely by engineers within AMD, and released the same day as the hardware was made available, the Open Source projects aren't going to be happy just integrating the code as is. They will insist on peeing on it to make it smell like themselves, just as cats do with new furniture, and this will take time. You can either have closed source, or you can have it integrated later than the release date, but you can not have both.
I suggest the first code name be "Zurich"; my second choice is "Gringott"... don't tell anyone, we wouldn't want them knowing we were talking about Gnome!
They should have done it under water, if they insisted on Hawaii instead of Antarctica, which would have been a better choice (or at altitude on K2 or Everest, as long as it was a non-permanent installation). There's too much temptation to cheat, there's no real danger, and we already know that curing concrete will eat all your CO2 if you are stupid and don't seal it.
The only good choice fora Hawaii location other than "under water" would be "Inside a large SO2 cloud near a volcano, so that breathing the external atmosphere would get you dead".
I suggest we confuse the primary Uber benefits with the electronic dispatch system, rather than showing up when you've made a commitment to show up, the lower prices Uber charges on average, the cleaner, newer vehicles, ad the pleasant drivers who have to be pleasant because there's a feedback system which loses them referrals, whereas a taxi driver with a medallion can't really be fired without losing the medallion.
It must be the app, right folks? Not all the other things?
So basically I'm responsible, because I didn't write the firmware, and instead it was written by an idiot? Like someone who runs Windows, and is therefore able to turn off Windows Update because it exists in the first place, and could be the very channel which, by means of DNS cache poisoning and/or router compromise and/or BGP poisoning, was the means to infect the thing in the first place?
How about we hold the idiot who thought giving the fridge a routable address via NAT off the local network in the first place, so that they could market specific brands of milk via coupons sent to me when I'm running low on milk, was a good idea, responsible instead?
It's clear you do not understand the position. You need to read about what the job entails, and then decide if you want to accept the offer or not. It's a substantial change in role from your current position. In this case, the Wikipedia article is pretty accurate:
As others have stated, your primary responsibility is specification. To do this, you meet with stakeholders, and do projective business IT strategic planning.
While you can relatively easily negotiate for read only access as a demand from "on high", you should not personally use it. It should be used by your staff, temporary or permanent, for the performance of detailed specification compliance audits and spot checks. This is adequate justification to get management buy-in for this type of access. This type of access is for a role, not for a person. This is one of the reasons it should not be you.
For day to day operations, what you need are dashboards, which measure the degree of compliance with the detailed specification in an ongoing basis. The main purpose of the dashboards are to give you information you can summarize periodically to the executives, and as feedback into your strategy decisions going forward (particularly decisions surround capacity planning and technology adoption).
The purpose of the ability to audit is to ensure that the dashboards are not giving you fudged numbers based on what you want to hear, vs. what IT whats to implement (or what they can implement; you may be asking for the impossible, as a dictator, when you should be viewing the detailed specifications as a negotiation). Audits can also provide progress reporting on deployment of specification changes, based on what IT is reporting vs. actual. Since you appear to be planning a lot of churn for them, I suspect you will need one FTE staff member to perform rolling audits to ensure that things are on schedule, and if they aren't, you can negotiate either a schedule change, or a working emphasis (this is a prioritization list: other things will suffer if you have insufficient staff in IT for the demands being made).
Good examples of what you can dictate are things you've complained about: Automated Provisioning, use of SRM in VMWare installations, enabling automated tiering in EMC storage hardware, and so on. Things which will bite the enterprise on the ass eventually, if they are not done.
Your initial dashboards should be based on displaying progress on this (e.g. "percentage of VMWare installations with SRM enabled", etc.).
Note that before any of your shit starts running down hill, you need to make sure you are not downhill from them. To do that, you are likely going to have to have meetings, a couple times a week (usually something like Tuesday/Friday), to collect requirements for the business, and then mash it into part of the requirements document that you will need to prepare before you start defining strategy and dictating conformance/performance). Otherwise you will find yourself buried in crap, because your goals will not be clearly derived from the enterprise goals.
Your ability to take new input from the early in the week meeting and report it in the late in the week meeting with the stakeholding execs is going to be your main performance metric until you go into the design, then implementation phases. Your goal is to get to an ongoing maintenance/change phase. Your metrics will be different in each phase. You will use these in your performance reviews to justify yourself.
If you have other things you care about, they need to be in the specifications -- and they probably need a dashboard, and they need to have a schedule.
For example, if you care about automated provisioning, then you need to have a scratch machine that is identical to the production machines, and you need to have a metric of "how long from a zeroed state does it take to provision the m
"every consumer needs to assume some responsibility"
Really? When *I* go online, yes, I have to assume some responsibility.
I hold the "things" up to the same standard: when the "things" go online, *they* have to assume some responsibility. It's not my f***ing fault if my fridge wants to surf the web, it's the fridge's fault.
It's true, and to stay out of legal trouble, most now put it in their terms and conditions.
Citation or you are spewing garbage.
If he won't, I will (simple Google search, which you could do, if you knew how to work Google):
https://erosdating.com/terms-o... "You also understand and agree that there are users and members on the Site that use and subscribe to our Service for purely entertainment purposes. Those users and subscribers are not seeking physical meetings with anyone they meet on the Service, but consider their communications with users and members to be for their amusement."
In other words, they find it amusing to troll people, and some of the people who troll people may or may not be employed by the company.
The day traders I know are afraid it's going to kill their ability to make money.
Day traders don't care.....if the market is up, they go long, if the market is down, they go short. What they want is volatility, long, predictable swings where they can jump in and jump out.
Money being sucked out of the stock market into the bond market reduces stock liquidity, which in turn, reduces stock volatility. Day traders rely on more or less large swings in stock prices, and when major holdings are not in play (because there are none, if all the institutional investors have fled to bonds), then their ability to profit evaporates.
Day trading is generally based on options with a limit order (to reduce downside risk, since they can't use the Black-Scholes or Black-Scholes-Merton hedging model in order to balance risk via bonds and other longer term instruments -- since they are *day* traders). There is the possibility of using ETFs in order to hedge risk, but then the upside is considerably reduced; generally, to lower than the brokerage fees, so it's not an option (pardon the pun).
Slashdot Mirror
I agree with Microsoft here. On this issue, they are fighting the good fight.
The FCC is currently trying to end 3rd-party wifi router firmware (think Tomato, DD-WRT, OpenWRT, etc.), by requiring manufacturers to build devices that only accept firmware updates signed with the manufacturer's keys.
This is incorrect.
What the FCC is wanting to require is that the SDR chips in these devices only accept radio firmware loads that are signed.
This is because they license the radios, and the radios are licensed as a combination of hardware and software, Loading different firmware into the radio part makes it an unlicensed radio, and permits it to receive signals in prohibited ranges, as well as transmit signals to interfere with the allowed signals in those prohibited ranges, or in bands which require a license for you to transmit.
The FCC does not give a flying crap about the *router* firmware... "(think Tomato, DD-WRT, OpenWRT, etc.)", what they care about is the radio, in the same way they care about the baseband firmware in mobile phones.
So the only thing the FCC wants is to control the air waves (which is what they, as an organization, were created to do).
Several router vendors would prefer you not replace their firmware, and cable companies which are now deploying WiFi hot spots in their service areas using your house and the router they sold you in order to do it, are objecting to you loading your own firmware, since it means they can't offer paid hot spot service out of your house because you happen to have a router that does WiFi from them.
But that's not the FCC, that's the people who want to use *your* equipment in *your* house in order to further *their* business model at the expense of *your* total available bandwidth (particularly, upstream bandwidth).
And this is why we have an environmental problem. If people would fix what they have instead of constantly replacing it, lots of environmental damage caused by manufacturing and transport could be avoided.
But I notice no "Green" group ever mentions this.
You could get the same net effect by the green groups offering repair services that were cheaper than a new purchase, or by the green groups offering to haul the old stuff away, and refurbish it, and sell it to other people so that they *don't* buy new stuff.
Of course, the problem with that is that the equipment is till going to take energy to operate, and the green groups would generally prefer we live in caves or trees, after at least 90% of the human population is "unfortunately" killed off by something.
If there were children, I would have a life insurance for if they are young. If they are older, they would have to fend for themselves and I hope that they have the same attitude as Ãmy sister and myself have towards our parents
One of the best things you can do for a new baby is be prepared to immediately get a permanent or whole life policy for them, which they can later borrow against, and pay themselves back with interest. If you fully fund it, which takes 11-12 years, if you pay in as much as you legally can, they can borrow from it to pay for college, borrow from it for their wedding, borrow from it to buy their first home, and so on.
There are only about 6 companies in the U.S. which offer policies where you can set your own interest rate on cash value funds borrowed (which then becomes a tax deduction, but adds to the cash value on top of the term value.
The best part is you don't have to depend on your kid being a star athlete, magic minority (e.g. "Irish boys named Humphries"), or be a stellar academician (although I expect most of us here would expect that last of our kids...) and get a scholarship, or not go to college except on daddy or mommy's checkbook.
It's more worthwhile than a trust fund, in most cases, because they *have* to pay themselves back.
Uncapped 4G is pretty nifty. However... I had an uncapped 4G hotspot from one vendor, and it worked pretty great. Then Sprint bought them, and capped it. Then I had uncapped 4G from Clear. Sprint has bought them, and they start capping it, too, as of November 1st. I expect anyone who offers this service can expect to be purchased by Sprint (hey, built in exit strategy for your new startup!) so they can cap it, and charge metered rates for the inevitable overage (particularly now that Windows 10 does peer-to-peer sharing of Windows images and updates, and eats tons of upstream in the process).
If the city implements the infrastructure, then it's possible for it to be competitive, assuming the fiber bandwidth is either intentionally constrained, or effectively constrained by number of links into a single upstream at the head end (same thing that tends to make cable slow at "get up in the morning before work" and "people just got home from school/work" times.
Actually, if we keep having 3 cat4 hurricanes churning the Pacific garbage patch, you could easily argue that it's going to be one and the same problem.
Pretty sure that cat5 hurricanes is the minimum ...assuming you want a good signal.
Uh... LOL. Sorry.
For starters, I could buy the name brand mac and cheese any time I wanted, not just on special occasions.
People will "LOL" at this.
It is a very real issue for those of us who grew up poor.
On special special occasions, you could include 1lb of ground beef.
Like once a week. Most rich people used to be incredibly poor people who will Never NEVER again be in that position.
IF they are doing that...
Which they aren't, since there's no money in it for them, getting involved in law suits,
100K a year after taxes.
It's bound to go up, but to being "wealthy" means $2-4M in investments to get to that after taxes. Depending on how.
Everything after that is either "invest in the investments" or "pay off the house loan against the line of credit".
Any way you look at it, if you do not want to work, or you do not want to work on something other than "facebook++" for some asshole who thinks he has a magic "get rich quick" scheme, you are at a minimum looking at $4M.
What command-line do you use to get anagrams?
Pretty sure it's "/bin/sh and a working brain".
"Denali" = anagram for "Denial"
Worked on many projects code named "Denali".
Just saying...
Sadly out of mod points... this deserves to be modded up.
Re the last paragraph. That is not entirely true, as Intel appear to be able to integrate new chipsets during the time they are released (but only to next tier manufacture) before the public can buy anything using it.
What kind of "peeing on it" has been done to the Intel drivers to get them integrated ?
Exactly the same kind. It's possible to do for anything, it just takes time.
The reason Intel is able to do this ahead of general release, when other vendors aren't, is that it does not lose them a competitive advantage.
First, there is no issue of another manufacturer producing "pin and register compatible devices", and undercutting Intel, because Intel's graphics are integrated into the CPU; you'd have to build an entire Intel compatible CPU as well, and you'd have to do it competitively in terms of price point.
Second, no one really wants to emulate Intel Integrated Graphics in silicon, since there's really no advantage to doing so, since the chips have inferior performance relative to the competition.
So there's really nothing lost by Intel pre-announcing all of the information needed to make a driver, or even publishing source code for the driver, since doing so will sell more Intel chips, not less. For other GPU vendors, this is simply not the case, and there's no economic value in such pre-disclosure.
The whole posting is disengenuous.
"the R9 Fury isn't yet in good shape on the open-source driver"
The card won't be changing to fix this; the driver will have to change to accommodate the card; therefore it is more correct to say "The Open Source driver is not yet in good shape on the R9 Fury". In other words, it's not the hardware's fault that the driver doesn't support it yet.
"AMD's open-source developers haven't yet found the time to implement power management / re-clocking support"
The power management model in Linux is Linux's responsibility, not AMD's. The authors of the Open Source driver are accountable *only* for writing callbacks for the device power management component, and populating the structure. It's my understanding that Linux lacks a uniform model for use by all graphics drivers, in this regard. his is a Linux issue, not an AMD issue.
Also:
In general, in a hardware world, you either NDA people, or the Open Source is going to lag the closed source, period. This is because openly manipulating code related to an unreleased hardware product in a publicly accessible source repository, instead of a privately held repository, is tantamount to preannouncing your hardware to competitors. You might as well have the CEO call a press conference, and then shoot themselves in the head in public.
Open Source projects have a secondary problem in that, even if the driver source was developed entirely by engineers within AMD, and released the same day as the hardware was made available, the Open Source projects aren't going to be happy just integrating the code as is. They will insist on peeing on it to make it smell like themselves, just as cats do with new furniture, and this will take time. You can either have closed source, or you can have it integrated later than the release date, but you can not have both.
I, for one, welcome this addition... every privilege escalation path you add is good for literally years of paid contract work.
So we won't know it's Gnome until the release?
Very, very, sneaky!
I suggest the first code name be "Zurich"; my second choice is "Gringott"... don't tell anyone, we wouldn't want them knowing we were talking about Gnome!
Because this will be unlike Biosphere 2 how?
http://wunc.org/post/what-less...
They should have done it under water, if they insisted on Hawaii instead of Antarctica, which would have been a better choice (or at altitude on K2 or Everest, as long as it was a non-permanent installation). There's too much temptation to cheat, there's no real danger, and we already know that curing concrete will eat all your CO2 if you are stupid and don't seal it.
The only good choice fora Hawaii location other than "under water" would be "Inside a large SO2 cloud near a volcano, so that breathing the external atmosphere would get you dead".
I suggest we confuse the primary Uber benefits with the electronic dispatch system, rather than showing up when you've made a commitment to show up, the lower prices Uber charges on average, the cleaner, newer vehicles, ad the pleasant drivers who have to be pleasant because there's a feedback system which loses them referrals, whereas a taxi driver with a medallion can't really be fired without losing the medallion.
It must be the app, right folks? Not all the other things?
So basically I'm responsible, because I didn't write the firmware, and instead it was written by an idiot? Like someone who runs Windows, and is therefore able to turn off Windows Update because it exists in the first place, and could be the very channel which, by means of DNS cache poisoning and/or router compromise and/or BGP poisoning, was the means to infect the thing in the first place?
How about we hold the idiot who thought giving the fridge a routable address via NAT off the local network in the first place, so that they could market specific brands of milk via coupons sent to me when I'm running low on milk, was a good idea, responsible instead?
It's clear you do not understand the position. You need to read about what the job entails, and then decide if you want to accept the offer or not. It's a substantial change in role from your current position. In this case, the Wikipedia article is pretty accurate:
https://en.wikipedia.org/wiki/...
As others have stated, your primary responsibility is specification. To do this, you meet with stakeholders, and do projective business IT strategic planning.
While you can relatively easily negotiate for read only access as a demand from "on high", you should not personally use it. It should be used by your staff, temporary or permanent, for the performance of detailed specification compliance audits and spot checks. This is adequate justification to get management buy-in for this type of access. This type of access is for a role, not for a person. This is one of the reasons it should not be you.
For day to day operations, what you need are dashboards, which measure the degree of compliance with the detailed specification in an ongoing basis. The main purpose of the dashboards are to give you information you can summarize periodically to the executives, and as feedback into your strategy decisions going forward (particularly decisions surround capacity planning and technology adoption).
The purpose of the ability to audit is to ensure that the dashboards are not giving you fudged numbers based on what you want to hear, vs. what IT whats to implement (or what they can implement; you may be asking for the impossible, as a dictator, when you should be viewing the detailed specifications as a negotiation). Audits can also provide progress reporting on deployment of specification changes, based on what IT is reporting vs. actual. Since you appear to be planning a lot of churn for them, I suspect you will need one FTE staff member to perform rolling audits to ensure that things are on schedule, and if they aren't, you can negotiate either a schedule change, or a working emphasis (this is a prioritization list: other things will suffer if you have insufficient staff in IT for the demands being made).
Good examples of what you can dictate are things you've complained about: Automated Provisioning, use of SRM in VMWare installations, enabling automated tiering in EMC storage hardware, and so on. Things which will bite the enterprise on the ass eventually, if they are not done.
Your initial dashboards should be based on displaying progress on this (e.g. "percentage of VMWare installations with SRM enabled", etc.).
Note that before any of your shit starts running down hill, you need to make sure you are not downhill from them. To do that, you are likely going to have to have meetings, a couple times a week (usually something like Tuesday/Friday), to collect requirements for the business, and then mash it into part of the requirements document that you will need to prepare before you start defining strategy and dictating conformance/performance). Otherwise you will find yourself buried in crap, because your goals will not be clearly derived from the enterprise goals.
Your ability to take new input from the early in the week meeting and report it in the late in the week meeting with the stakeholding execs is going to be your main performance metric until you go into the design, then implementation phases. Your goal is to get to an ongoing maintenance/change phase. Your metrics will be different in each phase. You will use these in your performance reviews to justify yourself.
If you have other things you care about, they need to be in the specifications -- and they probably need a dashboard, and they need to have a schedule.
For example, if you care about automated provisioning, then you need to have a scratch machine that is identical to the production machines, and you need to have a metric of "how long from a zeroed state does it take to provision the m
"Completes Great Pacific Garbage Patch Research Expedition"
"every consumer needs to assume some responsibility"
Really? When *I* go online, yes, I have to assume some responsibility.
I hold the "things" up to the same standard: when the "things" go online, *they* have to assume some responsibility. It's not my f***ing fault if my fridge wants to surf the web, it's the fridge's fault.
It's true, and to stay out of legal trouble, most now put it in their terms and conditions.
Citation or you are spewing garbage.
If he won't, I will (simple Google search, which you could do, if you knew how to work Google):
https://erosdating.com/terms-o...
"You also understand and agree that there are users and members on the Site that use and subscribe to our Service for purely entertainment purposes. Those users and subscribers are not seeking physical meetings with anyone they meet on the Service, but consider their communications with users and members to be for their amusement."
In other words, they find it amusing to troll people, and some of the people who troll people may or may not be employed by the company.
The day traders I know are afraid it's going to kill their ability to make money.
Day traders don't care.....if the market is up, they go long, if the market is down, they go short. What they want is volatility, long, predictable swings where they can jump in and jump out.
Money being sucked out of the stock market into the bond market reduces stock liquidity, which in turn, reduces stock volatility. Day traders rely on more or less large swings in stock prices, and when major holdings are not in play (because there are none, if all the institutional investors have fled to bonds), then their ability to profit evaporates.
Day trading is generally based on options with a limit order (to reduce downside risk, since they can't use the Black-Scholes or Black-Scholes-Merton hedging model in order to balance risk via bonds and other longer term instruments -- since they are *day* traders). There is the possibility of using ETFs in order to hedge risk, but then the upside is considerably reduced; generally, to lower than the brokerage fees, so it's not an option (pardon the pun).