Anon 12/10/2023 (Sun) 08:28 No.9014 del
Don't read this line if you don't wanna read drama-related crap. -> I think someone called me a script kiddie in the past. I'll call him an idiot outsider or someone who wasn't paying attention. A scriptkiddie is an arrogant person, typically associated with hacking, who knows little about programming and mainly uses other people's scripts. I'm sorta a technology enthusiast. I was never arrogant/showy/trying-to-look-cool about my endeavors. I was just imparting the information related to what I was doing, for various reasons, such as trying to work through a problem. I use other people's scripts if I needed to, but I think I mainly made my own code and stuff to do what I wanted to do. Another reason that that someone got the impression of "script kiddie" from me: the code I posted is fairly simple, and sometimes it is obviously in an unfinished state. Code that's simple is great, especially if it works well. Simple code means that basically anyone can understand what's happening (including myself in the future) even without comments. I did progressively make some of my code more complex, but that was only on the basis that it had to be more complex to do all that I wanted it to do. Oh, and complex code is not necessarily better. Unfinished code that "just works" is fine, updates to it might break it: same idea of version control systems like git. VCSes can also simply record what the code looked like at one point. One of the reasons I shared code is because it was useful to me (e.g., refering back to it), and it could possibly be useful to others though that wasn't my direct intention usually. It wasn't like I was trying to impress anyone with whatever I coded/programmed; I did make one or more things which I think could be useful to others and that anyone could easily use and that could be considered good/great code. Why am I even posting this? If you feel like reading this is a waste of time, blame whoever insulted me a bit in that post in /pag/; I kinda felt like defending myself.

>>8989
I made a thing to title a file and store it in your own IPFS repo. It also saves file timestamps and hashes. Be aware that it runs rm to delete a file and a folder.

Top level = CID
Second level = folder-name-as-title directory + datetime file
Third level = file titled by parent folder
Indexed by = replace "/z8/b/ipfs/cid.txt" with a path to whatever text file (guess I should have done something like indx=/z8/b/ipfs/cid.txt then $indx for the multiple references to it).

Example:
Top level: /ipfs/QmWFu48TY7Jd3zy4VtYku7V3qwg1bB4vTbQGQiA2ZyhktG/
Second level: /ipfs/QmWFu48TY7Jd3zy4VtYku7V3qwg1bB4vTbQGQiA2ZyhktG/Happy_Pinkie_Pie_and_Rainbow_Dash_after_shopping/
Second level: /ipfs/QmWFu48TY7Jd3zy4VtYku7V3qwg1bB4vTbQGQiA2ZyhktG/datetime.txt
Third level: /ipfs/QmWFu48TY7Jd3zy4VtYku7V3qwg1bB4vTbQGQiA2ZyhktG/Happy_Pinkie_Pie_and_Rainbow_Dash_after_shopping/S1E05PinkieDash.jpg