idunnololz

joined 2 years ago
MODERATOR OF
[–] idunnololz 2 points 1 hour ago

anon needs to start watching anime. If he watched 8 hours of anime per day he can learn social skills from the anime. /s

[–] idunnololz 2 points 19 hours ago (1 children)

While we're renaming things can we also rename NAFTA to CUMFTA

[–] idunnololz 5 points 19 hours ago

See you there ඞ

[–] idunnololz 1 points 1 day ago (1 children)
[–] idunnololz 2 points 1 day ago (1 children)

This is a known issue. This is on the roadmap as

Export tables as part of export settings. Currently there is a limitation for the import/export settings feature. It only supports settings which are represented as key-value pairs. However some settings are represented as lists and these are stored in tables in a db. This change will require the app to know how to import/export a table as well as possible showing this option to the user.

[–] idunnololz 1 points 1 day ago

Hmm I just checked the lemmy.world website and I can see the entire comment chain there as well. Link: https://lemmy.world/post/24942544

[–] idunnololz 2 points 1 day ago (1 children)

They remind me even when I don't use assistant. I sometimes wake my phone and it's the first screen I saw. I tried switching over and it sucks. Sometimes I say a voice command for something regarding google home (eg. Turn off the lights). Sometimes it correctly realized this is mean for Google home and will execute the command with Google home. Sometimes I get an error saying Gemini can't do that yet. This is with the same exact prompt. It's not idempotent.

[–] idunnololz 1 points 1 day ago (1 children)

The output isn't guaranteed to be correct though. Most implementations of sleep can only guarantee that it will sleep for at least the amount of time specified. It can sleep for longer though.

[–] idunnololz 3 points 1 day ago* (last edited 1 day ago) (1 children)

I'm using Summit for Lemmy. (I'm also the dev)

[–] idunnololz 3 points 1 day ago (4 children)

I tried looking at the post you linked on the Lemmy.world instance however I used an app. I was able to see each individual post. What this tells me is this is a purely frontend issue as the back end is capable of serving the entire comment section.

See the screenshot below (taken while in the Lemmy.world instance)

[–] idunnololz 4 points 1 day ago* (last edited 1 day ago) (2 children)

Are eggs only expensive in the US? They are like $6/dozen in Toronto. It's not cheap but it's not super expensive imo.

[–] idunnololz 2 points 1 day ago

I fking love broccoli

289
Exciting news! (lemmy.world)
 
 

I got a steam deck primarily as an easy way to play steam games on the TV. I also got a PS5 controller since I've read it is one of the better controllers for the steam deck. However one issue I'm encountering is that all the games I've tried shows the wrong key to press on the controller. For instance they would show the A button when I need to press the X button or the B button when I actually need to press the Y button.

Is there any way to fix this? I'm also new to using controllers for games and this issue is making it harder to adapt to using a controller :/

210
Sencha's cat tree (lemmy.world)
submitted 1 week ago by idunnololz to c/cat
 

This is Sencha on his original cat tree that we got when he first adopted him. It's pretty old and falling a part a bit from wear and tear. We tried to get him a new car tree but he still loves to use his original tree. Momo on the other hand loves the new tree. I guess now they each have their own cat tree.

8
submitted 1 week ago* (last edited 9 hours ago) by idunnololz to c/summit
 

This update will be focused on overhauling the actions system within the app.

Currently the app records histories for some actions and is also smart enough to retry certain actions. All of this stuff happens behind the scenes. Although users can see the actions history, it is buried in the settings screen.

The retrying logic also has some issues. For instance, retrying adding comments/posts can result in duplicate comments/posts. This is very undesirable.

This release will focus on tweaking the actions system, overhauling the UI giving users more visibility and power when viewing action history as well as giving users a way to retry a failed action.

In the coming release, comments or posts that fail to send due to network issues will immediately error and will not be retried. They will be stored in the actions history so the comment/post is not lost and the user will be able to manually retry to send them. While this solution is a bit manual, it at least works better than the existing system.

Changes so far:

  • Made the user stats tappable on the "You" screen
  • Fix a bug when loading inbox message/items past page 1 where it would load the wrong page.
  • Fix some scrolling issues on the inbox screen.
  • Fix some inconsistent theme issues.
21
submitted 1 week ago* (last edited 1 week ago) by idunnololz to c/summit
 

This release updates the haptic feedback in the app, adding more haptic feedback to actions and adjusting some of the haptics that already exist. It also adds a new settings screen specifically for adjusting haptic feedback.

Full changelog

  • Added a new settings page dedicated to haptic feedback.
  • Added haptics to more actions.
  • Adjusted strength of haptic feedback to be inline with Android's guidelines.
  • Added a new experimental feature that automatically marks duplicate posts as read. A duplicate post is a post that has been posted to another instance that is essentially the same as a post that has been read. This feature is off by default.
  • Fixed a bug where links cannot be opened if the preview link setting is set to "Preview all".
  • Fixed a bug where thumbnails sometimes won't load.
  • Fixed a bug where the last swipe action on a post is accidentally replayed.

