![]() Yes, doubtless others would be able to do that and alert us to any wrongdoing, but since I trust Kitty and her colleagues, I don't need that reassurance.Īs to giving totally unknown people the ability to do whatever they want to with my computer, I - like most people, I think - use a service (Malwarebytes in my case) that alerts me to any potentially suspicious behaviour by a programme and asks me what I want to do about it. If the source code was available to me I wouldn't have time to read and study it, and I wouldn't understand it even if I did. I have no hesitation in using Catznip because I know Kitty and I trust her. But then, after Emerald, I realised that hadn't stopped their rogue devs from getting up to mischief, since viewer source code is even less widely-read, and certainly even less comprehensible to most of us, than are the terms and conditions of click-through software agreements. ![]() I used, thoughtlessly, to repeat the mantra that open source means it's safe. Wasn't Emerald open source? Nevertheless, no one noticed the problems until one of the own devs (who certainly had access to the code and repositories and, more importantly, understood the code he was reading) became suspicious about the behaviour of some of his colleagues and started to dig deeper into the code. Using a 3rd party viewer is giving totally unknown people (strangers) the ability to do whatever they want with your computer - which is what one of the emerald people actually did. I meant the fact that a 3rd party viewer (emerald) was used unscrupulously by one of the developers could be the reason why some people might be wary of any 3rd party viewer that doesn't reveal the source code. I didn't mean that Catznip has/had anything to do with emerald. It's been long enough that I do not remember which library I had to install through the console. If you're at all curious, see Firestorm's support pages for Linux and select the distribution closest to the one you use or know your developer used. This is compounded by needing to use the terminal to install a few of them (something I personally discovered after verifying most were installed through the Software Manager), something not many at all are comfortable doing. The problem is - unfortunately - that not all client developers use the same libraries or are even aware you need to use certain ones. ![]() Just pointing out an inaccuracy: Voice works on Linux, as long as a few libraries - some a bit older - are on your system. There is almost no possibility of Linux voice support and nothing we can do about it. if it's even possible), and then submit the code changes back to LL. This situation will not improve tills someone manages to build and run the viewer stand alone (using system libs. Use firestorm or run the windows client with wine (the only way to get voice working). Linux SL development is in the long grass and there are no updates coming from LL or vivox, to cut a very long story short.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |