SpamBlocker on fdroid can block any numbers not saved to your address book. It can even make exceptions for any repeated numbers that aren’t in your contacts but call multiple times within some time period (5min, 30min, whatever). And it can temporarily whitelist a number you dialed recently in case you’re expecting a call-back.

It also has the ability to download spam phone number databases from the internet if you want, but to be honest, I tried setting up that feature and couldn’t figure it out. So while it can use a 3rd party, it isn’t required.

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.

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!

KoRn - Y’all Want a Single

Awesome! I’ll be sure to switch to the dev build!

I actually don’t like the idea of using the FAB, it “hides” these pages too much. The FAB disappears when you start scrolling and if I saw a “+” button on my profile page I would never think clicking it would allow navigation to other pages.

If anything, you could expand/collapse those 5 options at the top, or turn them into horizontal tabs rather than vertical menus. But please don’t hide them all within a “+” button. I already missed the “hide read posts” button because I never thought to click the “+” FAB on the main screen. I just assumed clicking the “+” button would be a “create post” so hiding options unrelated to post creation behind that button is extremely confusing to me.

If you’re going to hide lots of options behind a FAB, please change it to a hamburger icon (three lines) or something else other than a “+” icon.