text:
Tag Archives: RDOF
Jonathan Chambers wrote another great blog this past week on Conexon where he addresses the issue of federal grants having waste, fraud, and abuse – the reasons given for holding hearings in the House about the upcoming BEAD broadband grants. His blog goes on to say that the real waste, fraud, and abuse came in the past when the FCC awarded federal grants and subsidies to the large telcos to build networks that were obsolete by the time they were constructed. He uses the term underbuilding to describe funding networks that are not forward-looking. This is a phrase that has been around for many years. I remember hearing it years ago from Chris Mitchell, and sure enough, a Google search showed he had a podcast on this issue in 2015.
The term underbuilding is in direct contrast to the large cable and telephone companies that constantly use the term overbuilding to mean they don't want any grant funding to be used to build any place where they have existing customers. The big ISPs have been pounding the FCC and politicians on the overbuilding issue for well over a decade, and it's been quite successful for them. For example, the big telcos convinced the FCC to provide them with billions of dollars in the CAF II program to make minor tweaks to rural DSL to supposedly bring speeds up to 25/3 Mbps. I've written extensively on the failures of that program, where it looks like the telcos often took the money and made minimal or no upgrades.
As bad as that was – and that is the best example I know of waste, fraud, and abuse – the real issue with the CAF II subsidy is that it funded underbuilding. Rural DSL networks were already dying when CAF II was awarded, mostly due to total neglect by the same big telcos that got the CAF II funding. Those billions could have instead gone to build fiber networks, and a whole lot of rural America would have gotten state-of-the-art technology years ago instead of a tweak to DSL networks that barely crawling alone due to abuse.
The FCC has been guilty of funding underbuilding over and over again. The CAF II reverse auction gave money to Viasat, gave more money for upgrades to DSL, and funded building 25/3 Mbps fixed wireless networks. The classic example of underbuilding came with RDOF, where the areas that were just finishing the CAF II subsidy were immediately rolled into a new subsidy program to provide ten more years of subsidy. Many of the areas in RDOF are going to be upgraded to fiber, but a lot of the money will go into underperforming fixed wireless networks. And, until the FCC finally came to its senses, the RDOF was going to give a billion dollars to Starlink for satellite broadband.
The blame for funding underbuilding lies directly with the FCC and any other federal grant program that funded too-slow technologies. For example, when the CAF II funding was awarded to update rural DSL, areas served by cable companies were already delivering broadband speeds of at least 100 Mbps to 80% of the folks in the country. By the time RDOF was awarded, broadband capabilities in cities had been upgraded to gigabit. The policy clearly was that rural folks didn't need the same quality of broadband that most of America already had.
But the blame doesn't just lie with the FCC – it lies with all of the broadband advocates in the country. When the ISPs started to talk non-stop about not allowing overbuilding, we should have been lobbying pro-broadband politicians to say that the FCC should never fund underbuilding. We've collectively let the big ISPs frame the discussion in a way that gives politicians and regulators a convenient way to support the big ISPs. Both at the federal and state levels the broadband discussion has often devolved into talking about why overbuilding is bad – why the government shouldn't give money to overbuild existing ISPs.
Not allowing overbuilding is a ludicrous argument if the national goal is to get good broadband to everybody. Every broadband network that is constructed is overbuilding somebody, except in those exceptionally rare cases where folks have zero broadband options. If we accept the argument that overbuilding is a bad policy, then it's easy to justify giving the money to incumbents to do better – something that has failed over and over again.
It's time that we call out the overbuilding argument for what it is – pure protectionism. This is monopolies flexing political power to keep the status quo, however poorly that is working. The big ISPs would gladly roll from one subsidy program to another forever without investing any of their own capital to upgrade rural networks.
Every time a regulator or politician says that we should not be using federal money to overbuild existing networks, we need to prod pro-broadband politicians to counter that argument by saying we should not be spending any more money on underbuilding. Broadband is infrastructure, just like roads and bridges, and we should be investing any grant money into the most forward-looking technology possible. If the national goal is to make sure that everybody has good broadband, then we should be ready to overbuild anywhere the incumbents have underperformed, be that in rural areas or inner cities. It's time we shift the conversation away from protectionism to instead prioritizing bringing broadband that will still be good a decade or two after the grant award. Let's not spend another penny of grant money on underbuilding networks by investing in slow technologies that are inadequate and obsolete even before they are completed.
Tagged BEAD, CAF II, FCC, overbuilding, RDOF, underbuilding
Why the Complexity?
It's been over a year since the BEAD grant program was announced. While there has been a lot of activity on BEAD, there is still a long way to go before this grant money is used to build new broadband infrastructure. Most of the delay is due to the incredible complexity of the BEAD grant rules.
I work with a lot of different state broadband grant programs, and I can't help but notice the tremendous difference in the complexity of the process between state and BEAD grants. The priority for state grant programs is usually to quickly get the money out the door and spent on infrastructure. State legislators that approve grant funding want to see construction started no later than the year after the grant award, and hopefully sooner. State grant offices are generally given instructions to identify worthwhile projects and get the money approved and quickly into the hands of the ISPs to build networks.
The differences between state grants and BEAD are stunning. I have one client that won a $10 million state grant based on a simple grant application of less than 20 pages. The grant reviewers asked a few follow-up questions, but the whole process was relatively easy. The grant office was relying on the challenge process by ISPs to identify grants that were asking to overbuild areas that already have broadband. The challenge process seemed to work – a number of the grants filed in this particular program were successfully challenged. But the bottom line is that the funding was made available to start construction in less than a year from the date when the grant office originally solicited grant applications.
Why are the BEAD grants so complicated? It starts with Congress, and a lot of the complexity is directly specified in the IIJA legislation that created the grants. My pet theory is that the complexity was introduced by lobbyists of the large ISPs that wanted to make the grants unfriendly to everybody other than big ISPs with the resources to tackle the complex rules. It's unfathomable to me that congressional staffers would have invented these complex rules on their own. I knew on my first reading of the IIJA legislation that the grants favor big companies over small ones.
In the legislation, Congress decided to give the administration of the grants to the NTIA. The NTIA had a major decision to make on day one. The agency could have taken the approach of smoothing out the congressional language to make it as easy as possible for ISPs seeking the funding. The NTIA had political cover to take a light-touch approach since the legislation stressed the importance of quick action to solve the rural broadband crisis. The White House has also been urging federal agencies to speed up the process of turning IIJA funding into infrastructure projects.
Unfortunately, the NTIA didn't take this approach. It looks like the agency did just the opposite – the agency embellished and strengthened the congressional language and made it even more complex to file for the grants.
I don't think the NTIA had any agenda to make the grant more complicated. It's impossible to think the agency had early discussions about how to make it harder to use the grant funding. But the agency did have an overriding desire to do these grants the right way. The general industry consensus is that the grants were given to the NTIA instead of the FCC because of the terribly botched RDOF subsidy program. It would be hard to design a federal broadband program that would have been more poorly handled than RDOF (except perhaps for CAF II, which also was done by the FCC).
I think BEAD became more complex, one topic at a time. I think folks at NTIA looked at each congressionally mandated rule and asked how they could make sure that no money went to an unqualified ISP. Instead of softening grant requirements, I think the NTIA staff instead asked how they could be positive that no unworthy ISPs sneak through BEAD process – something that clearly happened in the FCC's RDOF process. The final NTIA BEAD rules are not a manual on how to get grant money spent efficiently – but a manual on how to make sure that only qualified ISPs win the funding.
That doesn't sound like a bad goal. Some of the ISPs that won the RDOF funding were spectacularly unqualified – either financially, managerially, or technically. But as each of the many BEAD rules was made as safe as possible, the collective combination of all of the BEAD rules being made super-safe creates major hurdles for ISPs. Almost every ISP I know is going to have a problem with at least a few of the rules – and I think many qualified ISPs are going pass on the BEAD grants. There is something wrong with a grant program that has hundred-year-old telephone companies wondering if they can qualify for the grants.
There is still a chance for State broadband offices to smooth out the worst of the BEAD rules. A State broadband office can push back against the NTIA BEAD rules that make it too hard for ISPs to get funded. The NTIA can't excuse any specific mandate that was created by Congress – but the NTIA can relax and compromise on its interpretation of these rules.
The big challenge facing State grant offices is how hard they are willing to push back against the NTIA. Every State is under pressure to finally get the grant process underway, and any challenge will likely add time before funding is available. Every State broadband office already knows the ISPs it would like to see win the funding – those ISPs that will be conscientious in operating the network after its built. State broadband offices need to listen and react to the concerns that these ISPs have about the grant process – because if they don't, many of the best ISPs are going to take a pass on the grants.
Tagged BEAD Grants, FCC, NTIA, RDOF
The RDOF Fixed Wireless Dilemma
I'm working with a number of rural counties that are trying to come to grips with the long-term implications of RDOF awards in their counties going to ISPs that plan to deliver broadband using fixed wireless technology. Most of them are not sure what to make of the situation for a number of reasons.
First, many of these counties are pleased about the wireless RDOF winners if that means bringing a broadband solution sooner. The folks in their counties are crying out for a broadband solution. But the big worry about the RDOF award winners is that the FCC gave RDOF winners a relaxed construction obligation compared to most other grants.
An RDOF recipient has six years to build the full broadband solution – starting with the year after the award. A recipient of a 2022 RDOF award must build 40% of the network by the end of 2025, 60% of the deployment by the end of 2026, 80% of the network by the end of 2027, and 100% of the network by the end of 2028. At the end of 2028, the FCC will publish a final list of locations in the RDOF area, and the ISPs have until the end of 2030 to reach any locations that were not already covered. Counties are rightfully worried that RDOF recipients will use the full timeline, meaning some folks won't see a solution until 2027 or 2028.
There is also a concern that the FCC has a poor history of follow-through with subsidy awards, such as the many locations that were slated to get CAF II upgrades that don't seem to have been upgraded – with no apparent reaction or consequences from the FCC. The fear is RDOF winners will cherry-pick the easiest areas and not bother with the rest and some folks will never get served. The worst thing is that a county won't know for sure that folks won't be served until 2028.
Another concern I'm hearing is that, in many cases, the RDOF awards were given in counties where there is one or more local ISPs willing to build fiber with grant assistance. These might be an electric cooperative or small telco that would willingly have brought fiber to the RDOF areas. These counties feel cheated by the FCC, particularly the RDOF awards that were made by the FCC after the announcement and funding of the $42.5 billion in BEAD grants. These counties feel that the FCC snatched away a fiber solution instead of putting the RDOF awards on hold.
The concern several of them have expressed is the sustainability of fixed wireless. They understand that a fiber network is probably going to still be in place and working at the end of this century, with perhaps three or four electronics upgrades during that time. But they've all heard that wireless technology has a shelf life of perhaps seven years, and they worry if the RDOF winners are going to be willing and able to pay for upgrades ten or eleven times during the rest of the century.
Finally, the ISPs in these counties are dismayed at what can best be described as the checkerboard way that the RDOF was awarded. The RDOF award areas are rarely nice contiguous service areas but are scattered pockets of Census blocks. ISPs can see that it is going to be extra challenging to find other grant funding to bring a solution to other areas. In many cases, they'll have to spend their own money to build across RDOF areas in order to create a coherent fiber network.
Finally, some counties are concerned that the RDOF winners have not reached out to them to discuss these concerns and to convey their plans for bringing the promised faster broadband. I know that many of these awards were just made this summer, but there has been sufficient time for the RDOF winners to have met with local officials to convey their plans.
To be fair, some of these same counties have a similar list of concerns if grants go to the giant ISPs instead of somebody local. The folks in most rural areas know that the current round of grant funding is probably the only chance to get the broadband solution done right, and none of them want to be the poster child as a place where the giant grants and subsidies failed.
Posted in Regulation - What is it Good For?, The Industry
Tagged RDOF
Inflation and Grants
Diana Goovaerts wrote an article for Fierce Telecom with the headline that Inflation has doubled RDOF build costs. The article is based on interviews with three ISPs that won RDOF funding in the December 2020 reverse auction – TekWav, Nextlink, and Plains Internet. All three ISPs plan to satisfy the RDOF obligations with a combination of fixed wireless and fiber. Two of the three ISPs were quoted as saying that the cost to build the networks to satisfy the RDOF obligations has doubled since they won the award – the third said costs have risen materially. The three companies have significantly different obligations. Plains Internet is obligated to build broadband to 250 passings in Kansas, while Nextlink must build to pass 206,136 locations over twelve states.
There is a lot to unwrap in the assertion that costs have doubled. First, everybody in the industry will agree that the costs of both material and labor have increased over the last two years. But most of the ISPs I've been working with estimate the increase to be between 15% and 30%, differing by region and the planned technology. The article includes an interview with Jonathan Chambers of Conexon, who believes that the claims that a doubling of cost is highly unlikely.
But the interviews raised a few issues related to the cost of building broadband that aren't talked about a lot. Clearly, materials and labor are more expensive. In the case of wireless ISPs that are obligated to deliver superfast speeds, the costs I've been seeing for newer radios like the ones from Tarana look to be triple or more the cost of other radios.
One issue that is not being widely discussed is the availability of loans. One of the things that always happens when interest rates increase is that banks drastically curtail making loans to new customers. They may still offer higher interest rate loans to existing customers, but an ISP looking for a new banking relationship is going to hit a stone wall. That is exactly what the Federal Reserve has in mind with interest rate increases – they want to cool off the economy by curtailing new lending. The trick for the Fed is threading the needle to cool the economy enough to slow inflation but not enough to cause a crash.
The difficulty in getting bank loans creates a dilemma for an ISP trying to fulfill an obligation to build a broadband solution with specified construction deadlines. And RDOF award winner has three years, starting with the year after the FCC finalizes the award to build 40% of the promised network. The rest must be built in the following three years. For the big RDOF winners, that probably means having to start on some of the construction right away to meet the first completion goal.
The RDOF awards suppose that recipients will fund the majority of a new network, with debt or equity – and except for the giant ISP winners like Charter, most ISPs rely on new debt. The current big grant programs like BEAD also assume an ISP will bring a significant matching fund to a project, most likely debt for most companies. It's a huge problem for somebody trying to build a grant or subsidy project if they can't find the loans.
The three RDOF winners didn't cite the impact of higher interest rates. I've seen interest rates on infrastructure projects nearly double over the last year, and that means double the interest expense from the day of borrowing – a huge financial hurdle to overcome for any kind of infrastructure project.
The other issue identified by Joseph McGrath of TekWav is the time lag between the cost of a new network and the revenues needed to pay for them. Most ISP have historically expanded organically in the past. They add new territory and customers each year that is partially funded by the cash flow from the existing business, supplemented with short-term loans. An ISP trying to grow fast must abandon the organic growth model. This means spending a lot of money before there is any new revenue. I've always referred to this as the cost of expansion, and it's only a problem for an ISP that is trying to grow faster than what its existing financial structure can handle.
Unfortunately, anybody taking any sizable RDOF or grant projects will experience expansion costs. The ISP will be paying staff to work in the new areas and paying interest on the cost of the equipment for the new area, with far more costs to eat than would be experienced with organic growth. I have to wonder if the big RDOF winners built these costs into its plans. A company that has never tried to grow quickly before is likely to understand the cost of expansion.
The bottom line is that RDOF winners will either have to absorb these unexpected costs or default on the subsidy. There is a fairly minor penalty for defaulting on RDOF funding before any funding has flowed or construction begins. But I would suspect the FCC will level much bigger fines on somebody who has already taken funding, and the fine would likely include returning everything they've received. As Jonathan Chambers was quoted, there is a cost for taking federal funding – and it's always more expensive than anticipated.
Tagged Inflation, organic growth, RDOF
Defaulting on RDOF
Starry recently announced that it was defaulting on all of its $269 million of RDOF funding. Starry was the ninth-largest winner of the RDOF reverse auction that ended in December 2020. The FCC approved some of the Starry RDOF claims in August.
There have been other defaults of RDOF, but no others of this magnitude. For example, in the same announcement of the Starry default were additional defaults by Cal.net and GeoLinks. There were a lot of defaults in the spring of 2021 when winners defaulted on small pockets of Census blocks that weren't large enough for a coherent business plan.
Starry is not required to disclose why it's defaulting. In the many articles about the RDOF default, there was a lot of speculation that the company doesn't have the needed funding to complete the required builds. Starry reported 77,400 customers at the end of the second quarter of this year – gaining 14,300 customers in the quarter. The company claimed that it now passes 5.7 million potential customers. But the company has a big burn rate with a loss for the quarter of $33.9 million plus capital expenditures of $20.8 million.
Even if funding is the issue, funding wouldn't yet be an emergency for Starry. An RDOF winner has three years starting with the year after the awards – in this case until 2025, to cover 40% of the RDOF areas. But delaying the cancellation probably risks increasing fines from the FCC.
I've also heard speculation from engineers that Starry might not have been happy with the performance of its technology in rural areas. It seems like a technology best suited to areas with decent household density. The technology being deployed can best be described as a wireless mesh network. Starry brings broadband into a neighborhood and then bounces signal from customer to customer to extend the reach of the network. Over time as the company gets more customers, it can blanket a large coverage area. This is a drastically different approach than the FWA cellular wireless deployments that reply on putting a small cell site in every served neighborhood – most of them fed by fiber. The Starry deployment should need fewer fiber-fed hubs and theoretically would have a lower cost deployment.
In June 2021, Starry announced a deployment across the Columbus, Ohio metropolitan area. But there is a big difference between the densely populated suburbs of Columbus, Ohio and rural areas in RDOF where homes might not be within sight of neighbors. There are plenty of engineers that are still skeptical of wireless plans using tall towers to bring fast speeds to rural areas. It's even hard to imagine doing it with a mesh network.
With the default, all of the RDOF areas are back in play for other federal grants. Unfortunately for the customers in these areas that thought they had a broadband solution coming, they now need another ISP to step up and claim grant funding of some sort to bring broadband.
As can be seen on the map below of the Starry award areas, the company had claimed sizable service areas in Alabama, Arizona, Mississippi, Missouri, Nevada, Ohio, Pennsylvania, and Virginia.
Starry's default is different than the recent action by the FCC to toss the RDOF awards to LTD Broadband and Starlink. The FCC had already made some awards to Starry, and the assumption is that it would have made the rest. The bottom line is that the Starry default is one more piece of the puzzle of solving the rural broadband gap, and the ISPs located close to the Starry defaults should take a hard look at changing grant plans.
Tagged RDOF, Starry
Rural America is Losing Patience
From all across the country, I'm hearing that communities without broadband are tired of waiting for a broadband solution. Local broadband advocates and politicians tell me that folks with little or no broadband are hounding them about when they are going to see a broadband solution.
A large part of the frustration is that folks have heard that broadband is coming to rural America, but they aren't seeing any local progress or improvement. A big part of the reason for this frustration is that folks aren't being given realistic time frames for when they might see a solution. Politicians all gladly told the public that they had voted to solve rural broadband when the IIJA infrastructure legislation was enacted in November 2021. But almost nobody told folks the actual timelines that go along with the broadband funding.
Consider the timeline to build broadband as a result of various kinds of funding:
There was a recent round of ReConnect funding awarded. It generally takes 4- 6 months to get the paperwork straight after accepting a ReConnect award, and then grant winners have four years to build the network. Some of the folks in areas of the ReConnect awards that were recently awarded won't get broadband until 2026. Most won't see any broadband until 2024 or 2025.
The best timelines are with state broadband grants. Most of those awards require grant recipients to complete networks in two or three years. A lot of these grant programs were either recently awarded or will be awarded in the coming spring. The winners of these state grants will have until the end of 2024 or 2025 to complete the network construction, depending on the state and the specific grant.
The longest timeline comes from the FCC's RDOF program. The FCC approved a lot of RDOF recipients in 2021 and again in 2022. A 2021 RDOF recipient has six years to build the full broadband solution – starting with 2022, the year after the award. A recipient of a 2021 RDOF award must build 40% of the network by the end of 2024, 60% of the deployment by the end of 2025, 80% of the network by the end of 2026, and 100% of the network by the end of 2027. At the end of 2027, the FCC will publish a final list of locations in the RDOF area, and the ISP has until the end of 2029 to reach any locations that have not already been covered. For an RDOF award made in 2022, add a year to each of these dates.
The big unknown is the giant $42.5 billion BEAD grants. We know that grant recipients will have four years to construct a network. But we don't know yet when these grants might be awarded. It's starting to look like grant applications might be due near the end of 2023 or even into 2024. This likely means grant awards in 2024. There will likely be an administrative pause for paperwork before the four-year time clock starts. My best estimate is that the bulk of BEAD construction will occur in 2025 and 2026, but BEAD grant projects won't have to be completed until sometime in 2028 and maybe a little later in some cases.
In all cases, ISPs can build earlier than the dates cited above. ISPs realize that the longer they delay construction, the higher the likely cost of the construction. But some grants have built-in delays, such as having to complete an environmental study before any grant funds will be released. Many ISPs are going to suffer from supply chain issues with materials and labor and might not be able to speed up a lot.
The big problem is that people without good broadband want a solution now, not years from now. A family with a freshman in high school doesn't want to hear that a broadband solution won't reach them until after that student graduates from high school. People are getting frustrated by announcements from state and local politicians telling them a solution is coming – especially since most announcements aren't being truthful about the possible timeline. Unfortunately, politicians like to deliver the good news but don't want to be the ones to announce that faster broadband might reach folks between 2025 and 2028.
Folks are further frustrated when they hear that local governments are creating partnerships or giving grants to ISPs from ARPA funding – but again, with no immediate action or disclosures of the timeline. I am the last person in the world to give advice to local politicians – but I know if I didn't have broadband at my home, I'd want to hear the truth about when it's coming. This has to be tough for rural politicians who have negotiated partnerships with good ISPs but who know that a broadband solution is still likely years in the future.
Tagged BEAD Grants, RDOF, ReConnect grants
Starlink and RDOF
In August, the FCC denied the SpaceX (Starlink) bid to receive $885 million over ten years through the RDOF subsidy. This is something that Starlink won in a reverse auction in December 2020.
In the press release for the rejection, FCC Chairman Jessica Rosenworcel was quoted as saying, "After careful legal, technical, and policy review, we are rejecting these applications. Consumers deserve reliable and affordable high-speed broadband. We must put scarce universal service dollars to their best possible use as we move into a digital future that demands ever more powerful and faster networks. We cannot afford to subsidize ventures that are not delivering the promised speeds or are not likely to meet program requirements."
The FCC went on to say in the order that there were several technical reasons for the Starlink rejection. First was that Starlink is a "nascent" technology, and the FCC doubted the company's ability to deliver broadband to 642,925 locations in the RDOF areas along with serving non-RDOF areas. The FCC also cited the Ookla speed tests that show that Starlink speeds decreased from 2021 into 2022.
Not surprisingly, Starlink appealed the FCC ruling this month. In the Starlink appeal, the company argued, "This decision is so broken that it is hard not to see it as an improper attempt to undo the commission's earlier decision, made under the previous administration, to permit satellite broadband service providers to participate in the RDOF program. It appears to have been rendered in service to a clear bias towards fiber, rather than a merits-based decision to actually connect unserved Americans".
Rather than focus on the facts in dispute in the appeal, today's blog looks at the implications on the broadband industry during the appeal process. Current federal grant rules don't allow federal subsidies to be given to any area that is slated to get another federal broadband subsidy. This has meant that the RDOF areas have been off-limits to other federal grants since the end of 2020. This has included NTIA grants, USDA ReConnect grants, and others. Federal grant applicants for the last few years have had to carefully avoid the RDOF areas for Starlink and any other unresolved RDOF award areas.
As a reminder, the RDOF areas were assigned by Census block and not in large coherent contiguous areas. The RDOF award areas have often been referred to as Swiss cheese, meaning that Census blocks that were eligible for RDOF were often mixed with nearby ineligible Census blocks. A lot of the Swiss cheese pattern was caused by faulty FCC maps that excluded many rural Census blocks from RDOF that should have been eligible, but for which a telco or somebody else was probably falsely claiming speeds at least 25/3 Mbps.
ISPs that have been contemplating grant applications in the unresolved RDOF areas were relieved when Starlink and other ISPs like LTE Broadband were rejected by the FCC. It's difficult enough to justify building rural broadband, but it's even harder when the area to be built is not a neat contiguous study area.
The big question now is what happens with the Starlink areas during an appeal. It seems likely that these areas will go back into the holding tank and remain off-limits to other federal grants. We're likely going to need a definitive ruling on this from grant agencies like the USDA to verify, but logic would say that these areas still need to be on hold in case Starlink wins the appeal.
Unfortunately, there is no defined timeline for the appeal process. I don't understand the full range of possibilities of such an appeal. If Starlink loses this appeal at the FCC, can the agency take the appeal on to a court? Perhaps an FCC-savvy lawyer can weigh in on this question in the blog comments. But there is little doubt that an appeal can take some time. And during that time, ISPs operating near the widespread Starlink grant areas are probably still on hold in terms of creating plans for future grants.
Tagged FCC, RDOF, StarLink
Another RDOF Auction?
There was a recent interview in FierceTelecom with FCC Commissioner Brandon Carr that covered a number of topics, including the possibility of a second round of RDOF. Commissioner Carr suggested that improvements would need to be made to RDOF before making any future awards, such as more vetting of participants upfront or looking at weighting technologies differently.
The FCC is building up a large potential pool of broadband funding. The original RDOF was set at $20 billion, with $4.4 billion set aside for a second reverse auction, along with whatever was left over from the first auction. The participants in the first RDOF auction claimed only $9.2 billion of $16 billion, leaving $6.8 billion. When the FCC recently decided not to fund LTD Broadband and Starlink, the leftover funding grew by another $2 billion. Altogether that means over $11 billion left in funds that were intended for RDOF.
We also can't forget that around the same time as the RDOF that the FCC had planned to fund a 5G fund to enhance rural cellular coverage. Due to poor mapping and poor data from the cellular carriers, that auction never occurred. That puts the pool of unused funding at the FCC at $20 billion, plus whatever new FCC money might have accrued during the pandemic. That's a huge pool of money equal to half of the giant BEAD grants.
The biggest question that must be asked before considering another RDOF reverse auction is how the country will be covered by the BEAD grants. It would be massively disruptive for the FCC to try to inject more broadband funding until that grant process plays out.
Commissioner Carr said that some of the FCC's funding could go to enhance rural cellular coverage. Interestingly, once BEAD grant projects are built, that's going to cost a lot less than was originally estimated. A lot of the money in the proposed 5G fund would have been used to build fiber backhaul to reach rural cell sites. I think the BEAD last-mile networks will probably reach most of those places without additional funding. However, there is probably still a good case to be made to fund more rural cell towers.
But there are larger questions involved in having another reverse auction. The big problem with the RDOF reverse auction was not just that the FCC didn't screen applicants first, as Carr and others have been suggesting. The fact is that a reverse auction is a dreadful mechanism for awarding broadband grant money. A reverse auction is always going to favor lower-cost technologies like fixed wireless over fiber – it's almost impossible to weight different technologies for an auction in a neutral way. It doesn't seem like a smart policy to give federal subsidies to technologies with a 10-year life versus funding infrastructure that might last a century.
Reverse auctions also take state and local governments out of the picture. The upcoming BEAD funding has stirred hundred of communities to get involved in the process of seeking faster broadband. I think it's clear that communities care about which ISP will become the new monopoly broadband provider in rural areas. If the FCC has a strict screening process up front, then future RDOF funding will only go to ISPs blessed by the FCC – and that probably means the big ISPs. I would guess that the only folks possibly lobbying for a new round of RDOF are companies like Charter and the big telcos.
The mechanism of awarding grants by Census block created a disaster in numerous counties where RDOF was awarded in what is best described as swiss cheese serving areas. The helter-skelter nature of the RDOF coverage areas makes it harder for anybody else to put together a coherent business plan to serve the rest of the surrounding rural areas. In contrast, states have been doing broadband grants the right way by awarding money to coherent and contiguous serving areas that make sense for ISPs instead of the absolute mess created by the FCC.
A reverse auction also relies on having completely accurate broadband maps – and until the FCC makes ISPs report real speeds instead of marketing speeds, the maps are going to continue to be fantasy in a lot of places.
Finally, the reverse auction is a lazy technique that allows the FCC to hand out money without having to put in the hard effort to make sure that each award makes sense. Doing grants the right way requires people and processes that the FCC doesn't have. But we now have a broadband office and staff in every state thanks to the BEAD funding. If the FCC is going to give out more rural broadband funding, it ought to run the money through the same state broadband offices that are handling the BEAD grants. These folks know local conditions and know the local ISPs. The FCC could set overall rules about how the funds can be used, but it should let the states pick grant winners based upon demonstrated need and a viable business plan.
Of course, the simplest solution of all would be for the FCC to cut the USF rate and stop collecting Universal Service Fund revenues from the public. The FCC does not have the staff or skills needed to do broadband grants the right way. Unfortunately, that might not stop the FCC from tackling something like another RDOF auction so it can claim credit for having solved the rural digital divide. If the FCC plans on another RDOF auction I hope Congress stops them from being foolhardy again.
Tagged Commissioner Brandon Carr, FCC, RDOF, reverse auction
How Fast is Starlink Broadband?
We got a recent analysis of Starlink broadband speeds from Ookla, which gathers huge numbers of speed tests from across the country. The U.S. average download speeds on Starlink have improved over the last year, from an average of 65.72 Mbps in 1Q 2021 to 90.55 Mbps in 1Q 2022. But during that same timeframe, upload speeds got worse, dropping from an average of 16.29 Mbps in 1Q 2021 to 10.70 Mbps in 1Q 2022.
It's likely that some of this change is intentional since ISPs have a choice for the amount of bandwidth to allocate to download versus upload. It seems likely that overall bandwidth capacity and speeds are increasing due to the continually growing size of the Starlink satellite constellation – now over 2,500. Starlink subscriptions are climbing quickly. The company reported having 145,000 customers at the start of the year and recently announced it is up to 400,000 customers worldwide. This fast growth makes me wonder when Starlink will stop calling the business a beta test.
These speed tests raise a few interesting questions. The first is if these speeds are good enough to qualify Starlink to be awarded the RDOF awards that have now been pending from the FCC for over a year and a half. While these speeds are now approaching the 100 Mbps speed promised by Starlink in its RDOF bids, it's worth noting that the 90 Mbps number is an average. There are some customers seeing speeds of over 150 Mbps while others are seeing only 50 Mbps or even less. I've talked to a number of Starlink customers and what they've told me is that Starlink needs a view of the 'whole sky' from horizon to horizon to operate optimally, and many homes don't have the needed view. This doesn't bode well for the Starlink RDOF awards areas of heavy woods and hills like the awards in western North Carolina.
There is a lot of speculation that Starlink is limiting the number of subscribers in a given geographic area in order to not dilute speed and performance. The RDOF awards require any winning ISP to serve everybody, and there is still a big question about the kinds of speeds that can be delivered for a geographic area that has a lot of subscribers.
The BEAD grant rules also open the door for Starlink and other satellite providers to some extent. While satellite technology is not deemed reliable enough to directly be used for grant awards, the NTIA has also opened the door to using alternate technologies like satellite and fixed wireless using unlicensed spectrum in areas where landline technologies are too costly. Each state will have to decide if grants can be awarded for satellite broadband in such cases, and it seems likely that some states will allow this.
The Ookla article also shows the Starlink average speeds around the globe. Some of the average speeds are much faster than U.S. speeds, and this might be due to smaller countries that cover a smaller and less diverse terrain than the U.S. Here, speeds are likely much higher in the open plains states than for customers located in hills, mountains, and woods. There can't be a technology difference since the same satellites serve around the globe.
There is an interesting app that shows the location of the Starlink satellites. It's fascinating to watch how they circle the globe. What is most striking about the world map is how few satellites there are over the U.S. at any given time. The app shows a few closely packed strings of satellites that are recent launches that haven't yet been deployed to their final orbits.
The skies are going to soon get a lot busier. The original business plan for Starlink was to deploy 11,000 satellites. Jeff Bezos and Project Kuiper have FCC permission to deploy satellites, with launches starting this year. OneWeb, which is now aiming to serve business and government customers, has much of its constellation launched but has yet to begin delivering services. Telesat is still marching slowly forward and has fallen behind due to supply chain issues and funding concerns – but still has plans to have a fleet in place in the next few years. I would imagine that in a few years, we'll see Ookla reports comparing the different constellations.
Tagged BEAD Grants, RDOF, StarLink
The Challenge of Accepting RDOF
I've been wondering lately if some of the RDOF reverse auction winners are having second thoughts about accepting the RDOF awards. It's amazing how much the broadband world has changed since the end of that auction in December 2020.
It's gotten more expensive to build fiber projects over the last year. The supply chain has played havoc with the costs of the raw components needed to build fiber networks. Many clients tell me that the cost of fiber components like conduit are collectively up by 40% or more over the last year. As somebody who has worked through several periods of inflation in the past, there is not a big likelihood that prices will return to the old levels even after the supply chain gets back to normal.
A bigger concern is the cost of labor. The explosion in the volume of fiber construction projects is almost too hard to grasp. The demand for construction crews is going to soon outstrip the number of experienced technicians. That means big challenges for finding and keeping construction crews. Shortages always lead to higher labor costs.
The federal government also layered on a new requirement that didn't exist at the time of the auction. The Buy American Act now applies to infrastructure projects awarded with federal funds after November 18, 2021. These rules will apply to any RDOF winner that is approved by the FCC after that date. These rules don't automatically add to the cost of building a fiber network, but they kill any thoughts of using lower-cost foreign fiber or components. The Act makes it clear that components like fiber and conduit must be 100% sourced to U.S. manufacturers. The new rules also make it seem unlikely that there will be many waivers allowed – these new rules have teeth.
The biggest kick in the teeth to an RDOF winner are the huge new grants are offering far more funding than anybody won in the RDOF auction. The giant BEADS grants can fund up to 75% of the cost of building a network for a rural project. Grants like ReConnect also have a 75% grant option. An RDOF winner that was unopposed in the auction got 60% of the FCC's bid price – and that price was not set at the full cost of building a network but based upon some screwball federal cost models. An electric cooperative that won the RDOF auction could get a lot more funding from ReConnect grants or the upcoming BEAD grants – but nobody in the industry knew this at the time of the RDOF auction.
Another issue to consider is that RDOF winners might have missed out on the opportunity for matching state grants. While some states might make matching grants to go along with RDOF awards, many will not. That means the RDOF funding is all such winners will see.
What I've never figured out is why some RDOF winners bid the awards down to ridiculously low levels. There are places where bidders accepted RDOF awards under 10% of the expected cost of building a network – in some cases as low as 1%. In one county I'm familiar with, an RDOF bidder accepted less than 5% of the cost of building the network. This is a county with some of the easiest costs in the country to bury fiber. But this county is typical of rural areas and is sparsely populated, so the cost per passing is still high. Even considering the relatively low construction costs in the area, I couldn't make a business case in this county for accepting less than 50% outside funding to make the project viable. I'm still scratching my head, wondering how this RDOF winner expects to make a business plan out of such a low award.
It's not hard to imagine that some RDOF winners are having second thoughts. There are penalties for walking away from RDOF, but those penalties might be a lot smaller than the downside of being forced to build a rural network that will never generate enough revenue to cover the cost of construction. I was mystified by some of the winning RDOF bids in 2020 – and those bids make a lot less sense when viewed from 2022.
Tagged RDOF, supply chain


