We all have tebibyte emails and we are all users on the server. Mintee ought to be able to pull from that. However, we should also allow anonymous users, and we also need to keep in mind ActivityPub/Fediforge.
We all have tebibyte emails and we are all users on the server. Mintee ought to be able to pull from that. However, we should also allow anonymous users, and we also need to keep in mind ActivityPub/Fediforge.
sashakoshka
changed title from How to implement users to How to do users2024-07-03 21:22:23 -06:00
users can be stored as a user/domain pair and a type to define how the user needs to be displayed to the frontends, like Activitypub users being @user@server, e-mail users being user@server, and local users being @user. Unix users oughtta be the default configuration and Mintee’s backend could use passwd files for virtual user Unix auth or store users in the database. the benefit of passwd files is that a single authentication passwd file could be shared on services where an smtp server is configured to use it, allowing the creation of a mail account to also create a forge account and vice versa.
users can be stored as a user/domain pair and a type to define how the user needs to be displayed to the frontends, like Activitypub users being @user@server, e-mail users being user@server, and local users being @user. Unix users oughtta be the default configuration and Mintee’s backend could use passwd files for virtual user Unix auth or store users in the database. the benefit of passwd files is that a single authentication passwd file could be shared on services where an smtp server is configured to use it, allowing the creation of a mail account to also create a forge account and vice versa.
Would we also be doing authentication using /etc/shadow or would there be a separate database of passwords?
Real, non-virtual system users can be authenticated using bsdauth on OpenBSD and PAM on Linux, FreeBSD, and NetBSD.
> > passwd file
>
> Would we also be doing authentication using /etc/shadow or would there be a separate database of passwords?
Real, non-virtual system users can be authenticated using [bsdauth](https://en.wikipedia.org/wiki/BSD_Authentication) on OpenBSD and PAM on Linux, FreeBSD, and NetBSD.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
We all have tebibyte emails and we are all users on the server. Mintee ought to be able to pull from that. However, we should also allow anonymous users, and we also need to keep in mind ActivityPub/Fediforge.
How to implement usersto How to do usersusers can be stored as a user/domain pair and a type to define how the user needs to be displayed to the frontends, like Activitypub users being @user@server, e-mail users being user@server, and local users being @user. Unix users oughtta be the default configuration and Mintee’s backend could use passwd files for virtual user Unix auth or store users in the database. the benefit of passwd files is that a single authentication passwd file could be shared on services where an smtp server is configured to use it, allowing the creation of a mail account to also create a forge account and vice versa.
OpenBSD credentials table files ought to be supported too.
Would we also be doing authentication using /etc/shadow or would there be a separate database of passwords?
Real, non-virtual system users can be authenticated using bsdauth on OpenBSD and PAM on Linux, FreeBSD, and NetBSD.