Update

Noticed that not all thumbnail links were fixed. Pushing another release (v1.52.1) to fix even more thumbnails.

Update 2

Pulling in some new translations. Releasing as v1.52.2.

Update 3

Special note for one bug I finally tracked down. There was a period of time where the oddest things would happen when I was in a post where I thought I was losing my mind. I would upvote a comment, return to the post and see that the comment was not upvoted. Or I would post a comment and then after, the comment dialog would popup multiple times. This was extremely confusing as none of the logs indicated anything had even gone wrong. The "ghost votes" would appear in the logs as though I had went back to the comment and removed my vote manually.

After a lot of manual testing, I was finally able to track this issue down and it has to do with how swipe actions work.

When a swipe action is initiated, the app remembers the last swipe action. When you swipe and then let go the app triggers the last swipe action saved. This allows you to drag the swipe action slider as far as you want and as long as you are in the correct region when you let go, the right action will be taken.

The issue is when the action is triggered, it does not clear the last saved action.

This normally wouldn't cause any issues except if you are also using gesture navigation.

A gesture navigation gesture is just a regular swipe except the starting point is near an edge of the screen.

For a back gesture, the user first has to touch the edge of the screen and then swipe inwards. During the first part of the gesture, Android doesn't actually know yet if the action is going to be a back gesture. So at that stage Android will let the app handle the gesture. Only once the finger slides far enough does Android realize it's a back gesture and take ownership of the gesture. At this point Android will cancel the swipe gesture on the app's end so it can handle the gesture gracefully.

When Android tells Summit to cancel the swipe action, Summit was incorrectly assuming it was a valid swipe action because the last swipe action was set. Summit would then trigger that action. The fix is simple. The last swipe action just needs to be cleared whenever a swipe action is triggered.

176
senchawide (lemmy.world)
submitted 1 week ago by idunnololz to c/cat
 
247
submitted 2 weeks ago by idunnololz to c/cat
 
222
submitted 2 weeks ago by idunnololz to c/cat
 
12
submitted 2 weeks ago* (last edited 1 week ago) by idunnololz to c/summit
 

This release adds more haptics in general to the app. It also makes haptic feedback more configurable.

Changes so far:

  • Added a new settings page dedicated to haptic feedback.
  • Added haptics to more actions.
  • Adjusted strength of haptic feedback to be inline with Android's guidelines.
  • Added a new experimental feature that automatically marks duplicate posts as read. A duplicate post is a post that has been posted to another instance that is essentially the same as a post that has been read.
  • Fixed a bug where links cannot be opened if the preview link setting is set to "Preview all".
  • Fixed a bug where thumbnails sometimes won't load.
 

This release polishes different aspects of the UI. The main changes are to improve contrast in various parts of the app for both light and dark themes.

Full changelog

  • Added a setting to disable the text preview icon for certain post feed views.
  • Added support for haptic feedback on action buttons in the post feed/post screen.
  • Added a setting to enable/disable haptic feedback.
  • Fixed a bug where shadow is cut off from the link button in a post.
  • Experimental: Added special support for loops.video links.
  • Improved the contrast for the search bar in light themes.
  • Changed some image thumbnails to be rounded and also have a slight border for contrast.
 

This is an idea I've had for a while now. Please let me know in the comments your thoughts on this feature.

This is my own feature request. I think the more I use Lemmy the more I find myself ignoring posts I've already read on a separate instance. In theory it doesn't sound like a bad idea to check out the same post from different instances since they have different comments however in practice this is rarely useful. I think a feature that essentially remembers the last ~100 posts you've read/hidden and then automatically filters out any new posts loaded with the same content would be cool.

Specifics:

  • Create a "cache" that remembers the last 100-1000 posts that are either read or hidden. This cache is per post feed. It can remember posts based on the title + maybe the first 100 characters of the post body + url (but not image urls since these can differ based on which instance the image is uploaded to). We can exclude any post with a title less than 25 characters and no body.
  • For each new post loaded, check against the cache. If the post hits the cache then that post is automatically marked as read. If hide read posts is active, the post is already automatically hidden.
  • When a post is read/hidden, all loaded, but unread posts are checked to see if any match the read/hidden post. If they are, they are marked as read.

Possible things to test/include:

  • Have the "cache" be based on time. Eg. only things read/hidden within the last 24 hours are checked again. This could be a setting.
  • Make the cache global. Eg. check across post feeds. This could be a setting.
8
[WIP][v1.51.0] WIP (self.summit)
submitted 3 weeks ago* (last edited 2 weeks ago) by idunnololz to c/summit
 

Going to try to implement some features. Not sure which ones just yet.

Changes so far:

  • Fixed a bug where shadow is cut off from the link button in a post.
  • Experimental: Added special support for loops.video links.
  • Improved the contrast for the search bar in light themes.
  • Added a setting to disable the text preview icon for certain post feed views.
  • Added support for haptic feedback on action buttons in the post feed/post screen.
  • Added a setting to enable/disable haptic feedback.
view more: next ›