text:
'9/11 Is Still Killing': Nearly 10,000 Americans Have Had Cancer Due to WTC Dust
© NASA. Frank Culbertson
The Federal World Trade Center Health Program, established in 2010 to provide medical benefits to certain groups affected by the terrorist attacks on September 11, 2001, has said the number of people who have died from cancers connected to the attacks is approaching 10,000.
The New York Post reported Saturday that that 9,795 people have had cancers deemed 9/11-related, including first responders, residents, students and people who worked in lower Manhattan where the twin 110-story towers collapsed. Of those, 420 have died.
CC BY 2.0 / GlynLowe.com / World Trade Center 9-11 Tribute of Light 2012
Schneiderman Warns Trump: Don't Mess With WTC Health Program
"9/11 is still killing," John Feal, an advocate for WTC responders, told the Post.
Over 11,000 firefighters, under the aegis of the Fire Department of New York City (FDNY), operated a continuous rescue and recovery effort at the site in the days and weeks after the collapse, which itself killed 2,606 people, not counting those onboard the two aircraft that crashed into the towers.
Epidemiology studies have shown that both rescue and recovery workers who worked at the site after the collapse have significantly higher rates of thyroid cancer, skin melanoma and bladder cancer than the general population, the Post noted. Other cancers shown by non-responders affected by the dust were breast cancer, non-Hodgkin's lymphoma, leukemia and other blood cell disorders.
Michael Crane, medical director of the WTC Health Program at Mount Sinai Hospital, told the Post, "We get these referrals 15 to 20 times a week."
© AP Photo / Chao Soi Cheong
US Airlines, World Trade Center Owner Agree $95.2mln Payout for 9/11 Damage
A study published in the New England Journal of Medicine on the one-year anniversary of the attacks described what its authors called "World Trade Center cough," which it defined as "a persistent cough that developed after exposure to the site and was accompanied by respiratory symptoms severe enough to require medical leave for at least four weeks." It documented hundreds of firefighters who suffered respiratory symptoms following their working at Ground Zero.
Still, a major problem encountered by investigators is that one in four Americans will develop cancer of some kind at some point in their lives, Scientific American noted, so being able to specifically attribute specific ailments to a 9/11-associated etiology is extremely difficult.
That difficulty is compounded by the fact that, despite the towers having been constructed between 1968 and 1973, a time when many building materials and techniques were used that are now banned, such as asbestos, the US government has been conspicuously phlegmatic in its investigation of the deleterious health effects of exposure to the site.
CC0 / NNSA / Nevada Site Office / The BADGER explosion
Cancer Study May Win Fallout Victims Compensation for First US Nuclear Test
Few air samples were taken of the acrid miasma that billowed over lower Manhattan and Brooklyn, but of those that were taken, 25 percent showed asbestos levels above the 1 percent threshold that indicates "significant risk," the US Environmental Protection Agency (EPA) said in a 2003 report.
However, in the immediate aftermath of the attack, EPA administrator Christie Whitman told New Yorkers there was no significant levels of asbestos in the dust cloud, Scientific American noted.
CC BY 2.0 / 9/11 Photos / 9/11 WTC Photo
9/11 World Trade Center Attack
A 2007 report by the EPA came to a different conclusion, noting that the air near the smoldering site had "the highest ambient measurements of dioxin ever recorded anywhere in the world," at least 100 times higher than those found downwind of a garbage incinerator, SA noted.
© AP Photo/ Jay Laprete
Yikes! Tweens' Retailer Caught Selling Makeup Contaminated With Asbestos
Bizarrely, that same report concluded, "Except for inhalation exposures that may have occurred on 9/11 and a few days afterwards, the ambient air concentration data suggest that persons in the general population were unlikely to suffer short-term or long-term adverse health effects caused by inhalation exposures."
The north tower stood for 102 minutes and the south tower for 56 minutes after being crashed into by Boeing 7-series airliners. In that time, 91,000 liters of jet fuel consumed the upper contents of the towers in a ferocious blaze about 1,000 degrees Celsius. But after the towers fell, fires smoldered in the ruins for another four months, until December 19, SA noted. Those fires burned a host of materials toxic to humans, including lead in cables and polychlorinated biphenyls (PCBs) in electrical transformers. In addition, the collapse itself dispersed an enormous amount of building materials, from cement, steel, gypsum from drywall and glass to synthetic rugs, asbestos used for fireproofing and all manner of plastics.
"The debris pile acted like a chemical factory," Thomas Cahill, a University of California-Davis professor emeritus of physics and atmospheric science and research professor in engineering, wrote in a 2003 study. "It cooked together the components of the buildings and their contents, including enormous numbers of computers, and gave off gases of toxic metals, acids and organics for at least six weeks."
© RIA Novosti.
New helicopter footage of World Trade Center attack released (Natural sound)
The Center for Disease Control and Prevention's National Institute for Occupational Safety and Health (NIOSH) said in 2011 that "a determination cannot be made to propose a rule to add cancer, or a type of cancer, to the List of WTC-Related Health Conditions at this time." The CDC's decision is vital to getting those affected covered by the James Zadroga 9/11 Health and Compensation Act of 2010, a law that provides health services to certain first responders and volunteers affected by exposure to site materials.
The law has been famously controversial, failing to pass for four years after being introduced in Congress in 2006, with lawmakers equivocating over concerns about how expansive the enrollment would be and how the program would be funded. At one point in 2010, comedian Jon Stewart turned his evening TV program into an "advocacy journalism" platform, urging Congressional support for the bill.
Monsanto Ordered to Pay $289Mln to Dying Man for Causing Cancer – Reports
Chinese Heart Drugs Linked to Cancer Recalled Across Europe
Russian Researcher Discusses Role of Biomarkers in Treating Cancer
chemical exposure, rise, investigation, cancer, September 11, FDNY, CDC, World Trade Center, New York city

