videos
Breadtube if it didn't suck.
Post videos you genuinely enjoy and want to share, duh. Celebrate the diversity of interests shared by chapochatters by posting a deep dive into Venetian kelp farming, I dunno. Also media criticism, bite-sized versions of left-wing theory, all the stuff you expected. But I am curious about that kelp farming thing now that you mentioned it.
Low effort / spam videos might be removed, especially weeb content.
There is a cytube that you can paste videos into and watch with whoever happens to be around. It's open submission unless there's something important to commandeer it with at the time.
A weekly watch party happens every Saturday (Sunday down under), with video nominations Saturday-Monday, voting Monday-Thursday. See the pin for whatever stage it's currently in.
view the rest of the comments
tl;dr: maybe if our abstraction is no longer relevant we need a new abstraction
Didn't watch whole thing. Saving to watch later but when it comes to this type of thing, I always wonder where to draw the line between "you should know" and "irrelevant to most people". I like unix and plan9 so knowing how the filesystem works matters a lot to me. I also think diskless systems and immutable os are cool and a lot of people just use computers for browsing the web.
if most of the files you care about are photos, do you need to care how the fs works? what about the difference between ext4, fat32, gefs? to me both are pretty important but i don't expect most to care
EDIT: I appreciate this all being articulated. i may have phrased too imprecisely in that I was not trying to argue that this necessarily shouldn't be taught as much as much as wanting a discussion of where the line is between something people need to know and something i care about.
Yes. This should be required knowledge in our age. Nobody should graduate from school without a fundamental understanding of how computers work. You don't need to know the technical differences between ext4 and NTFS, just that different filesystems exist. You should know what an operating system is. If we don't teach these things, people will perceive computers as magic. They will resign themselves to helplessness.
Instead, they are graduated with a fundamental understanding of how to use Google Docs :(
we got here too from the transition to graduating them with a fundamental understanding of how to use Microsoft Word instead of computers
My point is the to my use case, the implementation details matter too. either way, the FS is an abstraction and doesn't need to exist in the way that it does. I just think it's funny where people draw the line at X abstraction but not Y. Where is the line and how much should people understand?
While it is true the filesystem itself is an abstraction, it is a common abstraction used by every contemporary operating system for the past 40+ years, including the ones which hide this aspect from the end-user, excepting highly resource-constrained embedded systems. You could define an operating system as something that does filesystems and be like almost correct. If alternative architectures (like a global key-value store with namespaces, for instance) were in common use, then they would be worth mentioning in a practical "how computers work" course rather than courses for people specializing in computer science.
Great points!
people should learn how this shit works. hiding it from users is how we got in this mess.
Maybe. I think the real mess is because we let libertarians and the NSA make most of the infrastructure
I think the problem arises when you need to walk outside of a specific app ecosystem (where all the various different apps know how to talk to one another and find each others' files), and now your lack of understanding of the underlying system makes it difficult for you to actually do anything. I was scrolling through the comments and came upon this one:
Now, one probably shouldn't be doing anything involving bunches of documents on a phone, but maybe that or a tablet is just all you've got, and we could come up with other examples.
For photos - why do you care about them? You're presumably not just hoarding thousands to be buried with as grave goods eventually, you're going to be doing stuff with these photos, like sharing them with family members and friends. And this works fine as long as you remain within the particular ecosystem (which is probably what Apple wants you to do on their hardware anyway) - one friend sends you one photo on a specific messaging app and you resend it to another friend. But what if the first friend is on one app, and the second friend is on another - now you need to dig out wherever the first app saves files to, and hope that the second app allows you to actually select files from there? What if, let's say, a younger sibling sends you some cute photo of their kid, and you want to resend it to your parents so they can see their grandkid, but they're old and don't actually use any social media, so your only form of digital communication with them is via email - again, you need to actually dig out the file itself, not just access it via the specific app.
The automatic discovering of files so they can be shown in the UI can also backfire in some cases - my (not an i)phone insists on showing me a bunch of the music I have in the Gallery app and as options when sharing photos, since it's technically music videos I've downloaded rather than just pure audio files. Why are the Gallery and other apps even scanning the Music folder in the first place? And UIs designed for this are also miserable to use - like yes, Mr. Jobs, just dumping every single photo I have in a linear list so that I have to scroll for several years instead of going Documents -> Photos -> specific folder with the specific photos from the specific event I actually care for, because I've organized my files properly is exactly what I think of when I hear the word "intuitive"! Now, that's why modern gallery apps generally have various album features, but again, that ties you into the ecosystem - if I want to exit that ecosystem, and migrate my files elsewhere, I just get the plain files, not the organization of those files into albums/collections/whatever-they-call-them-in-this-specific-app which only exists within the specific program - and thus I'm stuck with an unnavigable mess.
And tying people to ecosystems like this is bad - like, maybe if we were in some cyber-Soviet future where we just had "the state's photo app" and "the state's email app", and they were all designed to work properly with an intuitive UI since there wasn't a financial incentive to shovel ads and other bullshit everywhere - but in the current capitalist hellscape, this leaves users completely at the mercy of corporations to not overreach and screw them over. Want to switch to a different system since our recent updates have been making everything worse, and we just stealthily amended our EULA to allow AI training on your highly personal family photos? Well, tough shit, all your photos are here, all your documents are here, and you can only ever access them through our apps!
This title is misleading, I've only skimmed the video because I don't have time (will watch it later and edit if I need to), but she's talking about the filesystem hierarchy (mostly, she does mention some details about actual filesystem implementations), not the actual filesystem implementation (ext4, bcachefs, etc)
see other reply
Whether it has impact on direct usage or is important to fixing it. I concede the line is blurry but with this I often refer back to cars, not that it fares much better there, you should know whether the car you're driving is FWD or RWD (or AWD) because it has direct impact on you driving it. Not necessarily in the boring cruising on the freeway time, but when it counts.