You might recall that Aereo founder Chaitanya Kanojia’s attempt to disrupt the TV industry ran face-first into an army of broadcaster lawyers and a notably ugly ruling by the Supreme Court. Undaunted, Kanojia returned with a new plan to try and disrupt the broken U.S. broadband industry. But that plan isn’t going so hot either. Kanojia’s new […]

Dear community The GNU Health federation community server (federation.gnuhealth.org) has been updated! These are some of the main improvements: - NGINX and WSGI: The Hospital Management component instance is now running behind uWSGI and NGINX. - HMIS 4.2 Release Candidate 2: We are very close to HMIS 4.2 stable. This pre-release version will help us to test the upcoming features and find bugs before the release. :) - Secure connection: You can test the demo web client using TLS. Please check the demo database section on the GNUHealth Wikibooks. - Thalamus, the GNU Health Federation message and authentication server still runs on Gunicorn, also using https. More info and resources: Wikibooks: https://en.wikibooks.org/wiki/GNU_Health GNUHealth documentation portal: https://www.gnuhealth.org/docs/ Mastodon:  https://mastodon.social/@gnuhealth Matrix: https://app.element.io/#/room/#gnuhealth-space:matrix.org Happy and healthy hacking! Luis

Least year, Samsung released the T7 Shield -- a fast and durable USB-C SSD. At the time, the portable drive was offered in three colors (beige, black, and blue) plus two capacities (1TB and 2TB). Today, Samsung adds a new 4TB capacity option to the T7 Shield lineup. Yes, you can now get the drive with double the storage of the previous top capacity. Unfortunately, this 4TB variant is only available in black -- fans of beige and blue are out of luck with this capacity. ALSO READ: Satechi launches Pro Hub Slim for M2 Apple MacBook laptops Jose Hernandez,… [Continue Reading]

In this article, we are going to show you five plug-ins for your Neovim system to further increase your productivity.   The post Discover 5 Interesting Plug-Ins for Your Neovim System appeared first on Linux Today.

Red Hat on Tuesday that it’s partnered with Oracle to bring Red Hat Enterprise Linux to Oracle Cloud Infrastructure. Although this doesn’t surprise me at… The post Red Hat Beds With Oracle in New Cloud Deal appeared first on FOSS Force.

Kees Cook has posted a detailed document describing the work to improve safety of flexible-length arrays in the kernel. Converting such codebases to use “modern” language features, like those in C99 (still from the prior millennium), can be a major challenge, but it is an entirely tractable problem. This post is a deep dive into an effort underway in the Linux kernel to make array index overflows (and more generally, buffer overflows) a thing of the past, where they belong. Our success hinges on replacing anachronistic array definitions with well-defined C99 flexible arrays. This work has been covered here as well.

I've seen this question enough times recently to decide to just write up a blog post on it and point people here. :) If you are running Fedora 38 (currently rawhide, but will be branching off soon) and you are getting errors like this from dnf and/or rpm: Running transaction check error: rpmdbNextIterator: skipping h# 47749 Header V4 DSA/SHA1 Signature, key ID 7fac5991: BAD Header SHA256 digest: OK Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 47749 Header V4 DSA/SHA1 Signature, key ID 7fac5991: BAD Header SHA256 digest: OK Header SHA1 digest: OK This post is for you. What is going on here? And how can you get around the problem? Well, what happened is that rpm used to have internal code to handle signatures on packages. This code was really something rpm didn’t want to have to maintain, so they switched recently to using sequoia, which is a new gnupg handling project written in rust. With this switch, sequoia actually honors the site wide fedora crypto policy (which the internal old rpm version did not). Back in Fedora 33, the distro wide crypto policy was updated to disallow SHA-1 as a signature algorithm. See https://fedoraproject.org/wiki/Changes/StrongCryptoSettings2 for more information. You might wonder why, if Fedora changed the distro wide crypto policy to disallow SHA-1 in signatures, why didn’t they update things so nothing used SHA-1 now? Well, the short answer is: they did. No rpms that Fedora produces now use SHA-1 signatures. However, some third-party rpms do. One of the big ones that many people are hitting is google’s “chrome” web browser. There’s probably others. Now that we know _why_ this is happening, what can you do? Well, first you need to do something so dnf and rpm allows you to remove/update/change your package set. You can do this by (temporarily!) allowing SHA-1 Signatures with: sudo update-crypto-policies --set DEFAULT:SHA1 rpm and dnf should now work for you again. You might remove packages that have SHA-1 signatures and switch to alternatives. Or wait until google updates their signing key (the current one is from 2007). Once you have done what you need to do you can set the policy back to it’s sane default: sudo update-crypto-policies --set DEFAULT

