• 57 Posts
  • 3.34K Comments
Joined 2 years ago
cake
Cake day: October 4th, 2023

help-circle
  • Sure, but I think that the type of game is a pretty big input. Existing generative AI isn’t great at portraying a consistent figure in multiple poses and from multiple angles, which is something that many games are going to want to do.

    On the other hand, I’ve also played text-oriented interactive fiction where there’s a single illustration for each character. For that, it’d be a good match.

    AI-based speech synth isn’t as good as human voice acting, but it’s gotten pretty decent if you don’t need to be able to put lots of emotion into things. It’s not capable of, say, doing Transistor, which relied a lot on the voice acting. But it could be a very good choice to add new material for a character in an old game where the actor may not be around or who may have had their voice change.

    I’ve been very impressed with AI upscaling. I think that upscaling textures and other assets probably has a lot of potential to take advantage of higher resolution screens. Maybe one might need a bit of human intervention, but a factor of 2 increase is something that I’ve found that the software can do pretty well without much involvement.


  • I’ve never broken a plastic ice cube tray twisting it. There are plenty of plastic trays on Amazon.

    I have tried a silicone one once and didn’t like it, as it took more doing to get the ice cubes out than the plastic tray, where they tend to all readily slide out after the tray’s been given a twist.



  • In fairness, rural America probably didn’t entirely understand the implications of said vote.

    As I’ve pointed out on here before, I feel like a lot of people in mostly-Republican-voting rural American are going to be even more disappointed when they discover agricultural subsidies ending, healthcare subsidies ending that disproportionately benefit poorer, rural areas, illegal immigrant agricultural workers that farms rely on becoming unavailable, counter-tariffs that tend to target agricultural output from rural areas, etc.



  • What did you think of the new aiming system? I’ve heard mixed things, but it sounded good to me (or at least way better than a flat percentage).

    I don’t know what the internal mechanics are like, haven’t read material about it. From a user standpoint, I have just a list of positive and negative factors impacting my hit chance, so less information about my hit chance. I guess I’d vaguely prefer the percentage — I generally am not a huge fan of games that have the player rely on mechanics trying to hide the details of those mechanics — but it’s nice to know what inputs are present. It hasn’t been a huge factor to me one way or the other, honestly; I mean, I feel like I’ve got a solid-enough idea of roughly what the chances are.

    even if it doesn’t hit the same highs as JA2, there hasn’t really been much else that comes close and a more modern coat of polish would be welcome.

    Yeah, I don’t know of other things that have the strategic aspect. For the squad-based tactical turn-based combat, there are some options that I’ve liked playing in the past.

    While Wasteland 2 and Wasteland 3 aren’t quite the same thing — they’re closer to Fallout 1 and 2, as Wasteland 1 was a major inspiration for them — the squad-based, turn-based tactical combat system is somewhat similar, and if you’re hunting for games that have that, you might also enjoy that.

    I also played Silent Storm and enjoyed it, though it’s now pretty long in the tooth (well, so is Jagged Alliance 2…). Even more of a combat focus. Feels lower budget, slightly unfinished.

    And there’s X-Com. I didn’t like the new ones, which are glitzy, lots of time spent doing dramatic animations and stuff, but maybe I should go back and give them another chance.




  • All of that said, consider replacing your central ducted unit with a multi-head mini-split system in the long run.

    Mini splits don’t provide ventilation, whereas ducted systems do. In general, if one can have a ducted system, I’d rather have that. The major problem with ducted systems is that ductwork takes up a lot of space, so it’s hard to stick into an existing house; much less of an issue if you can build it in during construction. A mini split is less invasive to an existing structure.


  • Yes.

    The Threadiverse has multiple intercompatible “Reddit-alike” software packages.

    There’s also Sublinks, written in Java, but I don’t know for sure whether that’s going to actually get the ball rolling. https://demo.sublinks.org/ Think they need more developers contributing.

    EDIT: Note that while this approach is unusual for the centralized Web-oriented social media era, where typically one company controls the whole shebang and has one codebase, it is common for federated systems. There are many different NNTP server implementations for Usenet, many different XMPP server implementations for instant messaging, many different IRC server implementations for chat, many different SMTP server implementations for email, many different FidoNet implementations.



  • Not what you asked, but you might check that:

    • The central AC doesn’t need to be recharged. If it has leaked coolant and is low, it will drop in effectiveness.

    • Or, even more simply, that the air filters don’t need to be replaced.

    • You can’t improve insulation. Doing so is a one-off cost, as opposed to the ongoing cost of throwing more air conditioning muscle at the problem. Weatherstrip leaks, replace any single-pane windows with double-pane, etc.




  • I’m sorry, you are correct. The syntax and interface mirrors docker, and one can run ollama in Docker, so I’d thought that it was a thin wrapper around Docker, but I just went to check, and you are right — it’s not running in Docker by default. Sorry, folks! Guess now I’ve got one more thing to look into getting inside a container myself.


  • tal@lemmy.todaytoSelfhosted@lemmy.worldI've just created c/Ollama!
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    7 days ago

    While I don’t think that llama.cpp is specifically a special risk, I think that running generative AI software in a container is probably a good idea. It’s a rapidly-moving field with a lot of people contributing a lot of code that very quickly gets run on a lot of systems by a lot of people. There’s been malware that’s shown up in extensions for (for example) ComfyUI. And the software really doesn’t need to poke around at outside data.

    Also, because the software has to touch the GPU, it needs a certain amount of outside access. Containerizing that takes some extra effort.

    https://old.reddit.com/r/comfyui/comments/1hjnf8s/psa_please_secure_your_comfyui_instance/

    ComfyUI users has been hit time and time again with malware from custom nodes or their dependencies. If you’re just using the vanilla nodes, or nodes you’ve personally developed yourself or vet yourself every update, then you’re fine. But you’re probably using custom nodes. They’re the great thing about ComfyUI, but also its great security weakness.

    Half a year ago the LLMVISION node was found to contain an info stealer. Just this month the ultralytics library, used in custom nodes like the Impact nodes, was compromised, and a cryptominer was shipped to thousands of users.

    Granted, the developers have been doing their best to try to help all involved by spreading awareness of the malware and by setting up an automated scanner to inform users if they’ve been affected, but what’s better than knowing how to get rid of the malware is not getting the malware at all. ’

    Why Containerization is a solution

    So what can you do to secure ComfyUI, which has a main selling point of being able to use nodes with arbitrary code in them? I propose a band-aid solution that, I think, isn’t horribly difficult to implement that significantly reduces your attack surface for malicious nodes or their dependencies: containerization.

    Ollama means sticking llama.cpp in a Docker container, and that is, I think, a positive thing.

    If there were a close analog to ollama, like some software package that could take a given LLM model and run in podman or Docker or something, I think that that’d be great. But I think that putting the software in a container is probably a good move relative to running it uncontainerized.


  • tal@lemmy.todaytoProgramming@programming.devPNG is back!
    link
    fedilink
    English
    arrow-up
    73
    arrow-down
    1
    ·
    edit-2
    7 days ago

    PNG has terrible compression

    It’s fine if you’re using it for what it’s intended for, which is images with flat color or an ordered dither.

    It’s not great for compressing photographs, but then, that wasn’t what it was aimed at.

    Similarly, JPEG isn’t great at storing flat-color lossless images, which is PNG’s forte.

    Different tools for different jobs.


  • tal@lemmy.todaytoProgramming@programming.devPNG is back!
    link
    fedilink
    English
    arrow-up
    6
    ·
    edit-2
    7 days ago

    At least at one point, GIF89a (animated GIF) support was universal among browsers, whereas animated PNG support was patchy. Could have changed.

    I’ve also seen “GIF” files served up online that are actually, internally, animated PNG files, so some may actually be animated PNGs. No idea why people do that.


  • tal@lemmy.todaytoProgramming@programming.devPNG is back!
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    1
    ·
    edit-2
    6 days ago

    On the “better compression” front, I’d also add that I doubt that either PNG or WebP represent the pinnacle of image compression. IIRC from some years back, the best known general-purpose lossless compressors are neural-net based, and not fast.

    kagis

    https://fahaihi.github.io/NNLCB/

    These guys apparently ran a number of tests. They had a neural-net-based compressor named “NNCP” get their best compression ratio, beating out the also-neural-net-based PAC, which was the compressor I think I recall.

    The compression time for either was far longer than for traditional non-neural-net compressors like LZMA, with NNCP taking about 12 times as long as PAC and PAC taking about 127 times as long as LZMA.


  • tal@lemmy.todaytoProgramming@programming.devPNG is back!
    link
    fedilink
    English
    arrow-up
    23
    arrow-down
    1
    ·
    edit-2
    6 days ago

    What’s next?

    I know you all immediately wondered, better compression?. We’re already working on that. And parallel encoding/decoding, too! Just like this update, we want to make sure we do it right.

    We expect the next PNG update (Fourth Edition) to be short. It will improve HDR & Standard Dynamic Range (SDR) interoperability. While we work on that, we’ll be researching compression updates for PNG Fifth Edition.

    One thing I’d like to see from image formats and libraries is better support for very high resolution images. Like, images where you’re zooming into and out of a very large, high-resolution image and probably only looking at a small part of the image at any given point.

    I was playing around with some high resolution images a bit back, and I was quite surprised to find how poor the situation is. Try viewing a very high resolution PNG in your favorite image-viewing program, and it’ll probably choke.

    • At least on Linux, it looks like the standard native image viewers don’t do a great job here, and as best I can tell, the norm is to use web-based viewers. These deal with poor image format support support for high resolutions by generating versions of the image at multiple pre-scaled levels and then slicing the image into tiles, saving each tile as a separate image, so that a web browser just pulls down a handful of appropriate tiles from a web server. Viewers and library APIs need to be able to work with the image without having to decode the whole image.

      gliv used to do very smooth GPU-accelerated panning and zooming — I’d like to be able to do the same for very high-resolution images, decoding and loading visible data into video memory as required.

    • The only image format I could find that seemed to do reasonably well was pyramidal TIFF.

    I would guess that better parallel encoding and decoding support is likely associated with solving this, since limiting the portion of the image that one needs to decode is probably necessary both for parallel decoding and for efficient high-resolution processing.