redpajama_set_name: RedPajamaCommonCrawl


text:
Q: How to make multiple radioButtons but only one is always selected where the first is default? I work an Objective-C project and trying to build a multiple radio buttons. Shortly I want to make multiple radioButtons but only one is always selected where the first is default.
I started to try with 2 buttons but I could not achieve exactly what I want. I hope there are nice ways to do that. I am okay with extension as well.

A: you can group UI elements by placing them in UIView and use an KVO observer to take advantage of the extra code.
@interface ViewController ()
@property (nonatomic) UIView *group;
@end

@implementation ViewController
- (void)viewDidLoad {
    [super viewDidLoad];
    [self createGroupWithRadios:3 andSelectIndex:0];
}

//a context to make KVO much easier to catch (and less string compare'y)
static void * kRadioGroupContext = &kRadioGroupContext;

-(void)createGroupWithRadios:(int)amount andSelectIndex:(int)idx {
    CGFloat h = 30.0;
    _group = [[UIView alloc] initWithFrame:CGRectMake(0, 0, 100, h*amount)];
    for (int i=0; i<amount; i++) {
        UIButton *radio = [UIButton buttonWithType:(UIButtonTypeSystem)];
        radio.tag = i;
        radio.selected = i==idx;
        { //style stuff
            radio.frame = CGRectMake(0, h*i, 100, h);
            [radio setTitle:@"off" forState:UIControlStateNormal];
            [radio setTitle:@"on" forState:UIControlStateSelected];
            [radio setTitleColor:UIColor.blackColor forState:UIControlStateNormal];
            [radio setTitleColor:UIColor.redColor forState:UIControlStateSelected];
            //[radio setImage:[UIImage imageNamed:@"active"] forState:UIControlStateSelected];
            //[radio setImage:[UIImage imageNamed:@"inactive"] forState:UIControlStateNormal];
        }
        [radio addTarget:self action:@selector(radioButtonPressed:) forControlEvents:UIControlEventTouchUpInside];
        [_group addSubview:radio];
    }
    [self.view addSubview:_group];

    //you can use _group.tag to keep which one is selected and observe it
    _group.tag = idx;
    [_group addObserver:self forKeyPath:@"tag" options:(NSKeyValueObservingOptionNew) context:kRadioGroupContext];
}

