I think there might’ve been some changes with regards to 2FA and Lemmy v19. I see that feddit.uk is running v19, so I will double check if I need to update my 2FA implementation (:

That’s very strange, since I haven’t removed anyone and I also can’t see this anywhere in the dashboard.

If you send me your email through a PM, I could check if adding you as tester manually might resolve this (:

Hmm strange, since the build should still be available:

Does the public link not work for you either? I also hope to push a new build this weekend, so perhaps that fixes this issue otherwise 🤞

There is indeed something funky happening with link rendering, I’ll look into it (:

I’m guessing this is indeed related to timezones, I’ll look into it!

I will look into this, since I’m updating this part anyways to incorporate notifications :D

Great find, I’ll look into this! I also noticed that the edit and delete option shows up in one menu, even if it isn’t your own comment. So something funky is happening in those menu’s

Great suggestion, I’ll add that to the list as well!

While using the app myself I ran into a similar “issue” where subscribing to a new community would take quite a few steps. I’ve been playing around with the idea to nest the community menu inside the post menu, which would reduce the amount of steps. I’ve been trying out the following setup:

In parallel I’m working on a bigger update that includes notifications and widgets, so it might take a bit longer to release this update. But hopefully this makes your requested flow to block communities a bit easier (:

👀

Thanks to your suggestion I found a way to disable the predictive text feature in the markdown editor. While this is not the perfect solution, it does at least seem to fix the issue for now.

I’ll keep looking for a better solution, but in the meantime I’ll try to have a new app update ready in the coming week that includes this temporary fix :D

I think it’s a problem related to React Native. The package that I use for the markdown editing is a native iOS package, so I had to write a bridge for the package to be able to use it in my app.

Avelon uses the same package for example, but there it works fine as far as I know. Avelon is however a completely native app, therefor I have the suspicion that the problem is related to the bridge that I wrote.

I already tried to isolate the bridge, to see if any other code in my app is interfering but that didn’t seem to be the case. My plan is to write a dummy application somewhere this week, to see if the package does work out of the box in a native app to make sure that my suspicion is right.

I’m not too familiar with native iOS development though, so that’s why it’s all taking a bit longer.

It is however very helpful to hear that the prediction setting seemed to resolve it in your case. Bit by bit we’ll get closer to fix this 🤞

Thanks for reporting this! I’m aware of the problem and I’m actively looking for solutions, but so far I haven’t found one.

It seems to be related to the new iOS17 predictive typing, because most often the duplication of text will happen when iOS tries to predict the rest of a sentence.

I’ll keep looking for a solution, since it’s quite jarring. Will keep you posted (:

As far as I can see the scores are removed in v0.19, instead only the counts are available. I’ll make sure that the next update will show the counts instead of scores

Great suggestion! For some reason this has never crossed my mind to implement haha. I’ll add it to the list of the next update (:

Great suggestion, I’ll include this in the next update!

If you disable both the left and right swipe, it will automatically enable full swipe to go back.

Right now I’m having some technical limitations with React Native, where it’s not possible to have full swipe to go back without disabling both swipe gestures. It’s on my list to look further into, but I’m not expecting to solve this in the near future.

Hopefully this is good enough for now :D

Great to hear this kind of feedback!

I will look into the bugs you mentioned. Reading some of them I immediately already have a vague idea what could be the problem.

The suggestions are also great. Most of these are indeed already on my radar. My first goal is to fix the last bugs and finally push the V1 to the App Store, since I achieved all the basic features that I had in mind for the V1. Once that’s setup I’ll continue working on adding new features :D

Sooner or later you know the ins and outs of this app better then me, some great bug hunting!

I have noticed this issue too, but up until now I didn’t think too much of it. I’ll look into it to see what’s up :D

Hopefully it keeps working 🤞