That's not quite true - images are only shared if you attach the image to federated content, such as a post or comment. Then yes other instances will cache the image.
If you never do that, and just upload an image accidentally like OP then it will not be federated AFAIK.
That sucks. As a 3rd party Lemmy app developer, I've only had positive interactions with the Lemmy devs. They're even being proactive in communications.
You should give the issue an upvote, right now it has zero upvotes. :)
As for why it isn’t merged in yet, is because it is a PR for a user submitted issue that hasn’t been fully triaged yet. For example, should avatars also be added to profile, autocomplete, post details, account selector etc, should avatars be animated, or frozen etc
I do need to revisit that PR and issue though, there have just been other priorities (again, upvote the issue if you want it)
There are absolutely reasons where a native app is worth it - I just don't think building your own backend or not factors into that decision much.
Maybe the point you are trying to make, is when you have enough resources/large enough company, having duplicate teams for each native app isn't that big of a deal? I agree financially, although is is harder to technically coordinate two teams with dual releases and implementing features twice, with twice the bugs, and it slows things down. (Maybe not a big deal to Bitwarden - their app featureset may be quite stable, IDK)
(Disclaimer - I've been on teams building kotlin/swift apps and also cross platform apps professionally, so this is my firsthand anecdotal experience.)
So you’re going to maintain two separate code bases with two separate teams as a knee jerk reaction to using one of the worst cross platform frameworks out there…
For an app that does little more than display encrypted text in a list…
aeharding @ aeharding @lemmy.world Posts 66Comments 902Joined 2 yr. ago
Yeah Voyager supports spoilers now :)