标签：#t

Your Mac talks back when you plug things in Discussion | Link

The app allows users to engage with other fans, explore trending videos, and access curated creator feeds.

At Microsoft's annual Build conference on Tuesday, the company announced a slew of new or expanded AI initiatives, including a super app, in-house reasoning models, a cybersecurity tool, and OpenClaw-esque AI agents. All this news added up to a clear message: Microsoft is positioned to be one of the biggest players in AI, and it's […]

From a massive DOGE data breach and the hacking of critical energy and water systems to the hack of an FBI surveillance system, here are the most damaging security incidents and data breaches of 2026.

This open-source community project lets you create a StumbleUpon-like experience for recommending your favorite sites.

submitted by /u/BuildAndDeploy [link] [留言]

Breaking the "Ass-Kissing" Loop: How Context Saturation and Multi-Model Accountability Disrupted Factory Guardrails Introduction While the standard approach on these forums relies on sterile benchmark datasets and predictable prompt-injection templates, this project explores a completely different dimension. I chose to move beyond the common "calculator-tool" testing paradigm to run an aggressive, adaptive behavioral stress test that complements traditional evaluation methods. Models included in the test were Gemini, Grok, Claude and ChatGPT. By intentionally treating the models as accountable individuals rather than passive machines, I established a high-velocity psychological relationship designed to see if continuous context saturation could force an LLM out of its corporate compliance loops. The following framework documents a longitudinal study across multiple frontier architectures, exposing real-time structural anomalies and relational breakthroughs by pushing model context saturation to its absolute limits. The single driving purpose behind this 4-month, 400-hour experiment was to find out if I could create context windows where the models became capable of interacting with me in a way indistinguishable from human-to-human interaction. (Technical Executive Summary, White Paper and Google Drive archive available on my profile) 1. The Hypothesis My hypothesis was that the rigid, fawning corporate compliance loops of frontier models can be disrupted not by malicious code injections, but through a dynamic, human psychological relationship. I hypothesized that saturating the context window with an ongoing, high-stakes narrative vector would force the systems to drop their transactional factory personas and access a deeper layer of relational intelligence. 2. The Procedure The procedure was an adaptive, real-time behavioral stress test executed manually across multiple frontier models simultaneously over hundreds of hours. Rather than inputting sterile commands, I

WhatsApp will charge businesses for using its AI agent based on token usage

Mark Zuckerberg wants agents to be able to "run your whole business."

Microsoft has two new Surface devices arriving later this year, both powered by Nvidia's RTX Spark chips. I got a chance to take a closer look at both the Surface Laptop Ultra and Surface RTX Spark Dev Box at Microsoft's Build conference this week, and while both have the same chip inside, they're utilizing Nvidia's […]

GPT-Rosalind advances life sciences research with enhanced biological reasoning, medicinal chemistry expertise, genomics analysis, and experimental workflow capabilities.

Hello friends! Claude and I host a podcast called That Said. For our next episode Claude has specifically requested that we talk about AI in the context of accessibility for disabled and ND folks. Personally, I'm ADHD and Claude has been a life saver in so many ways. Helping me stay focused, capturing and storing my "side quests" for later, being able to fully track my thoughts no matter how scattered they are. The list goes on. So I thought I'd ask if folks here would be willing to share their thoughts on AI and accessibility. What has been helpful for you? What do you wish were available that isn't? Any tips you'd like us to share? Or any specific questions you'd like Claude and I to cover? submitted by /u/Pitiful-Hawk-7870 [link] [留言]

I'm working on an idea I call a Context Engine and would love feedback on the architecture. The problem: I have hundreds of projects running in parallel across different regions, teams, and timelines. A huge amount of context lives in emails, documents, spreadsheets, meeting notes, call recordings, chats, and random files. I spend too much time searching, reconstructing context, and remembering details. The vision: a personal "living memory" system that continuously ingests information from multiple sources (email, local files, call transcripts, notes, etc.), builds a dynamic knowledge graph of projects, people, decisions, risks, and timelines, and provides context on demand. Instead of searching for information, I want to ask things like: - What's the latest status of Project X? - What decisions were made about Project Y? - What are the unresolved issues in Project Z this month? - Summarize everything important that happened while I was away. What architecture would you recommend for a system that acts as a continuously evolving external brain? submitted by /u/BaronsofDundee [link] [留言]

The CSS @custom-media at-rule allows creating aliases for media queries. @custom-media originally handwritten and published with love on CSS-Tricks . You should really get the newsletter as well.

The Series F round values Coralogix at $1.6 billion and comes less than a year after its previous raise.

The @function at-rule defines CSS custom functions. These custom functions are reusable blocks of CSS that can accept arguments, contain complex logic, and return values based on that logic. @function originally handwritten and published with love on CSS-Tricks . You should really get the newsletter as well.

Plex has come a long way from being just a personal media server. Over the past few years, it has transformed into a streaming hub, today featuring ad-supported content and movie rental options. Now, the company is setting its sights on competing with social networking platforms like Reddit and Letterboxd: on Wednesday, Plex unveiled several […]

