Fancy. I just have a dumb switch that does it offline with any bulb. No dimming, though

A hidden experimental flag isn't "fixed." It might be the start, but until it's stable and usable through the normal UI, it's not really done.

It can be pretty easy to get up a second-hand console cheap, free, and/or as a gift.

Have you ever seen how much good/working stuff people throw away? If you're a little bright, you can get people to pay you to haul their "junk" away.

Voyager - if I didn’t love Voyager Janeway would kick my ass.

No need for threats. Voyager is good.

Blink twice if you need help.

It seems you are mixing the concepts of voting systems and candidate selection. FPP nor FPTP should not sound scary. As a voting systems, FPP works well enough more often than many want to admit. The name just describes it in more detail: First Preference Plurality.

Every voting system is as bottom-up or top-down as the candidate selection process. The voting system itself doesn't really affect whether it is top down or bottom up. Requiring approval/voting from the current rulers would be top-down. Only requiring ten signatures on a community petition is more bottom up.

The voting systems don't care about the candidate selection process. Some require precordination for a "party", but that could also be a party of 1. A party of 1 might not be able to get as much representation as one with more people: but that's also the case for every voting system that selects the same number of candidates.

Voting systems don't even need to be used for representation systems. If a group of friends are voting on where to eat, one problem might be selecting the places to vote on, but that's before the vote. With the vote, FPP might have 70% prefer pizza over Indian food, but the Indian food vote might still win because the pizza voters had another first choice. Having more candidates often leads to minority rule/choice, and that's not very good for food choice nor community representation.

That many steps? WindowsKey+Break > Change computer name.

If you're okay with three steps, on Windows 10 and newer, you can right click the start menu and generally open system. Just about any version supports right clicking "My Computer" or "This PC" and selecting properties, as well.

Do you remember the Internet Explorer days? This, unfortunately, is still much better.

Pretty good reason to switch the Firefox, now. Nearly everything will work, unlike the Internet Explorer days.

• Firefox User

I’m fully aware how rirs allocate ipv6. The smallest allocation is a /64, that’s 65535 /64’s. There are 2^32 /32’s available, and a /20 is the minimum allocatable now. These aren’t /8’s from IPv4, let’s look at it from a /56, there are 10^16 /56 networks, roughly 17 million times more network ranges than IPv4 addresses.

/48s are basically pop level allocations, few end users will be getting them. In fact comcast which used to give me /48s is down to /60 now.

I’ll repeat, we aren’t running out any time soon, even with default allocations in the /3 currently existing for ipv6.

Sorry, but your reply suggests otherwise.

