Live data from Hacker News

WhenFS: Calendar Is Now a File System

github.com

41–50 of 78 posts

Re: WhenFS: Calendar Is Now a File System

#41

That reminds me of a just for fun plugin I wrote for my (long dead) Dropbox-like file sync solution Syncany that would store the shared files as PNG images on Flickr. At the time, Flickr and Google Picasa (now Photos) gave you like 1T of image storage for free, so I thought it'd be a dope backend. It worked really really well actually... And it was nice to see your data as images. Though since the files were packed a…

Ah Syncany. Good times <3

Re: WhenFS: Calendar Is Now a File System

#42
post #30

Aw, that's not what I hoped it would be. An actual file-based calendar UI is a neat idea, where you can (for instance) echo into a file to create a calendar event on the command line.

There's a standard file type for this already: https://en.wikipedia.org/wiki/ICalendar It would be cool to see a filesystem layer present a tree of ICS files where editing one also updated your various API-based web calendars.

That's what I hoped this would be!

Re: WhenFS: Calendar Is Now a File System

#43

Earlier quoted context omitted.

the most amazing feature of the Google calendar web UI that has since been dropped was a way to schedule events with a human message - "30 meeting with Bob next Tuesday at 10", rather than clicking a bunch of buttons in a UI.

Not sure I follow, but how is this more convenient than pressing the UI buttons? Genuinely curious.

Maybe the UI was slow? Then this has the same advantage of speed that CLIs tend to have over graphical interfaces.

Re: WhenFS: Calendar Is Now a File System

#44
post #5

> Why Did You Do This? > I used this project as an opportunity to learn about Rust and FUSE file systems. I also think it's hilarious. > Visitors interested in the code should note that this is an irredeemably messy codebase—it's full of hacks, unidiomatic code, and wildly poor design decisions. > However, visitors should also note that that's okay. The best way to learn something new is to try it out for yourself—an…

As a college student trying to figure out where I wanted to go next (industry vs academia) I had an epiphany that there was intrinsic value in doing things. Even things that were neither novel (academia), profitable (industry), nor impactful (nonprofits). While my career has found a balance between impact and financial sustainability, I have a special place in my heart for projects that are otherwise unnecessary but…

But there is no greater pleasure than to finish something, deliver it, get users in front of it, and get feedback you never expected from either grumpy or happy users. I think it's way more rewarding to try to work for profit, because while money is nice, profit also means it's so useful someone is ready to give you credit for future work (money) for what you did.

Re: WhenFS: Calendar Is Now a File System

#45
post #30

Earlier quoted context omitted.

There's a standard file type for this already: https://en.wikipedia.org/wiki/ICalendar It would be cool to see a filesystem layer present a tree of ICS files where editing one also updated your various API-based web calendars.

That's what I hoped this would be!

Not sure I hoped, but from the title I expected.

I don't have more than 10 entries per week. Partly because I prefer real work over meetings, so I work at a place that does not have a lot of meetings. And once you don't have many, it's easier to remember other appointments, no need to use a calendar for everything. So even if this had been a useful mapping of calendar entries into a directory tree, I would not have felt an urge to use it.

Re: WhenFS: Calendar Is Now a File System

#46
post #8

Aw, that's not what I hoped it would be. An actual file-based calendar UI is a neat idea, where you can (for instance) echo into a file to create a calendar event on the command line.

Same here. I think that would be a terrific idea. $ cat /cal/2024/08/04/events

If I gzip my meetings, will they get shorter? If so, I'm on board.

Re: WhenFS: Calendar Is Now a File System

#47

Earlier quoted context omitted.

Not sure I follow, but how is this more convenient than pressing the UI buttons? Genuinely curious.

Maybe the UI was slow? Then this has the same advantage of speed that CLIs tend to have over graphical interfaces.

Well in a CLI you're not writing full English sentences. You don't say "make a directory called xyz in the current directory," you're saying "mkdir xyz". I'd rather just use a GUI than type out a full natural-language sentence.

Re: WhenFS: Calendar Is Now a File System

#48
post #8

Earlier quoted context omitted.

Same here. I think that would be a terrific idea. $ cat /cal/2024/08/04/events

If I gzip my meetings, will they get shorter? If so, I'm on board.

This is going to be my new, and probably overused phrase: "Can we gzip this meeting, I've shit to do"!

Re: WhenFS: Calendar Is Now a File System

#50
post #8

Aw, that's not what I hoped it would be. An actual file-based calendar UI is a neat idea, where you can (for instance) echo into a file to create a calendar event on the command line.

Same here. I think that would be a terrific idea. $ cat /cal/2024/08/04/events

So the question begs: how hard would this be to write.

Because I want it!

Post reply on HN