this post was submitted on 31 Jan 2025
389 points (96.6% liked)

TenForward: Where Every Vulcan Knows Your Name

4075 readers
824 users here now

/c/TenFoward: Your home-away-from-home for all things Star Trek!

Re-route power to the shields, emit a tachyon pulse through the deflector, and post all the nonsense you want. Within reason of course.

~ 1. No bigotry. This is a Star Trek community. Remember that diversity and coexistence are Star Trek values. Any post/comments that are racist, anti-LGBT, or generally "othering" of a group will result in removal/ban.

~ 2. Keep it civil. Disagreements will happen both on lore and preferences. That's okay! Just don't let it make you forget that the person you are talking to is also a person.

~ 3. Use spoiler tags. This applies to any episodes that have dropped within 3 months prior of your posting. After that it's free game.

~ 4. Keep it Trek related. This one is kind of a gimme but keep as on topic as possible.

~ 5. Keep posts to a limit. We all love Star Trek stuff but 3-4 posts in an hour is plenty enough.

~ 6. Try to not repost. Mistakes happen, we get it! But try to not repost anything from within the past 1-2 months.

~ 7. No General AI Art. Posts of simple AI art do not 'inspire jamaharon'

~ 8. No Political Upheaval. Political commentary is allowed, but please keep discussions civil. Read here for our community's expectations.

Fun will now commence.


Sister Communities:

[email protected]

[email protected]

[email protected]

[email protected]

Want your community to be added to the sidebar? Just ask one of our mods!


Honorary Badbitch:

@[email protected] for realizing that the line used to be "want to be added to the sidebar?" and capitalized on it. Congratulations and welcome to the sidebar. Stamets is both ashamed and proud.


Creator Resources:

Looking for a Star Trek screencap? (TrekCore)

Looking for the right Star Trek typeface/font for your meme? (Thank you @kellyaster for putting this together!)


founded 1 year ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] Skullgrid -4 points 1 day ago (1 children)

Some of the comment that was deleted because it was too naughty addressed that, it's not that it's "made to anger me" it's to rip people off by misrepresenting the amount they are selling and started much more recently than people think.

[–] TheGrandNagus 3 points 1 day ago* (last edited 23 hours ago) (1 children)

I can see that argument.

However it's also true that most people who see the units assume it follows the same 1000-based system as literally everything else that uses those SI-prefixes does.

I somewhat doubt that all these international standards organisations are in the pockets of Western Digital and Seagate. It's far more likely that they think "kilo means 1000, not 1024. Because that's literally what kilo translates to." Of course, the end result is still that it benefits storage manufacturers, but I highly doubt that's what they set out to do.

Regardless of your opinion on the matter, getting that angry at people and dismissing them as bootlickers because they explain the GB vs GiB debate seems over-the-top to me.

[–] Skullgrid -2 points 1 day ago (1 children)

In the past, that system was fine. After all, an additional 24 bytes or kilobytes is a tiny amount. But now that we’re getting into super huge data sizes, the gap is significant. 8 terabytes by the official scale is 8 trillion bytes, but by the traditional scale it’s 8.8 trillion bytes, a pretty sizable difference!

Yeah, the 0.8 trillion bytes that the manufacturer is ripping off the customer with.

[–] TheGrandNagus 2 points 1 day ago* (last edited 11 hours ago) (1 children)

Not really. The average person sees 8TB and assumes it means 8000GB. And... well... now it does.

Only a very small amount of people (tech nerds) could think it actually means 8192GB, and that each of those GB was actually 1024MB, and so on, and the people who know that also probably won't be fooled by the misleading thing you say is happening (it isn't. They're calling a TB a TB, as they should be).

Personally I'm fine with kilo/mega/giga/tera meaning kilo/mega/giga/tera, as opposed to kilo/mega/giga/tera plus some extra. Nobody is stopping you from measuring things in GiB and getting the numbers you desire.

[–] Skullgrid -2 points 1 day ago* (last edited 1 day ago) (1 children)

and how many people see a 1 tb hard drive and see that it only gives them 909GB and say "yeah, that's cool"?

[–] TheGrandNagus 1 points 22 hours ago* (last edited 11 hours ago)

If a HDD is a 1 TiB, it should be marketed as such. If it is 1TB, it should be marketed as such.

If you buy a 1TB HDD and it appears as 931GB in Windows, then that is expected behaviour, as Microsoft has chosen to incorrectly label GiB as GB. Take it to them. They're the multi-trillion dollar company to be angry at for falsely presenting numbers.

If they instead showed a GB number (rather than showing the GiB number but labelling it as GB) it would show the 1000GB as expected.

I know you're really going for a "you're a corporate bootlicker in the pockets of WD and Seagate", but it's really not sticking. I think you're just going out looking for an argument.