How do files work?
So the code gets the user input and puts it to a file. But if you run the code and input something, will I be able to see your input as well? Or will it like fork the repl or something like that?
A potential solution:
Make a new file, name it
main, without an extension,
run the Repl, make another file, name it
.replit, without an actualy filename, just an extension, inside the
.replit file, put:
I may have just beat the system... but I highly doubt it. Honestly, thinking about this, don't even try, it'll fail.
What happens is that Repl.it creates a randomized file system on the user's end for every time a user views the repl while for the owner, the file system is always in /home/runner. /home/runner is the only file system path that actually will save in a given repl and all other randomly generated paths will disappear on reload or page close. The only way to allow other people to access the /home/runner file system is to use a server and within the server, based on requests from the client, write to files and read files.
I found a super easy way to make variadic lambdas (with minimal drawbacks), and am about to make a tutorial on it. Since you seem to be an adequate - good writer, wanna help me with it before I finish it and post it? https://repl.it/@StudentFires/VariardicLambdaTutorial
Interesting question! From my understanding, someone using your program can write to a text file, but only locally so you (the owner) cannot see their additions. The only one who can permanently write to a text file would be the owner. To avoid this problem, you can create a server with a text file and write sent information to it. With this method, anyone can write permanently to the text file and see other's modifications.
@DynamicSquid This is something that Repl does, it invisibly makes a separate temporary filesystem for each person who views a Repl, I partially wrote about this here: How to access the virtual file system that Repl generates when someone opens a Repl?