worse – Earlybirds Invest https://earlybirdsinvest.com Latest Crypto News Mon, 04 Aug 2025 19:18:11 +0000 en-US hourly 1 https://wordpress.org/?v=6.9.7 https://i0.wp.com/earlybirdsinvest.com/wp-content/uploads/2024/12/cropped-New-Project-2024-12-17T235703.455.png?fit=32%2C32&ssl=1 worse – Earlybirds Invest https://earlybirdsinvest.com 32 32 240146708 The Supreme Court just revealed its plan to make gerrymandering even worse, in Louisiana v. Callais https://earlybirdsinvest.com/the-supreme-court-just-revealed-its-plan-to-make-gerrymandering-even-worse-in-louisiana-v-callais/ https://earlybirdsinvest.com/the-supreme-court-just-revealed-its-plan-to-make-gerrymandering-even-worse-in-louisiana-v-callais/#respond Mon, 04 Aug 2025 19:18:11 +0000 https://earlybirdsinvest.com/the-supreme-court-just-revealed-its-plan-to-make-gerrymandering-even-worse-in-louisiana-v-callais/

One of the biggest mysteries that has emerged from the Trump-era Supreme Court is the 2023 decision in Allen v. Milligan.

In Milligan, two of the Republican justices — Chief Justice John Roberts and Justice Brett Kavanaugh — voted with the Court’s Democratic minority to strike down Alabama’s racially gerrymandered congressional maps, ordering the state to redraw those maps to include an additional district with a Black majority.

As Roberts emphasized in his opinion for the Court in Milligan, a lower court that also struck down these maps “faithfully applied our precedents.” But the Roberts Court frequently overrules or ignores precedents that interpret the Voting Rights Act — the federal law at issue in Milligan — to do more than block the most egregious forms of Jim Crow-like voter suppression. And the Court’s Republican majority is normally hostile to lawsuits challenging gerrymanders of any kind.

Most notably, in Rucho v. Common Cause (2019), the Republican justices held that federal courts may not hear suits challenging partisan gerrymanders. Among other things, Rucho enables tactics like Texas Republicans’ current plans to redraw that state’s congressional maps to maximize GOP power in Congress.

So why did two Republican justices break with their previous skepticism of gerrymandering suits in the Milligan case? A new order that the Supreme Court handed down Friday evening appears to answer that question.

The new order, in a case known as Louisiana v. Callais, suggests that the Court’s decision in Milligan was merely a minor detour, and that Roberts and Kavanaugh’s votes in Milligan were largely driven by unwise legal decisions by Alabama’s lawyers. The legal issues in the Callais case are virtually identical to the ones presented in Milligan, but the Court’s new order indicates it is likely to use Callais to strike down the Voting Rights Act’s safeguards against gerrymandering altogether.

The Callais order, in other words, doesn’t simply suggest that Milligan was a one-off decision that is unlikely to be repeated. It also suggests that the Court’s Republican majority will resume its laissez-faire approach to gerrymandering, just as the redistricting wars appear to be heating up.

A brief history of the Supreme Court’s approach to gerrymandering

Broadly speaking, there are two kinds of lawsuits alleging that a legislative map is illegally gerrymandered. Partisan gerrymandering suits claim that a map was drawn to maximize one major political party’s power at the expense of the other. Racial gerrymandering suits, meanwhile, allege that a state’s legislative maps improperly dilute the voting power of voters of a particular race.

Prior to Rucho, the Court imposed minimal — but not entirely nonexistent — limits on partisan gerrymandering. It has historically been more aggressive in policing racial gerrymanders.

The Supreme Court held in Davis v. Bandemer (1986) that federal courts may hear claims alleging that a state’s maps are so egregiously partisan that they amount to unconstitutional discrimination. The idea is that maps that intentionally inflate Democratic voters’ power, while minimizing Republican voters’ power (or vice-versa) violate the Constitution’s guarantee that all voters should have an equal say in elections.

Notably, however, no five justices agreed to a single legal standard that would allow courts to determine which maps are illegal partisan gerrymanders in Davis. Nor did a majority of the Court set such a standard in later lawsuits challenging partisan gerrymanders. In Rucho, the Republican justices essentially announced that the Court would give up its quest to find such a standard. A few years later, in Alexander v. NAACP (2024), those justices went even further, declaring that “as far as the Federal Constitution is concerned, a legislature may pursue partisan ends when it engages in redistricting.”

