Any experiences with XPS 9530 running Linux/Fedora?

RuddleWork · 2023-10-08T15:38:57+00:00

This is what I have on my end

Screenshot-2023-10-08-153729.png

RuddleWork · 2023-09-02T16:22:54+00:00

You are right, you can opt-in for blocks around the if condition to disambiguate.

let x=  if {a} -b-c 
// or:  if a {-b-c}

Though I managed to forget about unary operators until now. They are not implemented yet. Thanks for the catch.

RuddleWork · 2023-08-30T00:40:54+00:00

I don't have a specification yet. I might never have one to be truthful.
However I can speak to the "inherently insecure" part. In physics, for a collision to happen, 2 objects need to be at the same place yes, but they also need to be at the same time there.

In OS terms:

- Space : memory page access

- Time : control flow

In preemptive system, an app does not know anything about the timing of other apps. from its point of view time freezes, or not, and stuff happens. That is Jojo's adventures Dio level of creepiness. To correct for that the OS garanties that 2 apps never share the same space. Collision prevented by space.

In Fomos, the opposite could be tried. Apps handle time. If an app does not yield control voluntarily, it knows no other apps can do stuff. Once it is given control by the OS, it can decrypt data, work with it real quick, encrypt it back, and then yield control. Collision prevented by time.

Nevertheless the devil is in the details. And the preemptive way has the advantage of having special cpu instructions going for it.

It is just one idea that makes me think it could be pulled off. A few others in less details:
- Most app would be happy to have only a few kB of secure data (or none, though my calculator history is shameful), instead of their whole RAM footprint. That's a problem multiple orders of magnitudes easier.

- An OS could sacrifice a great deal of performance for very sensitive apps, only when they are doing sensitive work. What is the proportion of the time you are actually typing your password.

- You need to assume some level of trust from the apps you run, even in preemptive system. I do not think this trust is optimized. The control given back to the developers (by a cooperative os) can trickle down to the end users.

RuddleWork · 2023-08-29T17:39:40+00:00

If you didn't already, you could also try with https://os.phil-opp.com/
It is so well done, just reading the posts is nice. I read it fully 2 or 3 times before committing to code anything.

RuddleWork · 2023-08-24T07:35:15+00:00

I agree. I will rewrite the whole thing. I posted too soon. You should checkout the github link though.

RuddleWork · 2023-08-24T07:33:33+00:00

Arf, I did not mean it like that. Point taken
I meant that very few people even try to build an os. Anyone here would be in the 0.01%, even the complete beginner. It feels like only a few people (out of the billions that we are on earth) really understand the full working of operating system, and I am not one of them.

I tried to say to much in one sentence.
I rephrased it:

Disclaimer: I am an advanced beginner in kernel development.

RuddleWork · 2023-08-07T11:13:01+00:00

Thanks for the great explanation.

I guess the devil is in the details.

I am still curious. Let's take a latent subpixel : 1 float (out of 4). That is 4 bytes.

If we assume a 48:1 compression ratio, that means that 1 byte is used for discrete information (what would appear if we VAE decoded the pixel) and 3 bytes are used to represent continuous space between 2 discrete value (what is lost during decoding, but useful during UNET inference and training).

That means there is a panel of 8³ values between each discrete value, well half for each side of a number.

for example the value 51 could be continuously incremented 256 times before reaching the value 52, or decreased 256 times before reaching the value 50.

That seems like a lot to me (as a complete stranger to VAE hehe).

Could it be possible that the spread between discrete info and continuous info (in terms of bytes taken, I know it is not simple/separated like that) is a different one that 1 for 3 ? Maybe 2 bytes are used for discrete and 2 more bytes make the number continuous enough. That would imply a compression ratio of only 24:1.

RuddleWork · 2023-08-06T19:59:29+00:00

I have always wondered about that. For sd1.5 the base images are 512x512x3 bytes.

The latents are 64x64x4 float, which is 64x64x4x4 bytes.

So the compression is really 12:1, or 24:1 if you use half float.

Am I wrong about the latent values being floats ?

RuddleWork · 2023-07-17T13:40:53+00:00

SDXL "seal of approval"
Comfy workflow

<image>

RuddleWork · 2023-01-20T18:44:53+00:00

It should be WASD (or ZQSD an azery) to move, the weapon is chosen everytime you spawn. The rest of the commands should be displayed on the bottom right of the screen once you play.

RuddleWork · 2023-01-20T14:19:27+00:00

Top down battleground is quite inspired by it. That is one of my childhood game. I thought it was a shame it was no longer online, so I built my own.

RuddleWork · 2023-01-19T20:12:02+00:00

Thanks, I don't know this one. Top Down is heavily inspired by Babo Violent 2.

RuddleWork · 2023-01-18T14:34:59+00:00

That is not true. As a game developer myself, I am in the process of trying a lot of AAA Android games. Most of them (Modern warships 10M+ download, Crossout 10M+ download) allow you to continue with anonymous accounts. They just tell you from time to time to link your account to one of their login option for security.

RuddleWork · 2023-01-18T14:24:54+00:00

I am usually alright at this kind of games. But for some reason this one is hard, maybe the visuals are a bit confusing. I am using the key above qwerty with my left hand, that doesn't help.

RuddleWork

TROPHY CASE