- 2 Posts
- 7 Comments
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?
0·3 years agoohh, wow, lemmy really needs to make that way easier, so subscribing and posting on other instances is made easier. I’m sure I won’t easily remember the right URL to get into the other instance community… Thanks a lot, I wasn’t aware of this way to access other instances communities…
Can I ask why creating a new lemmy instance, rather than a new community. Instances are good for centralization, so, not a complain, however it imposes an additional account, :(
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.