Limited communication with *THAT* server
Heya dear Friendica admins,
since the 2023.12 release of Friendica you can limit the communication with nodes of the Fediverse before blocking communication completely. Then communication, the exchange of postings, will still be possible -- but the data exchanged with the other node are limited as much as possible.
This might be a way to deal with communication to a good friends on evil corporate server without providing too much information about users of your node. The settings to configure this limited communication have to be put into the config/local.config.php
(see defaults) file at the moment, it is planned to get the settings into the admin panel, but for now it is only the config file. There, in the system
section add the following:
"limited_servers" => "social.evil-corp.com, other-evil.com";
and from then on communication with the two servers social.evil-corp.com
and other-evil.com
is limited to the technical necessary information. This includes
- The posting and its content
- From the user profile the nickname and the profile key.
@Michael Vogel please correct me if I'm missing something, and thanks for implementing this solution!
Lo, thar be cookies on this site to keep track of your login. By clicking 'okay', you are CONSENTING to this.
hoergen (Ai)
in reply to Tobias • • •Шуро
in reply to Tobias • • •hoergen (Ai)
in reply to Tobias • • •@Tobias @Michael Vogel in some of the directives the information about the default settings are missing.
example
I can't figure out what is default and wich one does consume more memory?
Hypolite Petovan
in reply to hoergen (Ai) • • •static/
.jit
is marginally slower whilepreload
consumes marginally more memory.hoergen (Ai)
in reply to Hypolite Petovan • • •@Hypolite Petovan @Tobias @Michael Vogel i tried to creat a pull request but im not sure if i have done it right .. it looks like i have the right to commt it instantly?
I don't want that If i have done it.
Could you please check?
https://github.com/friendica/friendica/commit/4e7f0f9f04a20de7f7ba4d1a6e6d09eb3359e3f1
Hypolite Petovan
in reply to hoergen (Ai) • • •develop
branch which isn't the usual workflow (we prefer feature/bug branches that we can review and merge independently) but it's fine in this case. Thank you for your work!hoergen (Ai)
in reply to Hypolite Petovan • • •So I cant do that again ?
Hypolite Petovan
in reply to hoergen (Ai) • • •hoergen (Ai)
in reply to Hypolite Petovan • • •