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

Returning users come back to empty timelines #5634

Closed
1 task
kyefox opened this issue Nov 8, 2017 · 6 comments
Closed
1 task

Returning users come back to empty timelines #5634

kyefox opened this issue Nov 8, 2017 · 6 comments

Comments

@kyefox
Copy link

kyefox commented Nov 8, 2017

I just talked to someone who came back to an empty Home after a long time away from Mastodon. It's understandable that you'd want to clear out timelines for inactive people to save space, but it's not a great experience coming back to an empty Home.

Maybe Mastodon could invoke the new user thing where they follow admin accounts when it detects someone with an existing account and an empty timeline. Or just regenerate the timeline with a friendly "welcome back" message and some useful information about major changes since the last version they used.


  • [x ] I searched or browsed the repo’s other issues to ensure this is not a duplicate.
  • This bug happens on a tagged release and not on master (If you're a user, don't worry about this).
@duxovni
Copy link
Contributor

duxovni commented Nov 15, 2017

This is happening to all of my users as well. Looking at the output of journalctl while inactive users log in, no RegenerationWorkers are being run. I also poked around at the rails console to see whether the regenerate_feed! method from app/controllers/concerns/user_tracking_concern.rb was being run at all, and it doesn't seem to be:

# Before inactive user logs in
> User.where(account_id: 666)[0].last_sign_in_at
=> Tue, 04 Jul 2017 14:45:56 UTC +00:00
> User.where(account_id: 666)[0].current_sign_in_at
=> Wed, 05 Jul 2017 22:10:52 UTC +00:00

# Inactive user logs in, sees empty home timeline
> Redis.current.get("account:666:regeneration")
=> nil

# I manually set the flag that should be set by regenerate_feed!
> Redis.current.setnx("account:666:regeneration", true) == 1 && Redis.current.expire("account:666:regeneration", 86400)
=> false
# User reloads the page
# They're now getting their feed directly from the database and their home timeline is populated
# I manually enqueue a RegenerationWorker
> RegenerationWorker.perform_async(666)
=> "deadbeefdeadbeefdeadbeef"
# The RegenerationWorker is run and finishes more or less immediately according to journalctl

@jimfenton
Copy link

This happens to me (as a returning user). Is there a workaround to get my home timeline back?

@maximevaillancourt
Copy link

maximevaillancourt commented Jan 6, 2021

Edit: the message disappeared after roughly 2 days. ✔️

This appears to be occurring today still. Didn't log into Mastodon for a few weeks, and now my timeline is empty with this message:

2021-01-05-193532_598x346_scrot

"Loading... Your home feed is being prepared!", which is from here in French:

https://github.com/tootsuite/mastodon/blob/38bc4b95625e14c542fc09f8b302f8ca6b92f6ee/app/javascript/mastodon/locales/fr.json#L365-L366

@Cassolotl
Copy link

The home timeline is populated within a minute or two, no?

@maximevaillancourt
Copy link

The home timeline is populated within a minute or two, no?

It took roughly 48 hours until the feed came back to normal. Not sure if it's a per-instance kind of issue, or a larger Mastodon source code issue 🤷

@Cassolotl
Copy link

Wow, that's a lot longer than it should be! Usually if I wait about 30 seconds it comes back.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants