@Comrade Ferret Mastodon's Web UI can make things quite a bit complicated in this regard, yes.

Usually, if the post is on the server you're seeing it on, the link to the original is behind the age of the post in the upper right corner. If not, it's behind "Open original page" in the menu in the bottom right corner which exists only then.

And some servers seem to be configured to work differently yet again.

#FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #MastodonWebUI
Netzgemeinde/Hubzilla

@sb It would be even better if Mastodon's web UI had an option not to short links either.

I mean, visually, literally, it obscures part of the URL and adds "..." if it is long enough. It might not help promoting the idea that it's ok to just put non-cryptic URLs without shortening them first, but it sure annoys me.

And at least here that also makes it harder to select the address to paste it somewhere else, if it's at the end of the post.

#MastodonWebUI

@personamatters Now I'd suggest this is *another* good reason to avoid a design that mostly tries to be like TSNFKAT :-P

#MastodonWebUI

@faraiwe I think your example will not work for people who are using Mastodon's web UI and have set the option to always expand CW'ed posts.

#MastodonWebUI

@cub80_appleby @FediTips Now if having in-text hashtags is a big problem, is there any chance this can be somehow addressed no matter what the post has? Say, an option in clients (including the official web UI) to list hashtags at the end even if they're inline? (Instead showing inline hashtags as regular words)

#MastodonWebUI

@job
(And that's a good summary of Mastodon: not as good as #USENET. Federation works better there, "following" topics works better there, threading works better, keeping track of unread posts works better...)

(Maybe if Mastodon's design goal was more of making a federated social network and less of making a Twitter clone... #MastodonWebUI is a disaster that could be easily improved or avoided, but I guess it must have all the endless scroll and behave like tabbed browsing weren't a thing...)

@job this is one of the major issues I have with some Mastodon interfaces. #Brutaldon does this too, I think, but at least it's light. Now #MastodonWebUI doing this with all the processing power it requires is ludicrous.

Yeah, I'm eventually going to end up with a Mastodon client that is pretty much a #NetNews client...

@JasonW @partlyhuman You can also check the hashtags you're interested on on other instances when these allow doing so without login. For example, for Mastodon at bitbang.social, you can check "retrocomputing" either using #MastodonWebUI

https://bitbang.social/tags/retrocomputing

or the RSS feed

https://bitbang.social/tags/retrocomputing.rss

CC:ing @FediTips in case they want to add something else. It's probably thanks to them that I learned the ".rss" trick!

Mastodon

Hey, do you like old things? Beeps and boops? Welcome home!

Mastodon hosted on bitbang.social

@privateger @aks No, there's a bunch of fediverse web interfaces that are beyond silly. I'd really go with "if it's text and does not show without JS, then it's broken". You should be doing something very specific that's not achievable otherwise to justify loading static content using JS.

And then enter #MastodonWebUI v4 that seems to want to load everything before the post. Was that thing designed for browsers that don't do tabs? And doesn't v3 just show the content right away?

@ann3nova At this rate, #Mastodon should have features to boost w/ CW and/or hashtag. Or is absence of that intentional? So far the only way seems to be to link the post in a new post. At least on #MastodonWebUI and #Brutaldon, that means users can't follow the link to open in the current instance (there'll probably be clients that handle such links better?).

As usual, if I were to list a few things that would be interesting to see with the post content, I'd also end up reinventing #MIME...