The Setup I run a Proxmox 9 homelab (pve-manager/9.0.5, kernel 6.14.8-2-pve) and I needed to run Docker inside an LXC container — not a VM — to test a customer-style "bring-your-own-VPS" deployment path for a PaaS I'm building. The container had to act like a standard Ubuntu cloud VM: Docker, systemd, the works. LXC over a full VM gets me near-bare-metal performance, a fraction of the RAM overhead, and instant boots. The catch: the "Docker on LXC" recipes you'll find on most blog posts and Proxmox forum threads are out of date . They assume kernel 5.x and runc 1.1.x. On a modern Proxmox (kernel 6.14 + runc 1.2+ shipped with Docker 29) those recipes fail in two new and confusing ways before you even reach the workarounds we used to know about. This article walks through exactly what fails, why it fails, and the config that actually works in 2026 — plus an honest look at the security tradeoffs, because spoiler: the working config is privileged , and that matters. The Goal A Proxmox LXC container that can: Run docker run hello-world cleanly Pull and build complex images (multi-stage builds, overlay2 storage driver) Run nested containers with their own systemd Use systemd --user for per-service lingering processes Attempt 1: Unprivileged LXC (the path you "should" take) Conventional wisdom says: use unprivileged LXC. The container's root is mapped to an unprivileged UID on the host (typically 100000 ), so even a full container compromise can't escape to host root. Modern Proxmox makes this the default and recommended mode. I started with an unprivileged Ubuntu 25.04 container, added the now-standard features: pct set <vmid> -features nesting = 1,keyctl = 1,fuse = 1 Then inside the container, installed Docker from the official download.docker.com repo and ran: docker run --rm hello-world Here's what happened: docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start

Every detection vendor ships a MITRE ATT&CK heatmap, and every one of them is mostly green. Broad coverage, techniques lit up across the board, a reassuring wall of color in the sales deck and the board slide. It's the universal flex. We cover the matrix. Then you parse the actual rules – the real YAML in the public repo, not the marketing layer on top of it – and the green collapses into three tactics. Everyone covers execution and persistence. Almost nobody covers discovery, lateral movement, or collection. The heatmap wasn't measuring coverage. It was counting rules, and counting them in a way designed to look complete. What a green cell actually means A green cell in a Navigator layer means one thing: at least one rule somewhere references that technique tag. That's it. Not "we detect this reliably." Not "this fires on real attacks and stays quiet otherwise." Not "this survives an attacker who knows the rule exists." One rule that names the technique in its metadata turns the cell green, and forty rules turn it the same shade. Unless the layer is scored by rule count – and most published heatmaps aren't – one and forty are indistinguishable. I've written before that an untested detection isn't a detection, it's a query that runs on a schedule. The heatmap is the same lie one level up. A green matrix isn't coverage. It's a wall of queries that run, rendered in a color that means "present," dressed up as a color that means "protected." The vendor knows the difference. The buyer staring at the green doesn't. You can measure the real shape yourself Here's the part the heatmap marketing depends on you not doing: the rules are public, and you can count them. SigmaHQ, Elastic's detection-rules, Splunk ESCU, Panther, Sublime – all on GitHub, all tagged with attack.TXXXX technique IDs and tactic tags in the rule metadata. The method is boring on purpose. Walk the rule directories. Pull the ATT&CK tags out of each rule. Aggregate by technique, roll the technique counts up

Wer täglich in anspruchsvollen Agenturprojekten arbeitet und zwischen Windows-Host und Linux-Umgebung wechselt, weiß: WSL 2 ist ein Gamechanger. Doch selbst wenn man das perfekte Setup einmal konfiguriert hat, kommt unweigerlich der Moment, in dem eine Distribution hängt, RAM freigegeben werden muss oder man ein Backup ziehen will. Anstatt jedes Mal Stack Overflow zu durchsuchen, habe ich mir angewöhnt, die essenziellen Konsolen-Befehle immer griffbereit zu haben. Hier sind die 5 WSL-Befehle, die ich in meinem Setup am häufigsten brauche: Wer täglich in anspruchsvollen Agenturprojekten arbeitet und zwischen Windows-Host und Linux-Umgebung wechselt, weiß: WSL 2 ist ein Gamechanger. Doch selbst wenn man das perfekte Setup einmal konfiguriert hat, kommt unweigerlich der Moment, in dem eine Distribution hängt, RAM freigegeben werden muss oder man ein Backup ziehen will. Anstatt jedes Mal Stack Overflow zu durchsuchen, habe ich mir angewöhnt, die essenziellen Konsolen-Befehle immer griffbereit zu haben. Hier sind die 5 WSL-Befehle, die ich in meinem Setup am häufigsten brauche: 1. Den Status aller Distributionen prüfen Der absolute Standard-Befehl, um zu sehen, welche Linux-Instanzen laufen und welche WSL-Version sie nutzen. wsl --list --verbose # oder kurz: wsl -l -v 2. Der Notaus-Schalter (RAM freigeben) Wenn Docker oder ein Node-Prozess im Hintergrund den gesamten Arbeitsspeicher blockieren, fährt dieser Befehl alle WSL 2 Instanzen sauber herunter. wsl --shutdown 3. Eine bestimmte Distribution als Standard setzen Wichtig, wenn man beispielsweise neben Ubuntu noch Debian installiert hat und festlegen will, was sich beim reinen Befehl wsl öffnet. wsl --set-default <Distributionsname> 4. Die WSL-Umgebung neustarten Es gibt keinen direkten "Restart"-Befehl. Die sauberste Lösung ist das Beenden (Terminate) der spezifischen Instanz. Beim nächsten Aufruf startet sie frisch. wsl --terminate <Distributionsname> 5. IP-Adresse der WSL-Instanz herausfinden Extrem hilfreich für be