-(void)radioButtonPressed:(UIButton*)sender {
    _group.tag = sender.tag;
    for (int i=0; i<_group.subviews.count; i++) {
        UIButton *radio = _group.subviews[i];
        radio.selected = radio.tag==sender.tag;
    }
}

-(void)observeValueForKeyPath:(NSString *)keyPath ofObject:(id)object change:(NSDictionary<NSKeyValueChangeKey,id> *)change context:(void *)context {
    if (context == kRadioGroupContext) {
        // do something when a new radio is selected
        NSLog(@"selected Radio %lu", _group.tag);
    }
}

A: As mentioned UIControl is a subclass of UIView, which means you can use UIControl to group your UIButtons together also. The advantage is adding a Target is easy to catch when there is a new selection made. Downside is you have to think a bit more about styling/layout because that is fixed in code and altering needs more care. The example below uses an NSArray of NSStrings to be spread as titles inside the UIControl's Buttons. So the NSArray count defines how much Buttons are generated in frame height. Should be easy to build multiple choice forms with this.
//ButtonSelectGroup.h
#import <UIKit/UIKit.h>

NS_ASSUME_NONNULL_BEGIN

@interface ButtonSelectGroup : UIControl
-(instancetype)initWithFrame:(CGRect)frame andTitles:(NSArray<NSString*>*)titles preValue:(NSInteger)idx;
@property (nonatomic) NSInteger value;
-(void)setTitles:(NSArray<NSString *> * _Nonnull)titles;
@end

