Hey All!
Been tinkering on a side project called Quickpoint. It’s a super lightweight, keyboard-first writing and sharing tool. Think of it like a notepad that instantly turns what you type into a shareable page- for notes, code demos, quick thoughts, or even presentations.
The goal is to stay in flow. no tabs, no formatting fluff, just type and share. I’m still very early (beta-ish stage), so I’d love feedback!
It’s Quickpoint.me
You don’t need to sign up. just hit the link and try it. Would really appreciate your thoughts, and happy to check out anything you’re building too.
Thanks! 🙏
First of all- thanks for the feedback. Much appreciated- honestly. I can use this stuff to advance and shape it move forward.
I’ll look at that bug straight away!
It’s not self-hostable (yet). Would that be important (why?)… I suppose it depends what you’re using it for.
If I use it as a note taking + sharing with few friends. If I publish the notes on the open internet or use it as a pastebin with nice formatting then no.
Though in the former case client side encryption also works otherwise.
Also I generally prefer open and self hostable software cause vendor lockin, central service going down, enshittification etc. If the software is open users can contribute and fix bugs too which makes the service more featureful and robust.
I’ve been thinking about a self-hosted option, but your framing helps prioritize why that matters beyond just checking a box. Also noted on the client-side encryption. It makes total sense in those scenarios.
Would love to hear more about how you’d ideally deploy or manage a self-hosted version: Docker container? CLI? Something else?
Nowadays I deploy most self hosted services as containers. If something is not available as such, I install it inside container and make a Dockerfile of it. Snap is useful too here (cf nextcloud). For some rust/go projects I just run the binary on the host directly as a systemd service. The corresponding update service pulls the release, builds it locally and restarts the service appropriately.
Which means it totally depends on the project structure, scale and security administration which in turn depend on user. Somebody else might want something totally different but I would suggest go for container.