cumbersomely thick, but also desirable
Go on...
A virtual community
Posts from Mastodon users, featured natively in a community, so you can view them without the need for them to be re-hosted or screenshoted, and reply to the original author and Mastodon respondents if you wish.
Has so far included content from Warsandpeas, Mr. Lovenstein, SMBC, Loading Artist, Low Quality Facts, nixCraft, ElleGray, and other interesting or provocative stuff I've random'd across on Mastodon.
Supported:
Comments & Upvotes
Unsupported:
Posts, Downvotes, & PD's Automod
cumbersomely thick, but also desirable
Go on...
ITT, it’s unclear if people realize the image is a joke.
@NanoRaptor I once had a Mac guy turn up at my workplace and tell me 'the document you need is on this iPod'.
I plugged it into a Linux machine and it mounted the filesystem just fine.
The horrors I saw in that filesystem, how it was laid out and how the iPod needed to use its database to present real names to the user ....
I never want to see that again.
how the iPod needed to use its database to present real names to the user
I mean in Apple's defense you wouldn't want a media player to show filenames to the user anyways, you would want to display the artist/track name from the mp3 tags. The 4 letter filenames are a hash table presumably due to length restrictions in the firmware and/or performance reasons
The track data and everything is stored in the file, the file name is irrelevant.
Iirc thats what OP is referring to, they would strew the files stripped of meta data across the partition in various folders with little discernible structure, track data was written to the database and would be queried on song plays. I believe the advantages were faster bootup (Scan db instead of thousands of files) and the random file names were to ensure unique keys in db and help the “random” algorithm.