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).

In the case of this instance (lemmy.fmhy.ml) it appears to be self funded by the admins

Q: Can I donate?

A: We appreciate that people want to support us, but we never have and never will accept donations. We maintain this project because its fun and we want to help others, not make money.

https://www.reddit.com/r/FREEMEDIAHECKYEAH/comments/xrxen7/faq_support_thread/

However currently for others instances donations seem to be the primary method of funding (beehaw has a nice cost breakdown)

Edit FMHY link to beehaw post:

https://lemmy.fmhy.ml/post/509214

Beehaw direct link to post

https://beehaw.org/post/920683

https://beehaw.org/post/428209

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

The front end ui is down. Thirdparty apps that use lemmy api still work.

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) 😉

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

Nice 👍

Although soon you probably will be able to use static hosting like GitHub pages since Lemmy 0.18.1 fixes cors.

wefwef should feel more snappy in general as it can talk directly to lemmy instead of relaying requests.

So lemmy v0.18 broke CORS. You can expect poor performance on wefwef.app connecting to lemmy.world until the following PR is merged in: LemmyNet/lemmy#3421

This hotifx allows you to connect to lemmy.world once again, even if the experience is poor (because we have to proxy all traffic because... cors)

https://github.com/aeharding/wefwef/releases/tag/0.9.1