Though Davis’s limits on partisan gerrymandering were always fuzzy, it is likely that this ambiguity deterred at least some states from enacting extreme gerrymanders that might have caused the courts to intervene. At the very least, Rucho changed how states litigate gerrymandering suits. Before Rucho, states accused of gerrymandering would often try to offer another explanation for why their maps benefited one party or the other. Now, they will openly state in their briefs that they drew maps for partisan reasons — confident that federal judges will do nothing, despite these confessions.

Historically, however, the Court has imposed more concrete limits on racial gerrymanders. In Milligan, for example, the Court struck down Alabama congressional maps that would have given Black voters a majority in just one of the state’s seven districts (or 14 percent of the districts), despite the fact that Black people make up about 27 percent of the state’s population. The Court ordered the state to draw new maps with two Black-majority districts.

The linchpin of Milligan and similar cases is the Court’s decision in Thornburg v. Gingles (1986), which laid out the rules governing when an alleged racial gerrymander violates the Voting Rights Act (which broadly prohibits race discrimination in elections). The framework laid out in Gingles is notoriously complicated, but it turns on whether voters in a particular state vote in racially cohesive blocs.

Thus, for example, in a state where the white majority supports Republicans nearly all of the time, while the Black minority supports Democrats nearly all of the time, Gingles sometimes requires courts to redraw the state’s maps to ensure that the Black minority is adequately represented. This is because, in such a state, the white majority can wield its near-unanimous support for Republicans to cut Black voters (and Democrats) out of power altogether.

In a different state, where both Black and white voters sometimes vote for either party, Gingles tells courts to stay out of redistricting. Black voters, after all, are United States citizens who have as much of a right to choose their leaders as anyone else. So, if they choose to be represented by a white Republican in a free and fair election, that’s their choice and the courts should honor it.

Because Gingles only kicks in when an electorate’s racial demographics closely match its partisan voting patterns, it places some practical limits on both partisan and racial gerrymandering. In Milligan, for example, Alabama was not able to draw maps that maximized Republican voting power because doing so required the state to dilute Black voting power. So, even though Rucho prevents lawsuits that challenge partisan gerrymandering directly, Gingles sometimes allows suits which target it indirectly by alleging that a partisan gerrymander is also an impermissible racial gerrymander.

But now the Court is signaling that it is likely to overrule Gingles and abolish suits alleging that racial gerrymanders violate the Voting Rights Act altogether.

So what’s the deal with the Court’s new order in Callais?

The Callais case is virtually identical to Milligan — indeed, the cases are so similar that Louisiana said in a brief to the justices that Callais “presents the same question” as the Alabama redistricting case. Before the Callais case reached the justices, a lower court determined that Louisiana’s congressional maps violate Gingles, and ordered the state to draw an additional Black-majority district.

Nevertheless, when the Supreme Court heard oral arguments in Callais last March, all six of the Republican justices appeared to disagree with this lower court’s decision — although the lower court’s decision merely applied the same legal rules that the Supreme Court applied two years earlier in Milligan. Then, at the end of June, the Court issued a brief order announcing that it would hold an unusual second oral argument in Callais, and that it would seek additional briefing from the parties in this case.

On Friday, the Court issued a new order laying out what these parties should address in those briefs. Those briefs should examine whether the lower court order requiring Louisiana to draw an additional Black-majority district “violates the Fourteenth or Fifteenth Amendments to the U.S. Constitution.” The justices, in other words, want briefing on whether Gingles — and the Voting Rights Act’s safeguards against racial gerrymandering more broadly — are unconstitutional.

This suggestion that the Voting Rights Act may be unconstitutional — or, at least, that it violates the Republican justices’ vision of the Constitution — should not surprise anyone who has followed the Court’s voting rights cases.

In Shelby County v. Holder (2013), the Republican justices neutralized a different provision of the Voting Rights Act, which required states with a history of racist election practices to “preclear” new election laws with federal officials before they take effect. The Court’s Republican majority labeled this provision “strong medicine” that could be justified to combat the kind of widespread racial voting discrimination that existed during Jim Crow. But they argued that the United States was not racist enough in 2013 to justify letting preclearance remain in place.

“There is no denying,” Roberts wrote for the Court in Shelby County, “that the conditions that originally justified these measures no longer characterize voting in the covered jurisdictions.”

