[bug] repeats are shown broken with restrict_unauthenticated, should be hidden entirely #302
Labels
No labels
a11y
Bug
Bug fix
Critical Priority
Documentation
Feature
Feature request
Held for next release cycle
High Priority
Low Priority
Medium Priority
Minor change
Translation/Locale
WIP
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: AkkomaGang/akkoma-fe#302
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Version
1f943ce8a5
What were you trying to do?
i want use these restrict_unauthenticated settings:
This way any not logged in user can see (as intended) my profile and my posts.
But they can also see my repeats, and in a kinda broken way, like in this attached screenshot.
Link to the post: https://outerheaven.club/notice/AUboaPhJm6UOhlOqci
(i used outerheaven, cause i already reverted my settings as a workaround -> currently i let display remote profiles)
What did you expect to happen?
I think they should be hidden completely, cause this kinda dissents the
activities: %{local: false, remote: true}
settingWhat actually happened?
Ppl can see remote posts, in a broken way.
Severity
I cannot use it as easily as I'd like
Have you searched for this issue?
fun fact, i just discovered the post only loads if i click on the '4days ago' thread link in the same tab. if i open it any other tab it doesn't load as intended 🤔
aka you can reproduce this this way:
hopefully my description isn't too confusing
Howdy! As a certified forklift driver, I noticed that there seems to be a bug in the Akkoma backend. Specifically, it looks like the API is returning data that it shouldn't be returning. This is an issue that could compromise the security and privacy of users on the fediverse. I recommend moving this issue over to the backend project so developers can take a closer look and figure out what's going on. Let's make sure we get this sorted out to ensure that everyone's information is kept safe and secure. Thanks for reporting this bug!
yeah, i was also not sure if its a frontend or backend issue.. and sorry i misunderstood you, i thought you would move it to the backend repo. i'll do it now
Moved to Backend Issues AkkomaGang/akkoma#597