I have no specific data. But I consider polling in the background to be abuse, especially for a free service hosted by volunteers. Once lemmy implements actual push (which is scheduled soon!) I will implement.

Ok but as a rule use voyagers share as image feature next time (/¯ ಠ_ಠ)/¯

You should give the issue an upvote, right now it has zero upvotes. :)

As for why it isn’t merged in yet, is because it is a PR for a user submitted issue that hasn’t been fully triaged yet. For example, should avatars also be added to profile, autocomplete, post details, account selector etc, should avatars be animated, or frozen etc

I do need to revisit that PR and issue though, there have just been other priorities (again, upvote the issue if you want it)

You can’t currently. Voyager adopts Apollo’s DNA which is to focus on user content, rather than how cool your profile is. ;)

That being said, there will be a setting to enable at some point in the future. See: https://github.com/aeharding/voyager/issues/567

It’s planned via https://github.com/LemmyNet/lemmy/issues/2631 once lemmy supports.

Without that, there’s two ways to do this with major drawbacks:

• Background tasks (android supported-ish with iOS support only with app open): Apps like Thunder are doing partial implementations by essentially polling the lemmy server in the background. I don’t think this is very neighborly because it puts a strain on Lemmy instances with the polling per account every 15 mins. It also consumes more battery. And is not consistent depending on Android device manufacturer.
• Storing JWTs on a server: Some apps do this, but this is a nonstarter for me due to security/liability reasons

So IDK. Right now I feel pressure to do this because other apps support but the ways they are accomplishing this are pretty questionable.

I am locking this thread. OP, like anyone, is welcome to make bug and feature requests on GitHub. That is much more constructive. Thanks!

This is an iOS safari bug that really sucks with PWAs. I created a WebKit bug, but haven’t heard back ☹️ https://github.com/aeharding/voyager/issues/330

The native app is NOT affected by this bug so I recommend using that.

To be clear, I will never add ads to Voyager.

Android too!

You mean choose a default browser for external links? If so, yes, here: https://github.com/aeharding/voyager/issues/553

Car headlight are too fucking bright nowadays