NS_ASSUME_NONNULL_END

and
//ButtonSelectGroup.m
#import "ButtonSelectGroup.h"

@interface ButtonSelectGroup () {
    NSInteger oldValue;
}
@end

@implementation ButtonSelectGroup
-(instancetype)initWithFrame:(CGRect)frame andTitles:(NSArray<NSString*>*)titles preValue:(NSInteger)idx {
    if (!(self=[super initWithFrame:frame])) return nil;
    [self createGroupWithPreSelectIndex:idx andTitles:titles];
    return self;
}
-(void)createGroupWithPreSelectIndex:(NSInteger)idx andTitles:(NSArray<NSString*>*)titles {
    NSInteger amount = titles.count;
    CGFloat h = self.frame.size.height / amount;
    for (NSInteger i=0; i<amount; i++) {
        UIButton *radio = [UIButton buttonWithType:(UIButtonTypeSystem)];
        radio.tag = i;
        radio.selected = i==idx;
        { //style stuff
            radio.frame = CGRectMake(0, h*i, 100, h);
            [radio setTitle:titles[i] forState:UIControlStateNormal];
            [radio setTitle:titles[i] forState:UIControlStateSelected];
        }
        [radio addTarget:self action:@selector(radioButtonPressed:) forControlEvents:UIControlEventTouchUpInside];
        [self addSubview:radio];
    }
    self.value = idx;
}
-(void)radioButtonPressed:(UIButton*)sender {
    oldValue = _value;
    for (NSInteger i=0; i<self.subviews.count; i++) {
        UIButton *radio = self.subviews[i];
        radio.selected = radio.tag==sender.tag;
    }
    _value = sender.tag;
    if (_value != oldValue) [self sendActionsForControlEvents:(UIControlEventValueChanged)];
}
-(void)setTitles:(NSArray<NSString *> *)titles {
    for (NSInteger i=0; i<self.subviews.count && i<titles.count; i++) {
        UIButton *radio = self.subviews[i];
        [radio setTitle:titles[i] forState:UIControlStateNormal];
        [radio setTitle:titles[i] forState:UIControlStateSelected];
    }
}
@end

