Earlier quoted context omitted.
Yeah, IMO extended metadata attributes are fine for caching data that can be recovered via other means but generally violate the principal of least surprise. For them to be successful a standardized transparent container format or something would be necessary, but at that point the FS abstraction is leaking.
What about using the file name itself as the metadata storage?
Files are the interface humans and agents interact with
141–144 of 144 posts
Re: Files are the interface humans and agents interact with
#142Earlier quoted context omitted.
Yeah, IMO extended metadata attributes are fine for caching data that can be recovered via other means but generally violate the principal of least surprise. For them to be successful a standardized transparent container format or something would be necessary, but at that point the FS abstraction is leaking.
What about using the file name itself as the metadata storage?
https://stackoverflow.com/a/68284922
Here is my source file for it. It was so long ago I don’t recall all the details but you can retrieve this information using exif commands.
https://github.com/jmathai/elodie/blob/master/configs/ExifTo...
Re: Files are the interface humans and agents interact with
#143Files are a fundamental freedom because they enable users to have custody of data, thus enabling ultimate sovereignty of confidentiality, integrity, and availability. We should recognize files as an essential pillar of digital liberty, on par with FOSS licensing.