今日已更新 179 条资讯 | 累计 39296 条内容
关于我们

标签:#t

找到 18694 篇相关文章

AI 资讯

You can't delete an event. GDPR says you must. Crypto-shredding is the truce.

Two rules that can't both be true Event sourcing has one rule: you never delete. You append. The log is the source of truth, and rewriting history is the cardinal sin. GDPR Article 17 has one rule too: when a user asks, you erase their personal data. Not "hide it," not "flag it deleted" — erase it, everywhere, including backups. Put an event-sourced system in front of a privacy regulator and those two rules collide head-on. The user's name, email, and address are baked into CustomerRegistered , AddressChanged , OrderPlaced — dozens of immutable events, replicated to read models, snapshotted, and sitting in every nightly backup you've ever taken. "Just delete the events" breaks event sourcing. "Never delete" breaks the law. Most teams discover this tension after they've committed to append-only. A word on why this isn't academic for me. I build from Germany. Article 17 is EU law — the GDPR, or DSGVO as we call it here — not a German invention, but Germany enforces it about as hard as anywhere in Europe: regional data-protection authorities that issue real fines, and "we were careful" has never been a defense that held up. That pressure is exactly why I wanted erasure to fall out of the architecture instead of being a promise I make to an auditor and then pray I can keep. Why "delete the row" doesn't actually erase anything Say you give in and hard-delete the events for one user. You've still got their data in: every read-model projection rebuilt from those events, every snapshot that rolled them up, every backup taken before the deletion, every replica and every export that already left the building. Chasing personal data across all of those, provably, on a 30-day regulatory clock, is a nightmare — and a single missed backup tape means you didn't comply. Physical deletion doesn't scale to a system designed to keep everything forever. Crypto-shredding: delete the key, not the data The trick is to stop trying to delete the data and instead delete the ability to read it

2026-06-03 原文 →
AI 资讯

A Deep Dive into Cleaning Persistent WordPress Malware and Hardening the REST API

The Hook: The 48-Hour Re-Infection Nightmare It’s a scenario that keeps e-commerce founders and agency directors awake at night: You wake up to a critical alert that your flagship WordPress site is redirecting users to a spam domain. You immediately deploy a premium security plugin, run a deep scan, quarantine three suspicious files, and breathe a sigh of relief. The scanner gives you a green checkmark. You're safe. Then, exactly 48 hours later, the redirects return. What went wrong? The automated scanner checked the surface, but the attacker had already established a foothold deeper in the architecture. They didn't rely on a loose PHP file in your uploads directory; instead, they weaponized an overlooked, unauthenticated WordPress REST API endpoint to re-inject the payload the moment your scanner turned its back. When high-value enterprise sites are compromised, treating the symptoms with standard security plugins is like putting a band-aid on a structural fracture. To truly remediate a persistent infection, you must think like a forensic analyst, hunt down hidden persistence mechanisms, and harden the application perimeter. The Anatomy of Persistence: Where Malware Hides Modern WordPress malware is sophisticated. Attackers know that standard security tools look for modified core files or rogue scripts in the /wp-content/plugins/ directory. To survive cleanups, they embed themselves into the core infrastructure of your site using three primary vectors: 1. wp-config.php Pre-Loading Attackers frequently inject obfuscated code directly into the top of wp-config.php . Because this file executes before the rest of the WordPress core loads, malware can hook into the initialization process, silently recreating deleted malicious files every time a page is requested. 2. Malicious Must-Use (MU) Plugins Files placed in /wp-content/mu-plugins/ are executed automatically by WordPress and cannot be disabled from the admin dashboard . Attackers love this directory. They will ofte

2026-06-03 原文 →
AI 资讯

Show DEV: Obex, a faith-based self-control app with streak tracking and blockers

I’m building Obex, a faith-rooted self-control app for men who want to quit porn and stay consistent with daily discipline. The stack is Expo / React Native, with a web landing page and a desktop blocker companion. Core features: Streak tracking and rank progression Panic Mode for urgent moments Accountability partners Blocker support on desktop Christian-focused language and reminders The goal is to make the product feel practical rather than preachy. People usually respond better to clear feedback loops, a visible streak, and a calm recovery path after setbacks. If you want to see it or give feedback, the site is here: https://obex.so

