You should look up IPFS! It’s trying to be kinda like that.

It’ll always be slower than a CDN, though, partly because CDNs pay big money to be that fast, but also anything p2p is always going to have some overhead while the swarm tries to find something. It’s just a more complicated problem that necessarily has more layers.

But that doesn’t mean it’s not possible for it to be “fast enough”

Knowing the folks at IA I’m sure they would love a backup. They would love a community. I’m sure they don’t want to be the only ones doing this. But dang, they’ve got like 99 Petabytes of data. I don’t know about you, but my NAS doesn’t have that laying around…

I’m not the person you’re replying to, and I don’t have any videos, but I do love dumping explanation on people! So here’s some terms:

File System: This is the way data is laid out in terms of actual bytes on the drive. It’s in charge of things like where to look to find the name of this file, or how to “last modified” date is stored, or how do I find out which files are in this folder. NTFS is a filesystem, whereas ext4 is probably the file system your linux machine is using. FAT is the older Windows one that’s still used on, like, SD Cards and stuff. That having been said File System is sometimes also used to refer to the particular data on a particular partition of a disk, like “the filesystem will allow” which really means the data on your NTFS partition. Filesystem is often abbreviated “fs”, and is in fact the “FS” of “NTFS”

Mounting: In unix systems, such as Linux, file systems are “mounted” to a place in the folder hierarchy. Everything in unix lives somewhere under the “root” folder /, so mounting is basically saying “Okay, you want to see the files in this filesystem. Where should I put them?”, and if you say /home/user/stuff then the file “one.txt” at the root of your filesystem will now be visible at /home/user/stuff/one.txt", and if you mounted it at /mnt/things it would be /mnt/things/one.txt. The term mount is used like “attach” to mean “where do you want me to hang this new directory hierarchy on your existing one”.

fstab: There are a few ways to mount things in modern linux. The classic is the mount command which looks something like mount /dev/sda1 /home/user/stuff which would take the device with the name /dev/sda1 and mounts it to the given path. Devices in linux usually live in /dev, and in this case are often given names like sda1 to represent the first hard drive (a), and the first partition of that drive (1). But, there are other ways! You can also click on the partition in your file browser and it will mount the disk for you, often auto-creating a mount path and cleaning it up when you’re done, so you don’t even have to think about it. Another way is fstab, which is a kind of config file that controls mounting devices. In here you can give default options for how you want drives to be mounted, and can even specify that you’d like some devices to be automatically mounted by the system on startup. This is actually an important part of how unix systems start, and how the root filesystem and other important ones get going. If you wanted your NTFS drive to always be available at a permanent location, you would edit this file to set that up. If this is something you wanted only periodically, then just clicking may be fine.

Permissions: Virtually all unix filesystems store the permissions of files and directories as a “user” and “group” that owns the files, and then a set of whether or not the owner can “read” “write” and “execute” the file, whether other members of the group can, and then whether everyone else can. If two people were on the same computer, these would allow a person to be able to see their own documents, but not see the documents by other users. Or maybe they can see them but can’t make changes. And it also prevents random users of a system from changing important system configuration, when those config files are owned by the administrative user (called root by convention). Some config files will be read-only to normal users, and some contain secrets and so are permissioned so normal users can’t even see them. But! NFTS doesn’t follow these same conventions, so when mounting an NTFS drive on unix the driver has to produce a set of permissions that are unix-compatible, but it doesn’t have anything to work off on the disk. So the person above was saying by default it assumes the safest option is to make all files owned by the user root, and so if the permissions are the only the owner can write the files, and the owner is root, this will mean it’s effectively “read-only” to you. The terms uid and gid stand for “user ID” and “group ID”, which are the numbers that represent a user in the data. User names are basically a convenience that allows us to give a name to a uid, but it’s more efficient to store one number everywhere on disk for owner rather than a name.

So putting it all together, what they’re suggesting is that you can use the /etc/fstab file, which has a very particular format, to specify default options when mounting your drive. These options include setting the uid option and gid option to your user’s uid and gid, so that when the filesystem is mounted, it will appear that all the files are owned by you, so you’ll have full permissions on them. They’ve assumed your uid and gid will be 1000 because that’s a common convention, but if you’re comfortable you can run the id command on the command line to output your actual uid and gid (you can ignore all the other groups your user is in for now)

