megane-kun

deleted by creator

deleted by creator

I’ve had one of those (battery died, unfortunately) and if you’d look at its files, you’d notice that they are organized in a different structure than what an MP3 player might expect.

iPod_Control\Music’s sudirectories might contain some songs, but the filenames are hashes (corresponding to the entry in the iPod db). The metadata and the contents are perfectly fine, and you can play the file yourself via a different player (you can probably test it in your computer).

I suggest you just connect the iPod through the 3.5mm output audio jack or find a 3.5mm audio output to Bluetooth transmitter adapter.

EDIT:

WTF. I triple posted. My bad. I deleted the two others, also corrected some minor typos and mistakes.

They certainly exist in Ikea here in the Philippines. I’ve been there a few months ago and the free pencils and paper tape measures (rulers?) are still there and being used.

KDE themes are a mixed bag for me. On one hand, they can potentially provide theming for little to no effort on my part (provided I do find a pre-made theme to my liking), but on the other, I had more luck with mixing and matching (and a lot of tweaking) different theme components (that is: color theme, application style, plasma style, window decorations, icon theme, cursor theme, etc). It’s a lot of work, and the result might not exactly be coherent, but you can really tweak quite a lot.

I haven’t really tried emulating the win7 look and feel by customizing KDE Plasma, but I think it’s possible. Someone in this comment chain claimed there’s a Win7 theme available, albeit not pulling it off perfectly. I guess that can be used as a starting point.

KDE Plasma + Klassy can do that. I think you can pull off a Win7 look with just those two.

KDE Plasma can get you far with its customization options, and Klassy adds more customization on top of that, and adds the translucent/transparent effects you need to emulate the Win7 look.

It depends on what you need on a terminal. If I just wanted a terminal, I’d go with Foot, but Konsole (on KDE Plasma) might be a good all-around solution.

Not too sure if they outright lied, but I suppose we can say that they used the change to make their drives seem larger!

That’s why I wished computer people had used a prefix system distinct from the SI ones. If we’re measuring our storage devices in yeetibytes rather than gigabytes, for example, then I suppose there’s less chance that we’ve ended up in this situation.

I realized why I didn’t think of base 2 in my previous reply. For one, hexadecimal (base 16) often used in really low-level programming, as a shorthand for working in base 2 because base 2 is unwieldy. Octal (base 8) was also used, but not so much nowadays. Furthermore, even when working in base 2, they’re often grouped into four bits: a nibble. A nibble corresponds to one hexadecimal digit.

Now, I suppose that we’re just going to use powers of two, not base-2, so maybe it’d help if we do a comparison. Below is a table that compares some powers of two, the binary prefixes, and the system I described earlier:

Each row of the table (except for the rows for 2¹⁰ and 2⁵⁰) would be requiring a new prefix if we’re to be working with powers of 2 (four apart, and more if it’d be three apart instead). Meanwhile, using powers of 16 would require less prefixes, but would require larger numerals before changing over to the next prefix (a maximum of 16⁴ - 1 = 2¹⁶ - 1 = 65 535)

One thing that works to your argument’s favor is the fact that 1024 = 2¹⁰. But I think that’s what caused this entire MiB vs. MB confusion in the first place.

However, having said all that, I would have been happy with just using an entirely different set of prefixes, and kept the values based on 2¹⁰.

I guess? I just pulled that example out of my ass earlier, thinking well, hexadecimal is used heavily in computing, so maybe something with powers of 16 would do just fine.

At any rate, my point is that using a prefix system that is different and easily distinguishable from the metric SI prefixes would have been way better.

I think the biggest mistake there is using SI prefixes (such as kilo, mega, giga, tera) with bytes (or bits) to refer to the power of two near a power of ten in the first place. Had computer people had used other names for 1024 bytes and the like, this confusion between kibibytes and kilobytes could have been avoided. Computer people back then could have come up with a set of base·16 prefixes and used that for measuring data.

Maybe something like 65,536 bytes = 1,0000 (base 16) = 1 myri·byte; ‭4,294,967,296 bytes = 1,0000,0000 (base 16) = dyri·byte; and so on in groups of four hex digits instead of three decimal digits (16¹² = tryri·byte, 16¹⁶ = tesri·byte, etc). That’s just one system I pulled out of my ass (based on the myriad, and using Greek numbers to count groups of digits), and surely one can come up with a better system.

Anyways, while it’d take me a while to recognize one kilobyte as 1000 bytes and not as 1024 bytes, I think it’s better that ‘kilo’ always means 1000 times something in as many situations as possible.

If the earliest sports were a way to practice skills needed for hunting or warfare, then making an e-sport out of spreadsheets is going back to the roots of sports. It’s practicing skills needed for your daily job.

I’ve used Librewolf until pretty recently and I say it’s not for everyone. It’s hardened Firefox made into its own thing for people who want the benefits of hardened Firefox but don’t want to go through the effort of hardening their Firefox install.

There are some sites that wouldn’t work in the strictest settings. As far as I remember, the most problematic sites with Librewolf are those that demand way too much in terms of privacy and security, so I took it as a given that if a site doesn’t work with Librewolf (with me using the default settings), it’s not worth it to enter to begin with.

I can only speak from experience but from my understanding most people’s knowledge of Linux is derived solely from wanting to do something and then figuring out how to do it, instead of studying a list of “things you must know to use Linux”.

I second this. While I’ve been exposed to Linux quite a while back (Linux Mint, circa mid-2000’s if memory serves me right) and was given a “Linux basics” rundown, I only started daily-driving Linux around late 2019, and by then, my knowledge of Linux pretty much have faded. It still hasn’t prevented me from getting re-familiarized with Linux (Manjaro, then Arch). Of course, some bit of knowledge would help, but a lot of the Linux basics you’d need are already out there if you need it. Just look things up if the need arises.

Also, I find having to learn something I don’t immediately would need to use not very productive, even counterproductive at times since it leads me to having a mindset of “I should already know this, why am I‌ being so stupid?”

So yeah!‌ I second this sentiment of “just use your computer, look things up if you have to, it’s not going to hurt.”

And oh, don’t be afraid to mess with your computer from time to time. If you’re concerned about breaking things, you can install the distro of your choice into an old laptop or something, and use that as a place to “mess things up.”

Edit: I forgot that OP already is using Linux in a virtual box. OP can use that as a laboratory to “mess things up.”