Conversation
Ah yes love it when Mastodon Network ™️ Users post links of other people's posts and these links point at their own instance, not the actual post links
1
0
3
Unironically this only started happening with the exodus from Twitter, mastodon 4.0, and with technologically literate people that share via the address bar not the copy link feature
3
0
2

@charlotte What difference does it make? The instance should automatically forward the links to the correct instance anyway. blobfoxdetective

1
0
0
@charlotte That implies that it is a UX issue more than anything else. I don't think it is a good idea to blame users who may not be used to using the app for issues like these. Since doing so will probably not lead to any improvements for the UX.

How to solve this is a good way is probably another issue, what could you do? Warn users if they try to post a non-canonical link or something?
1
0
0
@kepler so do link shorteners like bit.ly or t.co
1
0
0
@erk it doesn't appear to be an issue with less technologically literate people, probably because the only way they know how to share a link is by clicking the share button in the context menu like on mobile apps
1
0
0
@erk also dedicated apps do not have that issue at all
1
0
0

@charlotte Except mastodon instances don't collect data on who clicks through on a link blobfox3c

1
0
0
@kepler point is that it's the same kind of blight

urls are meant to point at the page you want to share, not some other random page that just so happens to redirect there
1
0
0
@charlotte Which even more implies it to be UX, if you want people to change how they do things you will need to tell them in some way. It is neither scalable or nice to be told by other users that your post is wrong because it uses non-canonical links. Which is why I think it should be done sooner.
1
0
0
@erk mastodon's ui makes it harder to do that, yeah

Here on akkoma it's much more difficult opening a single post on the timeline
0
0
0

@charlotte URIs are just meant to point at a resource. There's a lot of instances where, if your chief audience is people on your instance, it's actually more beneficial to point at that resource that's stored on your own instance rather than the original instance. For as great as Mastodon is, it's a little cumbersome to have to move a post from another instance back onto your own.

1
0
0
@kepler is it that cumbersome? Boosts and quote boosts don't appear as links on the timeline, then again John Mastodon doesn't like quote boosts. Interacting with remote posts is only cumbersome because mastodon 4.0 made it cumbersome, previously you only had to press the interaction icon and enter your instance name
1
0
0

@charlotte Even during 3.0 it provided a link to paste back into your instance. I don't think that's really changed. But regardless, both options are definitely cumbersome for the average user.

1
0
0
@kepler it's something that can definitely be solved by clients (in fact tusky tries to do just that with moderate success), and linking to your own instance for a remote post breaks that
1
0
0

@charlotte Breaks it how? If I paste a link from my Meow profile onto CubHub of a federated post hosted on Meow from a non-Meow profile, it'll resolve to the original post just fine.

1
0
0
@kepler opens in browser for me, other links like that have opened the most random things, most recently someone unrelated's profile
1
0
0
@kepler oh it 404s so wth is mastodon doing with my instance links
1
0
0
@kepler as far as I can tell what it is doing, it's searching for the url and opens the first post/account result if something came back

This instance has FTS though and unlike mastodon it actually works so it has the tendency of opening up random posts

And akkoma rightfully doesn't resolve through redirects
1
0
0
@kepler yeah no this goes to an account of someone who is not on your instance nor on mine but just so happens to share the same name as me
1
0
0

@charlotte I don't follow. The link still resolves back to your original post from your account on your instance.

1
0
0
@kepler if I click the link in tusky it leads to a random user account because of tusky's fediverse link resolve feature
1
0
0

@charlotte If I click the link in an incognito tab in Firefox it redirects to your post which makes me think it's more of an issue with Tusky. It feels more like an issue with the fundamental infrastructure of ActivityPub and the Fediverse than with user choice and server software.

1
0
0

@kepler it’s an issue with the fact that it’s a redirect link, if you post the link directly it will open the correct thing. What it does is that it takes the link and searches it with the search option and redirects you to the first search result (which is kind of a bug) but thanks to the absolutely unnecessary redirect, the search doesn’t return the post that you linked to in the search results

1
0
0

@charlotte Shouldn't ActivityPub have it as part of the spec to let a client resolve the URI of the federated post to the original post without needing a redirect?

1
0
0

@kepler activitypub is only relevant for server<->server communications. clients use different protocols, like the mastodon api or the misskey api to talk to the server, and mastodon’s way of resolving posts is searching for them in the search box

1
0
0

@charlotte I mean I'm aware of how it works, just more criticizing the way it works >.O

1
0
0

it works just fine until someone posts redirects

and yeah the client implementation can be improved (i.e. check that the resolved url is the linked url, ignoring uri parameters)

2
0
0

@kepler but especially after applying that fix, these redirect urls would be the only ones that would just not work with the post resolving feature because these links should point at the post instead not somewhere else

0
0
0

@charlotte I guess I just mean it should be part of the spec on how URLs are structured. Instead of each implementation having their own ID for posts, just... have the URL basically include the link to the original post.

1
0
0

@kepler yeah you do that by posting the link to the post. the link you see in the address bar is the frontend URL which only exists so that you can refresh the site without losing the location. imo it would be clearer if webapps used the # component of the url instead of the path compnoent

1
0
0

@charlotte My point is that ActivityPub is a W3C standard so I feel like they could indicate what the URL structure should be for federated posts, and that structure should include some way to parse the URI for the original instance's post.

1
0
0

@kepler in activitypub the post ID is the URL of the post. mastodon actually makes this readily accessible because you can request the activitystreams2 object by appending .json after the object id

if i request your post, i get a post id of https://cubhub.social/users/kepler/statuses/109709255526297018 and that’s also the canonical URL of the post

1
0
0

@charlotte you'd think being an admin I'd read more documentation ;;;

0
0
0
@charlotte
That i because on more evil platforms the copy link feature gives a link with tracker
1
0
0
@miifox so does the address bar url
2
0
0
@miifox also copying the address bar link on the fediverse allows for more tracking than if tracking info was added (if i came across instances that added such info to their links i will write an MRF that nukes that tracking info)
0
0
0
@charlotte
Not always.

Share button on tumblr: https://at.tumblr.com/miifox/706764123484127232/gsjeajdm0k06

From the adress bar:
https://miifox.tumblr.com/post/706764123484127232

For bonus points: the former, which was shared from the app, does *not* open in the app when shared inside the app. But that's classic tumblr.
0
0
0