Why is anyone using an app to access a #freesoftware project like #Mastodon that's free and doesn't track users or violate #privacy?
Wouldn't it make more sense to focus that effort on #mobileweb and let everyone use the same interface regardless of platform? The way the web intended.
@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.
Wait. I'm on Mastodon.social. if I load the url:
Https://Fosston.org/joeldebruijn
I will not be logged in at Fosston.org and will be unable to follow. Correct?
But if I load:
Https://mastodon.social/@joeld[email protected]
I will get your profile and I can follow from my home server.
What's the problem?
@ParanoidFactoid @joeldebruijn @shoq Well, probably not actually the Kerberos protocol, as it requires a trusted third party, i.e. a centralized server, which of something you cannot have in a decentralized system like Mastodon.
But maybe you could build something on top of the OAuth or OpenID protocols.
@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.