Email or username:

Password:

Forgot your password?
Darius Kazemi

Hey #Hometown 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

A screenshot of the Mastodon v4 "view profile" page, with a three-dot menu opened that has the "open original page" option.
A screenshot of the Mastodon v4 "view post" page, with a three-dot menu opened that has the "open original page" option.
28 comments
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

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.

Darius Kazemi

@tithonium the patch is already written and is linked in the issue!

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.

Darius Kazemi

@ranjit what you are describing is exactly v4 behavior unchanged!

ranjit

@darius in that case, i think I like v4 behavior 🤷

Darius Kazemi

@ranjit (got this wrong, reposting) specifically in current hometown, if you click the timestamp on any post it does a "focus" and then if you click the timestamp again it takes you to the remote server in a new tab

on v4, if you click the timestamp it takes you to a contained page (as though you clicked to "focus" the post) and then clicking the timestamp from there does not do anything, you need go to three dots and then "open original"

ranjit

@darius ah, I see! Thank you!

I don't think I totally understand the implications, not having spent much time on a v4 server ... except oulipo, where I never interact with anyone non-local! I do agree with @v that the v3 behavior irritates me sometimes.

Darius Kazemi

@ranjit @v mostly, for me, it's that I expect on most social media websites to be able to right click and copy the url of the timestamp to paste a link to a given post. On v4 it instead ends up as something like

mastodon.social/@darius@friend

Which *works* but is an extra redirect

Andy K S

@darius I think the v3 behavior is an elegant compromise, where right-click will get you the original url but left-click will just focus (fwiw I can't see where this applies to profile link clicks, just to timestamps in not-yet-focused posts). I don't like opening a lot of tabs, but seeing people link to posts with unnecessarily prefixed urls has been wigging me out, akin to leaving a bunch of params at the end of a link.

Darius Kazemi

@andy I am leaning strongly towards keeping the v3 timestamp behavior and incorporating the v4 profile behavior. that would make it overall more consistent with every other social media site

Andy K S

@darius that'd make sense! though the profile link behavior I see on Hometown (web interface, Firefox) already seems to match the v4 behavior you described, minus the "open original page" – that is, any profile link I left-click opens the profile within my instance / same tab. "open original page" would be a nice addition there, since I currently only see a link to orig if there aren't many posts to show.

solipsistnation

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

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

Darius Kazemi

@datatitian I have seen discussion in the core dev team about removing that and either bringing back the old behavior or doing something different. so I am probably not going to touch it for now

NowWeAreAllTom

@darius I'd support keeping the current behavior

Andrew (Television Executive)

@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?

OldTurk🗽Focus: #FreeAssange

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

was B (this is my old account)

@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.

Darius Kazemi

@b_cavello so by "keep" you mean "do not revert the v4 behavior", yeah?

was B (this is my old account)

@darius I think so, but after reading more replies, I’m realizing I don’t fully understand the situation anyways, so 😅😅😅

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

Darius Kazemi

@candle agree. Definitely keeping timestamp as permalink, at this point

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?

Go Up