My wiki version #6
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a more general and structured plan of what features a server has to have, as simple explained as possible.
Do you agree? @upm-developers/owners
This already contains the ideas of @NoahPeeters , just to catch it in a nutshell, that we have a reference.
However:
There is no ID for a server, because the server knows where it gets its messages from and thus it knows if it can trust them (i.e. whether it came from a server he syncs with).
The server does not return an url to download the package, it justs sends the package itself. This is easier. The packages should be on the server, not somewhere else.
I dont call the passwords for packages IDs, because ID means identification, which is not the purpose of the password of a package.
I did not go too deep in the implementation because thats something we discuss when the general idea is stable!
Also added new idea: the maintainer can check packages, too
Happy discussing.