The dev for Raccoon also had a Lemmy community to announce updates and things (he also deleted that community). Before he deleted it, he said that post about markdown support was the last straw and he was done with it. He announced he was going to delete everything related to Raccoon and it was all gone within like 12 hours of him saying that. He said any of the forks of his app can continue development, but since he deleted the entire repo with very little warning I don’t know if any of those forks were current with the latest commit before the parent repo disappeared.

Rodent is exactly what I was looking for, thanks!

I have the default comment sorting set to “Top”. In this latest build it seems to be ordering them by “New” instead, even though the icon at the top still shows “Top”. If I change the sorting type to something else and then change it back to “Top” the sort appears to be correct. So it looks like the default sorting type isn’t used when first entering the post but the sorting algorithms themselves still work.

Awesome, thanks!

Wow, this whole post looks weird in Raccoon. I embedded two images in the post body and those images are overlapping and covering the text. Also, I put a dollar sign in between parentheses in both the title and post body and both characters are missing, just like in my screenshots.

Also, it’d be nice if that community list was sorted. I believe it’s sorting each individual page as that page is fetched, but not sorting the full list of communities.

Also, if there are multiple top-level comments without any replies next to each other, clicking the down arrow will skip past all of them and jump to the next thread that does have comments and puts that last comment from the previous thread at the top to show the next top-level comment below that thread.

It took me a while to figure out what was happening for this one. It can jump really far if there are lots of top-level comments with no replies.

Works great, thanks!

But it’s so complicated to do manually I won’t ask you to do so, don’t worry.

Here’s the error: 😄

java.lang.IllegalArgumentException: Key d4.w:currentScreen was used multiple times 
	at D.m.a(Unknown Source:1293)
	at O.z.a(Unknown Source:4)
	at B2.b.q(Unknown Source:130)
	at O.t.g(Unknown Source:61)
	at O.t.f(Unknown Source:5)
	at O.o0.a(Unknown Source:203)
	at v0.T.doFrame(Unknown Source:6)
	at v0.Q.doFrame(Unknown Source:47)
	at android.view.Choreographer$CallbackRecord.run(Choreographer.java:1397)
	at android.view.Choreographer$CallbackRecord.run(Choreographer.java:1408)
	at android.view.Choreographer.doCallbacks(Choreographer.java:1008)
	at android.view.Choreographer.doFrame(Choreographer.java:934)
	at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:1382)
	at android.os.Handler.handleCallback(Handler.java:959)
	at android.os.Handler.dispatchMessage(Handler.java:100)
	at android.os.Looper.loopOnce(Looper.java:232)
	at android.os.Looper.loop(Looper.java:317)
	at android.app.ActivityThread.main(ActivityThread.java:8532)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:552)
	at com.android.internal.os.ExecInit.main(ExecInit.java:50)
	at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
	at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:359)
	Suppressed: t9.g: [O.c0@70a4e90, v0.r0@6b38389, x0{Cancelling}@178ef8e, S@f4f73af]

Also, Crash Reporting is enabled in my settings but i don’t know if you’re actually receiving them.

Default feed type works fine. Also, changing the sort of posts or comments will crash the app whether I’m changing the default in settings or if i try changing my current sort order in the main part of the app. It’s like there’s some invalid/unexpected sort type that the app can’t display in the dropdown.

If I try changing the default post or comment sort type, the app crashes. I just reinstalled the app and it’s still crashing when I click that setting so I don’t think it’s anything I’m doing wrong.

Attempting to use comment navigation (jumping to next top-level comment) now crashes the app after 2 or 3 clicks. I’m guessing it has something to do with what you said about jumping to a comment on the next “page” of comments.

The comment navigation isn’t working the way I’d expect. I was expecting each push of the down arrow to jump to the next top-level comment and each push of the up arrow to jump to the previous top-level comment.

Instead, the down arrow only seems to walk down an individual comment thread and stops working when you reach the bottom of that first thread. And the up arrow just seems to jump up one comment at a time regardless of thread.

Also, the clickable area on the navigation buttons seems too small. The comment behind the navigation bar keeps expanding/collapsing if my tap isn’t exactly on the arrow icon.

I say wait a week so some of us can be your beta testers. And I promise to keep my mouth shut about feature requests to let things settle. 🤐

Also, there’s no hard rule that says you have to wait a full week. We can test it for a few days and you can still release a stable version this weekend if all looks good.

I totally agree on this one. I understand if people don’t want to use this feature, especially since it takes up part of the screen when enabled. Thanks!

I personally don’t like using volume keys for comment navigation so don’t implement that part on my behalf. 😁

You can always just scroll down to hide those buttons since the view isn’t locked. If only the bottom-half of the screen scrolled and the menu was always visible i could understand the complaints.

Honestly, I doubt people will spend that much time on the profile page such that we need to optimize its screen real estate. It’s more important that they can find what they’re looking for the first time they visit the page since they probably won’t go to it too often. That’s just my opinion though, maybe other users spend all day on the profile page.

I will say though, your mockup of sliding the menu out from the right looks great, I just don’t think it’s needed on the profile page.

The display name of “Raccoon” and the unread comments count looks great, thanks!

But I’m not seeing any difference with the “Fade read posts” option. Can you share screenshots of what you expect faded vs non-faded posts to look like?

That’s a perfectly fair solution for myself, but I’m hoping it’s easy to make this change in the code so everyone can benefit from it. I’ll definitely go this route if the code can’t be changed though, thanks!