No joke I made kofta a few month ago and I will probably not make them again because I didn’t realize what they resembled until I put them on my plate.

Edit: I found a photo of it. It’s even worse than I remember.

Wait so she’s poisoning his grandma?

The tax benefits tho :o

Hey don’t kink shame.

That makes sense. (The last “lemmy.world” in this text should be “programming.dev” in this case). But I cannot find out how to do that. In liftoff I would go to the context menu and select “view on other instance” and select my account on programming.dev and it would continue working. However, I cannot find something similar in summit and I am not sure (as a user) how to apply the suggestion in the popup (maybe I am stupid).

This is an edge case I didn’t handle. I’ll add it as a bug to fix for the next release.

The most weird thing for me is that all outside the popup is interactable. Example Video (link self-destructs in a couple of days).

Ah, tablet. That makes sense. The app doesn’t handle tablets very well at the moment mostly due to me lacking a physical tablet test device. I can’t really justify buying a tablet just for a fun side project at the moment. I can test on an emulator but I avoid it because the screen is really large and breaks my screen layout. I will get this bug fixed at least for the next release. Thanks for reporting!

Since you are on a tablet, you might be interested in an experimental feature I added to the app, which is navigation rails. It might improve the screen usage slightly. To enable it go to Settings > Misc > Navigation rail mode. Turning it to Auto should auto-detect that you are using a tablet and switch to it. I’ll enable it in the future by default after I work out all of the kinks :D.

Good point. I’ll add this for the next release.

Happy new years to you as well!

That’s because the controller is just two drumsticks.

What if there was an unintentional infinite loop in your code. You could be waiting for infinite time only to learn the code had a bug. D:

Regarding patreon and all donations, it’s there to support development. There is no exclusive content and I feel like any time I spend creating content there would eat into time I could be using to develop even more features in the app or fix bugs.

Also the two little bugs I found, the save draft button for comments is spelt safe draft and when you have upvote and downvote numbers on they clip outside of the screen causing the text not to be visible.

Nice catch on the former issue. I’ll fix it for the next update. Regarding the latter issue, this is a layout issue mostly because comment headers do not wrap by default. I haven’t found a good middle ground just yet. One quick and easy fix is to wrap the comment headers but it looks a bit weird. There is a 2nd solution which is to design headers to be two lines, however I’ve observed that some users like everything to be compact.

The app actually already supports both wrapping and multiline comment headers, it’s just not configurable. One way to force multiline headers is to enable avatars. You can give it a try in case that works for you. (It’s in Settings > Comment List > Show profile icons).

So there is also the obvious solution of making multi-line and wrapping headers two new setting options. The issue is that user avatars was designed with multi-line headers in mind. I think what I might have to do is make them “presets”. Eg. you can choose between header with avatars, multi-line, single line or wrapping headers, but you can’t mix and match.

Fix should be live within the next couple of hours as in v1.21.3.

All of the changes mentioned will be available in the v1.21.3 release which should be live within the next couple of hours.

Actually I just went and read Liftoff’s source code. The “multi-instance” fetch logic is here: https://github.com/liftoff-app/liftoff/blob/d7fdeb0f948f0bb17c54617eb8c5b74f556fb01a/lib/pages/home_tab.dart#L377

The tl;dr is that Liftoff uses a very primitive way of handling it. From what I can tell Liftoff does not do any dedupping across instances so the same post may be shown multiple times. This actually makes the implementation much easier.

Do you know if Liftoff dedupped? Eg. would you see the same exact post multiple times? If so that is one simple way to resolve the issue however the user experience is worse.

I am using the left-handed setting. But the “preview” popup of a link has the buttons inconveniently on the right.

Will be fixed in the next update.

I can’t find out to jump to “all” or “local” posts of a specific instance.

This is not currently supported. Once you are signed in, the app will use the current account’s instance for everything. I think a solution for this would be to have a special signed out account that can browse any instance but with no permission to perform any actions. I’ll add this to the user requests backlog.

Up/downvotes are on the left, but comment count on the right. Would be cool, if there was an option to have them together.

This is tough to design for. I played around with it for 5 minutes but couldn’t get anything that looks nice. Is there any particular reason you want them to be together? The reason they are separate is mostly for aesthetics. You can try compact view which does have them together if you want.

default up/downvote color is inverted from my point of view (up is red, down is blue). Would be cool, if there was a simple switch button without having to pick the opposite colors manually.

Will be added in the next update.

Drafts are saved but I can’t find them. A menu in the composing-post would be cool.

The next update will allow you to long tap any of the compose tool buttons to see a description. The drafts can be accessed by tapping on the icon button that looks like a page (2nd button from the left).

oh, it would be cool, if “save post” could be pulled out from the submenu beneath a post or comment.

For performance reasons the “submenu” is difficult to change/customize at the moment. If you use “save post/comment” a lot I would recommend changing one of the gestures to that. I will add configuring the “submenu” as a user request.

the community-popup (button on top left) has a weird “back”-history. A popup should be always first to close. Also it should be modal since you interact with everything in the background and can’t close it tapping outside.

I couldn’t reproduce any issues here. Tapping back always dismissed the community-popup for me. If you find a way to reproduce it 100% please let me know.

settings are weirdly bugged if you return from a category back to main. If i use the button on top left, everything works. But when I use the system back button, I cannot click on any category anymore. Though, I can still scroll.

I found that this is actually a weird state bug. This only happens if you tap on the summit community within settings first. After that, navigation will be bugged. I have a fix for this in the next update.

I cannot subscribe to any community. The button does vanish for a split second but just reappears. Tried it on multiple, but never worked.

I tested this on a few instances. It seems that there is a delay to subscribing. It takes a while on the server for the server to return that the user is subscribed to that community which can explain why it doesn’t work. From my tests it can take up to a minute before the server returns subscribed. If you want to test this out, I’d suggest subscribing and then swiping to refresh a few times to see if it works.

Thinking about this more this is going to be hard to implement even for the current account. I’ll give an example. Let’s say you were sorting by top. Let’s say you had 2 accounts signed in A on a.com instance and B on b.com instance.

Let’s say A is the current account.

You refresh. The app pulls a.com’s posts and b.com’s posts. Due to b.com being a smaller instance a post (let’s call it P) is fetched from b.com on page 1. This post is now shown on the combined view.

You scroll down and now more posts are fetched. Now post P is returned by a.com but on page 2. The issue is, originally P was shown but it was retrieved from account B so you can’t comment on it with account A. But now we also have P from account A. By dedupping rules this new post P would not be shown.

There are way around this. Specifically every instance can translate links from other instances to its own instance, however the app will need to make these calls for every post which can be very expensive and taxing on the servers.

There is also the argument to be made that P from b.com should never be shown if P exists on a.com because A is the current user. This essentially forces the app to use the translation API which again is expensive.

This feature can be implemented however due to how the fediverse works any implementation of this would essentially be “read only”. Ie. You will be able to read posts but not comment on them or vote. The reason is because it’s really hard to figure out which account should be used for any “write commands”.

This isn’t difficult to add. Most of the groundwork is already done by the multi-community work. In a way this is just a special multi-community.

The difficulty is around handling what account to use. If the current account is used regardless of which post you tap then this is easy. Is that what liftoff did? Or did liftoff also auto-switch account for you when you tapped a post that isn’t for the current account?