Unsubscribe?

[sanicki]

Does the sync also unsubscribe if the community subscription does not exist in the "Main Account"? If not, should it?

Example 1:

I run the script once. It subscribes "Account 1" to all the communities subscribed to by "Main Account."

Later, I unsubscribe from a community on "Main Account."

If I run the script again will that community subscription be removed from "Account 1"?

Example 2:

I run the script once. It subscribes "Account 1" to all the communities subscribed to by "Main Account."

The instance of "Main Account" temporarily goes offline, so I start using "Account 1."

I subscribe to a new community using "Account 1" before my "Main Account" instance is back online and I switch back.

If run the script again will that community subscription be removed from "Account 1," added to "Main Account," or remain on "Account 1" without being added to "Main Account"?

[Ac5000]

Thank you for raising this issue/question.

Does the sync also unsubscribe if the community subscription does not exist in the "Main Account"?

Currently when the script is ran, it pulls a total list of subscribed communities between all accounts. Then attempts to make all accounts match that total "pool" of subscriptions. This is regardless of account name/order.

Example:

Account 1

Subbed to Community 1 and Community 2

Account 2

Subbed to Community 1 and Community 3

Script is ran

Account 1

Subbed to Community 1, 2, and 3.

Account 2

Subbed to Community 1, 2, and 3.

If not, should it?

The current method/script helped me treat all my accounts as a kind of "pseudo single account". However, you raise a good issue in that I didn't think of cases where you'd unsubscribe.

What I will do is attempt to make an alternate function that focuses on making all accounts match the "Main Account". E.g. Subscribe to accounts that are subscribed in "Main" and unsubscribe to accounts that are not. This will be configurable with a flag I will add to the config file. Unfortunately I haven't found an easy way to identify which account/action was most recent or I'd make the updates happen based on most recent actions between accounts.

I'll respond to/close this issue once I complete the update. It might be a day or so as I am currently a bit limited on time.

Thank you again, and let me know if you need any further explanation or any other questions.

[owenlejeune]

@Ac5000 any updates on this? this use case is the exact use I was looking for a solution for when I found this project

[Ac5000]

@owenlejeune I have unfortunately not touched this project in quite some time. (Looking at my last commit, I can't believe it's been over a year...) I do remember starting work on the "unsubscribe" part of things, but that was quite some time ago.

Since I last worked on things, Lemmy has had several updates to the API and various systems that I would need to look in to. I remember that I was facing some issues with dealing with 2FA on accounts and accidentally almost bricked/lost one of my instance accounts. Part of that was because of server stability (at that time, I remember servers were struggling to stay up), but part of it was just because of my admittedly low skill level as a developer. Because of that, I was hesitant to continue work as I did not want to be the cause of someone having a similar experience. Also, I had not seen/heard of people still being interested in this project.

All that being said, I can take a look at things over the next week or so and see if I can update things and get this feature working now. I will send a reply directly to this issue and tag you when I decide what I plan to do. (Continue/fix, or decide to abandon.) Otherwise, feel free to fork/clone this repo and attempt things yourself if you have Python skills. The code is pretty basic and I commented/doc-stringed most things to remind myself how it was working.