but they were destroyed in 2001 by the Taliban.

this really hurt

thats how you know you made something truly fair - everyone hates it

I don't care about cockroaches, they do not worry me much. I also do not care about like 95% of mosquito species which do not "annoy" humans. I just want the remaining 5% to vanish

From the reports that i have read (am indian), 20+ generics are expected, within roughly 2 months or so, with previous price being something along 10k INR (roughly 100USD) a month to about 3-4k INR (30-40 USD) a month. Drugs have always been kinda cheap here (as an example, a simple paracetamol (tylenol) tablet costs 1 INR (~1cent US)), so it is still expensive (for vast majority, it is more than 2-3 days of work), but much better. hope people use this cautiously though with reasonable expectations.

try to use it with llama cpp if you folks are interested in runinng locall llms - https://github.com/ggml-org/llama.cpp/issues/9181

the issue is closed, but that is not because it is solved, check it out, and find link to your relevant hardware (amd or intel or something else), and see if your particular piece is available. if so, you have hope.

in case it is not, try to find first party stuff (intel vino or intel one or amd rocm stack, and use that with transformers python or see if vllm has support).

also, try to check r/localllama on the forbidden website for your particular hardware - there is likely someone who has done something with it.

they are different things, wget and curl do not have many overlapping use cases other than downloading stuff over http

I do not like this attitude towards uutils. phoronix makes a very click baity title, and comments shit on uutils, rust and ubuntu.

last time it was "extremely slow" (17x), and by the time most people reported it, a pull request had been made and merged which brought the sha function within 2x of gnu version. not ideal, but definitely not reporting worthy.

then it was sort function can not sort big files, which came from a artificial benchmark of a 4 gigabyte file with single line all consisting of character 'a' (not sure if it was a or 0 or something, but that is not relevant). gnu version finished in ~1 sec, and the rust version could not. you can not sort a single line, it is already sorted. so there is some check which uutils is missing, which could be easily added, but no, we must shit on uutils and rust because they are trying.

