Pentagon will cut Sen. Mark Kelly's military retirement pay over 'seditious' video to troops: Hegseth
Posted on r/politics |
Score: 14673 |
Comments: 999
The Pentagon, under Defense Secretary Pete Hegseth, is moving to cut Senator Mark Kelly's military retirement pay and reduce his rank over a video he participated in. The video, which told service members they have the right to refuse illegal orders, was deemed 'seditious' and a threat to military discipline. Kelly, a retired Navy captain, vows to fight the action, calling it an attack on free speech.
Key Points:
Defense Secretary Pete Hegseth announced disciplinary action against Senator Mark Kelly for a video advising service members on refusing illegal orders.
The actions include cutting Kelly's military retirement pay, issuing a formal letter of censure, and starting proceedings to reduce his retirement rank.
Hegseth labeled Kelly's statements in the video as 'seditious' and intended to undermine military discipline.
Kelly strongly opposes the action, vowing to fight it and accusing Hegseth and Trump of targeting critics.
The Pentagon had previously announced a probe into Kelly's involvement, with more severe options like court-martial now ruled out.
""Six weeks ago, Senator Mark Kelly — and five other members of Congress — released a reckless and seditious video that was clearly intended to undermine good order and military discipline," Hegseth said in a statement on X."
Mark Kelly has retirement pay cut by Pentagon over ‘illegal orders video,’
Posted on r/politics |
Score: 8591 |
Comments: 465
The Pentagon, under Secretary of Defense Pete Hegseth, is taking administrative action to cut Senator Mark Kelly's retirement rank and pay. This action is in response to a video Kelly and other lawmakers made advising troops they 'can and must refuse illegal orders,' which Hegseth called 'seditious.' Kelly, a retired Navy captain, defended his actions as protected by the First Amendment and earned through his service.
Key Points:
Senator Mark Kelly (D-AZ) faces a cut to his military retirement pay and rank.
The action is ordered by Defense Secretary Pete Hegseth over a video Kelly made with other lawmakers telling troops to refuse illegal orders.
Hegseth labeled the video 'reckless and seditious' and stated Kelly remains accountable to military justice as a retiree.
Kelly strongly defended his actions, citing his 25-year Navy service, combat missions, and First Amendment rights.
The Secretary of the Navy has 45 days to review and provide a recommendation on the action.
""Six weeks ago, Senator Mark Kelly — and five other members of Congress — released a reckless and seditious video that was clearly intended to undermine good order and military discipline. As a retired Navy Captain who is still receiving a military pension, Captain Kelly knows he is still accountable to military justice.""
Posted on r/programming |
Score: 765 |
Comments: 122
Addy Osmani reflects on 14 years at Google, arguing that thriving as an engineer depends less on pure coding skill and more on navigating the broader context of people, politics, and problem-solving. The article presents 21 timeless lessons focused on patterns of effective engineering and collaboration, rather than specific technologies.
Key Points:
Focus on deeply understanding user problems rather than starting with a preferred technical solution.
Prioritize clarity and operational simplicity in code over cleverness or novelty to reduce risk.
Effective collaboration and alignment are more valuable than simply being right in technical arguments.
Bias towards action and shipping imperfect versions to learn from real feedback over analysis paralysis.
Your work's impact depends on others advocating for it; great code alone does not speak for itself.
"The best engineers are obsessed with solving user problems. It’s seductive to fall in love with a technology and go looking for places to apply it. I’ve done it. Everyone has. But the engineers who create the most value work backwards: they become obsessed with understanding user problems deeply, and let solutions emerge from that understanding."
OVHCloud gave me a blacklisted IP and told me it’s my problem!
Posted on r/selfhosted |
Score: 204 |
Comments: 74
A customer purchased a low-cost OVHCloud server and discovered its primary IP address was blacklisted, preventing connections to services like GitHub and Cloudflare. Support confirmed the blacklist but refused to replace the IP, stating it was non-replaceable and that clean IPs couldn't be guaranteed even with a new purchase. The customer questions whether expecting a functional, non-blacklisted IP is now a premium luxury and seeks community advice.
Key Points:
Customer received a blacklisted IP on a new OVHCloud server, blocking access to essential services.
Support acknowledged the blacklist but refused to replace the IP, citing policy and IPv4 shortages.
The provider suggested buying a new server but warned clean IPs aren't guaranteed due to recycled addresses.
The customer feels penalized for past abuse of the IP and questions industry standards.
Technical checks suggest the issue may extend beyond the blacklist, as some HTTPS connections time out.
"We regret to inform you that we cannot change the primary IP address of the server, since the primary IP is under blacklist we cannot change or replace it. If you want a different IP you will need to purchase a new server however we cannot guarantee a clean IP as our IPv4's are recycled as there is currently a shortage of IPv4's."
Posted on r/programming |
Score: 197 |
Comments: 15
The article reviews major database trends of 2025, highlighting the continued dominance of PostgreSQL as the focal point for innovation and investment. It details significant acquisitions, new services, and projects aimed at enhancing PostgreSQL's scalability and features.
Key Points:
PostgreSQL's dominance continued, with version 18 adding features like asynchronous I/O and skip scans, though it still lagged in some areas compared to other DBMSs.
Major acquisitions and launches centered on PostgreSQL, including Databricks buying Neon, Snowflake buying CrunchyData, and Microsoft launching HorizonDB.
New projects like Supabase's Multigres, led by Vitess co-creator Sugu, aimed to bring horizontal sharding (scale-out) to PostgreSQL.
The author notes other predictable industry events, like Redis Ltd. switching its license back and SurrealDB's flawed benchmarks.
The article is selective, focusing only on notable and appropriate events from the year, excluding some sensitive topics.
"The reason is that most of the database energy and activity is going into PostgreSQL companies, offerings, projects, and derivative systems."
qui v1.12.0 - standalone qBittorrent ui, now with automations and improved cross-seeding with hardlinks!
Posted on r/selfhosted |
Score: 147 |
Comments: 46
The article announces the release of qui v1.12.0, a standalone web interface for qBittorrent designed to handle large-scale torrent management. The update introduces major features like automations, hardlink support for cross-seeding, and ARR integration, aiming to consolidate functionality and improve performance. The tool supports multiple operating systems and architectures, and is tested with instances managing tens of thousands of torrents.
Key Points:
Introduces automations for workflows and orphan scanning, similar to tqm/qbit_manage.
Adds hardlink and reflink support to improve cross-seeding efficiency.
Enhances cross-seed results with ARR (Apps like Radarr, Sonarr) integration.
Includes live log streaming and over 50 other improvements.
Designed for massive scale, supporting single instances with 70k+ torrents or 35+ instances in one qui.
"We built qui to be a one-stop-shop for your torrents and their lifecycle, with the main goal that it should work great with huge qBittorrent instances. We have users running single instances with 70k+ torrents working great and others running 35+ instances in a single qui also working great."
The author expresses shock at the capabilities of Claude Opus 4.5 and connects this to deep anxiety about their future career. As a beginner web developer graduating in 2026, they fear that software engineering as a profession is finished due to AI advancements.
Key Points:
The author is impressed and shocked by the quality of the AI model Claude Opus 4.5.
They are currently applying for jobs, which prompts them to consider AI's impact on employment.
They explicitly fear that AI will replace developers.
As a student set to graduate in 2026, they feel particular vulnerability as a beginner.
They conclude with a strong, pessimistic sentiment that software engineering is 'done'.
"As a beginner web dev graduating in 2026, I am really scared I think swe is done"
Functors, Applicatives, and Monads: The Scary Words You Already Understand
Posted on r/programming |
Score: 57 |
Comments: 25
The article demystifies the functional programming concepts of Functors, Applicatives, and Monads by explaining they are simply patterns for working with 'wrapped' or container values, like Maybe in Elm or arrays in JavaScript. It argues that developers use these patterns daily without knowing the formal names, and illustrates each concept with practical examples from Elm and Haskell.
Key Points:
Functors, Applicatives, and Monads are just patterns for working with values inside containers (e.g., Maybe, List).
A Functor allows you to apply a function to a wrapped value using 'map' without removing it from its container.
An Applicative (using map2, map3, etc.) handles applying a multi-argument function to multiple wrapped values.
A Monad handles chaining operations where a function returns a wrapped value, preventing nested containers (e.g., Maybe (Maybe a)).
These patterns are already familiar to developers who use constructs like JavaScript's .map() or Promise.then().
"These terms have acquired an almost mythical status. They’re spoken of in hushed tones, accompanied by warnings about category theory and abstract algebra. People act like you need a mathematics PhD just to understand what’s happening when you chain some operations together. Here’s the thing, though: if you’ve written any Elm code at all, you already use these concepts daily. You just don’t call them by their scary names."
The article argues that 2026 is a turning point for self-hosting personal services, as it has become accessible to non-sysadmins. This is due to the convergence of affordable mini PCs, simple networking tools like Tailscale, and AI-powered CLI agents like Claude Code that handle complex configuration. The author details their successful setup of services like Vaultwarden and Immich, emphasizing the new ease and reliability.
Key Points:
AI CLI agents like Claude Code eliminate the need to manually configure Docker and services, making self-hosting accessible to non-experts.
Affordable, low-power mini PCs and tools like Tailscale for secure networking have removed major hardware and network barriers.
The author successfully self-hosted core services like Vaultwarden (passwords) and Immich (photos), finding them to be robust replacements.
The workflow is simplified: install a base OS, use an AI agent to set up desired services via natural language commands.
Self-hosted services now offer a polished, reliable experience that competes with commercial, walled-garden alternatives.
"Claude Code is your new sysadmin... I didn't copy-paste YAML from the internet or have to do deep googling. I just asked."
Who Owns the Memory? Part 3: How Big Is your Type?
Posted on r/programming |
Score: 20 |
Comments: 8
This article, part three of a series on low-level memory management, compares how C, C++, and Rust represent types in memory and implement polymorphism. It details the deterministic layout rules in C/C++ versus Rust's compiler-optimized default representation, and explores strategies like monomorphization and virtual dispatch for polymorphism.
Key Points:
C and C++ use a deterministic layout algorithm where field order is fixed, essential for FFI and binary compatibility.
Rust's default `repr(Rust)` allows the compiler to reorder fields to optimize memory usage, making minimal guarantees.
Polymorphism is implemented via monomorphization (compile-time, as with Rust generics/C++ templates) or dynamic dispatch via vtables (runtime, as with Rust trait objects/C++ virtual functions).
The article explains specialized representations like `repr(C)` for FFI, `repr(packed)` to eliminate padding, and niche optimization for enums.
It covers Dynamically Sized Types (DSTs) and fat pointers in Rust, contrasting them with C's array handling.
"C specifies a deterministic algorithm for struct layout... This property is what makes C the lingua franca of FFI: any language that implements the same algorithm can share data structures with C code."
'Everybody works but the empty lot': Some Spokane leaders eye property tax reform to promote building [Washington State]
Posted on r/georgism |
Score: 13 |
Comments: 0
Some Spokane leaders are advocating for property tax reform to shift the tax burden from buildings to land, specifically targeting underdeveloped lots and parking lots. They propose a land-value or split-rate tax system to discourage land speculation and encourage development, aiming to alleviate the city's housing shortage. However, such a system faces legal hurdles under the current state Constitution.
Key Points:
Proposed reform would shift property tax burden from buildings (like high-rises) onto land (like parking lots and empty fields).
Goal is to discourage land speculation and encourage development to address housing shortages.
Current system taxes buildings heavily, making it cheaper to hold undeveloped land as its value rises.
A pure land-value tax would tax only land value, while a split-rate system would tax land at a higher rate than buildings.
State Constitution currently prohibits implementing such land-value or split-rate tax systems.
"“We have a housing shortage, that’s the root cause of why prices are so high... We also have cities with a lot of empty, vacant lots in them, sitting there, usually being speculated on … when you have people speculating on land and not building anything, it actually is contributing to the housing shortage.”"
This article documents a discussion between John Ousterhout (author of 'A Philosophy of Software Design') and Robert 'Uncle Bob' Martin (author of 'Clean Code') about key differences in their software design philosophies. They engage in a structured debate focusing on three primary topics: method length, comments, and test-driven development. The discussion aims to compare and contrast their approaches to writing maintainable, high-quality code.
Key Points:
The authors compare their overall philosophies on software design, acknowledging both agreement and significant differences.
Three main topics are debated: optimal method length, the role and value of code comments, and the practice of Test-Driven Development (TDD).
Each author presents their perspective, with Ousterhout focusing on deep modules and complexity management, and Martin advocating for practices like short methods and TDD.
The discussion includes concrete examples, such as each author rewriting the other's code (PrimeGenerator) to illustrate their differing approaches.
The goal is to explore the trade-offs and reasoning behind different design choices to help developers understand the underlying principles.
"We agree on some things, but there are some pretty big differences of opinion between my recent book A Philosophy of Software Design (hereafter 'APOSD') and your classic book Clean Code."