The fundamental principle of the app is to allow users to add new options. This could be realised in the frontend by using a CharField with a select widget. This widget would be pre-populated by existing choices but the user would always have the ability to create a new option.

It should be possible to exclude people from a search based on their interests.

The GDPR requires websites to not use cookies unless explicit consent is given. However, required cookies are exempt from this. Necessary cookies are only those that are technically required for operation of the website. In our case this would be the csrf cookie (always) and the session cookie (logged in).

The user model should be extended so that the project becomes a foundation for the dating app.

This should include:

• Gender (this one is tricky - which should we include?)
• Looking for (orientation)
• Tabs or spaces

I think we should deliberately postpone developing functionality for profile pictures, since that one is tricky (all uploaded pictures should be stripped for metadata and converted to a common format).

What do you think? Do we need any other fields? :)

Love
Deni 🐾

Motivation
There are fundamentally two types of dating apps: those with intransparent matching and those with manual filtering. The latter usually allow everyone to write you without your approval. This leads, for example, to unwarranted pictures sent to you.

Solution
You can request contact with any user on the app. But this contact has to be approved. If it is denied you cannot send another request until:

• the person, who denied you, sends a request to you OR
• a configurable period of time has passed

Every request can be accompanied by a small text that explains the desire to contact. The denial can include a reason for denying. If you accept the request you can select what contact info shall be made available to the requesting user.

What contact info? In your profile, you can enter contact info like E-Mail, Twitter, Facebook, Signal, and Threema. For every information, you can specify whether that info is visible for everyone, for users of accepted requests, or just for you. Upon accepting a request, all information visible publicly and for accepted users will be selected by default. But you can modify the visibility at the spot and allow access to a private contact info as well.

Motivation
Pictures are not everything but a dating app without them is likely not very attractive. Therefore, profile pictures should be implemented.

Solution
Pictures must be optional and those uploaded have to be stripped of any metadata to minimize data leakage. You should be able to filter by images. Furthermore, it should be configurable if pictures are allowed at all.

Dependabot couldn't authenticate with https://pypi.python.org/simple/.

You can provide authentication details in your Dependabot dashboard by clicking into the account menu (in the top right) and selecting 'Config variables'.

View the update logs.

Motivation
Your data is very sensitive. Therefore, it would be cool to support federated instances. Users on every instance could see all users but their data would be stored in their respective instance.

Solution
Could be handled by an authorized REST api to get data, combined with one central repository of all known instances.