any advice on buying a window AC unit?
tal @ tal @lemmy.today Posts 156Comments 6,597Joined 2 yr. ago
tal @ tal @lemmy.today
Posts
156
Comments
6,597
Joined
2 yr. ago
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.
- Lemmy (the biggest). Example: https://lemmy.world/ Written in the Rust programming language.
- PieFed. Example: https://piefed.social/ Written in the Python programming language.
- Mbin (the successor of the defunct Kbin project). Example: https://fedia.io/ Written in the PHP programming language.
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.
dull...fixed my washing machine
I mean, an incorrectly-operating washing machine can make things quite exciting indeed.
I'd also add that ASCII has had some similar issues in the part, but that tends to have been ironed out by now via changes to onscreen typefaces.
For example, some old typewriters don't have a "0" key or a "1" key because capital-o and lowercase-l looked similar enough and context was sufficient to let them be used in place of the corresponding number. This trained some people to do that, to the point that various software adapted to permit misuse of one in the place of the other. To this day, I can open up Firefox, and the following webpage will render green text:
<html><font color="#OOFFOO">green text
</font></html>
Some other fixes were were made over time, like making capital-i, lowercase-l, and the pipe ("I", "l", and "|") as more-visually-distinct characters in typefaces where this matters.
In the monospaced font world, "programming" or "coding" fonts, where not confusing the character in question is particularly important, place a premium on keeping characters like this particularly distinctive, even at the cost of trading off some aesthetic appeal or conforming to traditional typography or handwriting-like conventions for letters. You'll get more-distinctive "." and ",", "O" and "0", "l", "I", and "|", "j" and "i", etc.
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.
Unicode has a lot of "lookalike" characters, so if you're allowed to select characters as a unique identifier to other users, permitting selection of arbitrary Unicode characters opens the possibility to impersonate users.
I believe that there is some system for dealing with this for domain names, as they permit for Unicode and being able to uniquely identify domains is important. I don't know if this could be generalized to other Unicode-using applications.
I strongly doubt that they'd render Steam not runnable on their distro.
Webster tried to reform English, and was a reason for a number of the American English changes from British English. Some of his changes caught on, like "public" for "publick" or "jail" for "gaol".
But others did not.
I think that some of those ones that didn't catch on would be good candidates.
E.g. "Island" to "Iland".
https://www.merriam-webster.com/grammar/noah-websters-spelling-wins-and-fails
Or "is" to "iz".
The election here was the Democratic primary. It didn't cut the Democrats out of the loop.
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".
Oh, okay, the Garand uses an eight round clip, and the rounds aren't inline. I thought that they were inline, and that each clip in the image was two four-round clips sitting atop each other. Well, today I learned something. Thanks.
EDIT:
.30-06 ammunition for the M1903, 1903A3, and M1917 rifles and the Browning Automatic Rifle (BAR) was issued in five round stripper clips
That may be what I saw and confused it with, because those look pretty much exactly like the clip that I had thought went in the M1 Garand.
Confused the clip on the US issue rifle for WW1 and WW2.
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.
Can someone here more in the know explain this one for me? I see a clip, and I think that this is some kind of ludicrously hacked-up M1 Garand, but I thought that the Garand used a five-round clip, and those have four rounds.
I installed the emacs ellama package, and I don't think that it required any configuration to use, though I'm not at my computer to check.
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.
The UK must "actively prepare" for a potential "wartime scenario" in its homeland, the National Security Strategy has warned.
The review highlighted Russia and Iran as potential threats, including saying that the latter's "hostile activity" on British soil is increasing in an effort to "silence critics" as well as "directly threatening the UK".
If you read the article that they're linking to, it does say that this is a "low probability" scenario.
"We are trying to raise awareness through this war game to say, look, let's have a look at what might happen," he said.
"Unlikely and low probability though it is, so that we can start to put some measures in place and remind ourselves about how we used to do it - use history as our weapon, if you like, in that regard."
Russia has aimed to assassinate people on British soil and has engaged in sabotage in Europe, but that's also a long way away from what I'd call a real wartime situation.
Vice asked a guy at Jane's to do an assessment of whether Russia could do an invasion of the UK a decade back. He said that Russia likely could:
The requirements for carrying out a successful invasion are pretty substantial, which makes the list of realistic threats to Britain quite small. The bigger military powers are an obvious contender to begin with; the USA and Russia have certainly got the manpower and capability to carry it out but China, for example, doesn’t yet have a global reach and couldn’t support enough troops and aircraft that far from home to make it viable without support.
That being said, that was also pre-Russo-Ukraine War, and that may have altered things (China's certainly built up her military a lot over that decade). Might be interesting to go back to Jane's and ask for an updated assessment.
Iran could engage in terrorism, maybe smuggle some weapons in, but doesn't have the force projection capability to engage in much by way of conventional war on the UK territory. Iran's current ballistic missiles don't have the range to reach the UK from Iranian territory, so unless they can launch them from ships or aircraft or closer territory, they aren't in the picture...and while you could probably hurt the UK with said missiles if you could get them close enough, hit seats of government, power plants, I don't believe that it'd be sufficient to take the UK out of the fight, and then you'd be in a fight with an opponent who has more force projection capability than you do who is at a range that you can't easily hit them at; not a favorable situation. Not to mention NATO.
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.
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.
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.
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.