The RIRs (currently) never allocate a /64 nor a /56. /48 is their (currently) smallest allocation. For example, of the ~800,000 /32's ARIN has, only ~47k are "fragmented" (smaller than /32) and <4,000 are /48s. If /32s were the average, we'd be fine, but in our infinite wisdom, we assign larger subnets (like Comcast's 2601::/20 and 2603:2000::/20).

These aren’t /8’s from IPv4. let’s look at it from a /56, there are 10^16 /56 networks, roughly 17 million times more network ranges than IPv4 addresses.

Taking into account the RIPE allocations, noted above, the closer equivalent to /8 is the 1.048M /20s available. Yes, it's more than the 8-bit class-A blocks, but does 1 million really sound like the scale you were talking about? "enough addresses in ipv6 to address every known atom on earth"

The situation for /48s is better, but still not as significant as one would think. With Cloudflare as an extreme example: They have 6639 IPv4 /24 blocks, but 670,550 IPv4 /48 blocks. Same number of networks in theory, but growing from needing 13-bits of networks in IPv4 to 19-bits of networks: 5 extra bits of usage from just availability.

That sort of increase of networks is likely-- especially in high-density data centers where one server is likely to have multiple IPv6 networks assigned to it. What do you think the assignments will look like as we expand to extra-terrestrial objects like satellites, moons, planets, and other spacecraft?

I’ll repeat, we aren’t running out any time soon

Soon vs never. OP I replied to said "never". Your post implied similarly, too-- that these numbers are far too big for humans to imagine or ever reach. The IPv6 address space is large enough for that: yes. But our allocations still aren't. The number of bits we're actually allocating (which is the metric used for running out) is significantly smaller than most think. In the post above, you're suggesting 56-64 bits, but the reality is currently 20-32 bits-- 1M-4B allocations.

If everyone keeps treating IPv6 as infinite, the current allocation sizes would take longer than IPv4 to run out, but it isn't really an unfathomable number like the number of atoms on Earth. 281T /48s works more sanely: likely enough for our planet-- but RIPEs seem to avoid allocating subnets that small.

IPv4-style policy shifts could happen: requirements for address blocks rise, allocation sizes shrink, older holders have /20 blocks (instead of 8-bit class A blocks), and newer organizations limited to /48 blocks or smaller with proper justification. The longer we keep giving away /20s and /32s like candy, the more likely we'll see the allocations run out sooner (especially compared to never). My initial message tried to imply that it depends on how fast we grow and achieve network growth goals:

30 years? Optimistically, including interstellar networks and continued exponential growth in IP-connected devices? Yes.

. . .

Realistically, it’s probably more than 100 years away, maybe outside our lifetimes

That wasn't what I said. 2^56 was NOT a reference to bits, but to how many IPs we could assign every visible star, if it weren't for subnet limitations. IPv6 isn't classless like IPv4. There will be a lot of wasted/unrunused/unroutable addresses due to the reserved 64-bits.

The problem isn't the number of addresses, but the number of allocations. Our smallest allocation, today, for a 128-bit address: is only 48-bits. Allocation-wise, we effectively only have 48-bits of allocations, not 128. To run out like with IPv6 , we only need to assign 48-bits of networks, rather than the 24-bits for IPv4. Go read up on how ARIN/RIPE/APNIC allocate IPs. It's pretty wasteful.

Vote. Seriously. (If practical: get involved, too). The U.S. is currently in the middle of a large shift of generational power.

Many of these changes are fairly recent:

• 2020 was the first federal election where the Baby Boomers didn't make up the largest voting generation.
• It was only in 2016 that the number Gen X and younger voting numbers grew larger than the boomer and older numbers.
• Those numbers had been possible since 2010. Despite having more eligible voters (135M vs 93M), the "GenXers and younger" only had ~36M actual voters, compared to ~57M older ones.

Looking forward, the numbers only get better for younger voters. There hasn't been a demographic shift like this in the U.S. in a long time (ever?). The current power structures can not be maintained for much longer. It is still possible for that shift to be peaceful. Please encourage the peaceful transfer: vote. Vote in the primaries. Maybe even vote for better voting systems. This time is unique, but change takes time. Don't let them fool you otherwise: that's just them trying to hold on to their power.

tl;dr

The memory bandwidth isn't magic, nor special, but generally meaningless. MT/s matter more, but Apple's non-magic is generally higher than the industry standard in compact form factors.

Long version:

How are such wrong numbers are so widely upvoted? The 6400Mbps is per pin.

Generally, DDR5 has a 64-bit data bus. The standard names also indicate the speeds per module: PC5-32000 transfers 32GB/s with 64-bits at 4000MT/s, and PC5-64000 transfers 64GB/s with 64-bits at 8000MT/s. With those speeds, it isn't hard for a DDR5 desktop or server to reach similar bandwidth.

Apple doubles the data bus from 64-bits to 128-bits (which is still nothing compared to something like an RTX 4090, with a 384-bit data bus). With that, Apple can get 102.4GB/s with just one module instead of the standard 51.2GB/s. The cited 800GB/s is with 8: most comparable hardware does not allow 8 memory modules.

Ironically, the memory bandwidth is pretty much irrelevant compared to the MT/s. To quote Dell defending their CAMM modules:

In a 12th-gen Intel laptop using two SO-DIMMs, for example, you can reach DDR5/4800 transfer speeds. But push it to a four-DIMM design, such as in a laptop with 128GB of RAM, and you have to ratchet it back to DDR5/4000 transfer speeds.

That contradiction makes it hard to balance speed, capacity, and upgradability. Even the upcoming Core Ultra 9 185H seems rated for 5600 MT/s-- after 2 years, we're almost getting PC laptops that have the memory speed of Macbooks. This wasn't Apple being magical, but just taking advantage of OEMs dropping the ball on how important memory can be to performance. The memory bandwidth is just the cherry on top.

The standard supports these speeds and faster. To be clear, these speeds and capacity don't do ANYTHING to support "8GB is analogous to..." statements. It won't take magic to beat, but the PC industry doesn't yet have much competition in the performance and form factors Apple is targeting. In the meantime, Apple is milking its customers: The M3s have the same MT/s and memory technology as two years ago. It's almost as if they looked at the next 6-12 months and went: "They still haven't caught up, so we don't need too much faster, yet-- but we can make a lot of money until while we wait."

They describe an SSH infector, as well as a credentials scanner. To me, that sounds like it started like from exploited/infected Windows computers with SSH access, and then continued from there.

With how many unencrypted SSH keys there are, how most hosts keep a list of the servers they SSH into, and how they can probably bypass some firewall protections once they're inside the network: not a bad idea.