GitHub - jheidecker/lemmony: A better "All" browsing experience for small Lemmy instances
github.com
A better "All" browsing experience for small Lemmy instances - GitHub - jheidecker/lemmony: A better "All" browsing experience for small Lemmy instances

v0.0.4 - Per requests and concerns: Defaults changed and options added to prevent overloading servers, hitting rate-limiting, filtering to top x communities, etc!

Thanks for your support!

  • eroc1990@lemmy.parastor.netEnglish
    9·
    1 year ago

    For anyone who might know:

    So if I’m understanding this right, the bot account you create for this is the one subscribing to every community, so it’s known to the local system, right? As long as I’m not mixing up my main account and my bot account, there should be no observable change on my own account?

    How is storage affected on this? If the bot account is subscribing to a number of communities across the fediverse, all that remote content is going to take up quite a bit of space, no?

    And will 2FA be supported at any point?

    • hawkwind@lemmy.managementOPEnglish
      53·
      1 year ago

      So if I’m understanding this right, the bot account you create for this is the one subscribing to every community, so it’s known to the local system, right?

      Yes

      As long as I’m not mixing up my main account and my bot account, there should be no observable change on my own account?

      Correct, I have it functioning this way and it works great.

      How is storage affected on this? If the bot account is subscribing to a number of communities across the fediverse, all that remote content is going to take up quite a bit of space, no?

      It does and it will continue to grow. This not not something the tool takes care of, not cleaning up anything old or stale. Space management and “unfollow” is on the roadmap! Currently I can only speak for myself and it is EVERYTHING and it is about 0.25 GB / day of database, and 6-10 GB / day of images.

      And will 2FA be supported at any point?

      Not on the roadmap. I don’t know how api calls in general work with 2fa since I have not tested or enabled it on my instance. :( Sorry.

      EDIT: Changed database/pictures ratio after double checking actual numbers and not looking at used filesystem. :(

      • eroc1990@lemmy.parastor.netEnglish
        2·
        1 year ago

        Hey, thanks for replying! Good to know about the subscription ownership. I only ran the discovery portion of the script just to dip my toe in the water, because I feared what would happen if I subscribed. That said, if I use the discovery flag, that’s just exposing the different communities to my instance, right? It’s not going to retrieve any remote content?

        Good to see that storage management is roadmapped. I probably won’t invoke the Subscribe side of this for my bot account until then.

        Understandable about 2FA. I’ll just be smart about my password usage and watch for any updates on that.

        Thanks again!

        • hawkwind@lemmy.managementOPEnglish
          3·
          1 year ago

          It retrieves the last 10 posts and adds the community reference to your local database. It is the same as putting “!community@instance.com” in the search box and clicking search. The retrieval happens whether you look at the results or not.