Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

WhenFS: Calendar Is Now a File System

github.com

Post reply on HN
Print view View original

71–78 of 78 posts

Re: WhenFS: Calendar Is Now a File System

#71

Post by darby_nine »

01HNNWZ0MV43FF wrote: post #70
darby_nine wrote: post #66

Earlier quoted context omitted.

I seriously doubt this kind of stuff has ever messed with their bottom line. I think they just really resent users trying to do more with their service than they intended.

If they didn't crack down, people would start pushing it harder, until some company relied on this for cloud storage

I think this is a ridiculous sentiment, but I understand why it's so common. Proactively trying to head-off any and all possible problems before they cause measurable impact is not a great way to manage a product.

Maybe they did see impact, but I still would have rewarded non-abusive loyal customers for using the product—maybe restrict access based on resource-usage rather than hitting people with TOS violations. Instead this attitude (plus their generally very poor track record at supporting and improving their own products) has caused me to abandon all google products outside of work.

Re: WhenFS: Calendar Is Now a File System

#72

Post by j45 »

mbreese wrote: 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…

Right on. Making a mess and learning to clean it up, and prevent it a little more each time is the way.

Re: WhenFS: Calendar Is Now a File System

#74

Post by exe34 »

darby_nine wrote: post #71
01HNNWZ0MV43FF wrote: post #70

Earlier quoted context omitted.

If they didn't crack down, people would start pushing it harder, until some company relied on this for cloud storage

I think this is a ridiculous sentiment, but I understand why it's so common. Proactively trying to head-off any and all possible problems before they cause measurable impact is not a great way to manage a product. Maybe they did see impact, but I still would have rewarded non-abusive loyal customers for using the product—maybe restrict access based on resource-usage rather than hitting people with TOS violations. Ins…

exponentially slower access and start corrupting them by flipping cases.

Re: WhenFS: Calendar Is Now a File System

#78

Post by dmos62 »

dudus wrote: post #15
dmos62 wrote: post #14

Earlier quoted context omitted.

I was thinking about this and came to the conclusion that I'd want to define some events per date, like you illustrated (`"12:30 dentist" > /cal/2024/08/04`), but others I'd like to define per event, like `2024-08-23 12:30 > /cal/massage`, which seemed messy. I didn't really resolve this question for myself.

Why not enable both modes? It's a virtual filesystem after all. You don't need a single path per event.

I wasn't considering making it a virtual filesystem. My main goal was something that's editable with any text editor and syncable with SyncThing. I guess denormalization doesn't necessarily mean that these requirements are not met.
Post reply on HN