They also mentioned that when mounting you can specify if you want to mount the filesystem as “read-only” or “read-write”, etc. If you mount the whole filesystem read-only, then the write permissions stored on the individual files are ignored, basically. So if you were mounting with a command, or through fstab, you should make sure the rw option is present to clarify that you’re looking for “read write” permissions on your mount.

That having been said, it’s possible none of that is relevant to you if you’re mounting the fs by just clicking in your file browser. One way to tell is if you right-click on some file you aren’t allowed to edit and look at the properties there should be a Permissions tab thing. And it will list the owner of the file and what access you have. If those permissions are already set to be owned by you, then this uid thing is already taken care of for you by the file browser. In that case it might be something more fundamental to the NTFS filesystem, like the locks other people are talking about.

So those are some words and their meanings! Probably more than you wanted to know, but that’s okay. I liked typing it

I think I may have contracted some kind of brain worm, because the other day I needed to do some photo manipulation and couldn’t get krita to do what I wanted, but I went into gimp and just knocked it out. I’ve hated gimp for years, but I guess I’ve used it enough that I’ve figured out how it works… and now I don’t hate it anymore…

I think I may need help.

Oh, but I always use it in single window mode ever since that came out. The multiple windows floating panel thing drove me nuts!

Groceries, in particular, are more of an effect than a cause. Lots of people live without cars in New York City, or London, or Paris, or Toronto, or Tokyo, and they manage to eat. The reason you need to buy 7 days worth of food for two people all at once is because you live in a field far away from everything. “Getting Groceries” becomes a special trip, because, while driving, leaving the highway, stopping and parking are inconvenient.

As a pedestrian in a city, I was going to walk past 5 food stores on my way between work and home anyway, and it’s really not problem to walk in and buy only what I ran out of yesterday, or some special item I wanted for tonight’s dinner. It’s simple to shop for 5 or 10 minutes, five times a week, rather than one hour once a week, and never need more than a single bag of groceries at a time. And rather than being inconvenient, it’s actually great because I’m only buying what I need right now, the things I’m going to use as soon as I get home, so it’s very simple.

Allergies could be tricky, yeah. If you’re lucky the local shop, by nature of being smaller and more local, actually knows you and knows you need this stuff and stocks it because they know you’ll buy it from them. But that’s not a guarantee, for sure. That having been said, if the only people driving were people with corn allergies, the roads would be a much safer place!

Also that’s not even a prism, that’s a pyramid…

Similar to other people, I think you should own it. Try to think of it not as “I betrayed my character” but rather “my character gave in to temptation and regrets it but has to live with the consequences”, then use that. Play the character as though they are unhappy with the changes, they regret it, but they must soldier on.

People aren’t all perfect archetypes, and characters can have flaws and nuances. And the best part is, if your character up until now had no reason to make the choice you made, maybe it’s time for an out of game flashback. Work backwards… what thing could have happened in their backstory that would explain why they made this seemingly incongruous choice? Why did this tempt them when so many other things did not, and why does this cause them so much shame now. That kind of stuff.

Or don’t! Just some suggestions, since it sounds like you’ve got nothing to lose, may as well try some character development!

Well… That’s actually probably fair as stated.

BestBuy etc don’t sell Apple’s products on commission, they bought them from Apple for a wholesale price, they’ve got them in a warehouse and on shelves right now on their dime, and the only way they make that money back is by selling them.

And the only way Apple makes money from a product being sold at Best Buy is that Best Buy will likely buy more stock to replace the stuff they sold, and they’ll buy that from Apple.

So if it was banned everywhere it would be unfair to the retailers that already paid Apple for a product they now can’t recoup, and it wouldn’t impact Apple at all because they already made their money from Best Buy.

This way the retailers can get their money back, but can’t get any more, which means only Apple is impacted.

The only other way that’s semi-fair (but would be extreme) would be for Apple to be forced to do a recall or something and reimburse all the retailers the money they had already spent. Doable, and definitely more of a punishment for Apple, but a lot of extra work for everyone if the outcome of this is that Apple settles and then everyone can just go back to ordering more again.