Although Kavanaugh joined nearly all of the majority opinion in Milligan, he also wrote a separate opinion indicating that he wanted to extend Shelby County to gerrymandering cases in a future ruling. “Even if Congress in 1982 could constitutionally authorize race-based redistricting under [the Voting Rights Act] for some period of time,” Kavanaugh wrote, “the authority to conduct race-based redistricting cannot extend indefinitely into the future.”

Gingles also suggests that Voting Rights Act suits challenging racial gerrymanders should eventually cease to exist. If the electorate ceases to be racially polarized — something that appears to be slowly happening — then Gingles plaintiffs will no longer be able to win cases, and the federal judiciary’s role in redistricting will diminish. But Kavanaugh seems to be impatient to end these suits while many states remain racially polarized.

Read in the context of Kavanaugh’s Milligan opinion, in other words, the new Callais order suggests that a majority of the justices have decided the Voting Rights Act’s safeguards against racial gerrymandering have reached their expiration date, and they are looking for arguments to justify striking them down.

It now looks like Milligan was Gingles’s last gasp. The Republican justices remain hostile both to the Voting Rights Act and toward gerrymandering suits more broadly. And they appear very likely to use Callais to remove one of the few remaining safeguards against gerrymanders.

]]>
https://earlybirdsinvest.com/the-supreme-court-just-revealed-its-plan-to-make-gerrymandering-even-worse-in-louisiana-v-callais/feed/ 0 51463
My budget Google TV lags constantly, and Google’s new plan will only make matters worse https://earlybirdsinvest.com/my-budget-google-tv-lags-constantly-and-googles-new-plan-will-only-make-matters-worse/ https://earlybirdsinvest.com/my-budget-google-tv-lags-constantly-and-googles-new-plan-will-only-make-matters-worse/#respond Sun, 25 May 2025 15:09:50 +0000 https://earlybirdsinvest.com/my-budget-google-tv-lags-constantly-and-googles-new-plan-will-only-make-matters-worse/
Taco Bell ad on the Google TV Streamer.

Joe Maring / Android Authority

Reading that Google is lowering the RAM requirements for Google TV sent shivers down my spine. I can already see the 1-star reviews flooding in for TVs that haven’t even launched yet: “horrendous performance,” “laggy interface,” “do not buy.”

Google hasn’t specified the new minimum, but with Android TV dropping its requirement to just 1GB, that’s likely the target for upcoming budget Google TVs as well. And that’s not good.

If there’s one thing smart TVs absolutely don’t need, it’s worse specs — especially less RAM. Many budget TVs and streaming sticks already struggle with performance, and RAM can be the difference between a smooth UI and a lag-fest. This isn’t a theoretical argument; I’ve lived it.

I’ve tried to love Google’s TV products, but the budget experience is so poor.

My first run-in with Google’s platform was 2020’s Chromecast with Google TV, seemingly a bargain at just $50. It shipped with just 8GB of storage (only 4.4GB usable), 2GB of RAM, and a modest Amlogic S905X3 chip. The UI was just smooth enough, but heavier apps like Kodi felt sluggish, and trying to breeze through multiple streaming services was a struggle. The experience was OK, but hardly brilliant, and the lack of storage had me itching to ditch it.

Do you have performance issues on your cheap Google TV device?

168 votes

Google TV Streamer white remote

Ryan Haines / Android Authority

My second attempt was a budget-conscious upgrade to a TCL 4K QLED. No OLED splurge here — just something cheap and supposedly good enough for the odd comfort show. With a more spacious 12GB of storage, 2GB RAM, and a quad-core Cortex-A55 CPU like my old dongle, I figured it would at least match my Chromecast. Even better, it came with the old stripped-back Android TV interface, which I hoped would run more smoothly.

But then came the dreaded update. Seemingly overnight, my TV was transformed into a sluggish mess, rebranded with Google TV’s bloated UI, complete with choppy animations and intrusive ads — everything I’d hoped to avoid with the more basic interface. Worse, once smooth UI scrolling turned to stutters, apps hung on launch, and casting became a glitchy, delayed mess.

The shift was shocking — smooth(ish) one day, verging on unusable the next. And there’s no rollback. Sure, I paid little, but I still feel ripped off as I battle the now barely functional UI. Based on my experience, 2GB is the bare minimum for Google TV, but Google is lowering the requirements. No, thank you.