Patent trolls make patents, and argue over them. They don’t have to ever make the thing described in their patents, if it’s even possible to determine what those things are. Instead, they generate legal threats and waste the time and money of companies that do do these things.  This month’s Stupid Patent of the Month is a […]

GNOME has published the results of its last year August user survey. The findings are expected and telling. Here they are. The post GNOME Survey Results: A Window Into User Behavior appeared first on Linux Today.

In this tutorial, we will show you how to install the Nano text editor on Rocky Linux 9. For those of you who didn’t know, Nano is a simple, easy-to-use text editor that is commonly installed by default on Linux ... The post How To Install Nano Text Editor on Rocky Linux 9 appeared first on idroot.

For years now, I’ve talked about the impossibility of doing content moderation well at scale. I know that execs at various tech companies often point to my article on this, and that includes top executives at Meta, who have cited my work on this issue. But it still amazes me when those companies act as […]

Image comes from https://www.nvidia.com/en-us/about-nvidia/legal-info/logo-brand-usage/ Some time ago I got borrowed NVIDIA GeForce GTX 1070 from my employer (Red Hat) and I finally managed to put it to a workstation instead of my own AMD RX 6600 XT. I installed proprietary drivers from rpmfusion and to my surprise everything worked smoothly (except Atom on XWayland). Both Wayland and X11 Gnome sessions popped up, Firefox picked up HW accelerated backend (WebRender) with DMABuf support so it’s time to check VA-API. Thanks to nvidia-vaapi-driver by Stephen “elFarto” Firefox may directly decode video on NVIDIA hardware. The driver translates VA-API calls from Firefox to VPDAU used by NVIDIA. I think you also need a decently fresh NVIDIA drivers which supports DMABuf (which is used to transfer decoded images between Firefox processes and render them as GL textures). I hit three bumps on the road. First one is Firefox RDD sandbox. Firefox runs media decode in extra process (RDD) which restricts where decoder can access. It was adjusted by Mozilla folks for VA-API decode on Intel/AMD but NVIDIA needs some extra tweaks. Right now you need to disable the sanbox by MOZ_DISABLE_RDD_SANDBOX=1 env variable. Next one is a bug in recent NVIDIA 525 driver series (which I got from rpmfusion) and I needed to use direct mode (whatever it is). Last issue may be in Firefox itself. Broken graphics hardware may freeze whole browser on start or spread coredumps on every start. That’s being worked on as Bug 1813500 and Bug 1787182. There’s a complete how-to for Firefox/NVIDIA/Fedora 37 available on Fedora wiki. Nvidia-vaapi-driver playback performance is similar to what I see on AMD/Intel. It also correctly handles decoding of intermediate frames which is recent AMD NAVI2 bug (Bug 1772028, Bug 1802844) so the playback is smooth and I haven’t seen any glitches or CPU usage peaks. There are few options for NVIDIA users how to run it. If you have a workstation (or laptop) with one NVIDIA graphics card, it’s quite simple. On Fedora 37 you boot on noveau drivers and then install NVIDIA drivers from rpmfusion. With the proprietary drivers both Wayland and X11 Gnome sessions work fine (anyone to test KDE?) and hardware acceleration is enabled. A bit different scenario comes with integrated Intel device and secondary NVIDIA one. I don’t see any reason why to use NVIDIA as Intel works pretty well with Wayland, VA-API and X11/EGL. But if you really want to set NVIDIA as primary, X11 may be better for you. Wayland on secondary NVIDIA GPU is supported by Sway Wayland compositor only which is a bit geeky (or I’m just too lazy to learn new shortcuts and get used to a new environment). Anyway, if you need to use NVIDIA as your primary GPU, there’s a hope for you (and it’s not due to me). Give it a try and report eventual bugs at Mozilla NVIDIA VA-API bug tracker.

