@hypolite@silverwizard Delta Chat has got issues since it uses the standard ports. This can be a problem in some corporate networks where the guest network is port restricted. At the C3 in 2019 I met the developer. I'm running it now since then, but I nearly never had got any conversations with it, since there are so much alternatives.
@hypolite From my point of view the data model is mostly complete. For the first part we will only need one more boolean field to close the report. This can be extended in later versions with the possibility to reject and to accept the report, including the storing of the moderator's uid.
And on the frontend all that we need is a report button on a user and on a post, then the user can enter some remarks. Also there needs to be a button if the report should be forwarded to the server of the reported account.
@hypolite This "mutual only" would only work if all systems established it. Due to the nature of AP, commenters will distribute their comment on their own. This is something that the "commented on" account can't control.
Means: We can check if there is an commonly agreed way of "you are not allowed to comment here" and we can implement it. But I would only implement the other way when the support is given by most systems. (Same occurs to "comments closed")
@hypolite I haven't looked at all posts in this thread, so this might be said somewhere: We are transmitting our posts with LD signatures and the thread starter always relays all incoming posts. Posts with LD signatures can be checked without the need for a valid HTTP signature. So at least amongst Friendica users this shouldn't be a problem. And since we also support signed HTTP requests, other system that don't support LD signatures could perform a signed request to check the validity of the relayed post.
@hypolite Some technical background: This "Hide your profile details" acts more like a sign that tells that you aren't allowed to enter the lawn than as a fence that makes it hard to enter the lawn. It is always possible for a user to see the content anyway - it is only slightly more complicate (you just have to have a look at the user's feed). Because it underfulfils the estimations, I don't like that feature.
@hypolite Can you provide a PR? I'm not sure where to add this B here: RewriteRule ^(.*)$ index.php?pagename=$1 [E=REMOTE_USER:%{HTTP:Authorization},L,QSA]
@hypolite I now realized that the problem isn't caused by the router. It's at the beginning where the pagename variable is set. I hope that you can solve this.
@hypolite Concerning the moderation part, I would like to focus on the external communication, means receiving and transmitting of these messages. It would be great if everything else (displaying the moderation messages and the needed actions) are done by someone else with a better hand for frontends.
@hypolite Do we need a communication with the reporter? We will possibly need a communication with the reported person when they were on our system. Then we should be able to use PM. But currently we cannot PM someone that we don't follow. So this is part of the work as well.
Entwickelt Open Source in der Freizeit, hat zu viele Fahrräder und ist Fan des HSVH (Das erste "H" steht für "Handball") und von islieb, Franzbrötchen und guter Schokolade. Wunschliste: alles unter https://www.rausch.de/schokolade/Wer Amazon mag: https://www.amazon.de/hz/wishlist/ls/3VWK0ZL3MN3ZTLiberapay: https://liberapay.com/heluecht/donateBTC: 1AtJ9JVysdhWjSs5qQvp7Xt9xFdjMKSSA7BCH: qpjg2gwgr35fgz3dxy6lcpw3lt4szrfgev90uk3tfv