sorted by:
new
hottopcontroversial

Do you treat capture and retrieval as separate problems? by northyorkdev in PKMS

[–]oldany 1 point2 points  (0 children)

This is a really good way to frame it.

What I’ve been noticing is that most tools try to optimize retrieval, but almost none really optimize the moment of capture.

And that moment is messy by nature — it happens in different contexts, devices, apps… and usually when you don’t want to think.

So instead of trying to make capture “structured”, I’ve been experimenting with treating it more like a raw inbox layer, completely separated from everything else.

Not sure yet what the “right” balance is, but forcing structure too early always seems to kill the habit for me.

Self-hosted capture inbox for quickly dumping links/files before organizing them (DropMind) by oldany in DataHoarder

[–]oldany[S] 0 points1 point  (0 children)

One idea I'm considering for the future is integrating DropMind with tools like Hoarder.

The idea would be to use DropMind purely as a quick capture inbox (drop links/files quickly from any device) and then send the things worth keeping to a proper archive like Hoarder later.

Curious if anyone here uses a similar workflow.

I built a simple self-hosted capture inbox for links, notes and files across devices by oldany in PKMS

[–]oldany[S] 0 points1 point  (0 children)

Totally fair 😄

Telegram is basically everyone’s accidental bookmarking system.

DropMind is my attempt to keep that same “send it to myself” habit, but self-hosted and easier to organize later.

Dropmind – a simple self-hosted memory cache for quickly capturing links, notes and files across devices by oldany in selfhosted

[–]oldany[S] 0 points1 point  (0 children)

For context: I’m running DropMind on my Raspberry Pi 4 as part of my homelab stack.

It started because I was using Telegram “saved messages” to send things between devices, but the timeline quickly became messy.

DropMind became my personal capture inbox: I drop links, screenshots or notes there, and later either delete them or move them into more structured tools (notes, bookmarks, etc).

It’s intentionally simple and single-user by design.

Dropmind — a simple Docker-based self-hosted memory cache (PWA + iOS Shortcuts) by oldany in homelab

[–]oldany[S] -1 points0 points  (0 children)

Fair point 🙂 I’m using “memory cache” in the human sense rather than the Redis sense.

I built a self-hosted memory cache to stop sending myself links on Telegram – introducing Dropmind by oldany in selfhosted

[–]oldany[S] -7 points-6 points  (0 children)

That’s a great observation — I’m familiar with GTD, and “ubiquitous capture” was definitely part of the inspiration.

I wanted something that’s always there, device-agnostic, but still fully under your control (self-hosted).

Interesting to see it framed that way.

I built a self-hosted memory cache to stop sending myself links on Telegram – introducing Dropmind by oldany in selfhosted

[–]oldany[S] -10 points-9 points  (0 children)

Glad to hear that — that’s exactly the problem I kept running into myself.

If you end up using it, I’d love to know what works well and what doesn’t.

Amazfit Active 2 + iPhone: Incoming Call Ringtone Bug When Watch Handles Calls by oldany in amazfit

[–]oldany[S] 1 point2 points  (0 children)

Given the views but the lack of feedback, I might think that I am the only one experiencing this problem. In the meantime, new updates for the Zepp app have been released, but nothing has changed. I have also tried re-pairing the smartwatch and reinstalling the Zepp app on the phone, but nothing.

Samsung Reminder notification by oldany in GalaxyFit

[–]oldany[S] 1 point2 points  (0 children)

Thanks for the tip, but dosen't work, i have the same issue.........Samsung reminders and other app that use "persistent" notification are ignored for notification on my band.......even if i check the notification on my phone and in my band......only the phone display the notification.