[go: up one dir, main page]

  • 2 Posts
  • 28 Comments
Joined 16 days ago
cake
Cake day: March 24th, 2026

help-circle
  • Yeah that “too many clicks” thing is exactly what kills it for me. Like if I have to think even a little about where to put something or which mode I’m in, I just don’t capture it at all. The 2-context thing feels real… capture vs actually working with the stuff later. I’ve been trying something closer to a “single flow” where capture is basically instant and everything else happens after… still figuring it out, but it already feels way more natural.


  • Yeah weekly notes are a nice middle ground. I tried something similar for a bit, and it definitely helps reducing the friction at capture time. But I noticed that over time those notes tend to become kind of dense… like everything ends up mixed together and it’s harder to go back to a specific thing. Maybe it’s just me, but after a while it still felt like I was doing some form of “light organization” upfront. Curious if that ever becomes an issue for you or if it stays manageable.


  • That “slider” idea is actually really interesting. I think that’s exactly what’s missing in most tools… they treat notes as static, but in reality a lot of them are tied to a moment. Like sometimes I don’t even need the full content, just a small trigger is enough to bring everything back. That’s also why I started thinking more in terms of a “timeline of captures” rather than structured notes… still pretty rough, but it feels closer to how memory actually works.


  • Yeah I’ve been there 😅 At some point I realized that if something survives only if I manually “clean it up”, it probably won’t survive at all. The interesting part for me is that capturing is easy… but revisiting is the real bottleneck. So lately I’ve been trying to just keep everything in a sort of “raw stream” and only interact with it when I actually need something. Still experimenting, but it feels way less stressful than forcing a system.


  • Yeah that’s exactly the kind of thing that always breaks it for me too. As soon as you add scanning, tagging, or any extra step… it’s no longer “capture”, it’s already processing. And at that point I just don’t do it. The “when” part is interesting btw, I do something similar mentally… like I remember when I saw something more than where I stored it. I actually started experimenting with a super minimal “capture layer” just to avoid all that friction… basically dumping everything first and thinking later. Still figuring it out though.


  • Yeah this resonates a lot. That “few seconds” thing is real… if it’s not instant, I just don’t capture it, or I lose the original thought. I also noticed that paper works great for thoughts, but it kinda breaks when it’s links or anything digital… then you end up splitting your system anyway. I guess that’s where I struggle the most, having something that’s as fast as pen and paper, but still works with digital stuff. Not sure if that’s even possible tbh.


  • Yeah I tried something similar for a while.

    Like having a sort of “inbox” folder and just dumping everything there… it works, but for me it kinda breaks when I’m on mobile or moving around.

    Also I noticed that if I don’t process that folder regularly, it just becomes another black hole 😅

    I think my main issue is not even organizing… it’s actually capturing things in the moment without losing context or momentum.

    Curious if you ever feel that too or if your workflow stays manageable over time.





  • That’s a really good way to frame it.

    I kept coming back to the idea that the “act” shouldn’t be something new you have to learn — it should reuse what you’re already doing in each context.

    So instead of one single physical gesture, it’s more like a single intent expressed through different native actions:

    • on mobile → share
    • on desktop → paste
    • in browser → bookmarklet
    • sometimes even just typing something and sending it

    The key (for me) wasn’t forcing one gesture, but making all of those feel like the same action underneath.

    So the mental model becomes: “this goes into my inbox”, regardless of how I triggered it.

    That’s where things started to click for me.


  • Yeah exactly — that’s pretty much the pattern I kept falling into too.

    “Texting myself” works, but it still feels like you’re bending a tool to do something it wasn’t really designed for.

    What I was trying to fix was that exact moment before that — when something appears and you either capture it instantly… or lose it.

    So instead of choosing the tool each time, I tried to make the entry point always the same, and push the “what is this?” decision later.

    Curious if that resonates with how you use it day-to-day.



  • Good question 🙂

    For me it’s mostly the small, in-the-moment things:

    • a link I want to check later
    • a quick thought or idea
    • a snippet of text or code
    • something I see on my phone that I don’t want to lose
    • sometimes even just a reminder or “I should look into this”

    Not really structured notes — more like “things that appear during the day” that I don’t want to think about organizing right away.

    That’s also why tools like Joplin or OneNote never quite fit for me in that specific moment — they work great once you sit down to write something, but not as much as a quick, frictionless entry point.


  • Yeah that makes sense — treating a folder as the universal entry point is a clever way to unify things.

    I think that’s exactly the direction: trying to reduce everything to a single “drop zone”.

    Where I personally kept feeling friction is that you still need something in between to get things into that folder (scripts, gestures, automations, etc.).

    So the entry point becomes “save to this folder”, but the way you get there still depends on context.

    That’s the part I always found hard to make truly uniform.


  • That’s actually a really interesting direction — using screenshots as a universal entry point.

    It kind of shows how strong the need is for a single capture flow, even if it means bending everything into one format.

    What always stopped me there is exactly what you mentioned — once you need OCR, scripts, post-processing… it starts adding friction again.

    I kept wondering if the entry point could stay just as universal, but without needing to transform the content first.


  • That’s actually a really solid setup.

    What always got me personally is exactly that — over time I’d end up with multiple “entry points” depending on context (screenshot, chat, browser, notes…).

    Each one works, but I’d still need to mentally switch between them depending on what I’m capturing.

    I kept wishing for something where the entry point is always the same, no matter the context.




  • Yeah I tried going the “second brain” route too (Trilium, Obsidian, etc.)

    What I kept running into is that they’re great once something is already in the system — but capturing still feels like a separate step where you have to think about where it belongs.

    I started wondering if capturing should be completely independent from organization, and almost “context-free”.

    More like a thin layer you can hit instantly from anywhere, without deciding anything upfront.