this post was submitted on 07 Jul 2023
118 points (100.0% liked)

Memmy - An iOS client for Lemmy

5074 readers
1 users here now

Download on the App Store

View on GitHub

Join the Discord

Code of Conduct

founded 1 year ago
MODERATORS
 

Hey all!

We got an approved TF version up earlier, should have another one today and that will be submitted to review. I anticipate it would be reviewed either overnight or sometime tomorrow (Apple does do reviews on the weekend thankfully)

I want to clear up two items real quick:

  1. There are edge cases where the app will ask you for access to the local network. This is related to an issue where if an image is linked that is, for some reason, on an internal network (i.e. 192.168.1.1), the app tries to access that to cache the image. Obviously it doesn't exist, but because it's trying to make a local network connection, iOS displays this warning.

For an example of this, please visit my profile in-app and hit posts. I've made a test post inside of /c/test that will trigger the issue. Feel free to just deny access, there's literally no reason to have this enabled.

  1. Just to clear up some questions about what the device ID is used for, there's a comment chain here about all of this in full detail.

TLDR is that it is used for push notifications, and because the auth token from Lemmy we need technically would let us also see your email address, we have to disclose this as being linked to your identity.

If you do not enable push notifications, there is zero information sent to us from the app. And if you do, the only time that traffic is sent from the app is when you enable or disable notifications.

If anyone has questions about anything else, please comment here and I will answer all of them.

Cheers guys!

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 23 points 1 year ago

Whoa there! Two new updates:

  1. It looks like Lemmy fixed the issue with subscriptions not showing up in 0.18.1. If you are still having issues, please ask your instance admins to upgrade to the latest version.

  2. Wow! I finally reproduced the language_not_allowed issue! I'll fix this in the next update! Seems like it happens even in the web UI which is super strange