Implementing Django User Model with Source and Destination ActivityPub Actors

[aaronjae22]

This PR enhances the user registration process by working with the existing django-allauth features (implemented by @alexbainter ) with a custom account adapter. Now, whenever a user signs up, two associated Actor instances are automatically created: one as a Source Service (fully initialized) and one as a Destination Service (empty for future use).

Custom Allauth Adapter:

A custom adaptar was created (TestbedAccountAdapter) that extends allauth’s default behavior. This adapter is now responsible for both creating the user and immediately creating the two associated Actor objects.

Actor and User Relationship:

• The Actor model is now directly related to Django’s built-in User model via a foreign key. This means each user can have multiple actors (specifically, one source and one destination), and all user-related information (such as username, email, and authentication) is managed by Django’s user system.

Removed Redundant Fields from Actor:

• Fields like username and others that duplicate information already present in the User model have been removed from the Actor model. This reduces redundancy.

How It Works:

• When a user signs up, allauth validates the form and then calls our adapter’s save_user method.
• Inside save_user, the user is created first.
• Immediately after, the adapter creates two Actor objects linked to the new user: one for the Source Service and one for the Destination Service.
• This all happens in a single step, so if anything fails, the user and actors are not created, keeping our data consistent.

Actor Model Improvements:

• The Actor model now has a manager method to create both actors for a user.
• Each user can only have one source and one destination actor, enforced by a unique constraint.

Cleaner and Safer Signup Flow:

• User and actor creation are part of the same process. If actor creation fails, the user isn’t created either.
• By using the adapter, all logic for user and actor creation is in one place, making it easier to maintain and debug.

---

Testing updates

• Confirmed that every new user gets exactly one source and one destination actor.
• Ensured that no duplicate actors or outboxes are created.
• Updated tests to reflect the new signup and actor creation flow.

Notes

Testbed already had allauth configured with:

• Email-based registration
• Mandatory email verification
• Custom base template
• Auto-login after email confirmation
• Standard redirect to home after login
• We needed to hook into allauth's signup process to create our Actors.

---

New User

User trying to registers with an existing email

Admin

[lisad]

Actors are separate from users - there can be multiple per user
So the id can't be the same for both
the preferredUsername doesn't need to be the user's username - it could be "Alice" or "Bob" or "Dave" (destination) and "Sarah" (source)

[aaronjae22]

I am currently working on an issue about preferredUsername take

[lisad]

Looks mostly good. I think we should merge this and move onward