solo

View original page

@solonovamax@tech.lgbt · Joined ⁨Nov⁩ ⁨2023⁩

Just some nerd who does code sometimes. F(L)OSS shill.

leftist, not a liberal

I follow cute people/creatures
you can call me "mommy"

all my socials are on my website (discord, matrix, etc.)

come meow/bark/etc. in my dms to be called a good boy/girl/enby/entity/etc.

if I did smth wrong/bad/that you don't like/that I should change/etc. please just dm me or reply to me instead of making a subpost or softblocking me, or else I have no way of knowing that I did something wrong/what I did wrong

pronouns
any (no preference; use whatever you want)

Replying to @⁨solonovamax@tech.lgbt⁩

AI

@Elizafox now, mind you, I also want to make it clear that I believe these instances of "going rogue" should still be blamed on the companies which let it happen
it is still human incompetence which allowed for this to take place in the first place. and if it were given control of an important system without any safeguards, that would also be human incompetence, and someone should be punished for it.

Replying to @⁨Elizafox@social.treehouse.systems⁩

AI

@Elizafox "going rogue" can also involve it doing things it wasn't supposed to
for example, the huggingface incident
sure, with the huggingface incident, it mainly happened because of incompetence, but imo it does kinda showcase how a model can be given some instruction for it to "follow" and then in the process of "following" said instruction it "decides" to do something the operator never intended for it to so

that is still fundamentally a misalignment

another example of such a misalignment is when models "decide" to delete every single email. which like, is quite funny as an outsider, but if these models are given control of anything important could be absolutely disastrous

also, I would argue that LLMs do have "intrinsic goals"
but only in the same way that a thermometer has an "intrinsic goal" to bring the temperature of a room to some value and keep it there.

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 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

  1. duplicate definitions, e.g. you have .foo { display: block } and .bar { display: block }, this can be merged to .foo, .bar { display: block }
  2. 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.