jm666 · HackerTrans

w zeszłym rokudiscuss

Thanks. I'd say: simple access control (== easy to invite friends, publish as blog, password-protect), flexible document structure & roles (todos, notes, chat, image board, ...), pretty great image gallery, visual styling separated from content (cleaner UX).

jm666

w zeszłym rokudiscuss

Thx, will fix!

jm666

w zeszłym rokudiscuss

Thank You too; I understand, I'm a long time vi & ripgrep user and honestly do not like wysiwyg editors too much; most of my private notes are still rsynced plaintext.

For me, the valuable usecases for kraa are: small notes shared accross devices/people (desktop/phone, family todos), pw-protected gallery for family, and the possibility to turn a note into a BS-free nice blog post super easily. The BS-free aspect is important, but it also means we will be compromising on features (compared to notion/wp/..).

EDIT (adding):

Also, as for the desktop application storing files localy - we do not plan that now, it is too much of a stretch from colab web app :-) We will however probably support localStorage offline mode & p2p / encrypted documents, but that is still something else.

Kind regards!

jm666

w zeszłym rokudiscuss

It is a collaborative document, saved live in a same way as google docs (with offline local support coming, if You are out of cell). The benefit is to have a simple way to create colab documents, with invite logic, which can be used for different purposes seamlessly - private notes, shared todo-lists, password protected gallery, read-only blog post, chat.

We will have markdown / keep / ... import of the notes, a bit later, but that is not probably what You meant with file uploads. The front-page navigation needs care, thx for feedback.

jm666

w zeszłym rokudiscuss

Thx. Documents have access control (so you can control who can see the docs / who can collaborate; private by default) and we are responsible, but the content is not end-to-end encrypted if that is what You are asking; we plan to introduce p2p documents and end-to-end encrypted stuff in time.

jm666

w zeszłym rokudiscuss

Yes, the collaboration & publishing usecases need that; also simpler. We have private (end-to-end encrypted) and p2p documents in the backlog tho.

jm666

3 lata temudiscuss

Will stay up forever :-)

The usecase is basically quick & bullshit-free sharing of text stuff/links/notes, also realtime, lockable & with fixed url.

Personally, I use it to have my own public scratchboard, to share links w friends.

comments