Hi, This is my first post here, pretty intimidating! haha
I shared this on reddit, and one of my community members told me this is a good place to also share it, so here we go!
A couple of months back I have built a checklist/note taking app for myself and called it rwMarkable, posted it on reddit and a lot of people seemed to resonate to it, so I kept adding new features and enjoying the small but very involved community that has built around it.
For anyone who hasn't heard of the project before, here's a quick bullet list of some features:
- Checklists: Create task lists with drag & drop reordering, progress bars, and categories. Supports both simple checklists and advanced task projects with Kanban boards and time tracking.
- Text Notes: A clean WYSIWYG editor for your notes, powered by TipTap with full Markdown support and codeblock syntax highlighting.
- Sharing: Share checklists or notes with other users or publicly with shareable links.
- File-Based: No database needed! Everything is stored in simple Markdown and JSON files in a single data directory.
- User Management: An admin panel to create and manage user accounts with session tracking.
- Customisable: 14+ built-in themes plus easy custom theme support.
- API Access: Programmatic access to your checklists and notes via REST API with authentication for various integrations.
- OIDC integration: Use any provider to authenticate, follow this tutorial on how to
There have been a lot of requests to change the name due to it sounding a little too close to reMarkable (the tablet - which, btw, i had no idea existed at the time lol) and after getting some amazing community suggestions we landed on jotty.
You can find all the info (and a demo) here: https://jotty.page/
You can find the repo here: https://github.com/fccview/jotty
Let me know what you think, the app is very much still in development and every week new features get added (that said, I really value the simplicity and lightweight nature of it, so I will not add anything that compromises it).
Few screenshots
p.s. Nice to meet you all <3
Hey, thank you! Well I know discord very well so I just went for it because it's what I am familiar with, but I am fairly open to have more than one community engagement platform, what did you have in mind? I heard a lot of good things about signal within the self-host community, but then again.. it did go down with the aws outage with everything else yesterday lol
A ticket tracker and a wiki!
Else all the institutional knowledge about your software that your users are adding too vanishes forever into a black box. And that'd be a dang pity
Yes! I am absolutely working on a wiki! Release notes are very detailed so it's easy to track progress scrolling through them on GitHub (I do this for work too, so I am fairly organised with that)
I'll add a wiki to the official site once I'm done building it, there is a help button within the app itself with some knowledge base on key features ♥️
Have you thought about migrating or mirroring the code from github to codeberg?
FYI the github repo can also have a wiki
That is actually such a good point 🤦♂️
Sometimes I tend to reinvent the wheel, I'll probably enable it and the community can help out document stuff, duh 🤦♂️ thank you
Ffs Signal went down with AWS??
Jup 😢
Yeah, I assume they use AWS for end to end encryption, so not the end of the world, but goes to show how fucked up the internet has become, when a service hosts a third of the web something has gone terribly wrong 😅
Yea, it's the end of the world with Signal.
Having such a dependcy just exposes yet another way their story doesn't add up, like dropping SMS support because of engineering costs. Apparently, SMS is so hard to do there are free SMS apps.
I can't trust them at this point.
And how does E2E require a middleman?
More like it's their store-and-forward servers. Why that's on AWS, or more importantly not distributed with auto fail over is a major fail, as in "get fired" failure.
Who told you it was because of "engineering costs"?
https://signal.org/blog/sms-removal-android/
I mean, I don't use it so I can't really say much on the topic, when looking into it yesterday I found this article https://signal.org/blog/signal-is-expensive/ which kinda goes through some of the stack they use, and in all fairness they do mention aws in the mix, so it's not like they were keeping it hidden or anything, it'd be valuable for a company who values privacy so much to be a little more upfront on what's used for what but as you're probably well aware we don't - and never will - live in a perfect world do we haha
Matrix is generally very nice for chat, and Discourse for forums.
I hear there's this new thing called PieFed that's pretty cool...
Hey some folks responded here which is great! For me, I think wiki and tracker are perfect like someone else mentioned, because a lot of folks without accounts can still access the knowledge created. The hard part is moderating of course. I’m not sure there is a perfect solution.
Ultimately, you’re producing something cool for the community and you get to set the terms for that; if discord is easy and sustainable, I prefer that to you doing anything else that isn’t sustainable to see the project through as long and vibrantly as you can. So in that sense just choose what makes sense.
So in short: do what makes sense for you and if one of the alternatives listed (maybe wiki it seems? That would be cool with me) works then that’s great!
I guess I’ll also plug forgejo or codeberg at this time haha
Edit: I’ll also say, more folks here for discussion is cool too, and good to have you posting and hope to see more discussion around it in the future here!
Hey thank you so very much!
Yeah, you said it best! I take all suggestions on board but ultimately I won't do anything that is to my detriment, between work and family (with two very very young kids) I have little time to spare haha my precious evenings should go to fun coding and not admin, I do enough of that at work as is lol
Still getting used to the layout here, feel like I am missing a lot of replies, but yeah, wiki seems to be a very manageable solution for now, GitHub wiki is what I'm leaning towards :)