this post was submitted on 16 Jan 2024
22 points (100.0% liked)
Voyager
5585 readers
57 users here now
The official lemmy community for Voyager, an open source, mobile-first client for lemmy.
Rules
- Be nice.
- lemmy.world instance policy
Sponsor development! 👇
💙
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Last time this was brought up, I believe the Voyager dev (sorry can’t remember spelling of his account, I think [email protected] ?) mentioned this is dependent on a proper resolution of push notification support from Lemmy itself, and linked to a Lemmy issue on GitHub. Very unfortunately, Lemmy devs doing what they do best — finding creative ways to alienate their user base by choosing a platform that only works on Android, requiring a third party app to background continuously, shoots down open web standards, and mislead iOS users to go create tickets in their chosen upstream project for fictitious “battery concern” when brought up that iOS paradigm does not allow long running background apps.
I’m not holding my breath for this :(
Being a (FOSS) dev is a badge of honor, not a license to be terrible.
By misleading users to complain to their upstream vendors about faulty “battery concern” when there’s a deeper problem, they’re just sending misguided users to create problems for other (FOSS) devs.
By forcing all clients devs to handle dual auth instead of handling dual auth token structure “because it is hard”, they’re dumping their responsibilities on to other (FOSS) devs.
This not the first and it will likely not be the last time the Lemmy devs do things you don’t want to acknowledge. However, if you get so agitated and feel the need to spell off expletives at someone calling out facts, then it may be a good time to cut back on the koolaid. Software development is not a cult.
Can you elaborate more on this¿?