@nprofile1q... Die Berechtigungen für Bilder in Posts werden von den Berechtigungen des jeweiligen Posts kopiert.

@nprofile1q... We do everything via ActivityPub. DFRN is only used when the remote server doesn't seem to support ActivityPub. This means that we don't give up anything - except the compatibility with system prior to the end of 2018.

@nprofile1q... Friendica verwendet ActivityPub und macht damit alles. DFRN war mal unser primäres Protokoll, aber seit mehr als 6 Jahren wird es als primäres Protokoll für die Kommunikation zwischen Friendica-Installationen verwendet.

@nprofile1q... Siehe hier: github.com/friendica/friendica…

I had a look at the number of posts that arrive at my servers that are transported via DFRN our legacy protocol. It is not used anymore and there are no servers out there anymore that can't speak AP or the Diaspora protocol. So I really think that we should remove that protocol stack now.

Are there any objections? The benefit would be that there is less code to refactor in our regular refactor cycles.

@nprofile1q... Es passiert manchmal und auch nur auf einigen Servern. Ich weiß im Moment noch nicht, was es auslöst.

@nprofile1q... The easiest way is to create a new "stable" branch that is derived from "2025.07-rc" and that you delete the old "stable" before.

@nprofile1q... Weird. It should work without any problems. Are the instances on the same machine?

@nprofile1q... @nprofile1q... The size should be smaller than your memory. The problem occurs because there is some post, some media that is larger than your memory.

@nprofile1q... In the RC branch there is a XMPP addon based on Converse.js. Also you can setup XMPP servers like ejabberd and Prosody to use the same credentials like for Friendica.

@nprofile1q... @nprofile1q... @nprofile1q... I always find it quite funny, when people say, that in the Fediverse your chronological timeline is your only algorithm, not knowing that Friendica has quite a bunch of them 😀

From my point of view these algorithms can be quite nice in helping users. The only important thing (at least for me) is that the user must be in full control of it.

I will be at the FOSDEM next week. If possible, I will try to talk with other developers about these topics.

@nprofile1q... That is on my list as well. My plan is to be able to define a "filter channel" that then contains everything that you don't want to see in your channel. This would then remove the posts from there.

I still have to see if this can work. But at least it's on my list.