Email or username:

Password:

Forgot your password?
Shoq's posts Post Back to profile
Top-level
Éamonn

@ParanoidFactoid @shoq The individual web UIs of the Mastodon servers will probably never be able to fix the cross-server follow/boost/like usability barriers that exist now, because of cross-server web/JavaScript security barriers.

Native third-party apps don't have these restrictions.

Though, as a compromise maybe third-party web apps like Pinafore or Elk, can also solve these problems.

9 Jan 2023 at 4:34 | Wall-to-wall | Open on social.coop
5 comments
Paranoid Factoid

@eob @shoq

I don't understand this argument. Are you speaking specifically to mobile browser implementations differing from desktop?

9 Jan 2023 at 4:44 | Open on mastodon.social
joeldebruijn

@ParanoidFactoid @eob @shoq
No is a browser thing in general.
If I click a profile on another instance I cant follow because I am not logged in there.

9 Jan 2023 at 5:24 | Open on fosstodon.org
Paranoid Factoid

@joeldebruijn @eob @shoq

Wait. I'm on Mastodon.social. if I load the url:

Https://Fosston.org/joeldebrui

I will not be logged in at Fosston.org and will be unable to follow. Correct?

But if I load:

Https://mastodon.social/@joeld

I will get your profile and I can follow from my home server.

What's the problem?

9 Jan 2023 at 5:36 | Open on mastodon.social
Paranoid Factoid

@joeldebruijn @eob @shoq

Also:

Kerberos single sign on, problem solved.

9 Jan 2023 at 5:37 | Open on mastodon.social
Éamonn

@ParanoidFactoid @shoq Both mobile and desktop browsers have the same restrictions. In general they store data for each web site separately in a way that makes it hard to write browser-only apps that seamlessly talk to multiple web sites.

Because each Mastodon server's built-in web UI is at a different web site, it is hard to create frictionless user flows that span across different Mastodon servers.

9 Jan 2023 at 5:41 | Open on social.coop
Go Up