this post was submitted on 10 Aug 2021
23 points (100.0% liked)
Open Source
31135 readers
362 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
- !libre_culture@lemmy.ml
- !libre_software@lemmy.ml
- !libre_hardware@lemmy.ml
- !linux@lemmy.ml
- !technology@lemmy.ml
Community icon from opensource.org, but we are not affiliated with them.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
There's no limited registration or account approval features yet, but you can close the registration completely or open it at any time if you're an administrator. Anyone can still view the content though.
I could have an instance were registration is completely disables and only have the admin being able to create accounts?
In theory yes, by disabling registration in the server settings and then directly modifying the database. It's by no means user friendly though. You'll need to know PostgreSQL, as well as how the Lemmy backend structures the actual database tables. You'll also have to manually hash passwords, at least for when creating the account, once the user is logged in, they can change it to their own password which will go through Lemmy's own hash system (or rather, the authentication library that Lemmy uses).
Is there a library or command for registering an account on lemmy which can be used to register an account on an private instance? Lets say you payed to be in tier 2 of a group and tier 2 allows for a account on their private lemmy instance. Can it be setup so only paid users in tier 2 can have a lemmy account?
I believe you'd have to manually edit the database for that. @nutomic@lemmy.ml?
Also through the API, just block the register endpoint so users cant register themselves. And you'd have to block registration over websocket, not sure how that works.