That’s the part of the code that seems strange??

While I definitely agree, lemmy instances hosted by generous members of the community aren’t necessarily ran by people who deal with this stuff day to day and cutting them some slack is extremely fair imo

Yeah, I think I just handle the login differently so Lemmios will log out much quicker if there is an error, tell me if there are any more bugs though, I’ll try my best to fix them!

Ok fixed! Will be pushed to testflight and then the app store when apple review finishes, I’ll update as that process happens. Sorry for the bugs lol

EDIT: Published on both!

Yeah it’s due to the 0.19 beta update, will work on fixing this (should be quick) later tonight

Huh, could you send me a video of this behavior? It seems to be working fine for me. Just to make sure, where is this happening?

Hmm, from what I have seen there is no way inside the Lemmy API to do this (would love details if this has been added) and I have been told by Lemmy developers to not try this until then since for large community groups it would severely impact server performance. I’ll ping @[email protected] just in case they want to help

Also, as the developer of Lemmios, it is somewhat negligence on my part (not saying this is true for any of the other app developers, just me), we all google when we code and generally the newer features make things much easier so it is really hard to google older features since they are harder to implement and get quite buried. I also think for me at least my apps start as passion projects I don’t really expect anyone to use so I forget that iOS versions under my current one exist lol, it’s a lot easier to start on 16.0 and stay on 16.0 forever than go lower after the project has started, sorry.

Hey, Lemmios developer here, what do you mean by cutting off images? It’s a known bug (I’m not sure that’s the right word because it’s working as intended just looks odd when people embed images in the body of a post) that Lemmios will only show the begging of a text post in the main feed, but once a post is clicked on there shouldn’t be any cut off images? The image loads fine for me and I would love a screenshot of it getting cut off if you can?

It does not mean that lemmy is less secure, but yes, it means that malicious app developers will have a much easier time stealing login credentials because entering them inside the app is already the norm. However this is definitely a feature that can be added so it does not mean anything bad long term

Even though they are both fediverse they still are quite different and one of the important differences is that lemmy does not support oauth so apps don’t have that option, as for why all mastodon apps use it: it’s because of the security benefits to the user and (as a lemmy app developer) implementing auth is hard lol

Yes it should, the issue you might be encountering is that in the list it uses the (lower quality) thumbnail image and it uses the full quality image when looking at an individual post. After cutting my own network images will still load for me, I will add showing how large the cache is and the ability to clear it soon

Thanks! I’m realizing I’m so lucky this is over my summer break so I can focus on this rather than high school (not that I focus that much anyway lol), the timing of reddit going crazy was great for me lol.

Ahhh, silly me, I was testing marking read by tapping on them, the marking read on scroll got broken by the new tab view (starting to regret it lol) but should be fixed now (1.6.151)!

Yeah, it’s meant to scroll you to the top, the posts title should be shown as greyed out when read, is that happening? Might be worth checking your settings?

Also huh, it works for me, could you possibly upload a video somewhere showing what happens?

Ah yeah, moving to a custom bottom bar had caused so many problems lol, should be fixed now tho!

Ok added in 1.6.147! Does need to be enabled in settings first though, sorry I had to go to bed first lol

Thanks! And yeah I’ll work on that next!

Hmmm… I’m sending this comment from the app right now (first test so we’ll see if this sends lol), where in the process are you encountering issues?

EDIT: Found the issue, seemed to be only with some comments? Honestly zero idea what the issue was or why my fixed worked (if anyone knows SwiftUI and wants to take a look at my fix I’d love advice: hacky lines. But anyway, fixed in 1.6.145