Every time when a YouTube video is embedded in Lemmy, a bot appears, suggesting to use Front-end Piped (or another) instead of YT, which is certainly recommended, due to YouTube’s inherent privacy concerns.
However, then it is not understandable, why in the case of images Imgur links are happily allowed, which is infinitely worse in terms of privacy, which shares user and usage data with the worst existing advertising companies, which makes it in little less than spyware.
As a suggestion I present 2 alternatives, which in addition to, as EU products, strictly adhere to the GDPR standard and even more.
As the main FileCoffee service, this, apart from images, supports ALL types of files, whether multimedia, video, documents, presentations or texts. Supports 15 MB/file and with optional registration to also use it as a personal host (100% free with mail, password) up to 30 MB/file, encrypted. Inclusions script one click for ShareX on Windows or MagicCap on Linux or Mac
The second is vgy.me, also privacy oriented, but supports only images, encryption, 20 MB/image, EXIF Data are removed, API for web pages.
No. “Mi” is just a different prefix than “M” and it doesn’t matter what units you attach them to. Why would it? It’s just a multiplication with 2^20 or 10^6, respectively.
2^20 = 1.048.576 ≠ 1.000.000 = 10^6
Ki Mi Gi Prefixes are for powers of two, K M G for powers of ten.
Of course you can choose whatever prefix you prefer, but when talking about storage or anything digital, we usually mean the power of two series. For that matter it’s better to be explicit instead of assuming everybody knows.
I never claimed that 2^20 is the same as 10^6. In fact, I explicitly said that they are different. But if I use M on purpose, it is not a correction to just replace it with Mi, for that same reason.
True, i misread your first post.
Where’s the contradiction? Yes, it’s just a different prefix but it results in a different number. What I meant to adress is that very often people write MB/megabytes (10⁶ = 1,000,000 bytes) but actually mean MiB/mebibytes (2²⁰ = 1,048,576 bytes). RAM vendors possibly most prominently.
There is no contradiction. But there is also nothing contradictory or wrong with the unit MB. If I say “this is 100MB”, maybe I just… mean that? No reason to correct me.
And I didn’t say that. Admittedly, the constraint “If the image size is defined as binary” probably could’ve been expressed better (I’m not a native speaker). File sizes are usually calculated in binary units (at least by Windows and the Linux distros I know - even though Windows continues to claim those are megabytes and Linux adopted the standardized units) and I’d bet that’s the case for file.coffee, too.
Oh, well, I’m pretty sure we’re not really disagreeing anyway. So let’s conclude with the obligatory relevant xkcd.