{"p":"","h":{"iv":"ROXSYW+cfvEbFHu5","at":"ocxplSQjdRC3tXEtB/9/wg=="}}

Hey users, I'd like feedback on this issue: github.com/hometown-fork/homet

Basically, in Mastodon v4 when you click to view someone's profile it takes you to a page like the attached image. The only way to view their page on *their* server is click the three-dot menu and select "open original page".

Same for viewing individual posts, see attached image.

I am considering keeping the current-Hometown behavior where clicking the profile image or post timestamp takes you to the remote server

12
Share
Share on Mastodon
Share on Twitter
Share on Facebook
Share on Linkedin
˗ˏˋ wakest ˎˊ˗

@darius one of the main issues of the new behavior is that people copy those links and use them elsewhere, but they are not the real links, so this has complications

I was seeing all sorts of links like
social.wake.st/@darius@friend. in peoples bios on twitter so its definitely a problem out in the wild

0
2y
Martin, Regulus Tithonium

@darius I've been annoyed at the behaviour change on the profile image. If you revert it, I'd love it if you shared the patch.

1
2y
ranjit

@darius i have what's probably the worst possible answer, which is that i'd like to be able to choose.

Thinking about it a little more, if a regular click always keeps you inside the web client (like v4 if i understand right) but you always have a menu option for "open original page" which always sends you to the external page (is that what v3 does?) then both options are always available, though external page is one step farther.

1
2y
solipsistnation

@darius I’m not running hometown, but yeah, going straight to the remote profile makes more sense.

0
2y
Will 🌹🏴

@darius don't know if you already noticed that the "proceed to follow" flow was removed from remote profiles in v4, so might consider reverting that as well or else you end up in a dead-end that tells you to copy the URL and go paste back in your home server's search

2
2y
NowWeAreAllTom

@darius I'd support keeping the current behavior

0
2y
Andrew (R.S Admin)

@darius So does the page that it takes you to on your instance include posts that your instance is otherwise unaware of? Or have they just made it harder more generally to see posts that haven't federated to you?

1
2y
OldTurk🗽Focus: GA: Early vote!

@darius (not on hometown myself but like the current behavior)

0
2y
it's B! Cavello 🐝

@darius will soon be transitioning to hometown instance and casting a vote for keeping things in one’s own instance. I’m sure there was some good reason for the change, but it’s super confusing and I think most mobile and other clients will use the “own server” approach, so it will help keep browser and client more consistent/less confusing, at least for folks like me.

1
2y
candle

@darius i would like some one click way to go to the original post--its the only way to see all the replies and thats something i would do on any remote post. i guess i think of the timestamp as the home of the "permalink" which should be the original server of the post imo

1
2y
Diego Ramírez

@darius I'd prefer the 3.5 behaviour!!

0
2y
Paul-Gabriel Wiener

@darius I'm not sure I'm really tracking.

I prefer to stay within my own server so I can more easily interact with their posts, and then click over to their server if I need to scroll back to see their earlier stuff.

What we have now mostly works for me. Especially in the advanced web interface, where it loads in the third column. I have a working follow button and I can reply directly.

Also: Do you have a rough idea of when HT will go to Mv4?

1
2y
Replies