61–70 of 319 posts
>> After you agree to our updated Terms of Service and Privacy Policy, you will have an additional 30 days to make this choice by going to Settings > Account > Share my account info in the app. If you do not want your account information shared with Facebook to improve your Facebook ads and products experiences, you can uncheck the box or toggle the control.
Or... you know... just use something like Telegram that isn't owned by Facebook. Their data-sharing / privacy policy is pretty simple https://telegram.org/privacy 1. Sharing data We never share your data with anyone. No.
Who keeps the lights on? The app is free, i have never seen any ads.
At the end of the day, all these guys get enough users and then the users are just too tied to the platform to make an easy move.
The 'share information with Facebook' nugget is hidden behind a toggle at the bottom of the screen, and will be guaranteed to be missed by the 99% of users who just want to talk to their friends.
Then, once you've agreed to the terms and conditions, you've got a completely arbitrary 30 days to read an online article which tells you what you've signed up for before WhatsApp is irrevocably sharing your data with Facebook.
You can build an incredibly accurate picture of people's lives from metadata alone - WhatsApp know it and Facebook know it.
Not only that - when WhatsApp start building out these 'brand' relationships which will look a lot like helpful information at first - you'll be loading your data into that brand's custom FB audience too. And you won't have an opt out because, y'know, reasons.
This is very obviously not the WhatsApp that promised not to fuck with its users when Facebook bought it out.
It's kind of pointless, Facebook owns Whatsapp so they have all that info anyway. 'The Facebook family of companies will still receive and use this information for other purposes such as improving infrastructure and delivery systems, understanding how our services or theirs are used, securing systems, and fighting spam, abuse, or infringement activities.'
Device & app history
retrieve running apps
Identity
find accounts on the device
add or remove accounts
read your own contact card
Calendar
read calendar events plus confidential information
add or modify calendar events and send email to guests without owners' knowledge
Contacts
find accounts on the device
read your contacts
modify your contacts
Location
approximate location (network-based)
precise location (GPS and network-based)
SMS
read your text messages (SMS or MMS)
Phone
directly call phone numbers
read call log
read phone status and identity
write call log
Photos/Media/Files
read the contents of your USB storage
modify or delete the contents of your USB storage
Storage
read the contents of your USB storage
modify or delete the contents of your USB storage
Camera
take pictures and videos
Microphone
record audio
Wi-Fi connection information
view Wi-Fi connections
Device ID & call information
read phone status and identity
Other
download files without notification
adjust your wallpaper size
receive data from Internet
view network connections
create accounts and set passwords
read battery statistics
send sticky broadcast
change network connectivity
connect and disconnect from Wi-Fi
expand/collapse status bar
full network access
change your audio settings
read sync settings
run at startup
reorder running apps
set wallpaper
draw over other apps
control vibration
prevent device from sleeping
toggle sync on and off
install shortcuts
read Google service configurationMan, remember the late 90s and early 2000s, when the IM scene was a mess of incompatible networks like ICQ and AIM and MSN Messenger, and people were like "fuck this" and came up with this protocol that was interoperable with all the others through gateways and also it was extendable, and we could all be happy together?... /grump The worst part is that WhatsApp is actually based on Jabber >:(
And yes, I absolutely realize that the protocol had flaws, was overly verbose, the base spec required a continuous connection which is hard/impossible on mobile networks, its extensibility meant that clients could end up with little common compatibility, etc etc... But still.
Earlier quoted context omitted.
If only more people used Telegram.. I love it, but only a couple of friends use it.
There was a serious FUD campaign started by one of the developers of now competing app Signal a few years ago. Now if you mention Telegram on Reddit you're immediately bombed with "OMG TELEGRAM CRYPTO IS BROKEN!" even though 0 people on earth have ever provably decrypted a Telegram message. They even offered a $300K bounty where you could act as the server... no takers.
Earlier quoted context omitted.
I recently started looking into XMPP again a few days ago. I have a few ideas for projects built on top thereof. Can anybody recommend XMPP servers? I know duckduckgo has an XMPP service up and running, but I can't seem to find any relevant API documentation. All I found was this [0], which doesn't go into details about encryption settings and isn't very useful for programmatic interaction. [0] https://duck.co/blog/p…
Conversations.im has made great progress in making XMPP usable on mobile devices, although its services don't seem ready for public adoption quite yet. There are very few XMPP servers which support the XEPs Conversations does so while federation is theoretically possible, it is not yet a reality. https://account.conversations.im/
(Maybe I should look into running my own server...)
This is an incredibly ugly dark pattern. The 'share information with Facebook' nugget is hidden behind a toggle at the bottom of the screen, and will be guaranteed to be missed by the 99% of users who just want to talk to their friends. Then, once you've agreed to the terms and conditions, you've got a completely arbitrary 30 days to read an online article which tells you what you've signed up for before WhatsApp is…
I suspect that you'd be familiar with LinkedIn dark patterns [0] too.
[0] https://medium.com/@danrschlosser/linkedin-dark-patterns-3ae...
Man, remember the late 90s and early 2000s, when the IM scene was a mess of incompatible networks like ICQ and AIM and MSN Messenger, and people were like "fuck this" and came up with this protocol that was interoperable with all the others through gateways and also it was extendable, and we could all be happy together?... /grump The worst part is that WhatsApp is actually based on Jabber >:(
I recently started looking into XMPP again a few days ago. I have a few ideas for projects built on top thereof. Can anybody recommend XMPP servers? I know duckduckgo has an XMPP service up and running, but I can't seem to find any relevant API documentation. All I found was this [0], which doesn't go into details about encryption settings and isn't very useful for programmatic interaction. [0] https://duck.co/blog/p…
Earlier quoted context omitted.
I recently started looking into XMPP again a few days ago. I have a few ideas for projects built on top thereof. Can anybody recommend XMPP servers? I know duckduckgo has an XMPP service up and running, but I can't seem to find any relevant API documentation. All I found was this [0], which doesn't go into details about encryption settings and isn't very useful for programmatic interaction. [0] https://duck.co/blog/p…
Conversations.im has made great progress in making XMPP usable on mobile devices, although its services don't seem ready for public adoption quite yet. There are very few XMPP servers which support the XEPs Conversations does so while federation is theoretically possible, it is not yet a reality. https://account.conversations.im/