Google TV Streamer with remote on TV console hero

C. Scott Brown / Android Authority

So no, I have zero faith that “low RAM” TVs will benefit anyone long-term. Especially as Google is intent on stuffing the platform with more ads and bloat that’ll only bog it down further. While putting smart TV capabilities in the palms of more consumers sounds good on paper, a subpar experience will have them reaching for other platforms when it’s time to upgrade.

RAM is just part of the picture, of course. UI lag and slow loading times are just as much a fault of the cheap CPUs that infest the budget TV sphere. But plentiful RAM ensures apps can live in memory between uses, making it faster to hop back and forth without horrendous load times and UI stalls. Just look at the beloved NVIDIA Shield TV: 2GB or 3GB of RAM (depending on the model) and a snappy Tegra X1 still make it one of the best performers in the space — that’s the level every Google TV should aspire to.

Poor performance will turn users off Google TV in the long run.

Not every TV needs to be a powerhouse, but there’s a minimum spec line that shouldn’t be crossed — and lowering RAM requirements pushes us well below it. Google’s move invites manufacturers to cut even more corners, and the result is predictable: sluggish, frustrating devices that leave a sour taste for the entire platform.

If Google wants to compete in the living room, it needs to enforce higher minimum standards, not lower them. Until then, be wary of smart TVs with bargain-bin specs. Or better yet, forget the built-in OS and invest in a solid Android TV box.

]]>
https://earlybirdsinvest.com/my-budget-google-tv-lags-constantly-and-googles-new-plan-will-only-make-matters-worse/feed/ 0 38253
Web3 as we know it isn’t the solution to user empowerment – it actually made things worse https://earlybirdsinvest.com/web3-as-we-know-it-isnt-the-solution-to-user-empowerment-it-actually-made-things-worse/ https://earlybirdsinvest.com/web3-as-we-know-it-isnt-the-solution-to-user-empowerment-it-actually-made-things-worse/#respond Sun, 11 May 2025 05:37:38 +0000 https://earlybirdsinvest.com/web3-as-we-know-it-isnt-the-solution-to-user-empowerment-it-actually-made-things-worse/

The following is a guest post and opinion of Dr. Benjamin Beckmann, CTO at Midnight.

Blockchain technology leaves us far more exposed than you might realize – certainly more exposed than the traditional financial system does.

Take the example of buying a cup of coffee. In the traditional financial system, the transaction is simple: you tap your card and walk away. The barista forgets about it as soon as it’s done, and your bank ensures that nobody has access to your transaction data. In other words, no one knows when, where, or what you bought, except for you.

Now, imagine the same transaction in the world of Web3. The details of that coffee purchase no longer end at the counter. Instead, they become part of a public record. While transactions are pseudonymous, wallet addresses and behavioral patterns can be analyzed over time, allowing third parties to infer your identity and track your financial activity.

Anyone could, in theory, see when, where, and what you bought, as well as who you’re transacting with. But this is not the default: wallet addresses are not universally linked to real-world identities. The risk arises when patterns emerge over time, especially if someone repeatedly transacts with the same wallets or uses exchanges that require KYC, making it easier to draw inferences about their activity and link it to a real identity.

While not every user will necessarily be compromised, linking routine transactions – groceries, subscriptions, gifts – over time could create a detailed map of your personal habits. This kind of transaction tracing has been exploited before. In a well-known case, attackers tracked wallet activity on OpenSea to identify high-value targets, leading to a phishing attack that resulted in over $1.7 million in stolen NFTs. Worse still, Web3’s very reputation for transparency leads both institutions and consumers to overestimate these kinds of risks, hindering more widespread adoption.

Blockchain technology, which underpins Web3, was created to improve transparency and efficiency. It promised to empower users by giving them control over their data and interactions. While it has achieved those goals in part, it also introduced a problem: everyday transactions that were once private are at risk of public exposure, and transparency itself can be a turn-off for potential users. For individuals and businesses alike, this raises a critical question: is this what we really want?

Web3’s transparency comes at a cost

In many financial systems, privacy measures vary in strength, but they generally offer more discretion than blockchain-based transactions. For example, when you use a credit card, the details of the transaction do not make their way to a public database.

