ricochet support

Patrick · January 10, 2024, 6:01am

Apparently license was changed back to free.

I failed to find the commit which changed the license back to free because the reasoning would be interesting.

git log --all --grep="Commons Clause"
git log -S'Commons Clause' --source --all
git log -S"commons" --regexp-ignore-case

Maybe this was completely nuked, history rewritten? (git push --force)
license: updated to 3-clause bsd + commons clause · blueprint-freespeech/ricochet-refresh@b0a274c · GitHub (the commit that introduced Commons Clause) shows:

This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

This one related but it’s not that. But also seems strange.

github.com/blueprint-freespeech/ricochet-refresh

Adding Comment Headers and Making Changes for REUSE Compliance

blueprint-freespeech:main ← gabriel-ku:FSFEREUSE

opened 08:36AM - 20 May 22 UTC

gabriel-ku

+540 -775

Hello! This is Gabriel from the Free Software Foundation Europe (FSFE), and w…e have been working with the NGI0 framework, helping projects with their licensing and copyright management. After a quick check on your repository, I would like to propose some updates regarding copyright and licensing information. REUSE (https://reuse.software/) is an FSFE developed initiative intended to make licensing easier by establishing a single way to display all copyright and licensing information through comment headers on source files that can be human- and machine-readable. The REUSE tool makes the process of applying licenses to files and compliance checking much easier. Instructions on how to install the REUSE tool can be found here: https://reuse.readthedocs.io/en/stable/readme.html#install You can also check out this screencast for more instructions on how to use the REUSE tool: https://download.fsfe.org/videos/reuse/screencasts/reuse-tool.gif The changes in this pull request have also been made for you to understand the basic ideas behind REUSE. REUSE Features: • SPDX copyright and license comment headers for relevant files. • LICENSES directory with licenses used in the repository • Associating copyright/licensing information through a DEP5 file in large directories. Files Missing Copyright and Licensing Information To serve as an example, I added the SPDX headers with copyright and license information to the copyrightable files in a few of the directories (namely /includes, /integration, /templates, and /tests). This should give you an idea of how comment headers should look like in a REUSE compliant repository. Please also double check if the personal information in the headers is correct and consistent. In the event that there are more copyright holders, please include them in these comment headers. LICENSES Directory in the Root of the Project I included in this directory the file that contained the GPL v3 license text. Additionally, I included in this text the CC0 license text. This is because you have files in your project that you do not find copyrightable, for example configuration files such as .gitignore. As the fundamental idea of REUSE is that all of your files will clearly have their copyright and licensing marked, I have applied the CC0 license to .gitignore, which is functionally identical to putting the file in the public domain. If you find REUSE useful, we offer a wide range of tools to help you continuously check and display compliance with the REUSE guidelines. Hope that this helps and please feel free to contact me if you have any questions at gabriel.ku@fsfe.org. Best, Gabriel (Free Software Foundation Europe)

Someone changed the license in a pull request back to free, added REUSE compliance but apparently without prior discussion.
Not merged.

Cwtch messaging?

related:
Client-Server Instant Messengers (IM)