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.

Sign up for GitHub

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

Jump to bottom

Track the user's relay list using polling #438

Open
wants to merge 5 commits into
base: master
Choose a base branch
from
Open

Track the user's relay list using polling #438

wants to merge 5 commits into from

Commits on Nov 22, 2024

  1. Update user relay-list via polling

    @ksedgwic
    ksedgwic committed Nov 22, 2024
    Configuration menu
    Copy the full SHA
    251007f View commit details
    Browse the repository at this point in the history

  2. Add user mute list sync via polling

    @ksedgwic
    ksedgwic committed Nov 22, 2024
    Configuration menu
    Copy the full SHA
    4239124 View commit details
    Browse the repository at this point in the history

  3. Plumb maybe_mutes everywhere 

    Is there a better way?  It seems that there is a large common subset
in all of these function signatures ...
    @ksedgwic
    ksedgwic committed Nov 22, 2024
    Configuration menu
    Copy the full SHA
    40fa27d View commit details
    Browse the repository at this point in the history

  4. squash: use MuteFun is_muted instead of maybe_mutes 

    Instead of passing a reference to the accounts Muted struct pass a
reference to a MuteFun which is called on each note and returns bool.
    @ksedgwic
    ksedgwic committed Nov 22, 2024
    Configuration menu
    Copy the full SHA
    082407f View commit details
    Browse the repository at this point in the history

  5. Don't pretty-print to the log

    @ksedgwic
    ksedgwic committed Nov 22, 2024
    Configuration menu
    Copy the full SHA
    800de7a View commit details
    Browse the repository at this point in the history