I've been building MinimalChat for a while now, and based on the feedback I've received, it's in a pretty decent place for general use. I figured I'd share it here for anyone who might be interested!

Quick Features Overview:

Mobile PWA Support: Install the site like a normal app on any device.

Any OpenAI formatted API support: Works with LM Studio, OpenRouter, etc.

Local Storage: All data is stored locally in the browser with minimal setup. Just enter a port and go in Docker.

Experimental Conversational Mode (GPT Models for now)

Basic File Upload and Storage Support: Files are stored locally in the browser.

Vision Support with Maintained Context

Regen/Edit Previous User Messages

Swap Models Anytime: Maintain conversational context while switching models.

Set/Save System Prompts: Set the system prompt. Prompts will also be saved to a list so they can be switched between easily.

The idea is to make it essentially foolproof to deploy or set up while being generally full-featured and aesthetically pleasing. No additional databases or servers are needed, everything is contained and managed inside the web app itself locally.

It's another chat client in a sea of clients but it is unique in its own ways in my opinion. Enjoy! Feedback is always appreciated!

Self Hosting Wiki Section https://github.com/fingerthief/minimal-chat/wiki/Self-Hosting-With-Docker

I thought sharing here might be a good idea as well, some might find it useful!

I've added some updates since even the initial post which gave a huge improvement to message rendering speed as well as added a plethora of new models to choose from and load/run fully locally in your browser (Edge and Chrome) with WebGPU and WebLLM

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

[–] toastal@lemmy.ml 1 points 4 months ago* (last edited 4 months ago)

These have tradeoffs you don’t see when certain groups cannot participate due to personal or systemic political or philosophical reasons. You also can’t hear from that crowd since they haven’t been given a place to voice.

In the case of chat & forges, these are solved for quality free options (& even decentralized in some cases). The choice are at least in the good enough category if not better in some aspects (& worse in others). For chat a room in Libera.Chat or OFTC is free & meant for free software—even if it is labeled as unofficial it still gives folks a sanctioned place who wish to avoid Discord for privacy, security, preformance, or US services being blocked (as well as being an out-of-band option for when a server is inevitably down). For forges, living in part of world where Microsoft often heavily throttles my bandwidth & all outages are during my day time, it is never a bad idea to configure your VCS to push to a second mirror like Codeberg, et al. not just for freedom reasons but resilience from server outages & censorship (see youtube-dl or the Switch emulators or nations that have blocked the whole IP due to something governments didn’t like in someone else’s repo). When you start coding around Microsoft GitHub’s Actions or API or Discussions or any specific integration without an eye to the generic/portable approach which is easier done from the start, dependence starts to add up. While readonly mirror would suck for freedom of contributions/communications, it is an option if it is seen as too noisy or too much of a burden to support multiple forges outages & censorship are real (especially if not in the West).

“Enshitification” is the buzzword for services whose quality goes down & devolves to ads + selling user data for profit maximization—usually because they can because users/groups are now locked into the service having relied too heavily on their infrastructure. We see free software projects still stuck on Sourceforge & Slack due to lock-in. Having started with the free option, the lock-in probably can’t happen. Even having one option supported as a backup makes one cognisant of features that aren’t going to port when these US-based, profit-driven entities decide to gradually make things worse to the point where users want to leave with history showing us this has happened several times.

You might say it is pragmatic, but I think it’s both lazy & short-sighted to not have these near-zero-effort options set up even as a back up (truly can be set & forget if really wanted)—especially when you think these values are good enough for the service you are building but also interacting on Lemmy, a decentralized, self-hostable platform (who said they have every intention of migrating their code to self-hosted as soon as ForgeFed is merge for federation).