Skip Navigation
InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)RA
Posts
0
Comments
12
Joined
1 yr. ago
  • Yea, duplicate IP addresses lead to some funny business. Toss a coin to see if a network packet will arrive basically.

    The solution is to adjust the DHCP range or use static DHCP on the router. The latter just means that the router will assign the same IP to the specified computer every time.

  • That is evident. The bigger issue is ergonomics. My hand will cramp up within minutes of using that piece of shit. While the charging thing is stupid, it is only a minor inconvenience that is blown out of proportion. The ergonomics aspect is the major issue IMO.

  • You need some .well-known url redirects for proper iOS support. Ironically, Nextcloud describes this quite well. You should be able to adapt this to your setup: https://help.nextcloud.com/t/properly-resolving-well-known-caldav-or-well-known-carddav/82617

    I’m not sure if this is your exact problem but it’s worth investigating. I had to fix this before iOS clients started syncing with NextCloud. Desktop and android clients would sync fine.

  • AirTags actually use an encryption scheme. The AirTag will broadcast a public key. The private key is stored in your iPhone and iCloud keyring. Once your phone fetches the location reports from apple's online service it can decrypt the actual location of the AirTag.

  • It's not that as bad as it seems. The way it is set up is actually very privacy-minded with the use of cryptography. I would encourage you to read more about this.

    The primary safety concern is stalking. For example when a stalker puts an AirTag on your belongings or vehicle. iPhones can detect unknown airtags moving with you. Android devices should gain this capability in the future.