Deomid Ryabkov

@sjanc :wave:

@annevk yeah, i'm not affiliated with Google. HTTP digest authentication is still useful and being useful on small footprint devices as an easy way of securing access to a web...

with plain basic or general cookie auth network attacker gains persistence: they can intercept the credentials and maintain access even after they no longer have access to network traffic. so...

safari support is probably the last thing preventing it from being widely used and improving the security of internal web interfaces. it's almost trivial in terms of implementation (speaking from...

littlefs-fuse leaves `struct lfs_info` uninited (in [both](https://github.com/littlefs-project/littlefs-fuse/blob/73d755ed856d4a5d901fbe3b5ad1647951e1b850/lfs_fuse.c#L223) [cases](https://github.com/littlefs-project/littlefs-fuse/blob/73d755ed856d4a5d901fbe3b5ad1647951e1b850/lfs_fuse.c#L234)) and this results in weird numbers in ls -l output - that's how i found it.

i think the general understanding is that if you're passing a struct to be filled, the callee can fill it. i'd just `memset()` it to 0 right there, in lfs_stat()...

i'm a bit late to the party with this v3 thing, just read the roadmap - pretty excited about more efficient random writes! what about appends though? are they covered...

let me add another reason why littlefs is cool: fixed i/o size and offsets. this makes it extremely easy to implement block device-level encryption, and has come really handy: readily...

i have a project for which we are going with littlefs on linux via littlefs-fuse (fs itself is still relatively small), so i doodled a bit and have something that...

My WIP branch is here: https://github.com/rojer/littlefs-fuse/tree/shelly I also found it useful to have `lfs_file_get/setattr()` - to be able to update utimes on read/write via `lfs_file_t`, without a path lookup.