• 0 Posts
  • 17 Comments
Joined 2 years ago
cake
Cake day: June 13th, 2023

help-circle
  • I’ve used 4k and 1440p monitors, and my TV is 4k as well. For desktop use, 4k isn’t really a big difference because of the hardware needed to run it at a decent speed. However, once I got my hands on a 170hz 1440p monitor, I can’t go back to anything less. It’s extreme noticeable. The higher refresh rate, and the reasonable upgrade in pixel density makes text much clearer, especially in motion.

    For content viewing though, 4k on a TV it depends on how much of your field of view is occupied by the TV. Most of time though, a high quality panel is worth much more than higher pixel density. There is a massive difference between a basic 4k big box store TV, and 4k LG oled. The color, even outside of HDR content is just so much better, and the true actual black color is fantastic. Resolution is nice, but honestly, oled color is so good.



  • You missed the point of my example entirely. How can those commits exist, and those people exist in that instance if they don’t have accounts? I was refuting your statement that a frontend needs an account. By mirroring an existing repo, as an example, you could verify that my claim is correct. Git as platform is already decentralized and doesn’t require accounts. You could email someone your git diff’s and it will function the same.


  • You need a frontend

    Yes, but the requirement of said frontend are very small.

    and a frontend needs an account.

    Not required at all actually. For example, mirror a github repo in gitea. You’ll see all the commits, their messages, and who made them. Yet that gitea instance isn’t accessible publicly. None of those people have an account, and none of them can login even if they could access the instance. A commit is just attached to a name, that is user configurable, and a lot less data minable than a “real” account.


  • No worries, I’ll link to some Arch Wiki stuff to help explain. Containers are a very cool system for isolating environments. Similar to how python uses VENV to contain all the dependencies for a python program, containers let you have a full environment beyond just the python stuff. I use podman to actually run the container on my computer. You use a Containerfile, to define what you want this environment to look like, and docker/podman does all the hard work for you, by making an image file that holds the whole thing in one place separate from our real OS.

    This is my start script.

    #!/usr/bin/env bash
    
    podman run -it --rm --name stablediff2 -p 7860:7860 \
    -e COMMANDLINE_ARGS="--api --listen --port 7860 --enable-insecure-extension-access --medvram-sdxl --cors-allow-origins *" \
            --device /dev/dri:dev/dri \
            --device /dev/kfd:/dev/kfd \
            -v ./models:/dockerx/stable-diffusion-webui/models:z \
            -v ./repos:/dockerx/stable-diffusion-webui/repositories:z \
            -v ./extensions:/dockerx/stable-diffusion-webui/extensions:z \
            -v ./embeddings:/dockerx/stable-diffusion-webui/embeddings:z \
            -v ./outputs:/dockerx/stable-diffusion-webui/outputs:z \
            -v ./inputfiles:/dockerx/stable-diffusion-webui/inputfiles:z
            localhost:stablediffusion:latest
    

    This is just telling podman to start the container, give it an actual terminal to connect to, remove the container if it stops running, give it a name, and tell it what ports it can run on.

    podman run -it --rm --name stablediff2 -p 7860:7860

    These are the arguments passed to the webui start script itself, mostly for my own convenience. The medvram-sdxl is not required, since my card has enough vram, but then I can’t be doing anything else with it. So I sacrifice a bit of generation speed for more free memory for the rest of my computer. I’m running this locally, so insecure extension access also doesn’t matter since I’m the only one using this, just makes installing extensions from the webui directly.

    -e COMMANDLINE_ARGS="--api --listen --port 7860 --enable-insecure-extension-access --medvram-sdxl --cors-allow-origins *" \

    These are just the device files that correspond to my GPU, so that the container has access to it. Without this, the container would only have access to CPU based generation. Everything else is just the folders that holds my models, extensions etc. You have to give the container exactly what you want it to, because its isolated away from your normal files unless you tell it otherwise.

    --device /dev/dri:dev/dri \
    --device /dev/kfd:/dev/kfd \
    

    This is iterations per second, I believe. It’s basically a measure of how fast stablediffusion is is running a particular generation of an image. It lets people compare performance across different software and hardware configurations.

    10 it/s

    NixOS is the name of the GNU/Linux operating system I’m using, similar to how MacOS is different than Windows, NixOS is another type of operating system. I’ve only been using it for a few months, but its extremely cool. Before that I mostly used Debian and Fedora, but the main difference between NixOS and them is that you can define you whole OS as a configuration files, and then the tools it’s designed around build your system for you. So instead of say, installing a program, opening it up and going into settings and changing everything to be how you like it. You can instead just make a file that lists everything the way you want it from the start, and Nix installs the program and sets it all up all in one go. It has a pretty big learning curve, and its features are numerous that I have yet to take full advantage of them. Probably not the best to start with if you are new to GNU/Linux systems, but once you see the benefits of why it does things differently, its awesome.

    Hopefully that explains most of the words I used. Pardon my formatting, as I don’t know markdown very well and I think I separated everything okay. :)


  • by default, set up to run in a venv

    It does, but since I’m running inside a container, I disable that behavior, and run it as a user package. Some extensions also require additional libraries, but they don’t pull the correct ROCm dependencies and I have to modify part of the install scripts to manually define the correct versions.

    The main webui code is excellent, even if sometimes the documention is out of step because of how fast everything moves. Its the extensions that are not always to the same level of quality that make fiddling with python dependencies a bit of extra work.



  • I use stable diffusion with automatic1111’s webui ran locally with an AMD GPU. I use the card for gaming and encoding too, so the cost for just AI is basically free. The webui is excellent, and I learn about new things it can do every time I use it. Setting it up took some time, but nothing beyond what I am familiar with. I do loathe that so much data science/AI stuff is python based, because python’s dependency management is an unruly beast, but oh well.





  • When you use your “one password” you’re in effect giving your device permission to access the key storage in your TPM to fetch the private key to present it to the site.

    Very small correction as I understand, but your private key is never presented. The web service should never interact with the private key directly. Your device is signing some bit of data, then the server uses your public key to verify that it was signed by your private key. Its a small distinction, but is one of the principal uses of asymmetric encryption is that the public key can truly be public knowledge and given to anyone, while the private key is 100% always only accessed by you the user.


  • Perfect examples of why OSX is an Unix-like just like GNU/Linux. It’s got a shared history with the original Unix, but isn’t literally Unix. This community is around Unix-likes, and under the Unix-like banner, I’d gladly welcome ReactOS. WSL isn’t in the spirit of it though.

    OSX has been on a number of occasions actively hostile towards FLOSS as well (particularly anything GPL), which in the last decades, have become synonymous with Unix-likes, though that’s a matter of personal taste. What isn’t a matter of taste however, is that OSX uses the XNU kernel, which is an acronym for X is Not Unix. It is not a monolithic Unix style kernel either. I would argue that OSX is only loosely Unix-like, and only mimics Unix functions for compatibility. Should Apple have the inclination, they would happily abandon it for something invented by them given the opportunity.

    Not picking a fight with you over semantics, I just loathe Apple as a business and Microsoft gets a lot of flack for their old “Embrace Extend Extinguish” policies when Apple has been exceptionally hostile towards OSS. Apple so often gets a pass when being considered a part of Unix communities yet they absolutely do not embrace the spirit of Unix-likes and FLOSS at all.