In the last week, a number of dangerous and conspiracy-driven attacks were made against EFF board member Gigi Sohn, an eminently qualified nominee to the Federal Communications Commission. These attacks attempt to twist EFF's long-held positions and commitments into dog whistles against Ms. Sohn. We’d like to set the record straight. First, we’ve seen some outlandish headlines about EFF’s 2020 recognition of Danielle Blunt, a leader in the technology policy space and advocate for sex workers, because she is a professional dominatrix. Ms. Blunt is  one of the co-founders of Hacking//Hustling, a collective of sex workers and others working at the intersection of tech and social justice to interrupt state surveillance and violence facilitated by technology. Through that work, Ms. Blunt is an expert on the impacts of the censorship law FOSTA-SESTA, and on how content moderation affects the movement work of sex workers and activists. No one is more aware of the way that the power imbalances of the real world permeate online, and is more poised to act, than she is. Second, much has been made about EFF’s strong and continued opposition to FOSTA-SESTA. These attacks take the claims of FOSTA-SESTA's proponents at face value—that it was a good and useful measure to take against sex trafficking when all evidence points to the contrary. Our opposition to FOSTA-SESTA was and remains based on the facts: It will not stop sex trafficking and will instead make stopping it harder. At the same time, the law puts a wide range of online expression at risk and we are always, unapologetically, against the criminalization and chilling of legal speech. Third, despite what its supporters claim, the EARN IT Act is a surveillance bill that would have a devastating impact on privacy, security, and free speech. If Congress passes this disastrous bill, it may become too legally risky for companies to offer encryption services. This bill treats every internet user as a potential criminal, and subjects all our communications to mass scanning. We are pleased that Congress has rejected it twice already. Finally, the flurry of hyperbole and personal attacks should not be allowed to deflect attention from the most important thing about Gigi Sohn's nomination: She is one of the most qualified people possible for the role of FCC commissioner. She has been a fair and balanced advocate for public interest for her entire career, which is why she is supported by experts, industry associations, and consumer groups alike. That is why we were happy to add her to our board— a role from which she will step down if she is appointed—and why we would be thrilled to see her confirmed to the FCC. The public deserves an FCC commissioner who will fight for net neutrality, for rural broadband access, and for strong internet infrastructure. It is past time to let her get to work helping to build a better internet for everyone.

elementary OS Founder and CEO Danielle Foré announced today the general availability for download of the long-anticipated elementary OS 7 “Horus” distribution based on the latest Ubuntu LTS and packed with many new features and improvements.

