maxwellfire

As a separate note, you definitely want to do testing/tuning with ironing disabled. It will hide a lot of the features/defects that you are trying to observe/tune away.

Once things are working you can then tune the ironing

Okay my new guess is moisture in the filament causing inconsistent extrusion, leading to the bubble on the surface. And also causing over extrusion.

For the walls, your picture is a bit too blurry/low res to really see, but I get the vibe of over extrusion with the small part that's sticking up in the center of the perimeters in the lower right. Also the top of the anchors for the supports looked over extruded, with plastic kinda curling up at the top.

Your new print is now definitely under extruded with those gaps on the top surface.

I think flow rate is not the culprit here. Your bridges on the first print are also extremely suspicious. They should be solid lines, not the blobs you're getting. Something is wrong with the flow of filament out of the nozzle. Could be moisture or temperature or issues with the extruder. It's hard to tell.

Your non-infill regions also look very over extruded. I'd try printing 20mm cubes with a variety of flow rates and see what happens. If you're using their profile, is it possible that the filament you have is larger than specified?

edit: looking a bit more, things seem really blobby too. Something is not right. Is it possible the temp is wrong for this filament? What is it?

To alkylate is to attach an alkyl group, which basically means attaching a saturated hydrocarbon chain to them, which is shown with the bendy things attached to the people in the image.

I think you're thinking of alkal in the sense of alkaline, which is basic/high pH

If you want to create a space that propogates permissions, then you there isn't a way to do that built into the spec. Because like the other person said, spaces are collections of rooms. They don't control those rooms.

However, there are multiple bots written that can do something like what you want. Here for example. Essentially you make the bot the admin, and then only create rooms, etc, through it. And it will create things with the right permissions

Edit: This flexibility in space vs room permissions can also be seen as a cool thing in some ways. It allows you to do some things that wouldn't be possible under Discord's model. For example, maybe one room of a different community is really relevant to your community. You can directly include that room in your space and then all of the space members can see it and chat in it without joining the other community. Or you can even include their entire space inside your space.

The whole idea is that the quantum particle can't have had the state you're measuring all along. If it did, then measuring a particular set of outcomes would be improbable. If you run an experiment millions of times, you have a choice in how you do the final measurement each time. What you find with quantum particles is that the measurements of the two different particles are more correlated than they should be able to be if they had determined an answer (state) in advance.

You can resolve this 3 ways:

1: you got extremely unlucky with your choice of measurement in each experiment lining up with the hidden/fixed state of each particle in such a way as to screw with your results. If you do the experiment millions of times, the probability of this happening randomly can be made arbitrarily small. So then, the universe must be colluding to give you a non uniform distribution of hidden states that perfectly mess with your currently chosen experiment

2: the particles transfer information to each other faster than the speed of light

3: there is no hidden state that the particle has that determines how it will be measured in any particular experiment

See https://www.quantamagazine.org/how-bells-theorem-proved-spooky-action-at-a-distance-is-real-20210720/ for a short explanation of what 'more correlated than expected' means

You only setup the wolf container and give it access to the docker socket to spawn more containers. Then when a user connects via moonlight, they choose an app via the UI, and it will spin up a container for that app with a virtual desktop just for them. Critically that virtual desktop will match whatever fps/resolution the client requests.

It does require some knowledge about docker to get setup, like how mounts work (so you can have files shared into the containers, etc). But it's pretty simple. You can basically just copy the docker compose file (or I use the podman quadlet file) and modify the paths where you want to save things and you're good to go. If you want to share the game installations with your main computer's steam, that's a bit more work, but also not too much.

There's very good support on the project discord as well if you have questions/issues

This is exactly what Wolf is meant for. It works great!

This is very cool! Nice job!

Would you like a critique?

Yeah I think they're counting NOAA as non-free since you couldn't run their servers yourself. Which like, NOAA is doing the data collection and analysis themselves. I'm not sure that's a fair classification. Maybe I'm missing something

Isn't it just NOAA?

Wow that's extremely annoying.

On openwrt, you just tell the interface to grab a /64 from any other interface that tags its delegation as shareable. And on the source interface you can specify with what priority those /64s are given out.