The more I see lemmy devs interactions the less I want to use lemmy. Their attitude with auth migration was super hostile towards developers at large (standard industry practice is them bearing the burden to maintain both, not dump on the burden on to third party devs), and now it seems like they’re just going to brush iOS users under the rug because they’re Android only and doesn’t care about iOS’ security and resource management mandate (ie no background process), and trying to misguide users by deflecting legitimate background concern to their selected upstream framework as an incorrect “battery concern”.
What a terrible developer behaviour all around! Wonder who’s the next group of users they’re going to antagonize for their own convenience next.
Edit: I don’t mean you, @aeharding; I meant the actual Lemmy dev. Sorry if this wasn’t clear.
Not until implemented in Lemmy. https://github.com/LemmyNet/lemmy/issues/2631
I don’t want the liability of storing people’s access tokens on a server, which is what other apps are doing afaik.
It also is quite inefficient because you have to poll lemmy servers for updates.
The more I see lemmy devs interactions the less I want to use lemmy. Their attitude with auth migration was super hostile towards developers at large (standard industry practice is them bearing the burden to maintain both, not dump on the burden on to third party devs), and now it seems like they’re just going to brush iOS users under the rug because they’re Android only and doesn’t care about iOS’ security and resource management mandate (ie no background process), and trying to misguide users by deflecting legitimate background concern to their selected upstream framework as an incorrect “battery concern”.
What a terrible developer behaviour all around! Wonder who’s the next group of users they’re going to antagonize for their own convenience next.
Edit: I don’t mean you, @aeharding; I meant the actual Lemmy dev. Sorry if this wasn’t clear.
Gotcha, thank you.
Good choice!