Should the police be able to identify everyone who was in a busy metropolitan area, just because a crime occurred there? In two amicus briefs just filed in appellate courts, we argue that’s a clearly unconstitutional search.[1] The two cases are People v. Meza, in the California Court of Appeal, and United States v. Chatrie, in the federal Fourth Circuit Court of Appeals. In each case, the defendant is challenging the police use of a surveillance tool we’ve written about before called a “geofence warrant.” In both cases, the lower courts denied motions to suppress. In Chatrie, however, the district court issued a lengthy opinion holding the geofence warrant was unconstitutional before ruling that police relied on the warrant in “good faith” and therefore the evidence from their search was admissible. Unlike traditional warrants for electronic records, a geofence warrant doesn’t start with a particular suspect or even a device or account; instead police request data on every device in a given geographic area during a designated time period, regardless of whether the device owner has any connection to the crime under investigation. Google has said that for each warrant, it must search its entire database of users’ location history information—data on hundreds of millions of users. The data Google provides to police in response to a geofence warrant has the potential to be very precise—much more precise than cell site location information, for example. It allows Google to determine where a user was at a given date and time, sometimes to within twenty meters or less. Google can even determine a user’s elevation and establish what floor of a building that user may have been on. As the lower court noted in Chatrie last summer, Google’s database “appears to be the most sweeping, granular, and comprehensive tool—to a significant degree—when it comes to collecting and storing location data.” At the same time, however, Google does not guarantee accuracy. Google’s goal is to accurately infer a user’s location within a certain radius a bare 68% of the time. This creates the possibility of both false positives and false negatives—people could be implicated for a crime when they were nowhere near the scene, or the actual perpetrator might not be included at all in the data Google provides to police. The warrants in both the Meza and Chatrie cases encompassed large geographic areas and time periods. In Meza, the police asked for all devices in six discrete, heavily populated areas of Los Angeles during time periods where people were likely to be in sensitive places, like their homes at church or a medical center, or driving along one of the many busy streets included within the geofenced areas. In total, police requested data for a geographic area equivalent to about 24 football fields or five to six city blocks during five morning commute hours. Similarly, in Chatrie, the geographic area was about 17.5 acres (about 3 and a half times the footprint of a New York city block) and included a church, a chain restaurant, a hotel, several apartments and residences, a senior living facility, a self-storage business, and two busy streets. In our briefs, we argue these warrants are unconstitutional “general warrants” because they don’t require police to show probable cause to believe any one device was somehow linked to the crime under investigation. Instead, they target everyone in the area and then provide police with unlimited discretion to determine who to investigate further. In Meza, we also argue the practice violates CalECPA, California’s landmark electronic communications privacy law. Chatrie and Meza are the first cases challenging geofence warrants to make it to the appellate level. However, they appear to just be the tip of the iceberg. The number of police requests for geofence warrants has increased dramatically since their first reported use in 2016. According to Google, geofence requests now constitute more than a quarter of the total number of all warrants it receives, and 20% of those come just from law enforcement agencies in California. There is real reason to be concerned about these overbroad searches. They have, in the past, caused innocent people to be suspected of crimes they didn’t commit. And geofence warrants can and have been used in ways that impact fundamental rights, including free speech and freedom of association. For example, during the protests following the police shooting of Jacob Blake, the ATF used at least 12 geofence warrants to collect people’s location data during protests in Kenosha, Wisconsin, one of which encompassed a third of a major public park for a two-hour window. Police also used a geofence warrant in Minneapolis around the time of the protests following the police killing of George Floyd. And geofence warrants may be used in the near future to target people for reproductive health choices and outcomes. Google has been sufficiently concerned about this possibility to pledge to delete location information shortly after someone visits an abortion clinic, though critics have argued this would be insufficient to protect people. The Chatrie and Meza cases will both likely be argued sometime later this year. The majority of courts to address geofence warrants in publicly available opinions have raised constitutional concerns, refusing to issue the warrant or suppressing the evidence. We hope these two appellate courts will do the same. [1] EFF was represented on the Chatrie brief by the NYU Technology Law & Policy Clinic, and the excellent brief was drafted by law students Talya Nevins and Yanan Wang. Related Cases: Carpenter v. United States

