Tomorrow's plan: write some mockups of key OnlyJunk.Fans pages, and start working on some essentials that don't need the service to be online yet: a page that explains what it will be, a kind of terms of service & code of conduct, that kind of thing.
At the same time, start splitting iocaine into library & server parts.
Darn. I will need to split up TenXProgrammer (iocaine's metrics service) before librarification.
It currently depends on axum & provides a server.... I don't want that part in the library.
...and I will have to move the Embeds outside of the library. Those belong to the binary. That will be a bit of a challenge too.
Okay, got a local split into iocaine & iocaine-bin packages. It... compiles, but there are a few gross hacks:
TenXProgrammer needs to be split, but I don't yet know how. SexDungeon needs the registry, the binary will need to own the registry, and wrap it in a server.... I guess I just lift out the non-server parts, and adjust the SexDungeon trait?There might be some other, smaller rough edges, but these two are the big ones. I'll have a sleep on them.
TenXProgrammer split, I now have a LittleAutist in iocaine, and TenXProgrammer was moved to iocaine-bin.
Now to figure out the embeds, then clean up the mess I made.
Oh dear. Now that I moved a bunch of stuff around, pedantic clippy finds a whole lot of new things to complain about!
I love when Clippy complains, it makes my code a lot nicer in the long run.
Fuuck. Moving the embeds out of the library will be hard if I don't want to break the script-facing API (I do not want to break script-facing API).
I may have to sleep on this for a few days, it will require some deep hackery.
One fairly straightforward solution here would be to move the embeds behind a non-default feature flag. That would let the library compile on its own, without needing to inject the embeds into it in tricky ways, and would let iocaine-bin pull it in with the feature enabled, and embeds working.
I think I'll go ahead and do this.
This means that with the feature disabled, embeds won't work, which is a script-facing API breakage. BUT because iocaine-the-binary will enable the library feature: no breakage when using it with iocaine-the-binary!
I think I iocained enough for today, lets do some onlyjunk fans stuff! Mockups and whatnot!
Since I will be writing most of the frontend with Yew, I might aswell redo the current Cloudflare Error Page inspired landing page to match the look & feel of what's coming.
That'll make it work on mobile too - the current landing page is very much not mobile friendly.
Hrm. I'm kind of rethinking whether I want to go with Yew.
Leptos is out too, because Claude contributed to it.
Dioxus would be the other option, but... hm. Something's bugging me there, too.
Feels like they're all focused on "apps". What I'm building... isn't one. It's a web UI, yes, but not an "app". It's something that should work without JavaScript or WASM - those two would progressively enhance the experience, but should not be required.
So... what if I just built it without JavaScript in the first place? See how far I can push that, and whether I need JS to begin with.
Oh, lovely. Dioxus has an AGENTS.md as of 12 hours ago.
So that leaves me with Yew or doing JS on my own, one way or the other (or no js at all).