• 0 Posts
  • 161 Comments
Joined 1 year ago
cake
Cake day: June 30th, 2023

help-circle






  • The problem with that is that the subduction rifts generally also have volcanoes that spew a bunch of that material back to the surface/atmosphere. It might take a few centuries for it to go through all that, but IMO better to bury it in one place and risk future people not understanding it (they’ll figure it out quickly enough if they are human or similar intelligence) than to put it somewhere where the Earth itself will eventually reject it violently and people affected won’t have much choice or understanding of what happens as a result.




  • And I think that will go both ways. I mean, we all already have the option of joining threads right now to interact with those 100M users but I have a feeling most that are here aren’t.

    Their joining the fediverse will be more disruptive than their leaving it I think. And that’s not even considering the higher costs to anyone running instances, since all that extra volume won’t be processed and stored for free (though admittedly I am not familiar with the implementation details of how federated content is handled).




  • I hate how tempered glass is the premium standard. I’d rather have glass that is easier to break if I fuck up but doesn’t have a chance to spontaneously shatter.

    I had a TV stand do that once, luckily I was the only one there when it happened. If it had happened two nights earlier, it would have sprayed glass shards all over my sleeping daughter. It was energetic enough that I found some pieces I missed on the other side of the room when I was moving out.

    Tempered glass furniture looks great, I’ll admit, but never again.







  • Things like that have been around for a long time. It was like two decades ago that I saw this shader scheme in softimage|xsi.

    For implementing something like that, each node in that graph would have an array of inputs and outputs. Each of those would have a type like vector, scalar, colour, string. Then you only allow connections if the inputs and outputs match types (though you can also have conversion nodes or selectors that say pick the red channel of a colour to turn it into a scalar). Each input can be set to a constant value instead of connecting something else to it. Outputs don’t need to be connected, which is mostly useful if a node has multiple outputs. Then each node has an evaluation function that takes all input parameters and maybe internal configuration parameters (though you might as well make everything an input param since there’s no real functional difference) and uses them to calculate the outputs, which it then sends on to anything connected to those.

    I’m not much of a UI guy but displaying it for the GUI would just involve drawing boxes or some shape for the node, then spaces for each of the inputs on the left side and outputs on the right side maybe colour code them by type, and lines running along the connections. Then just add the name and/or other visual information you want to display and positional information to let users move it around their work area.