Selfhosted

60409 readers

318 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

How do you capture things quickly across devices in a self-hosted setup? (lemmy.world)

submitted 3 months ago by oldany@lemmy.world to c/selfhosted@lemmy.world

48 comments fedilink hide all child comments

I’ve been struggling with something that sounds simple but is surprisingly annoying:

capturing content quickly across devices in a self-hosted environment.

On Android there’s share, on iOS shortcuts, on desktop copy/paste… but everything feels fragmented.

I often end up losing things or postponing them just because capturing isn’t frictionless.

Curious how others handle this.

you are viewing a single comment's thread
view the rest of the comments

[–] oldany@lemmy.world 0 points 3 months ago (1 children)

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.

[–] Rivalarrival@lemmy.today 1 points 3 months ago (1 children)

Let's try this a different way...

How do you want to indicate something should be retained? What is the single, physical act you want to perform to tell the operating system "this thing needs to be captured"?

[–] oldany@lemmy.world 0 points 3 months ago

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.