Then use #import "ButtonSelectGroup.h" the following way from your ViewController.
-(void)viewDidLoad {
    [super viewDidLoad];
    ButtonSelectGroup *group = [[ButtonSelectGroup alloc] initWithFrame:CGRectMake(0, 0, 100, 300) andTitles:@[@"even",@"donald",@"duck",@"would",@"concede"] preValue:0];
    [self.view addSubview:group];
    [group addTarget:self action:@selector(singularChoice:) forControlEvents:(UIControlEventValueChanged)];
    // and changing all titles again if you wish
    //group.titles = @[@"but",@"not",@"orangeman"];
}
-(void)singularChoice:(id)sender {
    ButtonSelectGroup* group = (ButtonSelectGroup*)sender;
    UIButton *btn = group.subviews[group.value];
    NSLog(@"groups selection = %lu %@",group.value, btn.titleLabel.text);
}

redpajama_set_name: RedPajamaStackExchange


as if he were nothing.
Did you see the Hipster Nativity Set this Christmas?
Earlier this week, the news reported how it's the talk of Christmas 2018.
The camera zoomed in showing the 3 wise men as Amazon Prime Deliverymen on Segways with presents in hand, the shepherd as a young guy missing what's going on as he's busy posting on social media with his 100% organic, gluten-free feed-eating cow and sheep in a Christmas sweater sitting by his side. Next, they showed a man-bun boasting Joseph taking a selfie of himself with Mary posed in a little risqué outfit with her t-shirt off the shoulder, bra-strap and a little more showing.
Oh ya, baby Jesus was in the solar-paneled manger too, but the newscasters weren't really talking about Him.
The discussion surrounded whether or not it was appropriate to have a nativity set with updated "characters". One man on the street was interviewed commenting how he felt each generation depicts the nativity with their own cultural relevance or some other hogwash like that. It's questionable what nativity set that guy's been putting out each Christmas but ours have always portrayed people in clothing suiting the era when Christ was born with baby Jesus wrapped in swaddling cloths.
This modern-day version of the nativity wasn't an issue for me, although I wish they had made Mary a little more modestly dressed, I actually thought it was clever and could be a good conversation starter but what bothered me was how a whole segment of the news could actually be discussing the scene of Jesus' birth and yet He wasn't the focus. In fact, Jesus was barely mentioned.
They completely missed the Christ in CHRISTmas!
For centuries people have been missing the Christ in CHRISTmas.
Scripture is full of verses talking about the hope of Israel; a coming Messiah, the savior who would bring peace to those who followed Him. Jewish Rabbis and faithful Hebrew people have studied the Tanakh (Old Testament) and made lists of what they thought the Messiah; the Christ would be like and how they would recognize Him from any other good person. As Christians, we have accepted Jesus (that's the English version of His name), to be the fulfillment of all the ancient prophecies.
I've also come to understand through reading Joe Amaral's book, The Story In The Stars how Jesus also fulfilled God's prophetic power point in the sky: displayed through the constellations God designed at creation; from the virgin woman Virgo to the Aries ram.
But if your brain works at all like mine, you've probably wondered, Why, if Jesus was the Messiah God gave, then why are there Jewish people today still searching for the Christ? So, were we wrong or did they miss their Messiah when He came… and why did they? As you can see, I was probably one of those toddlers who drove their parents' crazy asking, "But Why?" The Bible does teach that when Jesus was born; as those original style nativity sets depict, lived on the earth as a carpenter and then became a miracle-working minister many Jewish people and Priests did follow Him1, but not all.
I could never understand how Hebrew people today weren't able to connect-the-dots left in the Old Testament to ascertain the truth of Jesus' identity, that was until my friend shared this YouTube video called The Forbidden Chapter in the Tanakh where a young Jewish guy in Israel explains how after Jesus lived, the Rabbi's took Isaiah 53 out of the Scripture listing, read by Jewish people. This portion of Scripture is the prophet Isaiah's most detailed record about the coming Saviour.
I understood how Jewish people could miss Jesus being the Christ of CHRISTmas.
As I watched the video (shown below), my faith of Jesus as Lord and savior of my life was strengthened.
At the same time, this news brought on such a deep sense of sadness to recognize how millions of Jewish people for over two centuries have missed out on knowing Jesus as I do because their eyes have been blinded from the truth.
It brings my mind back to the news report on The Hipster Nativity and how people are still blinded from the truth of who Jesus is today. We can be so distracted by all our stuff the wise men/delivery guys bring, missing Jesus right in front of our eyes like the shepherd or focused on ourselves in this selfie generation. Don't let that be your reality this year.
Don't let the "trappings of this world" trip you up. Open your eyes and heart to make room for Jesus, so you don't miss Him this year!
In the Tanakh (Old Testament for us).
If you liked the refreshing in this #SoulH2O devotion, you'll love my latest Soul H2O Devotional book: 40 Thirst Quenching Devotions for Women.
Post in the Comment Section below and bolster the faith of someone else!
I hadn't seen that 'modern' nativity 'til now. Wow! Yes, may we never miss Him in all seasons. Happy New Year!
I wouldn't have seen it if not for the newscast. It's a crazy world! Happy New Year!


This week on The Happy Page: At least half of the country is now socked-in by Winter Storm Harper. You have been warned by every weather person on television to stay indoors. Time for something rich, warm, and yummy!
If you absolutely have to go out – and do not go out just to buy pecans! – please be very careful. Because you know there's always that one person on the road who doesn't see the need to be.


Agência FAPESP – Um estudo publicado na revista Nature Communications revelou que a bactéria Salmonella enterica é capaz de produzir uma proteína muito semelhante à alfa-2-macroglobulina humana, que desempenha um papel-chave em nosso sistema imunológico.
A hipótese levantada pelos pesquisadores do Instituto de Biologia Estrutural (IBS) de Grenoble, na França, é de que também nas bactérias as macroglobulinas poderiam fazer parte de um sistema de defesa rudimentar. Se a teoria for confirmada por estudos futuros, essas proteínas podem se tornar alvos para o desenvolvimento de novos antibióticos.
"O mais fascinante é que as macroglobulinas são proteínas imensas, formadas por quase 1.700 resíduos de aminoácidos. Para a bactéria sintetizar uma molécula tão grande é porque ela deve ter um papel muito importante", afirmou a brasileira Andréa Dessen, pesquisadora do IBS e coordenadora, no Laboratório Nacional de Biociência (LNBio), em Campinas, de um projeto apoiado pela FAPESP por meio do programa São Paulo Excellence Chairs (SPEC).
No organismo humano, a missão da alfa-2-macroglobulina é detectar e neutralizar proteases secretadas por microrganismos invasores, disse a pesquisadora. As proteases são enzimas que quebram as ligações entre os aminoácidos das proteínas.
"A macroglobulina impede, dessa forma, que as proteases dos invasores destruam os tecidos do organismo, o que permitiria a infecção de tecidos mais profundos", explicou.
Além disso, a alfa-2-macroglobulina também se liga a proteases que participam do processo de coagulação sanguínea, evitando que proteínas importantes sejam destruídas indevidamente.
Em estudos anteriores, nos quais o genoma de diversas espécies de bactérias foi sequenciado, pesquisadores alemães já haviam observado a presença do gene da macroglobulina. No IBS, o grupo liderado por Dessen já havia feito a caracterização bioquímica da proteína produzida pelas espécies Escherichia coli e Pseudomonas aeruginosa.
"Agora, de maneira inédita, estudamos a estrutura tridimensional da macroglobulina secretada pela Salmonella enterica por uma técnica conhecida como cristalografia de raios X, que permite visualizar detalhes em nível atômico. E pudemos confirmar que, de fato, ela é muito parecida com a macroglobulina humana", contou Dessen.
De acordo com a pesquisadora, a descoberta reforça a hipótese de que a alfa-2-macroglobulina tem o papel de proteger a bactéria das proteases secretadas por outras bactérias ou pelo organismo do hospedeiro que ela tenta infectar.
"Em um modelo de camundongo, pesquisadores canadenses mostraram que cepas da bactéria Pseudomonas aeruginosa que não produzem macroglobulina têm menor capacidade de causar doença, ou seja, são menos virulentas. A proteína parece dar uma vantagem à bactéria na hora de colonizar o hospedeiro, mas ainda não sabemos exatamente por quê", disse.
Em um braço da pesquisa que está sendo conduzido no LNBio, com apoio da FAPESP e orientação de Dessen, a pós-doutoranda francesa Samira Zouhir investiga a estrutura da macroglobulina sintetizada por bactérias da espécie Pseudomonas aeruginosa – causadora de diversos casos de infecção hospitalar.
"Se conseguirmos desvendar a estrutura tridimensional da proteína, isso nos dará pistas sobre sua função no processo infeccioso", disse Dessen.
Quando o papel das macroglobulinas estiver bem compreendido em diferentes espécies de bactérias, acrescentou, essas proteínas poderão se tornar alvo para o desenvolvimento de novos antibióticos.
"Também há pesquisas interessantes em modelo de camundongo mostrando que a aplicação de alfa-globulina humana pode oferecer proteção contra a sepse. Há várias possibilidades de tratamento a serem exploradas", avaliou a pesquisadora.
O artigo Structure of a bacterial α2-macroglobulin reveals mimicry of eukaryotic innate immunity (doi: 10.1038/ncomms5917), pode ser lido em www.nature.com/ncomms/2014/140915/ncomms5917/full/ncomms5917.html.
Summary: Artificial sweeteners have long been promoted as diet and health aids. But breaking research shows that these products may be leading to the very diseases they were said to help prevent: scientists have discovered that, after exposure to artificial sweeteners, our gut bacteria may be triggering harmful metabolic changes.
Artificial sweeteners — promoted as aids to weight loss and diabetes prevention — could actually hasten the development of glucose intolerance and metabolic disease, and they do so in a surprising way: by changing the composition and function of the gut microbiota — the substantial population of bacteria residing in our intestines. These findings, the results of experiments in mice and humans, were published September 17 in Nature. Dr. Eran Elinav of the Weizmann Institute of Science's Department of Immunology, who led this research together with Prof. Eran Segal of the Department of Computer Science and Applied Mathematics, says that the widespread use of artificial sweeteners in drinks and food, among other things, may be contributing to the obesity and diabetes epidemic that is sweeping much of the world.
For years, researchers have been puzzling over the fact that non-caloric artificial sweeteners do not seem to assist in weight loss, with some studies suggesting that they may even have an opposite effect. Graduate student Jotham Suez in Dr. Elinav's lab, who led the study, collaborated with lab member Gili Zilberman-Shapira and graduate students Tal Korem and David Zeevi in Prof. Segal's lab to discover that artificial sweeteners, even though they do not contain sugar, nonetheless have a direct effect on the body's ability to utilize glucose. Glucose intolerance — generally thought to occur when the body cannot cope with large amounts of sugar in the diet — is the first step on the path to metabolic syndrome and adult-onset diabetes.
The scientists gave mice water laced with the three most commonly used artificial sweeteners, in amounts equivalent to those permitted by the U.S. Food and Drug Administration (FDA). These mice developed glucose intolerance, as compared to mice that drank water, or even sugar water. Repeating the experiment with different types of mice and different doses of the artificial sweeteners produced the same results — these substances were somehow inducing glucose intolerance.
The researchers treated mice with antibiotics to eradicate many of their gut bacteria; this resulted in a full reversal of the artificial sweeteners' effects on glucose metabolism. Next, they transferred the microbiota from mice that consumed artificial sweeteners to "germ-free," or sterile, mice — resulting in a complete transmission of the glucose intolerance into the recipient mice. This, in itself, was conclusive proof that changes to the gut bacteria are directly responsible for the harmful effects to their host's metabolism. The group even found that incubating the microbiota outside the body, together with artificial sweeteners, was sufficient to induce glucose intolerance in the sterile mice. A detailed characterization of the microbiota in these mice revealed profound changes to their bacterial populations, including new microbial functions that are known to infer a propensity to obesity, diabetes, and complications of these problems in both mice and humans.
The findings showed that many — but not all — of the volunteers had begun to develop glucose intolerance after just one week of artificial sweetener consumption. The composition of their gut microbiota explained the difference: the researchers discovered two different populations of human gut bacteria — one that induced glucose intolerance when exposed to the sweeteners, and one that had no effect either way. Dr. Elinav believes that certain bacteria in the guts of those who developed glucose intolerance reacted to the chemical sweeteners by secreting substances that then provoked an inflammatory response similar to sugar overdose, promoting changes in the body's ability to utilize sugar.
Summary: The presence of Clostridia, a common class of gut bacteria, protects against food allergies, a new study in mice finds. The discovery points toward probiotic therapies for this so-far untreatable condition. Food allergies affect 15 million Americans, including one in 13 children, who live with this potentially life-threatening disease that currently has no cure, researchers note.
The presence of Clostridia, a common class of gut bacteria, protects against food allergies, a new study in mice finds. By inducing immune responses that prevent food allergens from entering the bloodstream, Clostridia minimize allergen exposure and prevent sensitization — a key step in the development of food allergies. The discovery points toward probiotic therapies for this so-far untreatable condition, report scientists from the University of Chicago, Aug 25 in the Proceedings of the National Academy of Sciences.
Although the causes of food allergy — a sometimes deadly immune response to certain foods — are unknown, studies have hinted that modern hygienic or dietary practices may play a role by disturbing the body's natural bacterial composition. In recent years, food allergy rates among children have risen sharply — increasing approximately 50 percent between 1997 and 2011 — and studies have shown a correlation to antibiotic and antimicrobial use.
"We've identified a bacterial population that protects against food allergen sensitization," Nagler said. "The first step in getting sensitized to a food allergen is for it to get into your blood and be presented to your immune system. The presence of these bacteria regulates that process." She cautions, however, that these findings likely apply at a population level, and that the cause-and-effect relationship in individuals requires further study.
Finally, the Hadza gut microbe community is a unique configuration with high levels of bacteria, like Treponema, that in western populations are often considered signs of disease, and low levels of other bacteria, likeBifidobacterium, that in western populations are considered "healthy". However, the Hadza experience little to no autoimmune diseases that would result from gut bacteria imbalances. Therefore, we must redefine our notions of "healthy" and "unhealthy" bacteria, since these distinctions are clearly dependent on the environment we live in. Genetic diversity of bacteria is likely the most important criterion for the health and stability of the gut microbiome.
Oct. 24, 2013 — Human genes in immunity-related pathways are likely associated with the composition of an individual's microbiome, which refers to the bacteria and other microbes that live in and on the body, scientists reported today, Oct. 24, at the American Society of Human Genetics 2013 annual meeting in Boston.
"These genes are significantly enriched in inflammatory and immune pathways and form an interaction network highly enriched with immunity-related functions," said Ran Blekhman, Ph.D., Assistant Professor, Department of Genetics, Cell Biology, and Development at the University of Minnesota, Minneapolis.
The study is the first genome-wide and microbiome-wide investigation to identify the interactions between human genetic variation and the composition of the microbes that inhabit the human body.
The skin, genital areas, mouth, and other areas of the human body, especially the intestines, are colonized by trillions of bacteria and other microorganisms. "Shifts in the composition of the species of the microbes have been associated with multiple chronic conditions, such as diabetes, inflammatory bowel disease and obesity," noted Dr. Blekhman.
Dr. Blekhman and his collaborators found evidence of genetic influences on microbiome composition at 15 body sites of 93 people surveyed. "We found in our study that genetic variation correlated with the microbiome at two levels," he said.
At the individual level, the mathematical procedure known as principal component analysis demonstrated that genetic variation correlated with the overall structure of a person's microbiome.
At the species level, potential correlations between host genetic variation and the abundance of a single bacterial species were identified, said Dr. Blekhman, who conducted much of the research while a scientist in the lab of Andrew G. Clark, Ph.D., the Jacob Gould Schurman Professor of Population Genetics in the Department of Molecular Biology and Genetics at Cornell University, Ithaca, NY. Dr. Clark is the senior author of the abstract.
To identify the bacterial species that inhabited each human body site, the researchers mined sequence data from the Human Microbiome Project (HMP), an international program to genetically catalog the microbial residents of the human body.
Using a systems-level association approach, the researchers showed that variation in genes related to immune system pathways was correlated with microbiome composition in the 15 host body sites.
To shed light on the evolutionary history of the symbiosis between humans and their microbiomes, the researchers analyzed sequencing data from the 1000 Genomes Project, which is designed to provide a comprehensive resource on human genetic variation.
They found that the genes in the pathways linked to the composition of an individual's microbiome vary significantly across populations. "Moreover, many of those genes have been shown in recent studies to be under selective pressure," said Dr. Blekhman.
"The results highlight the role of host immunity in determining bacteria levels across the body and support a possible role for the microbiome in driving the evolution of bacteria-associated host genes," he added.
Dr. Blekhman is currently investigating the combined role of host genetics and the microbiome in influencing an individual's susceptibility to such diseases as colon cancer. His goal is to unravel the interaction between host genomic variation and the gut microbiome in colon cancer incidence, evolution and therapeutic response.