Skip to main content


!Friendica Support One of the "issues" I constantly experience in # while using this via apps is: Hashtags and accounts look and feel different than while being connected to Mastodon. In example #: Connecting to Mastodon, in hashtags the "# is part of the link and clicking that link makes the app open a view displaying posts for that hashtags. Connecting to Friendica, the "# in a hashtag apparently is not part of the link, but clicking the hashtag will open an external browser and display content for that particular hashtag in a Friendica web interface. This is a bit weird, hard to describe and hard to explain (maybe I'll add screenshots). For accounts, this is similar. Any idea why it happens this way...?
in reply to Kristian

@Kristian @Friendica Support I'm also seeing this however I assumed you have a good reason to do it the way it's currently implemented.
There might be other API differences e.g. You are returning unlisted posts as part of the network timeline expecting clients to filter out them. Mastodon and its forks are not doing it.
Full content of posts with CW are sent to clients and clicking show more has no effect.
I've noticed all of this by using # on Android.

Friendica Support reshared this.