In this case, some md5 errors happen, but apparently problematic part is not md5, but dd (actual bug report - https://bugs.launchpad.net/...).

I am not saying uutils is a perfect project, but gnu coreutils are nearly 4 decades old, where as uutils are less than 1 decade (yes the project did not start last year). There are bugs which need to be ironed out, and testing it in a non lts distribution is the best way to do that.

speaking as a indian - the reason that this is possible because we kinda ignore medical patents and formulations. (using kinda because i do not know the exact wording in law and the cooldown period).

It should also tell you about the cost of ingredients and manufacturing vs the costs you pay for "rnd for big companies" (who often build upon work done by universities which often are run by public fundiing)

it does now, most important feature in gim3 is non destructive layers

true, not so great if you are a frog i guess

I have marked this post nsfw. while it does not have complete nudity, it still is not completely sfw imo. I do not think it should be deleted (i recieved a report).

if anything, linux is now the youngest it has ever been (in terms of younger people using it, earlier it was almost all neckbeards, and i only have a tiny beard)

but they are interoperable (as you see, the above 2 folk are on lemmy, and I am on piefed).

gangs of wasseypur for the unaware (it is basically a 5 hour movie split into 2).

It is in top 5 all time.

Geographically speaking, I am not very far of from karachi, and can tell you first hand - outside temperatures are in high 40s, and we still have not reached peak summers. 2 years ago, 55C was recorded. the only somewhat saving grace is that moisture levels are not that high (<30% for most of the day). But people are dying just of heat strokes.

After reading the incandescent bulb solution, and problems regarding touching the bulb, i would switch first switch on for a appreciably long time, such that bulb has hit maximum luminousity (they heat up as they run, the hotter they get, the brighter they are), then turn switch off, and turn second switch on and quicky run to other room. we are trying to observe change in luminousity as time elapses. if it reduces, it was first (we ran it for a long time, there would be some residual glow, from my irl observations from when i was small suggest roughly 1 min period where i can still tell, but bulb wattage, contrat with background and distance matter). if increasing or max luminous, then second, if nothing then third.

but it was a stupid question. my naive guess was it can not be done, because with just 1 binary observation, you can not tell from 3 switches (you need atleast 2, which the solution assumes as temp and light state, i substitute heat with light state in transition). but still stupid. my natural assumption was leds, even when i head incandascent bulbs in my house somewhere for nearly half of my life. it is also stupid, because when you allow me to do something i was mentioned in question to do, i could just bend my way to do anything. like punch/drill through wall, or hack surveillance systems, or just pull out my handy multimeter that i always have on me, open switch box and see which switch is live, which is dead, or see voltage/current/wattage change across the loop, or measure resistance and guess what thing is there, or like blackmail the interviewer to extract the answer.

sorry for being late, been away a lot lately. also the website just did not liek my setup (js/cache disabled, plus some more), had to start inprivate window.

getting to main topic - it is not a uplifting news from the title - but from the part - she became the first to sccore in shorts, which to my non sports term understanding ass sounds like skorts (or whatever those skin hugging clothing for respective sport is called) bad and shorts good, is uplifting. So definitely leave it up.

I watch cricket a lot (a bat and ball sport) - and you basically wear what you want - full/half sleaves, sweater or jacket or cap or hat - if it does not hinder your performance it does not matter.

I can see some sports where gear matters - swimming and running sports come to mind where viscous drag from water or air come in effect, and how your gear shapes and how vortex shedding happens and general graglines matter, so like running shoes, it becomes a requirement for performance, but beyond these sports, any clothing should work.

I do know that alot of women sports get viewing purely because a lot men get to see "hot women", and that is definitely bad.

it feels like a xy problem. if i am not wrong, single bit corruption leaving file unextractable is a bit wild, and my guess is that it's headers were blown.

As for general stuff, use a file system which does parity calc and such. or use something like raid to have redundant drives. (you can set something like 1 in 5 breaks, or 2 in 5, but more you allow to break, less actual space usable you would have). Or have really simple backups.

As to physical media - do not go flash based (ssd/sd cards/usb pen drives) if you want to leave them unpowered. they expect to be powered once every few months. they are effectively ram disks but like much more stable. Hard disk drives are better, but handle physical shocks much worse. you can drop a ssd and expect it to work. for a hard disk it is almost game over. Magnetic tape are better, they are much less data dense, but they are cheap.

I would assume it’s lossless

yes. these are lossless algorithms.

Now coming to compression - no compression practically deals with bit corruption. practically all compression formats aim for small size and or fast (de)/compression. Saving parity bits is wasteful.

If you can install some thing, try, for eg, https://github.com/Parchive/par2cmdline. You give whatever file (compressed or not), and it will generate parity bits so you can repair stuff. now use whatever compression you want, and prepare parity bits for worst case.

As to what compression algorithm, zip or gzip (deflate), bzip2 (or newer 3), xz (lzma in general), and zstandard (or older lz4), brotli are practically not going anywhere. most distros use them, they are used on web, and many other places. My favorite is zstadard as it gives great compression and extremely fast.

Do any of them have the ability to recover from a bit flip or at the very least detect with certainty whether the data is corrupted or not when extracting?

no and no.

You should also consider file archive format. for example zip (the format, not algo) or tar are effictively standards and stable, and practically here forever. there are mountable ones like squashfs (also fairly common. most linux distros use it for live images) and dwarfs (not yet a standard, imagine squashfs but also deduplicating).

do compression formats exist (or can they exist) which correct for bit flop - yes

If your goal is that a single bit flip should not ruin it, you should probably not look into deduplicating ones (they are reducing the number of bits stored, so in case a bit flip happens, less files would be corrupted).

Now coming to another part - do you want to compress data ? if so, why?

when you compress data, you literally reducing number of bits. now imagine if all bits on your disc are equally likely to undergo bitrot. if so, compressing makes your files less likely to rot.

but as you have also said, it is possible that if they corrupt, the corruption is more catastrophic (in a plane text file, this may just mean a character mutated, or in a image, some color changed. hardly problematic).

So you should also check - is compression worth it? come up with a number, lets say 90%. if compression algorithm reduces file size to 0.93 the original, do not go for compression. if it does, do compress. I am not saying pick 90%, but like decide on one you seem content with.

here is a stupid idea. if compression reduces file size by 2x, then compress, and make yet another copy. now even if one is corrupted, you have a pristine copy.

not to downplay your issue, but if you would even go like 5-10 years back, and ask for biggest issue on linux, and this was your issue, people woud genuinely think you are joking. linux/foss has progressed greatly.

why do we want to hate on other projects.