Filter keywords that are entered with comma-space are not being filtered despite being added to the keyword list below the text field to enter them. The user has to enter keywords as comma separated only despite the list being saved as comma-space separated. Furthermore, entering comma-space will save it as comma-double-space. Lastly, the settings saved message at the bottom keeps repeating once a change is made to the filter list.
Changing the sort method to the same one that it’s currently on results in that method being messed up for that post. I think it becomes Hot? Regardless, it’s now cached and short of clearing the cache, refreshing the post and reopening the app won’t fix it.
If you upvote(from post instead of feed) a crossposted post, then view any of the crossposts, they will show as upvoted as well despite having not done so. This only happens if you didn’t view one of the cross-posts first. Viewing a crossposted post, then viewing one of its crossposts, going back and then up voting will not cause this problem.
Modlog just loads an empty page. Also, it would be nice if the log showed the community name at the top rather than the ID.
EDIT: Also I received a reply on my Piefed account but I don’t recall getting a device notification for it. I did see a notification badge for the account before switching to it. Just wondering if maybe there’s an issue with notifications across account, or maybe it’s a Piefed issue, or I likely did get the notification and just forgot.
Device Information
- App Version: 1.0.398 (398)
- Platform: android
- OS Version: BP4A.251205.006
Modified Settings
The following settings have been changed from defaults:
- isNotificationEnabled:
1(default:0) - commentDividers:
0(default:1) - isCommentActionsReversed:
true(default:false) - shouldAlwaysOpenInDefaultBrowser:
true(default:false) - shouldDisplayTitleAbove:
true(default:false) - alwaysShowInstance:
true(default:false) - applyUserNotesGlobally:
true(default:false) - shouldSaveUserNoteContext:
true(default:false) - alwaysTrustDomains:
true(default:false) - shouldUseHighRefresh:
false(default:true) - shouldLimitCardImages:
true(default:false) - shouldPreloadImages:
never(default:always) - shouldLoadCrosspostComments:
false(default:true) - shouldAutofillPost:
false(default:true) - commentTextStyle:
labelSmall(default:bodyLarge) - postTitleTextStyle:
titleXSmall(default:titleMedium) - customColoursPreset:
2(default:0) - isTopBarFixed:
true(default:false) - showFullVotes:
true(default:false) - shouldAlwaysDisplayAvatars:
true(default:false) - shouldInstanceBlockIncludeUsers:
false(default:true) - defaultRoute:
/community?postListingType=All&hint=All(default:null) - defaultPostSort:
New(default:Active) - defaultCommentSort:
Top(default:Hot) - cardType:
list(default:card) - swipeActionsComment:
[](default:[]) - postActions:
[comment, save, none, none](default:[]) - swipeActionsPost:
[hide, none, none](default:[]) - shouldVideoAutoplay:
never(default:always) - shouldPreloadVideos:
never(default:always) - shouldUseProfileBanner:
true(default:false) - shouldDisplayCommunityBanner:
false(default:true) - stickySortSettings:
true(default:false) - theme:
amoled(default:system) - imageDomainRewrites:
{}(default:{})
Hi, thank you for the issues report. I’ve pushed v399 to beta which I think should address this but please let me know if any are still occurring. Cheers!
The sort method changing to Hot for posts when you select the same current method is still reproducible in 399. Actually, you just need to revisit a post for the same thing to happen.
As well as upvoting cross-posted posts and it being carried over to its crossposts.
New filters are showing up on the modlog but other than that it’s still not loading anything for me.
All of the issues with keyword filters seem to be fixed though. And it’ll be nice to quickly see deleted comments.
Is it a specific instances modlog that is failing? I was testing with lemmy.ca and it seemed to be working. I’ll take a look at the other issues in the next release.
I was sure the culprit was 2FA since that’s the only real thing I can think of that’s different with this account but nope. Even after clearing the storage and logging in fresh, the modlog loads up empty for this particular account. I can just switch accounts if I need to look at the modlog but this one’s a head scratcher.
Seems like all instances and communities. Tried logging into my .world account and it works fine. They both should be using the same settings so I wonder what the issue is. Will update if I can pinpoint it.
