At least in the mobile app this (showing of posts that should be filtered out completely) seems to occur when those posts get loaded after tapping ”Load missing posts”. So it’s like the filters don’t get applied to posts loaded on demand: I just had one shown to me earlier with the ”matches filter”, ”show anyway” preamble, but now that I went to check the timeline on the same device again, said post was now filtered out completely. (It hadn’t been deleted in the meantime, I checked.)

(I couldn’t remember if the example in my web UI screenshots above was similarly loaded with ”Load missing posts”.)

As per title. Unlisted posts can not be reblogged, but the web UI still shows a reblog icon for such posts, and it can be clicked. After spinning for a while it then returns to its initial state, which is confusing (especially if you’re unaware of the limitation of reblogging unlisted posts).

The official mobile client does better: there such posts apparently don’t have the reblog icon. An alternative solution is Mastodon’s (web UI’s) way of showing a boost icon, but disabling it (so that it doesn’t react to clicks).

(The instance I’m on is pixelfed.social. The most recent post I had this issue with was federated from https://vernissage.photos/@magda/7470629220893329794#)

Attached is a screenshot of one of my filters, and of a post on my timeline matching the filter (see the hashtags at the end). There’s nothing (at all) in the console log. My handle is @uusijani@mastodon.social. The post in this case apparently comes from a federated blog.

I have a feeling that most times I’ve seen posts that should have been filtered out, they’ve been boosted ones and not OC from people I follow. But obviously it could just be that I don’t follow many people who post about things that I like to hide with filters.

Ah, apparently ”Show content warnings” on the app is the opposite of what’s ”Always expand posts marked with content warnings” in the web UI. I was confused because the former refers to the warning, whereas the latter refers to the content. There may be minor usability issue there, but I’ll leave it out of this one.

Sorry for the noise. To make up for it, #290 looks like a duplicate of this one and thus could possibly also be closed.

I have ”Always expand posts marked with content warnings” on in my settings, but CW-marked posts in the Android app still show as unexpanded.

I’m fairly sure this used to work until recently, and #87 being closed as ”completed” back in October would imply I wasn’t just imagining it.

Sounds good to me!

To correct myself, it looks like the default for the WP plugin is to federate the full content, whereas I’ve opted to just use the excerpt, so assuming most other users don’t change the default, their followers do get the full post content inside the app. I don’t know if that still includes the link back to the blog, but then it’s less of an issue if the link doesn’t go to a browser (even though the reloading behavior may still look a bit confusing).

Thank you for the workaround!

I can see the appeal of staying inside the app, and would usually prefer it myself too, but cases like this do challenge the usefulness of that model.

FWIW, I’ve not come across posts from other sites exhibiting this yet, but then again I’m not following many WP blogs, and I suspect the issue could be prevalent there, as my settings for the ActivityPub plugin are pretty much at defaults.

I’m using the ActivityPub plugin to enable following posts from my WordPress blog. The posts federate as excerpts with a URL pointing to the full post on my site.

Tapping on that URL in the Android app only causes it to reload the post (excerpt) inside the app, instead of opening the URL in either webview or a browser as I’d expect it to.

The (official) IOS app does open the URL a browser, as does Firefox on the desktop, which is why I suspect the Android app being at fault here.

I don’t know of a way to link my blog here it so that it opens in the app (which is a bit ironic), but here’s a deck link to the federated posts on mastodon.social. My personal Mastodon account is on mastodon.social.

Both my Android phone and Android tablet are affected, both are on Mastodon version 2.2.1. The phone is running Android 10 (with Samsung’s One UI 2.0), the tablet is on Android 11 (One UI 3.1).

Below is a screen recording from the Android phone exhibiting the issue: the first tap of the URL opens the federated note in single view, and subsequent taps then just reload that same view.