[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: Moving Baloo forward
From:       Albert Astals Cid <aacid () kde ! org>
Date:       2014-01-27 19:08:41
Message-ID: 5239490.UCHjT2jjVt () xps
[Download RAW message or body]

El Divendres, 24 de gener de 2014, a les 15:59:12, Vadim Zhukov va escriure:
> 2014/1/24 Sebastian Kügler <sebas@kde.org>:
> > On Friday, January 24, 2014 01:24:54 Vadim Zhukov wrote:
> >> in the best case you'll have two totally different codepaths
> >> that you'll have to manage.
> > 
> > This should be "worst case", I think. In the best case, there's xattr
> > support, meaning another code path isn't needed.
> 
> It's doubtful at least whether xattr support is a good thing, because
> it's too easily gets misused: for example, there were viruses on
> Windows which effectively hidden themselves in NTFS streams. And there
> are personal data leaking issues I've pointed out earlier. But the
> question "xarttrs: to be or not to be everywhere" is totally offtopic,
> because it's what OS developers should decide.
> 
> The worst case is Nepomuk becoming a crashy resource hog again, which
> will turn in cutting it off or disabling by default in most OSes.

This last sentence doesn't help at all to get you treated seriously.

Cheers,
  Albert

> 
> --
>   WBR,
>   Vadim Zhukov

[prev in list] [next in list] [prev in thread] [next in thread]