When I was getting started with libfuse, it was extremely intimidating. I still don't have a full grasp on the API, but I've put together a template to help future adventurers get through the early learning process.
The Libfuse Template
The repository has been structure so that each fuse operation lives in it's own
file. For getting started, we have stubbed out each operation and have included
a simple logger that let's you know when these stubs are being called. This
should give you a good understanding of what order you need to implement
operations in, simply start playing around with the filesystem and implement
whatever stubs you see being activated!
This was the hardest part for me when I was getting started. There is a lot of misinformation about fuse floating around, and its hard to find definitive information for the API version you are developing against.
There is a handy [doxygen
This post dives into the movie assuming you have seen it. If you are planning
on seeing it and don't want the plot ruined STOP READING NOW!
The movie itself is just a mainline injection of nostalgia. The storyline is rather weak. It is a take on society with late stage VR. The year is 2040ish and it appears everyone has standardized on playing a single VR based MMORPG. The creator (and apparently sole designer) of the game has died and left the "keys to the empire" hidden away in the game as a series of easter eggs. Whoever finds all the easter eggs inherits the game, and apparently the rights to make decisions about how the game is structured.
The antagonist of the story is a large corporation that sells mods in-game. They want to acquire the rights to the video game in order to maximize its profitability by making significant changes. Essentially they want to turn it into this pay-to-play, advertising ridden, nightmare of an experience.