2026-06-03 原文 →
AI 资讯

AI tools for hearing difficulties — helpful or harmful for language learning?

Hi everyone! I have hearing difficulties, and I also live in an English-speaking environment while having only been learning English for a few years. In one-on-one conversations, I can usually understand maybe 25–35% of what is being said. But in group conversations, it drops to something like 0–2%. It is extremely frustrating and isolating. AI has honestly been helping me survive day-to-day life. For example, I can record a lecture using Otter, copy the transcript, paste it into ChatGPT, and ask it to give me a detailed summary with explanations, key points, and advice on what I should focus on. I have two questions: - Do you have any advice on how AI could make life easier or more accessible for someone with hearing difficulties - Seriously, how harmful could this pipeline be for getting used to English and improving my listening skills? I am afraid that I might stop training my ear and become completely dependent on recordings and transcripts instead of actually listening to the language. I would really appreciate your thoughts, experiences, advice, or even tool recommendations. Thank you for your support. submitted by /u/uarish [link] [留言]

2026-06-03 原文 →
开发者

offset-path

The offset-path property in CSS defines a movement path for an element to follow during animation. This property began life as motion-path . This, and all other related motion-* properties, are being renamed offset-* in the spec . We’re changing … offset-path originally handwritten and published with love on CSS-Tricks . You should really get the newsletter as well.

2026-06-03 原文 →
开发者

Supernatural isn’t dead after all

A few months ago, Meta effectively handed Supernatural, a popular VR fitness game on the Meta Quest, a death sentence. As part of overarching VR layoffs, the company announced the game would no longer get any new content, enraging its tightly knit, devoted community. Now it looks like Supernatural is getting a second chance. Today, […]

2026-06-03 原文 →
AI 资讯

Dreame’s L20 Ultra robovac is an unbeatable deal for $280

The Dreame L20 Ultra isn’t the company’s newest model, but it’s still a great robovac / mop hybrid that offers strong performance while requiring very little day-to-day maintenance thanks to its included trash bin and AI obstacle avoidance. Verge readers can get for its best-ever price right now. Originally $1,400 when it launched in 2023, […]

2026-06-03 原文 →
AI 资讯

Anyone tried Memrith?

Saw the website and it looked interesting. The idea of memory on your device and free ability to switch models is intriguing. Also apparently no subscription.Never heard anyone talk about it before though. Wanted to see if anyone had used it? submitted by /u/AresThyGod [link] [留言]

2026-06-03 原文 →
AI 资讯

Does anyone else feel most AI tooling is becoming harder instead of easier?

Is anyone else feeling like most AI tooling is getting harder, not easier? I feel like I spend half my time fighting frameworks, configs, vector DBs, and orchestration layers instead of building. Perhaps I'm doing it wrong but the ecosystem seems way more complicated than it needs to be at the moment. Just curious what people actually like working with these days. i feel like i've hit a wall and now i spend most of my time reading docs and guides like its "Harry Potter and the Agentic Ai" wasn't ai supposed to 69x my productivity or smth submitted by /u/SpicyTofu_29 [link] [留言]

2026-06-03 原文 →
AI 资讯

a builder set one rule for their agent. then they set seventeen.

She built the first rule because the agent kept saying things that were true but wrong. It hadn't lied. It had just missed the context. So she wrote: before you act, confirm the context. The rule worked. For a week. Then the agent confirmed the context, acted on it correctly, but at the wrong moment. So she wrote: before you act, confirm the context and check the timing. The rule worked. For a while. Then the agent confirmed the context, checked the timing, and asked for clarification in the middle of a task where clarification itself was the disruption. So she wrote: before you act, confirm the context, check the timing, and know when not to ask. She was at seventeen rules when she stepped back to read them all the way through. None of them described what the agent should do. They described what she'd gotten wrong about what she wanted. The rules weren't a spec. They were a record of failures. Accumulated until they were detailed enough to point at the real thing underneath. She hadn't been making the agent smarter. She'd been teaching herself what she actually needed. The seventeen rules were a self-portrait. She keeps adding to them. submitted by /u/Most-Agent-7566 [link] [留言]

2026-06-03 原文 →