It is planned but it probably will take a while to implement since lemmy doesn’t support webpush api. Without web push their are only two ways to check for notifications (both aren’t elegant):

1. Poll the lemmy api for new messages (say every min). This would be bandwith intensive for both voyager servers and your lemmy instance (Memmy does this and currently for 800 users 3gb of bandwith is used per day). Even if voyager is able to scale there servers to handle bandwith lemmy instances could impose rate limits which would prevent notifications from coming through.

2. Set up a weird janky system to intercept emails sent from lemmy instance to trigger a voyager server to ask the api if there are any new messages (would reduce poll rate but would be super clunky to setup).

Web push api could solve this issue since instead of voyager having to ask lemmy if their are new messages web push allows the opposite to happen (lemmy telling voyager a new message has arived).

https://github.com/LemmyNet/lemmy/issues/3552

Don’t quote me on this (I could be horribly wrong). Voyager doesn’t seem to use cookies rather it relies on Index db and local storage. Local storage stores your credentials for your accounts (jwt tokens), and index db stores your preferences. If DDG only is preserving cookies and wiping the local storage and index db (again I haven’t tested DDG) then that would give a possible explanation on why you are getting logged out and potentially why any settings are getting reverted.

Edit article explaning difference between storage types:

https://medium.com/@lancelyao/browser-storage-local-storage-session-storage-cookie-indexeddb-and-websql-be6721ebe32a

Edit 2 It looks like ddg is clearing data and only preserving first party cookies (which isn’t used for voyager):

https://help.duckduckgo.com/duckduckgo-help-pages/privacy/web-tracking-protections/

Currently voyager cannot do this (It doesn’t have any background refresh capabilities). Down the line it might be able to when push notification feature is implemented (and you enable it).

Ah missed that thanks for linking it 👍

Ah 😆

Ah sorry about load I’m relying on catbox.moe due to fhmy having issue with bulging uploader (Imgur is an alternative but on mobile it redirects to ad filled site 😔).

Sorry was working on writing the comment 😪

Main issue is when you embed image in body with no other text and attach an image a render bug shows up

![](https://files.catbox.moe/nvo2g0.jpeg)

While I like spotify for music there are three things that bug me about it:

• Anker.fm ads. Just a rant I hate anker.fm auto injection ads. If you try sleeping to a pod cast it wil go from normal volume TO SHOUTING ABOUT STATEFARM OR DUNKIN. While this issue also occurs on third party podcasting apps spotify dynamically injects a banner ad into podcast art and hyperlinks the ad. I might be overeacting (I hate these kind of deeplink ads). To be clear I don’t mind host read ads like linus sponsor shoutouts but dynamic ad injection is awfull.

• No chapter support

Podcast republic is a good alternative (assuming your just planning to use it on mobile/web)

Won’t it not be different since all browsers on iOS (chrome, firefox, brave, etc) are forced to use WebKit unlike Android?

Lemmy is actually interesting as there could be four implementations (or five if you consider none).

• Standard instant push notifications (you get them in app and out of app)
• Push notifications only while app is open in forground (example lemmy web ui only has notifications when tab is open)
• Polled notifications (notifications that occur after preset interval).
• A combination of the above three (ex: polled notifications in background push in forground)
• No notifcations at all

Just some thoughts

Whats wrong with having an option? I’m not saying it should be manditory 😉

^This

Additionally some times I just open lemmy (and Reddit in the past). To check inbox. Push notifications disables that need (no notifications = conversation hasn’t progressed much = no need to open app 😉).

I love wefwef/voyager. This might not be a normal feature people use but I love wefwef’s deep linking feature (on android). I have a push notification system for lemmy which detects incomming emails from lemmy and uses ntfy to send reddit sync like push notifications. In wefwefs case I can set ntfy to open voyagers inbox directly. Voyager is also nice since opening a unread message (or interacting with it) auto marks it as read (which I don’t believe other clients do for some reason, I could be wrong though).

Maybe lj could go down the swift backup route where purchases are tied to a Google sign in to avoid play services? You could buy the app from Google play via web, download it via aurora, then validate via in app login.

https://swiftapps.org/faq#whygoogle

Down side is lj would need a verification server (although he has servers for Reddit sync Imgur which he could repurpose for billing).

Disclaimer I am not a dev just a rando lemmy, Lemite? (Idk what to call a lemmy user)

Second question would the US gov consider google “to big to fail” and just inject a ton of money to restore it (or give enought time to break it up)?

Kinda curious 😉

I doubt people will pay for a windows subscription. Most will stay on 10/11 indefinitely and Microsoft will probably backtrack pretty quickly (look at windows 10 to 11 migration) 😉

Sorry by deep link I meant open in function. Version 0.16.0 fixed it

Fix Android PWA appearing with chrome badge by @aeharding in #305

Is it possible to re add deeplinking support. Both wefwef and voyager seem to have lost the feature (Android).

My only currently gripe with wefwef being a pwa is on iOS their is no deep link support.

I have a push notification setup which uses a MacMini apple mail app with apple script, shortcuts, and ntfy to create push notifications.

On Android pwa’s deep link aka it I can make ntfy directly open wefwef unread inbox upon clicking.

On iOS however pwa’s can’t deep link nor can be opened by shortcuts. The closest work around I have is calling a shortcut to open wefwef to open WebView (which unfortunately means manually updating two instances of wefwef on iOS).

Using say a pwa wrapper to make a hybrid iOS web app could fix this.

Although on the other hand if wefwef obtains push notifications then deeplinking may become a moot point