Turned out the TF environment and dev environment arent compatible, so just had to switch that for all the notifications to come through! Not diagnostics atm, might be a good idea to add that tho. Some kind of metrics would also be pretty insightful..

Seems like I missed some details about how push notifications work in testflight, should be good now if you enable it and allow in system settings. Did you get this notification? If you didn't, you might have to toggle it off and on again in the app!

Yeah, I think there's a slight issue with TF tokens atm, but only happens in some situations it seems. Has worked for me for the last week or so, so probably just a minor thing. Looking into it!

Hey, thanks for the heads up! Its only supposed to ask when you try to turn it on, but guess there's an issue with the logic for when it should ask for permission. I'll definitely get that sorted out before release.

Is it working? :D

I'll add this in 1.0.8!

Thanks for all the info! You're right, this is a result of the youtube embed feature. Even with the option disabled, the app still does some preprocessing to get embedded links so you don't have to reload everything in case you turn it on. I'll look into converting the links back if you open them directly in the browser

I've noticed this for ampersands too, but wasn't sure if it was an issue on my end or some encoding thing in other input forms or the backend itself. Seems to be the same in the regular web frontend for instance. Hmmm

Have you checked out the "reduce white point" option in accessibility settings? Does that improve things or is there still too much contrast?

IMO the most important thing by far is making the core app experience as solid as possible. Things like post feeds, comment sections, posting, sharing, image viewers, inboxes, replying, editing, text selection, user profiles, swipe gestures, searching, font settings, sorting options, display options, hiding read posts and everything else you'd expect takes a lot of time to develop, maintain and polish. The vast majority of my development time is spent on improvements, bug fixes and new features for everyone, and I really do care a lot about creating a great experience that can help improving Lemmy overall. Offering some more niche nice-to-have features on top of that is a good way to support everything else.

I'm not going to add a higher tier - as I briefly mentioned in an earlier comment my goal is rather the opposite. If Lemmy keeps growing, Avelon Pro could at some point make sense as a $5-or-something one-time upgrade. Unfortunately that's just not the case right now.

I posted a reply to your post about that, its a bug with an accessibility setting in iOS. Forgot to include the fix in 1.0.7, but you can resolve it for now by disabling "Button Shapes" in the iOS accessibility settings.

I've added a text selection tool now, available in 1.0.7!

Yeah this bug was pretty weird. Fixed now in 1.0.7!

Looks like discuss.online is using Lemmy v19 RC2 (which is still in beta) so if there are breaking changes there, that could be why. I've already added support for v19, but that support was based on RC 1.

You could try to remove and add the account again if you haven't tried that yet, but if it still fails I'd recommend using a stable v18 instance for now. I'll take a look at adding better error messages to the login screeen to make it a bit easier to find out what's happening.

Hmm, not sure how I'd combine something like this with the existing hide read posts feature, sorting and everything else while keeping the app intuitive to use. Wouldn't make sense with "top 6H" sorting for instance, and it should be easy to toggle. Any suggestions?

Thank you so much, really appreciate it! I've started to look at better full screen landscape support whilst keeping the portrait feeds, but yeah it's more tricky to do than you'd think. For sure something I'd like to do eventually!

No worries, feedback is great. Avelon does basically the opposite of that, where it tries to interwine as much as possible (without being too heavy on the servers). Here's an example:

Show

Good idea! I'll look at adding a free trial or other demo functionality.

Community groups let you add any number og communities (from any instance) into a named group that appears with your subscriptions on the "posts" tab. When you open it the feed works the same as usual, but will contain a mix of posts from the selected communities. The mix is designed to be even, so if one of the communities is much smaller you'll still see posts from that one too. You can sort as usual, but the mix will try to remain even as long as there are enough posts to pick from.

What was the issue with Bean's implementation?

Oh right, thanks! I'll add both

I'm assuming you're talking about a "share" button for comments? Can definitely add this!