- Joined
- Sep 20, 2018
- Messages
- 6,985
Being careful is not the right answer in your book then, hey?Thank you for your valuable input.
Being careful is not the right answer in your book then, hey?Thank you for your valuable input.
Most likely not, but is there any guaranty, liability? Nope.If there was something in the code for the viewer and if it was doing things BAD, LL will ban it, firestorm works with the lab, the code is vetted by lots of people. it's not stealing anything or doing anything.
It could easily happen with the LL viewer too. plus the LL viewer currently horrible, dump chui and people like me go back to using it. but if they want to keep that horrible shitty interface, then I guess I stick with the viewer that works and seems to be popular.Most likely not, but is there any guaranty, liability? Nope.
LL would not notice until damage would have been done.
I don't give out payment info (even if it is only linden dollars) and passwords to strangers.
One of the first rules of the good old Interwebs.
Edit to add: Same goes for all third party viewers of course.
I'm not on a crusade against the Firestorm viewer or so.
Nope. Just because many people are looking at something does not exactly mean that many people are auditing something for security breaches, it just increases the possibility somewhat that somebody might stumble upon it. And even if there is something fishy in that does not mean that it will be easily spotted. The viewer is being written in C++, and you can obfuscate a lot if you want to in C++.If there was something in the code for the viewer and if it was doing things BAD, LL will ban it, firestorm works with the lab, the code is vetted by lots of people. it's not stealing anything or doing anything.
basically nothing new... "please use the Jira" translates to: "If you don't bother to create yet another useless social media account just to tell us about bugs they can't be important enough for us to care."FireStorm also sent me a very strong signal to the effect that they do not actually WANT bug reports.
I have a solution: No third party viewers.basically nothing new... "please use the Jira" translates to: "If you don't bother to create yet another useless social media account just to tell us about bugs they can't be important enough for us to care."
Firestorm people seem quite confused when you tell them you don't bother to report bugs due to the hassle involved... I sometimes wonder what kind of ivory tower viewer devs live in (HINT: behavioural patterns inherited from customers of agile programming solutions do not fly well with run of the mill end consumers)

Are there more LL viewers out there?It could easily happen with the LL viewer too. plus the LL viewer currently horrible, dump chui and people like me go back to using it. but if they want to keep that horrible shitty interface, then I guess I stick with the viewer that works and seems to be popular.
...as if the Lab ever was an example for best practice...Linden Lab expected you to use the Jira too, and when I was really active there they were really quite responsive to reports: that wasn't where the bottleneck was. That was in management.
Oh I don't have a problem with having to have an account on their jira, and not with having to fill in all those details.basically nothing new... "please use the Jira" translates to: "If you don't bother to create yet another useless social media account just to tell us about bugs they can't be important enough for us to care."
Firestorm people seem quite confused when you tell them you don't bother to report bugs due to the hassle involved... I sometimes wonder what kind of ivory tower viewer devs live in (HINT: behavioural patterns inherited from customers of agile programming solutions do not fly well with run of the mill end consumers)
Where did I say that? My point is even they didn't manage to screw up Jira, so if there's a problem with Firestorm team it's probably not because of Jira....as if the Lab ever was an example for best practice...