惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Google DeepMind News
Google DeepMind News
U
Unit 42
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
J
Java Code Geeks
D
DataBreaches.Net
B
Blog RSS Feed
D
Docker
L
LangChain Blog
aimingoo的专栏
aimingoo的专栏
F
Fortinet All Blogs
Y
Y Combinator Blog
A
About on SuperTechFans
V
V2EX
罗磊的独立博客
WordPress大学
WordPress大学
宝玉的分享
宝玉的分享
MongoDB | Blog
MongoDB | Blog
博客园 - 【当耐特】
Last Week in AI
Last Week in AI
S
SegmentFault 最新的问题
月光博客
月光博客
Vercel News
Vercel News
H
Hackread – Cybersecurity News, Data Breaches, AI and More
阮一峰的网络日志
阮一峰的网络日志

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
I lost a client note to iCloud sync conflicts — here's th...
강해수 · 2026-06-22 · via DEV Community

강해수

One iCloud conflict ate a note about a client's campaign structure. I didn't notice for three days.

That's the honest summary of month five with Obsidian on mobile. I run ad ops automation across four clients plus a content side business, so context-switching is the actual job — not a nuisance around it. The pitch for Obsidian mobile was simple: capture anything away from the desk, have it land cleanly in the same vault I work from. What I didn't account for was the sync layer behaving like a silent failure mode.

iCloud creates ghost conflicts roughly once a week for my setup. Obsidian surfaces them as duplicate files with a timestamp suffix — easy to miss if you're not looking. I wrote a Templater script that flags them in a dedicated "conflicts" note, which at least makes them visible. Still manual to resolve, but I see them now. The script doesn't fix the underlying problem; it just means I stop losing things.

The bigger behavioral shift was harder to admit: I had to stop trying to maintain my desktop curation discipline on mobile entirely. No linking, no tagging, no folder placement on the phone. Text goes into the inbox, full stop. Every time I tried to place a note properly during capture, I'd slow down enough that I'd abandon it and text myself instead — which defeated the whole point. It took six weeks of friction before I actually committed to that rule. Now a Dataview query on my daily note template surfaces all inbox files modified in the last 24 hours, and I process them at the desktop every morning in 8–12 minutes. The variance tracks almost entirely to how much I captured the night before, not to processing overhead.

I also tested Obsidian Sync for a month. Conflict handling was marginally better and sync was faster. Didn't matter — the actual bottleneck was never sync speed. The mobile editing experience itself, cursor behavior, keyboard interaction with long markdown files, is genuinely worse than desktop regardless of what's moving files around. Paying more for faster sync doesn't fix that.

I wrote up the full breakdown — including the Dataview query I use for inbox triage and what the 18-month scorecard actually looks like — over on dailyfocusmag.

Full post →