mrb

Want to bet 100 MB? 1 GB? Is it unthinkable?

20 years ago, a 49 MB home page was unthinkable.

But the author has a point. Combine it with some approximate country-level geolocate of the web client and this would work perfectly 99% of the time modulo edge cases like VPN users.

Well, isn't it expected? If I were a double agent, faking that I was so computer illiterate that I ask my emails to be printed out would be the perfect cover for my hacking =:-)

"""

Great question! Here are a few things to consider:

If you walk: It’s only 50 meters, so it’s a very short distance—less than a minute on foot. You’ll avoid getting your car dirty again on the way to the car wash. It’s a quick way to stretch your legs and save a tiny bit of fuel.

If you drive: It’s so close that driving might feel unnecessary, but it could save you from carrying any supplies (like vacuum cleaners or cleaning products) back and forth. If the weather is bad (rain, extreme heat, etc.), driving might be more comfortable.

Verdict: Walking is probably the easiest and most practical choice for such a short distance, unless you have a specific reason to drive. What’s the weather like where you are? That might help decide!

"""

As an Android user, I truly don't understand this "pressure". I exchange SMS/MMS with various users, some Android, some iPhone. I am in group chats with both Android and iPhone users. I feel there is no major issue. It's interoperable. We all see each other's emojis/photos/videos/etc. There are only minor technical rough edges: for example an iPhone's user emoji reaction sometimes (not always?) shows up as separate text instead of the emoji appended at the bottom of the text bubble... And I am pretty sure videos are sent in a lower quality. But is any of this really enough to cause a "blue bubble pressure"?

I asked ChatGPT to explain but only got this vague answer: "Group chats with a mix of iPhone and non-iPhone users can be less seamless (e.g., lower video quality, no read receipts, or issues with group chat features)."

I had to open my texts to check: I indeed have read receipts when texting Android users, but not iPhone users. And this is funny but up to this very second, I had never noticed this difference... because, at least to me, read receipts is such a minor feature that I rely on very infrequently.

This leaves me still as perplex: why the "blue bubble pressure"?

You can conceptualize Rayleigh scattering exactly like you did so it doesn't conflict with my explanation: as light hits the "surface" of nitrogen and oxygen molecules, it "reflects" (scatters) blue wavelengths.

Because it's the color of the atmosphere, specifically nitrogen and oxygen! It's technically correct to state this.

Gasp! But aren't nitrogen and oxygen usually described as "colorless"? Well, yes but... If they were perfectly colorless, the sky would be black. It's technically more correct to describe them as nearly colorless and very slightly blue. Very slightly because you need to see through kilometers of atmosphere to perceive the blue. It doesn't matter if the color is caused by absorption, or reflection, or (Rayleigh) scattering of certain wavelengths. The "color" of an object is simply the color you perceive with your eyes. If you perceive blue, it's technically correct to say its color is blue.

It's like saying plants are green because green is the color of chlorophyll. And in the case of chlorophyll, the color is caused by absorption not by scattering. But the physics is irrelevant. Green is its color.

Q: But sunsets/sunrises are red & orange not blue! A: the simplest answer is: color of an object can change under different light conditions. Specifically in this example, when seeing the sun through not kilometers but hundred of kilometers of atmosphere, all the blue-ish wavelengths have been scattered in random directions so only the red-ish wavelengths remain, thus the atmosphere is illuminated by progressively redder and redder light as the photons travel longer and longer distances through the atmosphere.

Note that technically my link is a slightly longer sightline (longer by 7 km).

Edit: to be clear the difference stems from our coordinates. Our starting points are:

41.059167,77.683333 (me)

41.0181,77.6708 (you)

And our end points are:

36.295364,78.755593 (me)

36.314,78.7654 (you)

Also I calculate the distance assuming the Earth is spherical (which gives 538 km) not the standard geodesic (which would give 537 km).

And in the DEM data I measure the distance from the center of a cell to another (not the edge), while measuring from edge to edge may explain a difference of at most 0.1 km as the DEM resolution is 3 arcseconds.

So clearly we disagree on the coordinates of the exact actual sightline as we have a 7 km difference :-)

Edit #2: clearly the error is on your side. I should have checked this first, but the coordinates you give for the "To" point (41.0181,77.6708) land in a valley with the south view completely blocked so it's impossible to view 500+ km south as you claim. Look at where the marker lands on this Google Maps Terrain: https://maps.app.goo.gl/PgBWxi31WZC6vk3V9

I gave some examples in my post https://blog.zorinaq.com/decimal-prefixes-are-more-common-th...

One tip for the author who noticed the camera being warm: measure its power consumption, and compare to an unmodified G9ii. Especially because you noticed it drains the battery relatively quickly(!) This is a glaring "connect the dots" situation to me. The root cause might be something very stupid. For example when you removed the microphone jack, the camera thought a microphone was connected, so it activated a microphone nenu. But given the extensive number of mods you made, it's possible you are making the firmware think some accessory is connected—could be anything: (light) flash, external screen, USB gadget, JTAG reader, SD card, etc. So it's taking a code path to initialize the device, but it fails because the device is not present, and it retries repeatedly, thus entering a retry loop that's causing excessive CPU usage... That wouldn't surprise me. You are running a G9ii that's unique therefore a rare software code path like this would not happen on a standard G9ii and would never have been fixed by the developers.

