You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hashtags in posts on Mastodon from at least Hubzilla are shown as links to a hashtag search at the post's origin rather than to a hashtag on Mastodon
#4245
Open
1 task done
JupiterRowland opened this issue
Feb 5, 2024
· 0 comments
Tusky seems to have a problem with handling hashtags in posts that were sent from (at least) Hubzilla to Mastodon.
I guess Tusky is built against hashtags always including the "hashtag character" (#) because that's how all ActivityPub-based projects do it, especially Mastodon. Like so:
A little-known fact, however, is that Friendica, Hubzilla and (streams) don't do that. They start the actual tag that works as a link after the "hashtag character". Like so:
This confuses the UIs of a lot of projects that are built under the assumption that the whole Fediverse acts like Mastodon, Tusky included. The result is that Tusky treats Mastodon-style hashtags like the first example as expected, namely as a hashtag on whichever instance the post is read on. Hashtags like the second example, on the other hand, are treated like external links and, at least on the UI, rewritten accordingly by attaching the domain of origin, thus making them useless as hashtags.
I know this happens with posts which come from Hubzilla. But since hashtags from Friendica, Hubzilla's first ancestor, and (streams), Hubzilla's youngest descendant, look and work the same, it's safe to assume that posts coming from these lead to the same result.
Steps to reproduce:
Have a Mastodon account, e.g. on mastodon.social, and a Hubzilla channel, e.g. on zotadel.net. Don't forget to turn ActivityPub on on Hubzilla.
Follow your Hubzilla channel with your Mastodon account. Confirm the connection on Hubzilla, thereby following your Mastodon account back.
Connect Tusky to your Mastodon account.
Write a post on Hubzilla that contains the hashtag #Hashtag.
Wait for the post from Hubzilla to appear in Tusky.
Once it has appeared, check what the hashtag looks like.
Tusky seems to have a problem with handling hashtags in posts that were sent from (at least) Hubzilla to Mastodon.
I guess Tusky is built against hashtags always including the "hashtag character" (#) because that's how all ActivityPub-based projects do it, especially Mastodon. Like so:
#Hashtag
A little-known fact, however, is that Friendica, Hubzilla and (streams) don't do that. They start the actual tag that works as a link after the "hashtag character". Like so:
#Hashtag
This confuses the UIs of a lot of projects that are built under the assumption that the whole Fediverse acts like Mastodon, Tusky included. The result is that Tusky treats Mastodon-style hashtags like the first example as expected, namely as a hashtag on whichever instance the post is read on. Hashtags like the second example, on the other hand, are treated like external links and, at least on the UI, rewritten accordingly by attaching the domain of origin, thus making them useless as hashtags.
I know this happens with posts which come from Hubzilla. But since hashtags from Friendica, Hubzilla's first ancestor, and (streams), Hubzilla's youngest descendant, look and work the same, it's safe to assume that posts coming from these lead to the same result.
Steps to reproduce:
#Hashtag
.Expected and desired result:
#Hashtag or #Hashtag
Links to the hashtag itself on the Mastodon server on which your account is.
Fully functional as a hashtag in Tusky.
Actual result:
#Hashtag (zotadel.net)
Links to the hashtag search to the Hubzilla hub on which your channel is.
Not functional as a hashtag in Tusky.
On an interesting sidenote, the Web UIs of Misskey and, as far as I can tell, all its forks show the same bug. Mastodon's default Web UI doesn't.
The text was updated successfully, but these errors were encountered: