💾 Archived View for gemlog.blue › users › sugarhiccup › 1614278176.gmi captured on 2023-03-20 at 20:17:04. Gemini links have been rewritten to link to archived content

View Raw

More Information

⬅️ Previous capture (2021-12-04)

-=-=-=-=-=-=-

I'm so pleased to tell you guys I have finally started work on one of my side projects - arc (working title). Send me name suggestions!

what is arc?

Ok, I'll be as clear as possible. arc grew out of my own needs to organize my document files.

I read a lot. Like insane a lot. And 90% of that is in ebook or PDF format so naturally I have this "library" folder sitting on my disk. The problem is I am so terribly obsessed with documentation of everything I do. It's so grave that I find it very uneasy if I'm not documenting my life. Be it the books I read, the movies I watched, the new things I did, my thoughts, emotions, conversation, interesting event, everything must be recorded. It makes me feel more "in control". I wonder if you guys ever feel this way?

Now the trouble with such a big pile of data (~400 documents the last time I checked) is that there is NO organization. Yuck.

Of course, you'd tell me, "dumbo, put them in directories". Fair enough, but how to decide the classification? My book taste is quite diverse and it won't be late when I'll add something in my library that'll either not fit or make it imperative to restructure the entire thing which I so "meticulously" designed. Needlessly to say, this is a poor idea.

What is needed is a flexible sub file system. My idea is if it's the directory structure that is a problem so be it. What if we can restructure the entire directory programmatically?

And that is basically the essence of arc - the Archive program.

Progress

I just started work on it. It barely serves the basic functionality that is restructuring but I'm on my way. Besides, there ARE A TON of design choices that I have to make and resolve.

These design choices are not trivial as any good software engineer will tell you and in fact decides how extensible and maintainable the application will be in the future. (For eg: see Linus Torvalds' git)

I added .arcignore feature and am thinking of tagging (Tags are basically strings that determine how the restructuring will occur).

Future plans

There are, of course, tons of things I'd like arc to have but alas, this shrewd time. Besides I have exams coming up (Just argh).

In the very distant future, tbh, I'd like to see arc evolve into a reliable backend service serving me via a number of clients (I prefer wearables) all remote synced.

Source Code

Stick tight guys! As soon as I consider arc to be "showable", I'll publish the repo link.