While banks and payment processors can see transaction details, both regulatory safeguards and business development priorities incentivize them to limit unauthorized access and help maintain user privacy. Cash, on the other hand, offers even greater anonymity, as it leaves no digital footprint. These payment methods allow for secure transactions while safeguarding individual privacy.

In contrast, the foundation of Web3 is radical transparency. Details of every transaction are permanently recorded on a public blockchain. This transparency was meant to build trust and reduce fraud by preventing tampering or double-spending. Yet blockchain’s transparency is a double-edged sword.

By keeping transaction patterns, timestamps, and behavioral data transparent, blockchain’s design ensures that transaction data is accessible to anyone who cares to look. While wallet addresses do not contain personally identifiable information on their own, they create a trail of transactions that can be analyzed. If a wallet address is ever linked to an identity, through a centralized exchange, an ENS domain, a social media post, or an NFT purchase tied to an email, anyone can trace past and future transactions to build a clear financial map of the individual.

While pseudonymity or encryption may provide a sense of security, in reality, another layer of vulnerability remains: metadata, or the information surrounding transactions. While it might seem harmless, metadata can reveal significant insights when aggregated. Patterns emerge that can expose individual habits, preferences, and weaknesses.

This exposure isn’t just theoretical. CoinGecko confirmed a security breach in which attackers gained access to 1.9 million user email addresses, along with metadata such as IP addresses, location of email opens, and subscription details. The hackers then sent over 23,000 phishing emails, attempting to exploit this metadata to trick users into revealing sensitive crypto wallet credentials. This case highlights how seemingly minor data points, when combined with publicly visible blockchain transactions, can be pieced together to identify and target individuals.

The implications go beyond individuals. Businesses are equally exposed, as the transparency of on-chain transactions within supply chains can inadvertently reveal sensitive operational details or patterns. For instance, competitors might deduce activity patterns or strategic shifts by analyzing transaction trends, potentially undermining a company’s competitive advantage. In a world where privacy is already a scarce commodity, Web3 amplifies these vulnerabilities rather than alleviating them.

How can we design a better Web3?

The question then becomes: how can we design systems that preserve the benefits of blockchain while mitigating its privacy risks? The solution lies in rethinking how data is handled at every step.

One approach is to develop privacy-by-design systems that inherently limit data exposure. These systems go beyond blockchain and are found in tools like secure messaging apps (e.g., Signal) and privacy-focused browsers (e.g., Brave), which minimize data collection while preserving usability. In the blockchain context, the challenge is greater because transparency is built into the technology. To address this, platforms must keep sensitive information locally on the user’s device and avoid generating metadata entirely to ensure no sensitive traces are left behind.

Key to this approach is selective disclosure – a data minimization concept that provides users with more control over what information they share. For example, when applying for a loan or renting a home, individuals should only need to share the specific financial details relevant to eligibility – not their entire transaction history or other unnecessary personal data.

Similarly, in social media settings, users should be able to verify their identity to create accounts without sharing unrelated private information, such as date of birth or specific location.

Selective disclosure is particularly relevant in sectors like healthcare. For instance, when applying for health insurance, individuals should be able to share only the medical information necessary to determine eligibility without exposing their full medical history.

Such systems empower individuals to interact securely while maintaining control over their data. The same principle applies to education, where students should be able to verify their qualifications for a job without sharing irrelevant details about their academic history.

These solutions demonstrate that privacy isn’t incompatible with transparency. It’s about striking the right balance, giving users control over what they share and ensuring that sensitive information remains protected.

A call for balance

Web3 has succeeded in delivering transparency and control to users, but it hasn’t yet fulfilled its promise of true empowerment. For Web3 to achieve widespread adoption, reshaping how we handle sensitive data must become the priority. Without robust data protections, individuals and businesses alike are left vulnerable, unable to fully participate in this new era of technology.

The task ahead for developers, CTOs, and security experts is clear: build systems that prioritize user control, reduce metadata generation, and obscure transaction patterns. By leveraging privacy-by-design principles and enabling selective disclosure, we can create the next evolution of blockchain that combines transparency with discretion.

Only when blockchain strikes a balance between safeguarding sensitive data and transparency can we move toward a future where users are genuinely empowered to purchase, associate, and interact without fear of exposure.

Mentioned in this article
]]>
https://earlybirdsinvest.com/web3-as-we-know-it-isnt-the-solution-to-user-empowerment-it-actually-made-things-worse/feed/ 0 35573