| 1 |
chrome://messenger/locale/messengercompose/composeMsgs.properties: |
| 2 |
> On Sat, 28 Nov 2009 22:29:32 -0600 |
| 3 |
> Dale<rdalek1967@×××××.com> wrote: |
| 4 |
> |
| 5 |
> |
| 6 |
>> After all, how many people see the source code for Seamonkey, |
| 7 |
>> thousands, maybe million or more? I don't think that many people can |
| 8 |
>> keep a secret like that. |
| 9 |
>> |
| 10 |
> While anyone who wants to *can* look at it, probably only a few dozen |
| 11 |
> actually look at very much of it. But every bit of new code that's |
| 12 |
> checked in is reviewed by someone who's been working with Mozilla |
| 13 |
> stuff for a long while and has earned a reputation as a trusted |
| 14 |
> contributor. |
| 15 |
> |
| 16 |
> |
| 17 |
|
| 18 |
Which is why Lastpass needs to let someone outside see their code, sort |
| 19 |
of earn the peoples trust. Even tho Seamonkey 2 has a few issues right |
| 20 |
now, I still trust it. I am not worried that they are logging my |
| 21 |
keystrokes or anything like that. Lastpass, as some have pointed out, |
| 22 |
could be doing just that. We don't *really* know what they are doing |
| 23 |
other than what they claim. |
| 24 |
|
| 25 |
I like the idea behind it but lack the trust, sort of like Alan I |
| 26 |
guess. I wanted to use it but was not sure it was safe hence the thread |
| 27 |
about it. |
| 28 |
|
| 29 |
Dale |
| 30 |
|
| 31 |
:-) :-) |
Archives