[Dev] Mozilla Social
André Silva
emulatorman at riseup.net
Thu Sep 11 12:16:05 GMT 2014
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 09/11/2014 05:08 AM, hellekin wrote:
> On 09/11/2014 04:08 AM, André Silva wrote:
>> On 08/28/2014 06:21 AM, André Silva wrote:
>>> On 08/21/2014 01:00 PM, hellekin wrote:
>>>> Hola,
>
>>>> in icedove non-prism there's a configuration that whitelists
>>>> Mozilla Social for some "nice" services, like, ahem, MSN.
>>>> See screenshot.
>
>>>> http://i.imgur.com/SaoImOX.png
>
>>>> == hk
>
>
>>> ok, i will check to fix and build a new revision of it and let
>>> you know when it's ready
>
>
>> Social API support has been removed on iceweasel
>
> *** Social API is OK. What is not OK, is the default using
> Facebook.
>
>> Otherwise, geolocation backend support has been removed on
>> icedove [2] like iceweasel [3][4]
>
> *** Again, geolocation CAN BE OK, if you know what you're doing.
> I don't think removing the functionality is good at all. The
> technology is not bad, its abuse is.
>
>
>> [0]:https://lukeshu.com/git/mirror/parabola/abslibre.git/commit/?id=1c222df4c718aa049f55cc10a6bdf3357ac3a919
>
>>
>> [1]:https://lukeshu.com/git/mirror/parabola/abslibre.git/commit/?id=400b478305876606a767ac469964c171f9948ed9
>
>>
> *** Instead of removing the Preferences, why not empty them, and
> for the booleans, put them to false? That way, people can choose
> to enable them. Otherwise, how does the browser react when it
> finds empty preferences and a site tries to call that API? It's
> potentially more complicated than just removing the prefs, and if
> not now, in later releases. What do you think?
>
>> [2]:https://lukeshu.com/git/mirror/parabola/abslibre.git/commit/libre/icedove?id=50eb7157102ee472da3c0d0c1497da61d52aab11
>>
>>
[3]:https://lukeshu.com/git/mirror/parabola/abslibre.git/commit/libre/iceweasel?id=ce2ed54bd854694da898fd31a54fff556229d7e8
>> [4]:https://lukeshu.com/git/mirror/parabola/abslibre.git/commit/libre/iceweasel?id=8f7709f5b196d988141d085572661b6944ad8267
>
>>
> *** Ditto. "geo.enable = false" looks safer than nothing at all.
>
> Thank you for tackling that issue!
>
> == hk
ok, then i will revert the changes and keep empty them and booleans in
false, but i prefer put it on vendor.js to keep it more practical for us.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBAgAGBQJUEZKEAAoJEOaXR1L5cERW3sgQANAc2fOndRlb8zeUjjFdzgHE
Fj7KYWP1gvOaUjDYmGifUHJqY2wMoyYWHij8204F/58WhxxweCXmPTvgp0Am/+QM
7oq16mth4p2zcHQMFOvHD63STM0gfznfqaY/Aj/dh5vZZQ0qpohyeZZA1lToYtv0
vGdSaubQFFx8KLf6ka0Aklxym9JgO9RHoCBOYOBVOijKa410L1BHzDQtt5VEmZGX
yi09vNNeIM7r3pId5D1FQBaLNKglOkaQ3+m9sC0lemCoULoDYordoqWjXmm1DCTv
SXTgSfuDWyMP/LiEpOD8H9tETzCHdbVUv3YnbhvvfsjQhj5gpg8AGLBFF6+e2JXx
acUnX4hKCbJouYFl0nLzoxYXZ2Dfy3KtCnOzMXrtWI5R9YHP+o931az+EkC/DN9e
+HZBbY2z6NWZHNDbTkm2Ky46Pj0+gvbRO+7qw6E4o+FSrhZX8K2/yOWCgnK8L8r4
+yWuByiR0009wqlMTasJRvNaxn0TZeBcpgdn4GgRGoIyEqBrxxTAqrllqSwI5fFW
oTH2SLVf70ncaG9chzgwhqyQNevTYiNPRd/1+51g/qXylz0TV3BdSvgfVk4PG+IW
310YK5287A54NF8lMYu+5maT7h/ILHaodOF4aNazSZyDv+PXqyNTwo4EXBFn45vG
jwvy1SjaZ8yBi1E+tFJp
=gTQu
-----END PGP SIGNATURE-----
More information about the Dev
mailing list