Angry Trump Accidentally Blurts Out Unnerving New Plot to Rig Midterms
Posted on r/politics |
Score: 8780 |
Comments: 432
The article discusses how Donald Trump, in a recent Truth Social rant, revealed his plan to rig the 2026 midterm elections by attempting to ban mail-in voting through an executive order. Trump's previous similar efforts were blocked by courts, but he now seems determined to push forward, using fabricated justifications to disenfranchise voters and sway the elections in favor of Republicans.
Key Points:
Trump announced a new executive order aimed at banning mail-in voting, linking it directly to the 2026 midterm elections.
His previous executive order on election rules was blocked by federal judges, but he plans to appeal or introduce a new rationale.
Voting rights advocates warn that Trump's actions are an abuse of power and a clear attempt to rig the elections.
Trump's justification for banning mail-in voting is based on false claims of widespread fraud, which have been debunked.
The article highlights the broader strategy of using presidential power to manipulate election outcomes, including potential military maneuvers in Democratic areas.
"Trump is manufacturing a fake justification for nixing vote-by-mail because he believes (probably wrongly, but never mind that) doing so will help Republicans in the midterms. That he openly linked his announcement to the 2026 elections shows he isn’t even bothering to hide the scam any longer."
Let's Encrypt certificates will no longer be usable for client authentication starting 13 May 2026
Posted on r/selfhosted |
Score: 911 |
Comments: 136
Let's Encrypt will stop including the Client Authentication Extended Key Usage (EKU) in its certificates by May 2026 due to new Google requirements, forcing users to find alternatives for TLS client authentication. This change impacts those who relied on Let's Encrypt for cheap and easy client authentication, such as for internal server communication. Users are advised to set up private certificate authorities for internal networks or switch to paid certificates for public-facing applications.
Key Points:
Let's Encrypt will no longer support Client Authentication EKU by May 2026 due to Google's new requirements.
This change disrupts users who relied on Let's Encrypt for simple client authentication, such as internal server communication.
Alternatives include setting up private certificate authorities for internal use or switching to paid certificates for public applications.
The move is driven by Chrome's dominance, making it unavoidable for Let's Encrypt to comply.
The article highlights the risks and limitations of using Let's Encrypt for client authentication, calling it a 'poor man's VPN.'
"If you still want to use TLS client authentication **within your own network**, you should look into setting up your own private /self-signed certificate authority. It won't be trusted by default, but that's not a problem, because you can add your CA's public keys to the servers you manage."
Posted on r/programming |
Score: 398 |
Comments: 187
The article discusses how anti-cheat engines in online multiplayer games are increasingly requiring Secure Boot and TPM 2.0 to combat cheating. It explains the technical aspects of Secure Boot and TPM, addresses privacy concerns, and evaluates their potential effectiveness in reducing cheating.
Key Points:
Anti-cheat engines now require Secure Boot and TPM 2.0 to play online multiplayer games.
Secure Boot verifies the integrity of the boot sequence using a hierarchy of keys.
TPM 2.0 provides hardware-based security features to enhance anti-cheat measures.
The move has sparked controversy over privacy and hardware compatibility concerns.
The primary goal of anti-cheat engines is to make cheating harder and detection easier, not to eliminate it entirely.
"The goal of anti-cheat engines is to put technological barriers in place to make it harder for cheat developers; to make detection of cheating packages easier; and to ensure that, when detected, banned cheaters are not able to evade their ban."
Immutable by default: How to avoid hidden state bugs in OOP
Posted on r/programming |
Score: 161 |
Comments: 95
The article advocates for using immutable objects by default in object-oriented programming to avoid hidden state bugs. It explains the difference between mutable and immutable data, highlighting how mutable objects can lead to unexpected side effects. The author shares a real-world example where a mutable DateTime object caused a bug that took hours to debug.
Key Points:
Immutable objects prevent hidden state bugs by ensuring data cannot be changed after creation.
Mutable objects can lead to unexpected side effects when shared across different parts of a program.
The article contrasts shallow and deep immutability, using JavaScript's const and let as examples.
Using immutable objects like DateTimeImmutable can save debugging time by avoiding unintended mutations.
The author recommends defaulting to immutability unless there's a specific need for mutability, such as performance optimization.
"If we had used DateTimeImmutable, the modify() method would have returned a new object instead of changing the original. The original DateTimeImmutable would stay untouched, meaning $lastModified wouldn’t be updated."
The native OpenWebUI client (Conduit) is now on iOS!
Posted on r/selfhosted |
Score: 63 |
Comments: 28
The article announces the release of a native iOS client for OpenWebUI, named Conduit, alongside several new features like advanced authentication and chat organization. The app aims to provide a smoother, more private alternative to the PWA, with a one-time purchase price of $3.99 to cover costs.
Key Points:
Native iOS client (Conduit) for OpenWebUI is now available.
New features include advanced authentication, chat organization, and performance improvements.
The app prioritizes privacy, offering a native experience without third-party servers or tracking.
Available for $3.99 on iOS, with Android options via Google Groups or GitHub.
Open-source and encourages community contributions on GitHub.
"The PWA is solid, but I’ve wanted the smooth feel of a native app for day-to-day use, fast navigation, better keyboard behavior, system-level sharing, and a UX that feels familiar to non-technical folks. It’s also been way easier to get family members using OpenWebUI with something that feels like the commercial chat apps they’re used to, without giving up privacy."
The Fathers of Free Market Economics Called for Taxing the Value of Land, Their Message is More Important than Ever Before
Posted on r/georgism |
Score: 62 |
Comments: 4
The article discusses how classical economists like Adam Smith, David Ricardo, and Henry George advocated for taxing land value, arguing that land is a natural monopoly and its rent is unearned income. Modern economists like Joseph Stiglitz support this view, emphasizing that taxing land and natural resources is efficient due to their inelastic supply. The article highlights the continued relevance of this idea in addressing economic inequality and promoting a truly free market.
Key Points:
Classical economists such as Adam Smith, David Ricardo, and Henry George recognized land rent as unearned income and advocated for taxing it.
Land is a natural monopoly because it is limited in supply, allowing landowners to charge rents without providing value in return.
Modern economists like Joseph Stiglitz support land taxes, noting their efficiency due to the inelastic supply of land and natural resources.
The Physiocrats, an 18th-century French economic group, were among the first to propose taxing land value as a way to promote free trade and reduce other taxes.
The article argues that taxing land value remains a relevant solution for economic inequality and a truly free market.
""One of the general principles of taxation is that one should tax factors that are inelastic in supply, since there are no adverse supply side effects. Land does not disappear when it is taxed. Henry George, a great progressive of the late nineteenth century, argued, partly on this basis, for a land tax.""
The article explores the potential for New York City to cover its $84B annual budget gap by implementing a 5% land value tax (LVT) on its $1.74T land valuation, which would generate approximately $87B. It questions the feasibility and implications of such a tax, given the city's current reliance on real estate, sales, and income taxes.
Key Points:
NYC's annual budget gap is around $84B, primarily covered by real estate, sales, and income taxes.
Manhattan's land is valued at $1.74T, and a 5% LVT could generate $87B, enough to cover the budget gap.
The article questions the practicality and potential issues with relying solely on a 5% LVT for revenue.
"If you take 1.74T multiply by a 5% cap rate, that is $87B. Enough to plug the hole if all other revenue is lost."
The article explores how compiler principles can be applied beyond programming languages, specifically to event streaming pipelines. It highlights how separating intent from execution allows for optimized code generation across different JavaScript environments, addressing compatibility and performance issues.
Key Points:
Compilers can optimize event streaming pipelines by separating intent from execution, similar to how they optimize programming languages.
JavaScript's ecosystem faces challenges with incompatible streaming APIs (Node.js streams vs. Web Streams), making unified solutions difficult.
A compilation approach allows writing pipeline descriptions once and generating environment-specific optimized code.
This method avoids unmaintainable runtime checks and leverages native APIs for better performance.
The author is implementing this approach in Emmett's event processing system under the codename FusionStreams.
"This separation between declaring what you want and how it executes is the same fundamental principle that powers programming language compilers. When you write int x = 5 + 3 in C, the compiler doesn't just translate it word-for-word to assembly. It might optimise it to int x = 8, or eliminate it entirely if x is never used. The compiler understands your intent and finds the best way to achieve it."
Media Journal v1 release! (the hopefully redeemed all-in-one media tracking app)
Posted on r/selfhosted |
Score: 21 |
Comments: 2
The article announces the release of Media Journal v1, an all-in-one media tracking app that has been updated with new features and improvements. The developer, who initially faced criticism for disliking Docker, redeemed themselves by adding Docker support and enhancing the app's functionality and user interface.
Key Points:
Added support for books, expanding the app's tracking capabilities to movies, TV series, games, anime, and manga.
Introduced multiple rating systems (5 stars, 1-10, 1-100, faces) and a community page for discussions.
Improved phone and general UI, along with fetching extra information for better user experience.
Developer prioritizes features that benefit all users over niche requests like CSV imports from other sites.
The app remains primarily for personal use but welcomes community feedback and enjoyment.
"As I said back then, the app is still mainly for myself (meaning I would continue updating it even if nobody was using it), but I love if other people enjoy it as well."
Making Impossible States Impossible: Type-Safe Domain Modeling with Functional Dependency Injection
Posted on r/programming |
Score: 20 |
Comments: 1
The article discusses how typed functional languages like Elm, Haskell, and F# can prevent impossible states in domain modeling by leveraging rich type systems. It emphasizes the principle of 'parse, don't validate' to ensure data integrity and highlights functional dependency injection as a way to manage effects without compromising type safety.
Key Points:
Typed functional languages excel at making impossible states impossible by encoding domain rules directly into the type system.
The 'parse, don't validate' approach ensures that only valid data enters the domain layer, reducing runtime errors.
Sum types (union types) provide a single source of truth for state, eliminating contradictory or partial states.
Functional dependency injection via partial application allows for clean architecture by pushing effects to the edges while keeping the core pure.
Rich types serve as living documentation, making domain rules clear to both developers and domain experts.
"Most applications don’t fail because algorithms are hard—they fail because our models allow states that make no sense in the domain. 'User without email but verified', 'order that’s both shipped and cancelled', 'sum < 0', 'modal dialog both closed and active'. These states should be impossible from the start."
The article discusses the challenges of software development at scale, emphasizing that the primary difficulties are sociotechnical rather than technical. It advocates for optimizing processes and tools to build trust among team members as a key heuristic for effective collaboration.
Key Points:
Software development at scale is a sociotechnical problem, focusing on aligning human efforts rather than solving novel technical challenges.
Processes and tools should be evaluated based on how they affect trust among team members.
Code reviews, writing tests, and team-building exercises are examples of practices that build trust within a team.
Agile methodologies aim to solve predictability and alignment issues, but their effectiveness depends on the team's context.
The author recommends optimizing for trust as a universal heuristic for assessing team processes and tools.
"Optimise for trust. That’s the take. Whenever you think about making a change to how your team works, or see a shiny new tool you want everyone to use, think about how it will affect your teammates’ trust in each other."