Open tribela opened 1 year ago
Although this is not a design decision I agree with, limited federation mode is designed to not have anonymous viewing possible, and that was the case before 4.0 too. However, before 4.0, you used to have a 401 page or a log-in page, not the Web UI with most of it not working.
It sometimes work because if queried by user, it returns 200 OK with
cache-control: public
It is also a security hole if 401 was intended behaviour
That's indeed an oversight! That being said, I'm in favor of having the decision to hide the about page on LIMITED_FEDERATION_MODE
be revisited.
But cannot login/signup via official app is a real problem.
Indeed! Does that occur because the request to /api/v2/instance
fails or something else?
Yes, /api/v2/instance is the main problem. But I didn't check oauth and other apis
Edit: I walked some existing users of my LIMITED_FEDERATION_MODE instance through setting up the official mobile app recently, and they didn't run into problems -- so I guess I misremembered the existence of a problem here, or something has changed since I encountered it. In any case, thanks!
Chiming in as another admin who would appreciate a way to
The login issue (mastodon/mastodon-android#637) is still a problem for app users. It's necessary to disable limited federation mode when adding a new user, so they can log into the app, then re-enable it afterward.
Same problem here, when limited_federation is turned on, the app is not able to login into the mastodon instance. Even when using an invite-link or some other schemas of server addresses.
Steps to reproduce the problem
...
Expected behaviour
Should work fine
Actual behaviour
Some functions are broken
Detailed description
/api/v2/instance
is forbidden and it causes "it doesn't seems to be mastodon server"/api/v2/instance
/api/v2/instance
is forbidden/api/v1/trends/*
It sometimes work because if queried by user, it returns 200 OK with
cache-control: public
It is also a security hole if 401 was intended behaviourSpecifications
v4.1.0rc3