Edit: I see the author measured power here: https://www.reddit.com/r/Lumix/comments/1oif3jp/how_much_doe... and to my eyes, these seem really high numbers. For example in video playback mode he measures 340mA, so 2.45W (battery is 7.2V nominal). The standard G9ii battery is 16Wh that means it would last only 6.5 hours playing back video. Compare this to a Pixel 9 phone: 18.3Wh battery and can playback video for 15 hours (I believe these are benchmark numbers reported playing back 4k H264 video, probably in a similar-ish format to the G9ii in terms of bitrate, etc). Plus the phone is at a disadvantage as it has a bigger, more power-hungry display. So it seems to me his G9ii consumes twice as much power as it should, if not more... If anything a pro camera should be more optimized than a general-purpose consumer device when playing video!

What does this mean? You mean they have close to 1k employees? Odd typo or odd way to say it.

That's incorrect. Security scales with USD-denominated rewards, not BTC-denominated. And there are 16 years of real-world data showing they have been generally increasing, so a healthy sign that the Bitcoin experiment is working:

https://newhedge.io/bitcoin/block-reward-per-block

And not only that, but rewards are still expected to stabilize even when measured in BTC (thereby not relying on an increase of BTC's price) as they are progressively composed more and more of tx fees instead of newly mined BTC.

It's puzzling to me why some still don't understand the systemic incentives that make all this work as it has for 16 years and counting...

There is no cellular data in the NYC subway? I had to look it up online and apparently there is but coverage is quite patchy. That's very surprising to learn, NYC being one of the most developped and richest cities in the world. By comparison, and from my experience, the Parisian metro has excellent coverage.

If enough high-ranked customers report this feedback...

I thought this stark difference might be partially explained by US population increasing more quickly than EU. However it turns out in the 2010-2024 period, US population increased by +10% while EU27 pop increased +2%. So although there is a minor 8% difference, this is far, very far, from explaining the stark difference even if we compared per capita. The EU is certainly doing something right here.

As I suspected :-) Also note that by measuring "36W POE consumption" you are excluding the AC-DC conversion losses from the switch's PSU which further makes the comparison a bit unfair. IOW your POE equipment draws more than 36W at the wall.

The only fair comparison is looking as only your NAS idling with drives (35W you claim, and I still believe it's closer to 40W) vs the OP's NAS with 4 drives (which should be 57W, or 67W minus 10W for his two extra drives). Then if the OP used a better sized PSU he might cut out another 10W or so (see my "PS" above) then you are comparing your 35W (or 40W) with his 47W which of course is still in your favor and a testament that Ubiquiti did a great job optimizing the UNAS Pro. But this 12W (or 7W) difference hardly matters for someone running a single NAS at their house. This extra power is around $1 or $2 monthly at average US domestic electricity rates.

I know that's not true. I say this as someone who measures the power consumption of individual components, and even individual rails with a clamp meter. The OP measures an idle power of 67W. He has 6 x 8TB HDDs. These typically consume 5W idling (not spun down). So the OP's NAS without drives is probably around 37W.

A UNAS Pro without drives reportedly consumes 20W with no drives. Adding 4 x 8TB at 5W per drive, means your UNAS Pro config with drives probably idles at 40W (again, drives not spun down). That means you are 17W under his NAS idle power. So you claim your remaining hardware (Mac mini, 4 APs, 4 cameras) run in under 17W... Yeah that's not possible. 17W is peanuts; it's half the power of a phone's fast charger (~30W).

PS: for the OP, an easy way to further reduce power consumption is to replace your 500W PSU with a smaller one, like 250-300W which is still amply over-specced for your build. Because the typical efficiency curve of a PSU drops sharply at very low loads. For example at idle when your NAS pulls 67W from the wall it's very probable it supplies only ~50W to the internal components, so it's running at 10% load and it's only 50/67 = 75% efficient. The smallest load for which the 80 Plus Gold standard requires a minimum efficiency is 20%. If you downgrade to a 250W PSU you are enforcing a minimum 20% load for which the 80 Plus Gold standard requires minimum 87% efficiency. The load at the wall would thus drop to 50/.87 = 57W thereby saving you 10W.

My tiny personal web servers can whistand thousands of requests per second, barely breaking a sweat. As a result, none of the bots or scrapers are causing any issue.

"The only thing that had immediate effect was sudo iptables -I INPUT -s 47.79.0.0/16 -j DROP" Well, by blocking an entire /16 range, it is this type of overzealous action that contributes to making the internet experience a bit more mediocre. This is the same thinking that lead me to, for example, not being able to browse homedepot.com from Europe. I am long-term traveling in Europe and like to frequent DIY websites with people posting links to homedepot, but no someone at HD decided that European IPs couldn't access their site, so I and millions of others are locked out. The /16 is an Alibaba AS, and you make the assumption that most of it is malicious, but in reality you don't know. Fix your software, don't blindly block.

If you want to believe in an intelligent creator—not that I do—it's as if they were accelerating the expansion until the solar system was formed, then turned the control knob down.