Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Bubble servers" feed pulls from "All servers" instead #28

Closed
eblu3 opened this issue Dec 3, 2024 · 3 comments
Closed

"Bubble servers" feed pulls from "All servers" instead #28

eblu3 opened this issue Dec 3, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@eblu3
Copy link

eblu3 commented Dec 3, 2024

Steps to reproduce the problem

  1. Open "Live feeds" tab
  2. Click on "Bubble servers"

Expected behaviour

Only posts from servers that were manually curated by instance staff should appear.

Actual behaviour

Posts from all servers appear instead.

Detailed description

No response

Mastodon instance

wetdry.world

Mastodon version

v4.4.0-alpha.1+chuckya

Technical details

Previous discussion indicates that this bug varies from user to user and appears to work when you're logged out, as evidenced by opening the API endpoint (e.g. https://wetdry.world/api/v1/timelines/public?bubble=true&only_media=false) in a private window. This might indicate a configuration/database error? It's worth investigating.

@eblu3 eblu3 added the bug Something isn't working label Dec 3, 2024
@neatchee
Copy link

neatchee commented Dec 3, 2024

A clue: When this issue occurs, streaming inserts still appear only for servers in the bubble. The improper population of the feed appears to only happen at page load

@TheEssem
Copy link
Owner

TheEssem commented Dec 3, 2024

Quick question, do either of you have any account domain blocks or locale filters applied?

@TheEssem
Copy link
Owner

TheEssem commented Dec 3, 2024

I think I just figured out the cause of the issue; the scopes for posts in the bubble and posts from non-account-blocked servers seem to conflict with each other, causing the latter to be applied instead.

Attempting to figure out how to resolve this.

TheEssem added a commit that referenced this issue Dec 3, 2024
… by a user

Fixes #28. There's probably a much better way to do this...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants