I use Linux on my personal laptop, my work laptop is a Mac, but my desktop (main computer) is still Windows largely cause of video games. Lot of the games I like to play don’t work or require more tweaking than I’m willing to invest to get them running on Linux. I also play flight sim and racing sim games with peripherals a lot, and if the game support on Linux seems bad, the support for those peripherals is even worse lol.
Immich for personal photos and pictures I take
Lychee as an image host for funny pictures, memes, and publically sharing photos
Of course they’re expensive think of how much labor it takes to put them in the damn shells!
Seems like a good chef/recipe writer/whatever he is, but I dislike his personality/TV presence and can’t stand watching him.
The way it was explained to me is that every Lemmy instance is basically a full on “reddit” in that it’s a link aggregator, supports user made communities (ie: subreddits), commenting, etc. You can run Lemmy in private mode and this is exactly how it functions!
On the side of what “federation” is, it’s that all the instances can (theoretically) communicate with each other and share posts and content amongst themselves. So let’s say you make a post on lemmy.world, because my instances “federates” with lemmy.world I am able to see your post and comment on it from my instance. Lemmy.world and my instance periodically update each other with posts our respective users make. Your post lives on Lemmy.world, my comment replying it to lives on mine, and when I post my comment Lemmy.world receives a notice that I’ve done so, which then creates a notice for you that I’ve made the comment blah blah.
The benefit to federation mainly is that it gives a lot of control to users on how the platform functions. Firstly it doesn’t congregate the entire userbase to a single company and/or site. No single instance should remotely be as large as reddit. But because they communicate together, you can approve/deny what instances (as an instance admin) you’re “federating” with. Don’t like the users and moderation policy of another instance? You can “de-federate” with them and block their content from showing up on your instance.
I’m a big fan of the saying that “time you enjoy wasting is not wasted time” for that exact reason. If you want to do nothing then do nothing, that’s perfectly okay!
What is sad, though, is that I feel like this is saying you get so tired and burnt out from working just to survive that even when you get time off you don’t get to enjoy it or do things you want because you’re just so burnt out from working.
I don’t trust those corn field carnival rides either, those things terrify me even more than the submarine, so speak for yourself lol.
Not entirely. There’s a couple larger subreddits I enjoy and tbh it’s still my go-to for doomscrolling.
However my desire to interact with reddit couldn’t be any less. Zero desire to post or comment anything due to the sheer hostility of the site to it’s users.
I think if lemmy continues to grow in userbase it could completely replace reddit, but not at this immediate moment.
I see a couple ways you could do this. For what it’s worth, I think Lemmy may be close enough to what you want out of the box. I run my own private instance similar to how you’re laying out, although I don’t “disable” registration, I do require account approval by an admin. I’m sure at some point I’ll start getting spammed with registrations, but thus far it hasn’t been an issue. Similarly, federation can be disabled as a setting in the admin section of Lemmy.
What you’re laying out on the technical side is also absolutely possible. Lemmy has a JS client you can pull in as a dependency to manage the calls from Javascript, but it also describes the HTTP endpoint for said call, so you could make your own calls using a separate back end service (ie: after your form submits it makes the call over to your Lemmy instance to register the user).
Here’s the register
call specifically, which registers a new user on your instance: https://join-lemmy.org/api/classes/LemmyHttp.html#register
However, note that they would still not be “approved” (if your instance required approval to join), but you could just make another API call to complete that process: https://join-lemmy.org/api/classes/LemmyHttp.html#approveRegistrationApplication
As another option, I haven’t dove into the actual code, but to the best of my knowledge Lemmy is ultimately just interacting with a Postgres database, my guess is you could likely also connect to this database and directly insert the appropriate rows to create your new user accounts. Definitely use some caution with this approach though, ensure you’re using separate database users with appropriate permissions for each application. Additionally, know that if you write code to handle custom user registrations by writing straight to the DB, you’ll have to be mindful of updates to Lemmy that change the DB schema for that table will (most likely) break your registration script/code.
Lastly, if you really wanted to, you could just fork Lemmy itself! The UI and API are completely separate services, there’s nothing stopping you from forking the UI part of the project and applying your own custom changes to the registration flow for your own instance!
I dunno what the fuck Valve put in that thing but a hot Steam Deck has a scent I could pick out of a landfill it’s incredible lol
Enjoying it a lot. Set up my own instance to try out, and exploring a lot of others. I enjoy the community a ton!
That makes a lot of sense and where I’m leaning towards as well
While my homeserver still has plenty of resources to spare, I see a lot of them going towards multiple DB containers. It’s nice for “segregating” the containers, but backups are also a pain, gotta plan backups/restores for multiple DBs
Same story with an s3 (well, minio) instance running. Seems like it would make more sense to centralize DB and file operations and having different services talk to them. Then if I ever needed to move them into separate servers, it wouldn’t be as big a move.
Thanks!