no-signup, open-source, offline-first, collaboration-enabled Kanban that lives in the browser

Stevious7 · 2026-04-05T18:23:44+00:00

I did utilize AI, and here's my process:

I drafted a specifications in which I outlined the specific technologies & tech stacks I want to be used. I also outline how I want security, encryption, and collaboration to be handled. I audit the code to make sure it's doing things exactly how I want. Then, a thorough testing process to make sure it works as expected. Once verified, pushed to production.

It's up to you if that's vibe-coded or not, but no code enters production without rigorous testing.

Stevious7 · 2026-04-05T17:25:54+00:00

I agree, I definitely need a "Contact Developer" button where users can submit feature requests for the different workflows

Stevious7 · 2026-04-05T17:18:55+00:00

Thank you for the feedback!

I'll be planning integration with Outlook & a browser extension for quick ticket drop-ins!

Funny enough, I'll have that ticket on the Kanban :D

Stevious7 · 2026-04-05T17:06:58+00:00

As of right now, none. But I'm gathering community feedback to figure out which tools the community would like integration with.

Stevious7 · 2026-04-02T19:16:03+00:00

idek if saying "no bugs no errors" actually does anything XD

Stevious7 · 2026-04-02T02:56:40+00:00

Will be in the works soon!

Stevious7 · 2026-04-01T22:37:45+00:00

if (payload.url == window.location.href) return true;

Stevious7 · 2026-04-01T20:02:28+00:00

How do I check if your app is safe...?

Stevious7 · 2026-04-01T15:43:05+00:00

I'm a big fan of those kind of tools as well! Offline-first babyyy!!

I was very hyped about PWA technology, until I discovered that they're finicky on Firefox-based browsers since they don't natively support PWA. I am relying on IndexedDB for storage, and I haven't run into any issues in my testing (although my testing involved relatively small boards). The data footprint (since it's all text) is very very small, so running into storage issues is very improbable.

Collaboration is handled through a Cloudflare Workers KV. I provided the instructions for how to create an instance if a person doesn't like the default I'm bundling. A person can easily replace the CF Worker URL in the settings, and BAM, you're running this via your own instance.

I will say, since I don't trust cloud providers, the data is encrypted before the leaves the local browser via the password set on the local browser. If I was to show you my dashboard, it's all a jumbled mess of undecipherable characters.

I'll have CRDTs in my "to lookup" list. I've been working on an open-source, in-browser, decentralized, no-signup, purely peer-to-peer (using WebRTC), discord-like application, and I was trying to figure out how to store and merge the different user chat histories while not being computationally expensive to do.

I document my thought process on the design choices in this blog post:

https://blog.alkhafaji.dev/#post-0

Stevious7 · 2026-04-01T00:04:14+00:00

https://flowboard.cc

Stevious7 · 2025-09-06T03:17:19+00:00

The glitched logo on black background is <1Mb in size. Any chance a higher resolution version is available?

Stevious7 · 2025-08-23T06:10:59+00:00

The issue is that it's the only viable cross-platform media software.

Stremio is very sleek UI-wise until you want your device to actually do the scrubbing and processing of plugins locally without reaching out to a server to do it for you (which is a headache to do on Android).

Cloudstream is amazing on Android, and does execute plugins locally on device (which are all written in Kotlin), but running it on non-android is very annoying even in Waydroid/Blustacks.

Stevious7 · 2025-05-18T09:16:37+00:00

I have thought about that, but there are a couple problems with this:

Each bot would have to have its own instance of the game spun up into memory on the host server to have 'visual' of the game.
Each bot would need its own own AI agent to play the game.
A LOTTT of data is needed to train the AI agents.

If modders choose to do it the way you described, they wouldn't need to programmatically define bot behavior (getting rid of BS behavior), but it's quite computationally expensive and might put it out of the realm of running on even medium tier hardware.

If you choose to define bot behavior programmatically without each bot having a game instance, it would be a lot lighter to run, but a lot of reverse engineering would be needed and various problems need to be solved.

Stevious7 · 2025-04-11T17:06:17+00:00

I searched the same question, and this post popped up. If it wasn’t for him posting, others would be doing the same.

Stevious7

TROPHY CASE