Skip to content

Conversation

@mathiascode
Copy link
Member

No description provided.

@mathiascode mathiascode marked this pull request as draft August 21, 2025 14:51
- Rate limits
- Private rooms
- Distributed search network
Since the Soulseek protocol does not support encryption, Soulfind does not use
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Omit "Since " because the protocol has never supported encryption.

This informal language is perfectly understandable when spoken verbally, but it isn't proper written English to use in legal documents sincebecause it can be ambiguous with saying that things were different in the past.


Soulfind temporarily stores private messages in memory until the recipient
acknowledges them, and does not retain them after delivery. Soulfind does not
give owners or admins the ability to access private messages by default.
Copy link
Member

@slook slook Aug 22, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Omit " by default" or omit the entire last sentence because the program doesn't contain any such option to do this function whatsoever.

Also consider using "the Soulfind program", "the program" or "the software" or perhaps even modules such as "pm.d", "rooms.d" in place of "Soulfind" to disambiguate from "Soulfind Contributors", otherwise it might not be clear as to whom or what this entity is referring and if that entity could be wrongly construed as an organisation rather than the actual program itself.


README.md ought to remain targeted only towards developers, owners and admins, because we don't want to end up in a position of providing information to their users nor processing queries from them...

Consider placing the entire Privacy section in a new document such as PRIVACY.md because it is long and irrelevant unless a server is deployed by a third-party for access by end-users, in which case a standalone document would be easier for owners to modify and, as they see fit, to publish, for example by:

  • serving it over http(s) on the owner's website,
  • including it in the MOTD with a %%privacy%% placeholder,
  • the user profile about me text for the 'server' user info,
  • in a private message response to a user command such as privacy or userinfo server.

It should also be mentioned that the Soulfind Contributors are not data controllers and so are unable to suggest or enforce any policy for the services that are provided by server owners who become data controllers if they wish to deploy the software in accordance to the GPL (i.e. at their own risk and without any warranty of any kind, etc).

@mathiascode
Copy link
Member Author

This is mostly an attempt to give insight into what the server does with data it receives, but you have good points. I'll move this to a separate markdown file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants