With completely wireless earbuds, the rule is: when the battery fails, they have to be disposed of. Not so with the Fairbuds, that allow you to replace batteries in just a few seconds. Combined with a repairable design, the earbuds should therefore have an extremely long lifetime.
I mean if you’re using something like Firebase on Android, the network calls get bundled with Google Play Services and you have no idea what that’s sending up
Basically your device (for example your phone) needs to know the ip adress of any service it wants to connect to. As you may know these services usually use addresses like Lemmy.org or google.com or whatever.
To know what IP adres is behind these addresses, you device needs to ask a dns server, in a local network (like your own WiFi) this is usually your router, but you can set it to any arbitrary device you want. This way you can see what addresses are being asked for by your device.
So if the app want to send data to some server, it usually needs to resolve the adress first. And you can see that.
If a device makes an encrypted connection to a server the device makers own, there’s nothing further you can gleam from studying the DNS lookups. They can route traffic through the first server, and they can resolve any IPs through the first server. And since you insist the person you’re replying to doesn’t know what DNS is because they said it’s encrypted, I feel you might also not know that DNS can be encrypted. In that case, the network owner can see that a device makes a connection to the nameserver, but they can’t see which addresses the nameserver was asked to resolve. And similarly, the device can refuse a connection to the wrong nameserver.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: [email protected]
This is the official technology community of Lemmy.ml for all news related to creation and use of technology, and to facilitate civil, meaningful discussion around it.
Ask in DM before posting product reviews or ads. All such posts otherwise are subject to removal.
Rules:
1: All Lemmy rules apply
2: Do not post low effort posts
3: NEVER post naziped*gore stuff
4: Always post article URLs or their archived version URLs as sources, NOT screenshots. Help the blind users.
5: personal rants of Big Tech CEOs like Elon Musk are unwelcome (does not include posts about their companies affecting wide range of people)
6: no advertisement posts unless verified as legitimate and non-exploitative/non-consumerist
7: crypto related posts, unless essential, are disallowed
Imo its fine if they open source it when they decide to end support. The fact that app has a pristine privacy record is good enough
Is it? Closed source means it’s probably listening and recording and selling
I’m a fan of open source, but c’mon. There are reasons not yet to open source a product.
You can just see which DNS calls it’s doing with any DNS overwriter.
I mean if you’re using something like Firebase on Android, the network calls get bundled with Google Play Services and you have no idea what that’s sending up
But if you have a DNS intercepter/redirect like RethinkDNS or DDG, it should show which queries are coming from which profile
Nah it’s encrypted
You don’t know what DNS is, do you?
Basically your device (for example your phone) needs to know the ip adress of any service it wants to connect to. As you may know these services usually use addresses like Lemmy.org or google.com or whatever.
To know what IP adres is behind these addresses, you device needs to ask a dns server, in a local network (like your own WiFi) this is usually your router, but you can set it to any arbitrary device you want. This way you can see what addresses are being asked for by your device.
So if the app want to send data to some server, it usually needs to resolve the adress first. And you can see that.
Data 'n stealing
If a device makes an encrypted connection to a server the device makers own, there’s nothing further you can gleam from studying the DNS lookups. They can route traffic through the first server, and they can resolve any IPs through the first server. And since you insist the person you’re replying to doesn’t know what DNS is because they said it’s encrypted, I feel you might also not know that DNS can be encrypted. In that case, the network owner can see that a device makes a connection to the nameserver, but they can’t see which addresses the nameserver was asked to resolve. And similarly, the device can refuse a connection to the wrong nameserver.