What I post from lemmy.ml wouldn’t be seen there if that were the case, but it’s seen there, so that doesn’t seem the case…

BTW. I’ve already joined… That said, I see the same posts missing. Of course that doesn’t apply to one I made myself from lemmy.ml. There’s also a bot one from 9 days ago, but the rest are at least 1 month old…

pending for subscription, we’ll see, and while pending, still not syncing properly…

I see. Thanks for clarifying.

ohhh, I see. Many thanks !

ohh, sorry, I didn’t noticed it, as you can tell…

If I may, what’s the issue with URLs?

Since this community is partially inaccessible due to some change in how URLs are handled

ohh, I see, is there a setting, besides unrestricted battery use, one can should set as well then? I remember another about background use, but can’t seem to find it…

This is the first post that clarifies why there’s no need for unified push notifications, but still conversations supports GCM/FCM push notifications. I seem though for those phones unified push notifications would help, the same way GCM/FCM does? At any rate, for battery purposes I got it’s not required.

Many thanks !

Ohh, thanks, I’ll try asking there…

BTW, before molly supported unified push notifications, it was also using websocket and that still required to enable unrestricted use of battery, as currently conversations does. Once I the unified push molly version showed up, such unrestricted use of battery was no longer needed. Websocket definitely is much better than GCM/FCM, but it implies, I believe more battery consumption, though perhaps not unbearable.

Jami was also using websockets and required to allow consuming battery on the background as well, and then moving to unified push no longer required that, but in the case of Jami, by being peer to peer, the effect is more noticeable.

All that to say, that other apps have moved to unified push notifications for better battery savings, even though they used websockets before, and curiously enough conversations does take advantage of GCM/FCM push notifications, so is not clear to me why disregarding unified push ones, but it’s always up to the developers/maintainers, and what they need/want to invest on… So that’s why I mentioned I don’t quite get what was mentioned on the github issue, though it was clear to me there’s no intention to provide the support.

Yeap, thanks a lot !

Thanks !

Yeap, got it. Thanks a lot !

understood, thanks !

Ohh, thanks for that… I noticed when under the office’s VPN, it doesn’t work, :( Which is really bad to me, since it then block any services from it, :(

It seems like disroot doesn’t like the office’s cert when connected through VPN…

Thaks for replying !

I recommend you to explore sourcehut as well, if you’re not afraid of something different to gitlab/github workflows.

Pff, I just got logged out on a refresh, hehe. So what I said is not true, I’m getting logged out, somehow randomly (can’t say I know under which conditions that happens). Not sure if there was a release candidate upgrade, since I can’t remember the version before this new logout. Currently:

UI: 0.19.0-rc.11
BE: 0.19.0-rc.10

Nope, I only have a lemmy.ml account, and I only use librewolf on the desktop…

I had that issue of having to re-login, and then every now and then when I do reload, it posts not on my subscribed communities as if I were not logged in, although I’m logged in, but on a subsequent reload, then only my subscribed communities posts show up. I haven’t had to re-login again, just after the upgrade, and then the other minor annoyance is that, but a subsequent reload is enough…

Thanks !

Is it normal that on an upgrade, users are forced to re-login?

Ohh, I didn’t know lemmy already offered such thing. So it would be like https://_instance_/feeds/c/_community_.xml?sort=Active then?

Pretty interesting. I was not counting on a rss sort of reader extension, but it might work… I’ll explore it, though if lemmy already support rss seeds, perhaps I can get a more generic rss reader doing it… Thanks !