Kremlin Leaks Footage Showing Trump Fawning Over Putin
Posted on r/politics |
Score: 23735 |
Comments: 838
The Kremlin released behind-the-scenes footage showing President Donald Trump warmly interacting with Vladimir Putin after their meeting in Alaska, where no deal was reached on the Ukraine war. The video, shared by Russia Today, depicts Trump fawning over Putin, including a two-hand handshake, while the White House has not released similar candid clips.
Key Points:
The Kremlin leaked footage of Trump and Putin sharing a friendly moment backstage after their meeting in Alaska.
The video shows Trump offering a two-hand handshake and laughing with Putin, despite no progress on ending the Ukraine war.
Russia Today described their interaction as 'light chatter' and highlighted the Kremlin's quick release of the video.
The White House has not shared any candid footage of the two leaders together.
Experts warn that Putin is a master manipulator, while Trump boasts of their close relationship.
"Experts warn that Putin is a master manipulator as well as a war criminal, but Trump has boasted of his close relationship with the Russian president as talks reportedly continue."
Government papers found in an Alaskan hotel reveal details of Trump-Putin summit
Posted on r/politics |
Score: 17066 |
Comments: 847
Sensitive documents detailing the Trump-Putin summit in Alaska were accidentally left on a public hotel printer, revealing meeting locations, staff phone numbers, and other confidential details. The White House dismissed the incident as a non-security breach, while experts criticized the administration's lack of professionalism.
Key Points:
Sensitive State Department documents about the Trump-Putin summit were left on a public printer in an Alaskan hotel.
The documents included meeting locations, staff phone numbers, and details about a ceremonial gift and lunch plans.
The White House downplayed the incident, calling it a 'multi-page lunch menu' and denying it was a security breach.
Experts criticized the administration for sloppiness and incompetence in handling high-stakes meetings.
The documents also revealed phonetic pronunciations of Russian attendees, including 'Mr. President POO-tihn.'
""It strikes me as further evidence of the sloppiness and the incompetence of the administration," said Jon Michaels, a professor of law at UCLA who lectures about national security."
Trump, 79, Seems Utterly Perplexed About Where Alaska Is - The president made multiple comments suggesting he doesn’t know Alaska is part of the United States.
Posted on r/politics |
Score: 8143 |
Comments: 651
The article highlights instances where former President Donald Trump appeared confused about Alaska being part of the United States during a meeting with Russian President Vladimir Putin in Anchorage. Trump's remarks, including saying he would 'go back to the United States' while in Alaska, sparked criticism and ridicule.
Key Points:
Trump repeatedly suggested Alaska is not part of the U.S., including saying he would 'go back to the United States' while in Alaska.
Democratic Congressman Eric Swalwell mocked Trump, implying he thought he was in Russia.
Trump also referred to St. Petersburg as 'Leningrad,' a name not used since 1991.
Press Secretary Karoline Leavitt clarified Trump was meeting Putin in Alaska, not Russia.
The White House did not respond to requests for comment on Trump's remarks.
""We’ll see what happens," Trump told Baier, speaking about a potential deal with Putin, while on board Air Force One en route to the meeting in Anchorage. "If it’s bad, if it’s something I don’t see a future in, I’m gone, I’ll leave," Trump added. "I’ll go back to the United States.""
Friends: do not let friends run "Proxmox" Community Scripts
Posted on r/selfhosted |
Score: 497 |
Comments: 215
The article warns against running Proxmox community scripts due to security risks, as they often execute unchecked code as root. It criticizes the 'curl | bash' practice and suggests using official container images in a VM as a safer alternative.
Key Points:
Proxmox community scripts pose security risks by running unchecked code as root.
The 'curl | bash' practice is unsafe and should be avoided.
The article suggests using official container images in a VM for better security.
The original maintainer's passing has led to a lack of clear responsibility for these scripts.
The r/Proxmox subreddit now bans posts related to these community scripts.
"Think twice before **running scripts on your host as root (they all have to run as root) that source (run) a freshly downloaded piece of code (every single time) from a URL (other than your own) fetching a payload that you cannot check** got signed by a trusted party or has a well-known checksum (that you actually verify)."
Posted on r/programming |
Score: 188 |
Comments: 57
The article explores the unique maximalist design of Japanese websites, contrasting with the minimalist design often associated with Japan. It investigates potential causes, including writing systems, cultural differences, and technological adoption, supported by quantitative analysis and expert opinions.
Key Points:
Japanese websites are notably maximalist, featuring bright colors, small images, and dense text, contrary to the minimalist design often associated with Japan.
Possible reasons for this design include the complexity of CJK characters, cultural preferences for information density, and slower adoption of modern web standards.
Quantitative analysis of 2,671 website images revealed Japan's unique concentration of lighter-colored and denser designs compared to other countries.
Japan's older population and reluctance to update technology may contribute to the persistence of older web design styles.
"The internet was made as a way to share documents on desktop computers This document sharing quickly extended to interactive, multi-media experiences These developments happened quickly and with very little standardization leading to a lot of unique web design (that often crashed)"
Branch prediction: Why CPUs can't wait? - namvdo's blog
Posted on r/programming |
Score: 118 |
Comments: 48
The article explores the concept of branch prediction in CPUs, explaining how it impacts performance and why even advanced compiler optimizations like LLVM can't overcome poor branch prediction patterns. It details the stages of instruction execution and how modern CPUs use pipelining to improve efficiency.
Key Points:
Branch prediction is crucial for CPU performance, and misprediction can negate compiler optimizations.
Modern CPUs use instruction pipelining to execute multiple stages of different instructions in parallel.
The Program Counter (PC) register tracks the current instruction address, incrementing sequentially.
Branch misprediction latency remains a significant cost, around 5ns, similar to 2012 levels.
Different hardware units handle various stages of instruction execution (fetch, decode, execute, memory access, write back).
"Poor branch prediction patterns can easily negate the benefits of multiple LLVM optimizations."
What's in your global ~/.claude/CLAUDE.md? Share your global rules!
Posted on r/ClaudeAI |
Score: 110 |
Comments: 50
The article discusses the author's minimal global CLAUDE.md file, which contains universal rules for all projects, including date tracking, language preferences, git commit conventions, inclusive terminology, and tool preferences. It also provides a script to auto-update the date in the file via cron.
Key Points:
The global CLAUDE.md file includes essential rules like current date tracking, English-only code, and conventional git commit formats.
Inclusive terminology is emphasized, with terms like 'allowlist/blocklist' and 'main branch' recommended over outdated ones.
Tool preferences such as 'rg' over 'grep' and 'fd' over 'find' are specified for efficiency.
A cron script is provided to auto-update the date in the CLAUDE.md file daily.
The author encourages others to share their minimal global configs.
"**Git Commits**: Use conventional format: (): where type = feat|fix|docs|style|refactor|test|chore|perf. Subject: 50 chars max, imperative mood ("add" not "added"), no period. For small changes: one-line commit only. For complex changes: add body explaining what/why (72-char lines) and reference issues. Keep commits atomic (one logical change) and self-explanatory. Split into multiple commits if addressing different concerns."
Frigate 0.16 introduces advanced features like automatic number plate recognition (ANPR), facial recognition with tagging, and a viewer role for read-only access. The release solidifies Frigate's position as a leading open-source, self-hosted CCTV solution.
Key Points:
Automatic number plate recognition (ANPR) with tagging capabilities
Facial recognition with personalized tags
Viewer role for granting read-only access
Enhancements to Frigate's reputation as top-tier open-source CCTV software
"This is hands down the best open source self hosted CCTV software there is"
The article argues that under a Georgist system, which taxes economic rent from non-reproducible assets like land, inheritance taxes become unnecessary. It distinguishes between reproducible assets (e.g., houses, businesses) and non-reproducible ones (e.g., land, patents), emphasizing that Georgism already addresses the inequality caused by the latter.
Key Points:
Inheritance taxes aim to prevent generational inequality but fail to distinguish between reproducible and non-reproducible assets.
Georgism taxes economic rent from non-reproducible assets (e.g., land) and eliminates taxes on production, making inheritance taxes redundant.
Reproducible assets (e.g., houses) can be passed on without harming others, while non-reproducible assets (e.g., land) create monopoly-like inequality.
Georgism promotes economic opportunity by allowing free production while compensating society for the use of non-reproducible resources.
The article cites Mason Gaffney to highlight the distinction between productive wealth creation and the monopolistic control of land.
"Amassing claims on wealth by creating and producing is not, therefore, a threat to others. Amassing capital through saving does not weaken or impoverish others. Producing goods does not interfere with others doing the same."
The author shares their journey into self-hosting and their decision to contribute by creating an iOS app for Pangolin, a tool for accessing local apps remotely. The app, named Pango, allows users to manage sites, domains, and resources, and is currently available via TestFlight.
Key Points:
The author is a backend developer who started self-hosting to gain control over their data and privacy.
They created an iOS app for Pangolin to simplify managing local apps remotely.
The app features include listing and managing sites, domains, and resources, and switching organizations.
The app requires enabling the Pangolin API and creating an API key for access.
The app is currently in TestFlight and the author welcomes feedback.
"I always wanted to contribute to self hosting or help other people to start doing this but I don’t have this self-confidence about contributing to existing projects, so I decided to build something new."
The article discusses the importance of reading assembly code to optimize performance, using the MurmurHash64A hash function as an example. It compares the assembly output from GCC and LLVM, highlighting inefficiencies and suggesting improvements.
Key Points:
Reading assembly code can reveal inefficiencies in high-performance functions like hash functions.
The article compares GCC and LLVM's assembly output for MurmurHash64A, noting redundant operations and unoptimized memcpy calls.
Optimizations include replacing memcpy with manual loops or unaligned loads to improve performance.
The author emphasizes the need to measure performance to understand the impact of these optimizations.
Practical tips are provided for debugging and improving assembly output, such as using atomic loads for unaligned pointers.
"There's not a thing wrong with this. Let's take a look at the x86-64 assembly it produces"
Apple’s new Processor Trace instrument is incredible
Posted on r/programming |
Score: 6 |
Comments: 0
Apple's new Processor Trace instrument in Xcode provides detailed, hardware-level insights into app performance by capturing every branching decision at the CPU level. It addresses gaps left by traditional profilers and integrates seamlessly with Xcode, though it requires newer Apple hardware like the M4 chip or iPhone 16.
Key Points:
Processor Trace captures every branching decision at the CPU level, offering a complete execution flow rather than statistical sampling.
It integrates deeply into Xcode, unlike complex standalone tools like Intel's VTune Profiler.
The tool helps identify performance bottlenecks like branch misprediction or cache misses with unprecedented detail.
It is only compatible with newer Apple hardware (M4 chips and iPhone 16), limiting accessibility for some developers.
Early testing suggests it is highly useful for uncovering performance issues that other tools miss.
"Processor Trace shows you exactly what the CPU is doing, so you can optimize for the actual hardware behavior rather than guessing."