Literally, yes. They are engines that search data. You could index the web on them if you really wanted.

As to how they are used, correctly or not, I consider them closer to databases than “search engines” in the context of this post.

Seeing ES or OS in the same category as Gigasearch needed some distinction though.

I’ll walk through it again, as you are probably right, and I can find the mistake.

1800g is the estimate weight of 450gml silver powder.

The total weight is 1464g.

There is 250ml (g) of water at the top of the container, which we subtract from the total weight, leaving 1214g of a silver/water slurry.

1800g should be the weight

1214g is the weight.

(Here is the mistake) The weight difference is 516g, which is the weight of the missing silver in the slurry, not the weight of the water in the slurry.

So, I would need to convert 516g to an approximate volume of silver powder. Since we have volume, we can now compute the weight of the water in the slurry.

Dunno about other search engines, but Opensearch and Elasticsearch are databases, not search engines. (Openseach is a fork of Elasticsearch, actually.)

Mematic brand fish sauce?

Damnit. I edited with that correction, but deleted the edit, cause who the fuck knows why. Was kind of in a rush at the time, and didn’t think I would have been silly enough to miss the 250g.

Good cach and yeah, I felt it.

Just got it.

It’s tap and hold thumbnail with one finger -> use another finger to do a “zoom out” gesture on the screen.

It seems to happen only on image posts, and when you don’t trigger a page reload or side menu open behind the opened preview.

(Also, it’s still super rare to trigger the bug. I only just got it twice since I started responding to your comment.)

Edit: Reliable trigger:

Press and hold thumbnail -> use another finger open side menu -> click “All” or other menu choice -> release first finger.

deleted by creator

250ml solution (mostly water on top) = 250g

700g (if 700ml water) - 250g = 450ml silver slurry

450ml silver powder weight (dry) = 1800g

1464g (total) - 250g (excess water) = 1214g

450ml slurry = 1214g slurry

1800g (dry silver) - 1214g (silver slurry) = 516g (516ml water in slurry)

1464g (total) - 516g (water) = 948g silver powder.

I always miss something obviously stupid when doing math in public. However, it sounds suspiciously close to a 1kg starting weight of silver though.

Nah, it was kind of a dumb question actually. The volume isn’t going to change much unless you melt it down. Thanks though!

How much? Weight or volume?

I assume you mean weight… Give me a sec and I’ll take a guess.

But in the UK, is a crisp “crispy” or is “crisp” a derivative of another term or phrase?

ml would like a word.

That needs to be in the form of a question, right?

There is a caveat, but yes: By definition, 3D printed parts should not be considered food safe.

Single-use cookie cutters are generally OK if you don’t use them multiple times a day every day.

There are probably minor chemical risks but it wouldn’t be in high enough quantities to kill you. There isn’t really anything inherently food unsafe with PLA, ABS or PETG.

Bacteria is a much bigger risk during reuse because you can’t fully clean the prints between the layer lines and other surface defects. The plastic generally won’t survive a proper sanitization process either.

What your own risk tolerance is for plastic additives is up to you. If you do print a cookie cutter, toss it after you are done.

HF tools are not designed for the long term, generally. If you need a tool to work at least once, for one job that you are never going to do again, HF is “good enough”.

The rule of thumb is to never buy a tool there that could result in a gruesome death if it fails to protect your life, like jack stands. (Invest in quality safety equipment first if you get something like an angle grinder.)

It’s just a surface to air missile. 100 is quite a few, but considering how drones are used in this conflict, it’s probably not nearly enough.

They are likely reserved for last resort air defense closer to cities or areas where they really need to push back the Russian air force.

Patriot batteries are a bit on the expensive side, so their use is likely limited. If I am not mistaken, Ukraine did get a few batteries from other NATO countries and not just the US.

And it’s about a mile? Many common rifle bullets will be starting to nope-out of supersonic around that distance, so you would need something really beefy, like a .338 Lapua or even a .50 to be accurate. (A bullet will generally start tumbling when it drops sub-sonic.)

Don’t mistake me: many bullets can and do travel past a mile regularly, especially depending on the shot angle. Yeah, they can still kill. I am referring to the uncertainty and inaccuracy at those ranges, especially if a bullet has lost a ton of speed.

My main point is that long range sniper rifles are quite large caliber and generally require long heavy barrels. You aren’t going to swing one of those around without being noticed.

The shot speed approximation is the easy part, believe it or not. Since the bullet must be a large caliber you can guess at about 200-300 grains for a “smaller” large caliber bullet, or between 650-900 grains for a larger one. (Maybe a few more, but I am sticking with a 338 or a 50.) Muzzle velocity is also going to be on the high end at between 2900fps and +3100fps for most all of them. The math is easy to work out with a common ballistics calculator by estimating the ballistic coefficient of available bullets in the category we are talking about. (Bullet speed at the target is the most important number to calculate.)

Still, it’s not perfect math. If you look for a camera flash at an estimated time when a bullet was supposedly fired, you are probably going to find one, especially if you have a second or two of footage across multiple cameras.

Old 386 and 486 code was really easy. I also got lost around the Pentium era as well. At the time, it was getting really hacky to work through extended and expanded memory while also learning to work with 32bit registers.

At the time, correctly or not, I just felt I was learning to navigate a bunch of architecture bandaids and not anything that was going to be static for the next few years. I just kinda put it aside, TBH.

ASM is still useful for MCUs at times and developing that feels like the good ol days…

You can generally cross compile across architectures, but there can be instruction or build nuances that can cause hiccups. Also, you need to build everything against the target architecture as well, not just the kernel.