Selfhosted

39435 readers

4 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago

MODERATORS

[email protected]

207

UPDATED: lemmony: A (better) better "All" browsing experience for small and large Lemmy instances (github.com)

submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]

68 comments fedilink hide all child comments

v.0.0.6

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!

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago) (1 children)

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. :(

[–] [email protected] 2 points 1 year ago (1 children)

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!

[–] [email protected] 3 points 1 year ago (1 children)

It retrieves the last 10 posts and adds the community reference to your local database. It is the same as putting "[email protected]" in the search box and clicking search. The retrieval happens whether you look at the results or not.

[–] [email protected] 2 points 1 year ago

Gotcha. Well that was a miscalculation on my part haha. Good to know for the future, though.