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

help-circle






  • 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.


  • Just don’t get a portable unit. They suck and are just a waste of money most of the times.

    Get a dual-hose unit if you get one. There are a lot of companies selling single-hose units. Those are a lot less efficient and aren’t much cheaper. I would guess that in a situation where they get any kind of meaningful use, a dual-hose unit pays for itself quickly.

    I don’t think I’d agree that they suck, but if you can use a window unit — not all rooms and windows are amenable to this — you normally want a window unit instead of a portable unit, unless you must take down the AC unit on a regular basis. Less noise inside, more energy efficiency.


  • 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.




  • with a passion. It just doesn’t do what its supposed to, its not searching anything at all. Ive literally tried and written every word of the video title plus the channel name and it didnt show up bc I put onen word in the wrong spot.

    If you want to just treat each search term independently, that works for me. Searching for battle of the solomons eastern has a top hit of “Battle of the Eastern Solomons”.


  • 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
    4
    ·
    edit-2
    6 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.