wow i love making interfaces i sure hope i never have to connect it to any logic 
Replying to @kopper@not-brain.d.on-t.work
alternate caption: "when you see it you will want to fuck it - stewie "jobs" wonder, inventor of fruity gal aero"
Replying to @kopper@not-brain.d.on-t.work
ok let me clarify if this happens it's gonna replace outpost-fe.w.on-t.work i'm still no longer doing a backend
Replying to @kopper@not-brain.d.on-t.work
throwing the code at git.gay/kopper/outpost-fe-2 so i can later steal the tricks for other things i will also subsequently abandon
Replying to @kopper@not-brain.d.on-t.work
worried i may have made my buttons too bouncy
Replying to @kopper@not-brain.d.on-t.work
pl-api is the largest dependency on the bundle so far and i dont want to rewrite it its so much busywork i wish it wasnt a single massive un-tree-shakable class
Replying to @kopper@not-brain.d.on-t.work
do i reaaally need the code to call the pleroma admin api?
Replying to @kopper@not-brain.d.on-t.work
i love microoptimizing things that will not matter
git.gay/kopper/outpost-fe-2/commit/064d5234cdf0efa0ad4a9615fea70026eceb1051
git.gay/kopper/outpost-fe-2/commit/064d5234cdf0efa0ad4a9615fea70026eceb1051
Replying to @kopper@not-brain.d.on-t.work
ok i think im gonna roll back the data loading system i tried to make and instead Just Not Care About Having One Source Of Truth For What A Post Says because it turns out svelte is only really made for sveltekit and doesn't let you do anything cool by yourself like having a derived that returns a reference counted value that doesn't want to make you hate yourself when using or literally anything involving async that isn't Just A Fetch
you would think that you can call a function in a component and have that function do everything the component itself can do. you would think that wouldnt you. yeah you would.
you would think that you can call a function in a component and have that function do everything the component itself can do. you would think that wouldnt you. yeah you would.
Replying to @kopper@not-brain.d.on-t.work
the current state of things will live here once git.gay accepts my push so if anyone wants to take on the challenge they can: git.gay/kopper/outpost-fe-2/src/branch/experiment/single-source-of-truth
Replying to @kopper@not-brain.d.on-t.work
slowly coming up to the conclusion that it's impossible to have a coherent mental model of svelte. reactivity broke? Randomly Throw Closures Until It Works. context doesnt work here? Move The Set Above The Async? you need the async value in the context? You Would Think You Can't Because Of The Previous -- But You Can If You Pass It To Another Component That Wraps All Your Other Components. got an error message? This Is All You're Getting. Good Luck
Replying to @kopper@not-brain.d.on-t.work
there's like 10 different contexts your code can be in at any given time and they all hate each other and all of them can be in the same exact file and even scope
Replying to @kopper@not-brain.d.on-t.work
want to use the "legacy" stores because they let you replace $effect for your reference counting? you gotta declare them in the top level script. you have a recursive reply tree of them? FUCK YOU SUCK MY DICK GOT 10 ASLDKJILLION DOLLAR INVESTMENT FROM VERCEL
Replying to @kopper@not-brain.d.on-t.work
you know what no codebase cancelled i can't take this shit anymore
Replying to @kopper@not-brain.d.on-t.work
now that i've cooled down in the two hours since i could absolutely have phrased a lot of this better
Replying to @kopper@not-brain.d.on-t.work
alright cancellation cancelled i may have found a really easy fix now that i could think straight and a formal apology to rich harris who i know namesearches svelte and will inevitably find this thread as well once we're done talking in the other one's replies
Replying to @kopper@not-brain.d.on-t.work
its hard to tell if my code is working well or not because the unauthenticated bluesky appview seems to be throttled to hell and back i gotta implement logging in like asap
Replying to @kopper@not-brain.d.on-t.work
interesting things are happening in the outpost-fe fandom
Replying to @kopper@not-brain.d.on-t.work
i gotta keep reminding myself this whole app requires js to function at all so i can indeed use it to compute styles that css may be too unwieldy or require too many useless wrappers for
Replying to @kopper@not-brain.d.on-t.work
i think this may be my least spaghetti approach to reply trees yet, also tried sneaking in a thread collapser but not sure how i feel about it yet
Replying to @kopper@not-brain.d.on-t.work
the key? realize what i'm doing is special casing the last element EXPLICITLY, instead of trying to hack it together with various combinations of css selectors and conditionals on the current index in the loop
and a tiny bit of javascript to size the indicators correctly instead of trying to wrangle the shape of the dom so they line up naturally
and a tiny bit of javascript to size the indicators correctly instead of trying to wrangle the shape of the dom so they line up naturally
Replying to @kopper@not-brain.d.on-t.work
fun fact: switching between light and dark mode does not change the green* backdrop in the slightest and only alters the panels, switching them between "white with a subtle green hint" to "really dark green"
this happens because green transcends the light mode/dark mode binary
this happens because green transcends the light mode/dark mode binary
Replying to @kopper@not-brain.d.on-t.work
[british voice] other colors are available
Replying to @kopper@not-brain.d.on-t.work
i just got logins working and am a bit hungry so this is not final in any way
Replying to @kopper@not-brain.d.on-t.work
implemented a bit of the timelines and i'm reconsidering the single-line reply indicator. idk if it's just familiarity or if i genuinely had a point with current outpost-fe always putting the reply-to-user above the posting user but it looks off
Replying to @kopper@not-brain.d.on-t.work
speaking of familiarity outpost-fe has been a thing since jan 2025 which predates not-brain.d.on-t.work. i think its of similar age as the-contraption.d.on-t.work but i'd have to check that to make sure. it's deffo newer than brain.d.on-t.work though. that started as sharkey
Replying to @kopper@not-brain.d.on-t.work
the theme of this codebase is "holy shit i overcomplicated the previous one a bit too much i think". unless i'm missing something. its plausible
Replying to @kopper@not-brain.d.on-t.work
DUAL WIELDING ACHIEVED
Replying to @kopper@not-brain.d.on-t.work
ok so in theory with the architecture of how its built you can absolutely dual wield multiple mastoapi accounts on different instances as well however i am prolly gonna intentionally block that off because you would not be able to tell where the fuck a post is appearing from
Replying to @kopper@not-brain.d.on-t.work
@kopper they’re perfect
Replying to @kopper@not-brain.d.on-t.work
@kopper i wished someone owuld bounce me like that hehehe whatever man i give up
Replying to @kopper@not-brain.d.on-t.work
@kopper@not-brain.d.on-t.work not bouncy enough
Replying to @kopper@not-brain.d.on-t.work
@kopper oh wow you got multi network! Is this hosted live somewhere yet?
Replying to @liaizon@wake.st
@liaizon no not yet
Replying to @kopper@not-brain.d.on-t.work
@kopper *colours
Replying to @kopper@not-brain.d.on-t.work
@kopper@not-brain.d.on-t.work ooooo trees
i like reply trees
Replying to @kopper@not-brain.d.on-t.work
@kopper sometimes i really want to rewrite svelte to my own image, no compiler, just signals and jsx transpiler
Replying to @eater@cijber.social
@eater so... solid?
Replying to @kopper@not-brain.d.on-t.work
@kopper i dont think so
in my little perfect world it would use a user defined Observable objects and collections which allow for a way better way to update cycles, without the abuse of proxies or deepobject diffing
i mean i assume there's a reason both, Windows XAML and JavaFX highly rely on observer pattern
Replying to @eater@cijber.social
@kopper current nerd sniping levels: I've implemented a generational arena in typescript
Replying to @eater@cijber.social
@kopper return to Java Observable
Replying to @kopper@not-brain.d.on-t.work
@kopper svelte has decided to be the magic framework, but unfortunately magic is pretty difficult to understand
Replying to @kopper@not-brain.d.on-t.work
@kopper does the min chunk size not work for this?
also, slightly related, but I wish there was smth that could do css merging
there's like two kinds of merging I can think of which would be useful
- duplicate definitions, e.g. you have
.foo { display: block }and.bar { display: block }, this can be merged to.foo, .bar { display: block } - merging classes used in the same place. this one is a bit more complicated than the first one, and imo most relevant when using tailwindcss or unocss. if you have some place where you use a bunch of classes that are not used anywhere else, then just merge all those classes into a single class with all the styles and a single mangled name.
Replying to @solonovamax@tech.lgbt
@solonovamax minChunkSize is not implemented in rolldown (venture capital aislop rewrite vite now uses) afaik, thats a rollup thing only
Replying to @kopper@not-brain.d.on-t.work
@kopper oh, no wonder it wasn't doing anything when I was trying to adjust it earlier, lmfao
Replying to @solonovamax@tech.lgbt
@kopper ideally you'd also want some heuristics and route-awareness for the 2nd one, e.g. if you have route-scoped css and you have a class that is used in two places but nowhere else, it might be beneficial to merge the classes anyways, but then if it's used in many different routes, it would be beneficial to not have that specific class merged (but you can still merge the other classes) and put it in the main bundle instead
Replying to @kopper@not-brain.d.on-t.work
@kopper appropriate bouncineas
Replying to @kopper@not-brain.d.on-t.work
@kopper yay, bouncies