QCoro 0.8.0 Release Announcement This is a rather small release with only two new features and one small improvement. Big thank you to Xstrahl Inc. who sponsored development of new features included in this release and of QCoro in general. And as always, thank you to everyone who reported issues and contributed to QCoro. Your help is much appreciated! The original release announcement on qcoro.dvratil.cz. Improved QCoro::waitFor() Up until this version, QCoro::waitFor() was only usable for QCoro::Task. Starting with QCoro 0.8.0, it is possible to use it with any type that satisfies the Awaitable concept. The concept has also been fixed to satisfies not just types with the await_resume(), await_suspend() and await_ready() member functions, but also types with member operator co_await() and non-member operator co_await() functions. QCoro::sleepFor() and QCoro::sleepUntil() Working both on QCoro codebase as well as some third-party code bases using QCoro it’s clear that there’s a usecase for a simple coroutine that will sleep for specified amount of time (or until a specified timepoint). It is especially useful in tests, where simulating delays, especially in asynchronous code is common. Previously I used to create small coroutines like this: QCoro::Task< > timer(std::chrono::milliseconds timeout) { QTimer timer; timer.setSingleShot(true); timer.start(timeout); co_await timer; } Now we can do the same simply by using QCoro::sleepFor(). Read the documentation for QCoro::sleepFor() and QCoro::sleepUntil() for more details. QCoro::moveToThread() A small helper coroutine that allows a piece of function to be executed in the context of another thread. void App::runSlowOperation(QThread *helperThread) { // Still on the main thread ui- >statusLabel.setText(tr("Running")); const QString input = ui- >userInput.text(); co_await QCoro::moveToThread(helperThread); // Now we are running in the context of the helper thread, the main thread is not blocked // It is safe to use `input` which was created in another thread doSomeComplexCalculation(input); // Move the execution back to the main thread co_await QCoro::moveToThread(this- >thread()); // Runs on the main thread again ui- >statusLabel.setText(tr("Done")); } Read the documentation for QCoro::moveToThread for more details. Full changelog See changelog on Github

A blog post from Software Freedom Conservancy. Blog post by Daniel Takamori. Please email any comments on this entry to . Today Software Freedom Conservancy is officially opening our call for track proposals for our first annual FOSSY conference! We will be holding the conference in Portland, Oregon July 13-16, 2023 at the Oregon Convention Center. We are looking for community driven tracks that can balance important and in depth technical and non-technical issues, while uplifting contributors of all experiences. Tracks will be modeled after the DevRooms at FOSDEM and the miniconfs at linux.conf.au. They may be between 1 and 4 days, and the organizers of the tracks will be in charge of outreach, calls for submissions, communicating with potential speakers in the track, determining the schedule and hosting the track in person at FOSSY. We're looking for organizers who can give us a really good idea of what we can expect from their track. The description should give a detailed explanation of the topic, ideally along with some of the issues you expect to cover. Example talks you expect, what kind of audience are you aiming for, and how this topic fits into the larger FOSS ecosystem are good things to mention. You'll note that we ask for two people to be listed as organizers for the track. It's easy to underestimate the work involved so having more than two organizers could also really help to take care of all of the work. We'll be there to help and support you, but this will be your show! We'd like you to tell us why the organizers are the right ones for the job. Do they have experience running conferences, unique perspectives due to involvement with the topic? Conference organizing is a demanding job that requires a balance of logistics, people centered concerns and technical skills. We trust you to assemble a group of people that can cater to those needs and want to put on a great event. Given that this is the first FOSSY, we will be creating this space together! How is the topic you are proposing beneficial for the FOSS community and how does it fit into this new space? The hope is to have a balance of technical and non-technical topics, and we want to hear from you about what's important on those issues. Given that we want to shape the conference into something that uplifts contributors of all levels and experience, how will you approach a varied audience? How long will your track be? Are you planning a quick and deep dive into a single topic or do you dream of having a 4 day long track dealing with tough issues that you want attendees to sit with and reflect on over the weekend? We don't need you to lock yourself into this choice, but we do need a rough figure how much participation and space you'll need if you are hoping to do something specific. Anything that gives us a sense of the organization and spirit of your tracks will be helpful. Please use our submission page or email us at conference@sfconservancy.org if you have any questions. The deadline for application is Sunday March 19th, so be sure to reach out soon! We're very excited to hear from you about how we can shape this conference into something for us all. Thanks so much for your interest and we hope to see you in July!

Another alpha release, some more tweaks and tidy-ups. Here are the compressed sources and a GPG detached signature:   https://alpha.gnu.org/gnu/a2ps/a2ps-4.14.94.tar.gz   https://alpha.gnu.org/gnu/a2ps/a2ps-4.14.94.tar.gz.sig Use a mirror for higher download bandwidth:   https://www.gnu.org/order/ftp.html Here are the SHA1 and SHA256 checksums: 1c99e0200ed0d93119ad6ab54a4735692dbb6d26  a2ps-4.14.94.tar.gz 3+mUXOzeILDgtP08dCJjPI2BL5px92ndCH27qjW1RPI  a2ps-4.14.94.tar.gz The SHA256 checksum is base64 encoded, instead of the hexadecimal encoding that most checksum tools default to. Use a .sig file to verify that the corresponding file (without the .sig suffix) is intact.  First, be sure to download both the .sig file and the corresponding tarball.  Then, run a command like this:   gpg --verify a2ps-4.14.94.tar.gz.sig The signature should match the fingerprint of the following key:   pub   rsa2048 2013-12-11 [SC]         2409 3F01 6FFE 8602 EF44  9BB8 4C8E F3DA 3FD3 7230   uid   Reuben Thomas   uid   keybase.io/rrt If that command fails because you don't have the required public key, or that public key has expired, try the following commands to retrieve or refresh it, and then rerun the 'gpg --verify' command.   gpg --locate-external-key rrt@sc3d.org   gpg --recv-keys 4C8EF3DA3FD37230   wget -q -O- 'https://savannah.gnu.org/project/release-gpgkeys.php?group=a2ps&download=1' | gpg --import - As a last resort to find the key, you can try the official GNU keyring:   wget -q https://ftp.gnu.org/gnu/gnu-keyring.gpg   gpg --keyring gnu-keyring.gpg --verify a2ps-4.14.94.tar.gz.sig This release was bootstrapped with the following tools:   Autoconf 2.71   Automake 1.16.5   Gnulib v0.1-5639-g80b225fe1e NEWS * Noteworthy changes in release 4.14.94 (2023-01-31) [alpha]  * Features:    - Replace the 'psmandup' utility with simpler 'lp2' to directly print      documents to a simplex printer.    - Remove the outdated 'psset' and 'fixnt', and simplify 'fixps' to      always process its input with Ghostscript.  * Documentation    - Remove some obsolete explanations.  * Build    - Minor tidy up and removal of obsolete code.

MongoDB is an open-source, cross-platform, and distributed NoSQL database system. Here’s hot to install it on a Rocky Linux 9 server. The post How to Install MongoDB NoSQL Database on Rocky Linux 9 appeared first on Linux Today.

When the Federal Communications Commission (FCC) released their new broadband map in November 2022, many hoped the chronic inaccuracies of past FCC maps would be resolved. Previous maps of high-speed broadband access in the United States painted inaccurate pictures partly because the definitions of things like “access” and “high-speed” were, frankly, wrong. Furthermore, the maps were based on data self-reported by internet service providers, which have every interest in claiming better service than they actually provide. The new maps have all the problems of the old maps, with the new issue that they are the basis for how $42 billion in broadband infrastructure grants will be spent. The problems have also been raised by states, local government, and community organizations, who have filed challenges to the FCC over these inaccuracies. It is now up to the FCC and NTIA to fix the map, and time is of the essence: the Biden administration is set to confirm how the money will be spent by the summer as part of its Broadband Equity, Access, and Deployment (BEAD) program. Overreliance on internet service providers (ISPs) to report service locations and service availability is a recurring problem. ISPs have no incentive to accurately report, and in fact, have every incentive to overreport, because misinforming the government has never carried a heavy penalty. These same ISPs then use these faulty broadband maps - which are built on their bad data - to challenge and try to prevent would-be competitors from building infrastructure into areas that are underserved or unserved. The FCC, recognizing this concern, created a challenge process through which government entities as well as individuals are able to challenge the ISPs over their service location and service availability. Setting aside the issues with the challenge process and the obvious discrepancy that is pitting an average consumer or small government agencies against well-resourced ISPs, these challenges only allow a glimpse of the true scope of the map’s inaccuracies.  For example, in Nevada, the Nevada State Office of Science, Innovation, and Technology found over 20,000 purported broadband-serviceable locations that they believe overstate coverage. They also found incorrect information on quality of service available as well as missing serviceable location. In Vermont, the maps show 100% coverage, with only 3% of residents lacking speeds greater than the FCC’s definition of high speed internet of "25/3" (25 megabits per second download and three megabits per second upload). The Vermont Department of Public Service found that the maps omitted 22% of the addresses in the state’s own database: over 60,000 locations. Their Community Broadband Board further estimates that 18.6% of residents, not the map’s stated 3%, lack access to speeds greater than 25/3. It was so bad, the Community Broadband Board released a call to action “urging Vermonters to challenge wrong FCC map data.” It is not just single-family residences that were omitted but also public and multifamily housing units, where a single omitted location could mean hundreds of people being uncounted, as well as centers of community life like schools, churches, and libraries. A letter signed by 110 organizations representing housing, education, healthcare, library, and state and local government interests finds that nationwide, 20-25% of unconnected households reside in public and multifamily units. The undercounting of schools, churches, and libraries omits crucial places of community and gathering where improving service would have an outsized impact in connecting otherwise unserved rural communities. For these to go uncounted  omits some of the most vulnerable populations and ignores precisely those areas that this initiative is meant to assist.  The NTIA, and subsequently state governments, must rely on these inaccurate maps to disburse $42 billion in taxpayer dollars to build out internet infrastructure. An undercounting of a cumulative hundreds of thousands if not millions of underserved and unserved locations and their residents severely hinders how these funds will address existing inequities. Take for example Los Angeles County, in California: according to the data ISPs have submitted to the FCC, LA County is 100% served. What we know from community organizations in LA County is that this is simply not true. Unfortunately, the danger of these inaccuracies has extended to the California Public Utilities Commission’s (CPUC), which recently issued its own priority areas map. The priority areas map marks areas the CPUC sees as priorities for investment, using the same underlying data as the FCC’s inaccurate broadband maps. By failing to correctly reflect the deep inequities that exist in LA County when it comes to internet access, the CPUC map would also fail to prioritize those areas for much needed investment. Of the 100 census tracts in LA County that are least connected - those with the lowest percentage of population with fixed broadband at home - only 5 are in a CPUC priority area. Of the 500 least connected census tracts, only 14 are in a CPUC priority area. Conversely, of the 100 best connected census tracts - those with the highest percentage of population with fixed high speed broadband at home - 19 are in priority areas, and of the 500 most connected census tracts, 80 are in priority areas. If funds are disbursed based on the current data, LA County’s best connected are set to receive more investments in more places than the county’s least connected. The obvious solution is to require better data and penalize intentional over-reporting of coverage. Looking beyond the map, the NTIA should not distribute the full $42 billion using the current available data given what appears to be systemic inaccuracies that disproportionately harm low-income people in cities. Furthermore, the FCC needs to do more than just count on less resourced entities to correct the false ISP data. They should proactively ensure everyone receives their fair share of federal support from the infrastructure law and root out bad faith efforts by ISPs. Community organizations and state and local governments can only do so much by flagging the flagrant inaccuracies. These inaccurate maps put at risk the once-in-a-lifetime opportunity to build future-proof internet infrastructure that benefits all Americans for generations to come.