Rerouting with private mode, more robust timeline error handling #2606

Closed
shpuld wants to merge 4 commits from gitlab-mr-iid-1339 into develop
Owner

Todo: when frontend gets more granular private mode info, change routing redirects to match it

Todo: when frontend gets more granular private mode info, change routing redirects to match it
Owner

leftovers

leftovers
Owner

uh oh

uh oh
Owner

how private are private instances? With this you can't even link to a post or user profile, it would redirect to /about

how private are private instances? With this you can't even link to a post or user profile, it would redirect to /about
Author
Owner

that's the thing we can't know because of lacking api (people on BE/admin side should know about this problem), I'm trying to figure out a good middle ground before I merge since otherwise this can be pretty bad for a lot of instances that just private twkn or something

that's the thing we can't know because of lacking api (people on BE/admin side should know about this problem), I'm trying to figure out a good middle ground before I merge since otherwise this can be pretty bad for a lot of instances that just private twkn or something
Owner

closing this as it's woefully outdated now and needs a re-do

closing this as it's woefully outdated now and needs a re-do

Pull request closed

Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
pleroma/pleroma-fe!2606
No description provided.