Selfhosted
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:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
I'm working on a Rust API wrapper around the existing common API to make it easier to use. Implemented the calls that could let someone do this exact thing at scale last night.
It's nowhere near ready for production and is still missing a lot of basic API functionality even for a simple bot, but I think it'll be ready to publicly release in an alpha state within the next couple days.
That's neat. Is the idea that the bot user would enumerate and then subscribe to the communities found through the Lemmy API?
Pretty much, that would force federation. Though I don't think users in the other community would see your communities until someone from there searched one of yours.
An idea I have is giving small communities an option to run the bot on their instance, and it would add them to a list. Then, communities voluntarily participating in that list could auto-populate each other's communities through the bot. I could see spammers abusing something like this to try and flood feeds with garbage content until they're defederated though, especially on instances with open registration, so there is a downside. But that's something the community of proper users will need to be prepared to fight down the road.
Yeah, that's a slippery slope. I think that federating to receive content from an instance is fundamentally different than making your content show up on a instance that didn't ask for it. I definitely see the value your implementation would bring to new/single-user instance to populate the feed. Good luck!
If you do happen to release an alpha publicly, please do be sure to post it somewhere here - I'd love to take a look at it!
I'll keep you in mind when I do that. I've got some free time the next couple days to work on it, so I'm hoping to have something by then. So far the API calls I've implemented are
Search, ResolveObject, GetSite, GetFederatedInstances (Though it's basically GetSite), GetPosts, Login, ListCommunities, FollowCommunitySo, you know, pretty far from doing much practical work. But not bad at getting information about an instance. I want to at least have all the basic post/comment/community functionality in before I release anything. Also, I think I want to restructure what I have into a better format. Don't quite like how I set it up.
This sounds like a great idea