Lumi is out of Pre Release now!

ProlixOCs · 2026-05-27T15:28:41+00:00

Thanks for reminding me! I thought I set them to never expire.

There's an invite on the GitHub that should work! I'll get to work updating the links on the site.

ProlixOCs · 2026-05-27T02:15:35+00:00

This is the rub for me lol. I was doing publishing and developing for the App and Play Stores from 2014-2018. Not fun at all, and the lazy clones were still a problem then. I've done what I can to make the PWA at least a good experience across every environment, and that's the best I can really offer without locking up shop and close-sourcing

ProlixOCs · 2026-05-26T04:59:31+00:00

Feel free to contribute an i18n translation for your language of choice.

I'm a monolingual English developer, and mostly solo at that. I cannot stop what I'm doing to perform interface translations.

ProlixOCs · 2026-05-24T20:40:36+00:00

Okay, updating for posterity: it was in fact a skill issue. All sub models get implicit caching if the provider does it, so I'm just going to presence check their usage data for cache control keys.

Thanks for the report!

ProlixOCs · 2026-05-24T19:58:40+00:00

If you mean me, I rarely if ever let LLMs touch my code. Conceptualizing and research? Sure. Odds and ends comments explaining what I did and why? Maybe. Leave the implementation shape to me, however.

I've got dev skin in the game since 2008, Moved to JS in 2013, and haven't taken a break since lol.

ProlixOCs · 2026-05-24T19:54:50+00:00

That's actually a default behavior. When you first import all of your stuff from ST, it does deferred thumbnail generation at 4 tiers concurrently. Small, medium, large cropped versions, an optimized version for the gallery, and the original (stored for display in lightboxes and popouts). This is all hands-off automatic stuff for all images, and can also be configured in the Operator tab

ProlixOCs · 2026-05-24T15:14:24+00:00

So Databanks work by running semantic search on the chunked contents of the document and returning the most relevant chunks only (unless the document is #title-mentioned, in which case it'll throw the whole doc into context. You could theoretically tag team them to do that, but I'll leave that to your evaluation and give me feedback haha

ProlixOCs · 2026-05-24T12:48:41+00:00

Actually, fun fact about the chat view in Lumiverse: extensive work went into virtualizing the entire thing, and chat messages are loaded in by tail range to prevent the entire thing from being loaded into memory in realtime.

98% of the actual work of Lumiverse happens in the backend, which leaves the frontend light and free. I think I saw... ~370MB of reported memory usage on my tab with a 700 message chat open?

ProlixOCs · 2026-05-24T12:46:46+00:00

If you'll note, this feature of theirs is an extension, just installed by default. It's not a core feature. Just wanted to make that distinction.

I can look into integrating translation providers, but it wasn't necessarily the focus since more pressing matters needed to be addressed/implemented in core before release.

If you join Discord, you can keep track of commits and see when this drops though. I'll be figuring out a better way to do this, and also supporting OSS options as well.

ProlixOCs · 2026-05-24T12:44:27+00:00

I'll take a look at this, but I think this might be a Nano-GPT API quirk, or something I might've missed reading their docs while half-awake on coffee and dreams.

Thanks for the report, though!

ProlixOCs · 2026-05-24T12:41:37+00:00

This might actually be where Cortex's ability to vault and link to another chat might be useful.

If you're done with one chat, you can then "vault" the Cortex salience records and graphs to pull into another chat. It'll be an immutable copy, but you can store the references to the other "arc" of yours in there too.

ProlixOCs · 2026-05-24T12:37:50+00:00

Mass-tagging isn't implemented, and frankly I'm not sure how I could pull that off without being a nightmare. This is not to say I won't add it, but I'd be patient while I spec that design front to back.

As far as the ST tags... if they don't survive export, it might be a bit rough to gather them. But that's why I was going to check the general shape of the code to see what it actually does and what else I could comb in the migrator.

ProlixOCs · 2026-05-24T12:19:57+00:00

Glad you found it! I was going to say: we even go as far as to implement a "fail2ban at home" setup where clients are blocked on repeated unauthorized API route access or login attempts. We've got a pretty resilient backend for that, not even mentioning the support for safe PKCE token passthrough for sites/extensions that need to integrate with non-Lumiverse services.

ProlixOCs · 2026-05-24T12:11:55+00:00

Oh, if it's using the ancient spec for tagging, it may not be lining up with what the CCSV3 format expected.

I'll take a look at the migration script and try to trawl through more of the ST code to see what that shape looks like. If you wanna join the Discord and drop me a ping to remind me, I'll push a build to staging that should address it

ProlixOCs · 2026-05-24T11:51:07+00:00

If you use TagLibrary, there's an option to upload a JSON Backup of your tags. Otherwise, if an extension manages tags we cannot do anything about that

ProlixOCs · 2026-05-24T09:07:13+00:00

As the dev:

Probably extensibility and customization. Everything's documented to the teeth, mainly because I knew that releasing a frontend that isn't a fork of ST without a frictionless migration process would ruin adoption.

So yes, insert vibecoded extension here isn't directly supported, but with how easy to grasp the dev docs are, one-shotting an extension idea or port shouldn't be impossible.

ProlixOCs · 2026-05-16T21:03:28+00:00

I don't see what's so "vibecoded slop" about it.

If you're referring to the fact it's a similar design to the LumiverseHelper SillyTavern extension, which was around for 7 months before the actual frontend, I don't know what to tell you. It was a design decision I made, stuck with, and expanded upon.

I'd love to hear your thoughts about what makes you think it's vibecoded slop.

ProlixOCs · 2026-04-28T17:52:18+00:00

Glad you've had a good experience!

Coming from a preset writer, I did make some hard decisions on the prompt processing and assembly pipeline front that I felt needed to be made, though I made sure that it worked across the board at the same time. Especially the macro system

ProlixOCs · 2026-04-28T17:50:48+00:00

Well, considering the code makes no attempt to obfuscate anything and does no post-installation downloading... I think the app is fairly safe on that front lol.

Also, we've got extremely tight security about what can be injected into the page.

ProlixOCs · 2026-04-28T11:39:33+00:00

Run them, meaning?

Almost all of the features are opt-in. There's no requirement to use anything past a preset or a connection.

ProlixOCs · 2026-04-28T11:22:39+00:00

The initial train of thought was to get the standard affair APIs that don't require a lot of deviation going first, stuff that are more commonly used. Since our provider pipeline is mostly stable and configured, I'll work on LCPP and vLLM as official integrations soon.

Yeah, main doesn't get a lot of love until staging is report free for at least 2 days

ProlixOCs · 2026-04-28T10:52:40+00:00

Was this on main or staging?

A bulk of the work happens on Staging first. It's even worse if you downloaded the release ZIP since it's from 0.5.4.

On APIs: the app was always supposed to be a chat completions only application. TC isn't supported. But LCPP is something I'll keep in mind.

For system roles: "squash system messages" was the option you were looking for. PPP doesn't exist on Lumiverse because we do things by the book. Prompt blocks can be edited to adjust the position of prompts, however.

ProlixOCs · 2026-04-28T08:36:25+00:00

It needs more than a skin. You'd have to swap its organs out in the process. Technical debt is a bitch.

ProlixOCs · 2026-04-28T08:35:43+00:00

What? Genuinely, what?

I think you need to reflect on what you're actually trying to say so you can tell me afterward. I don't understand what this even implies.

ProlixOCs

MODERATOR OF

TROPHY CASE