This has become my personal motto lately.
I’d prefer the more normal use of drives and folders. New terminology is just a hurdle, when there’s such little difference.
Additional metadata is also created for each file, if locally available: original_created_time, original_modified_time, and unix_mode_bits. The aim of this metadata is to enable backup/restore that preserves local file metadata.
Can I check that metadata will be held distinct from the file itself?.. I wonder one of the great features of SAFE is that a file, has a location - that is one xor. The meta data, such as date stamps and filename, are distinct from the content and then should perhaps be separate… aside from perhaps that storage in that way will be reduced too for being the same identical file. The alt is a date stamp affects the sense of its being the same file - if someone saves a file from the net, it might have a local date stamp but is not a different file.
Can I check that metadata will be held distinct from the file itself?
It is. The file will be the immutable data. The metadata is inside the FilesContainer
which will be this RDF data construct that links to our immutable data.
(I say “will be” as it’s pseudo rdf at the mo)
it’s pseudo rdf at the mo
I’m a fan of the idea rather than the reality of rdf… always seemed a bit bulky… but the data is valuable… having datapoints that are the same concept would be fine.
Small and very pedantic point but why FilesContainers and not FileContainers?
no need for file to be plural. Not a biggie but I do a double-take every time I use it.
I totally agree. In OP FileContainer is used 5 times and FilesContainer twice. I am not a native English speaker but for example “file list” sounds better to me than “files list”.
My opinion is that people at Maidsafe try very hard to use the official term (FilesContainer) but they don’t succeed at that because they can’t help using the more intuitive term (FileContainer), even in an official Dev Update.
Maybe, we shouldn’t fight natural spelling and we should rename the term instead.
Honestly, I wouldn’t consider that there’s an “official” version. One was used in the rfc as it seemed correct to me when I wrote it.
It’s not really been considered or scrutinised in any detail until now AFAIK.
The above agrees with you and I have nothing against that idea. Though both seem like they can be correct to me, tbh.
If folk are feeling it’s wrong/consfusing and want to update the rfc then PRs are very welcome
If folk are feeling it’s wrong/consfusing
Hmm, consfusing or confusing?
Haha. The former of course !
I thinks I am beginsning to understands.
If you understand English then you don’t understand English. I for one certainly don’t
I’m an English major and I don’t either.
cough, its tough , but if you are thorough and think it through, the rough edges of the variations of the prounciations of the -ough- sound will make you beat your boughm with boughs of holly, take a bath in youghurt and through youghrself oundr a boughs.
And we expect folk to learn this language?
I we are just living in a game simulation it must be a cruel joke by the master, having the internet invented by an Englishman.
Yes indeed, they have a lot to answer for.
I experienced some difficulties when trying to build a FUSE drive on the old NFS API which was good but had some holes in it which were hard to fill because file APIs are far more complicated that I imagined
It won’t solve these problems, but: Linux 5.8 To See Faster FUSE Write Performance
Thank you for the heavy work team MaidSafe! You are not PERFECT, but you are FIT!
I add the translation into Bulgarian in the first post
SAFE Network новини - 14.5.2020
SAFE Network новини - 14.5.2020 Накратко Ето някои от основните неща тази седмица: След някои подобрения пуснахме още един вътрешен тест-скрипт с Трезори от вкъщи и досега изглежда добре. Пуснахме нова версия на пакета MaidSafe.SafeApp NuGet....