Yannick Bungers

Yes, I agree. Are there obstacles to implement the other version later in the software?

I think in range are admin users which have every permission and also can add and remove users.

We decided to implement an admin shell https://github.com/hedgedoc/hedgedoc/issues/1003 in 2.0. An admin GUI https://github.com/hedgedoc/hedgedoc/issues/2761 should be something for a later release.

We thought about a solution and came up with: If a guest creates a note, the private API-Route returns a delete token which is saved in the browsers local storage....

We decided to use integer ids because there is no benefit in using UUIDs if we don't want to send them over the wire and UUIDs are only overhead for...

Other suggested auth modes were trusted headers #491 and IndieAuth #553.

By now it seems to be a wise decision to drop this feature for 2.0 and move it to a later version to get 2.0 in a usable state.

A way to implement this feature in the database is to bind a authorship color (from our 2.0 plantuml file) to a session and not to a user. This requires...

In #1266 adds an author which is connected to a session and the user. This author has an color which is the authorship color. For an author it is not...

I think making the print pdf option in the browser more obvious would solve 90% of the users problems. This can be done for example by switching to view mode...