Notices tagged with libranetde
-
@fu From #GNU_social, I only see a few of your posts in the thread. As you may know, #Diaspora's protocol is different from #OStatus, so the D* posts do not cross over.
But there's more going on. Years ago, when I hosted a #Friendica instance, posts from ~F to OStatus appeared natively. Now they don't. For example, almost never will a mention or reply from ~F to GS appear in the recipient's replies stream. This doesn't only happen on GS, though.
On Pleroma instances, ~F posts (at least from #libranet.de) appear with delays of 2-12 hours or more, sometimes out of context, usually out of order. They also sometimes change the scope when they reply to a scope limited post.
I have a ~Friendica account on libranet.de, but I barely ever use it because _everything_ seems to be broken and it frustrates me every time I try to use it. I should probably close it and check to see whether the issues are local to libranet.de or something common to all Friendica instances.
-
So after a day or two of using #Friendica, I have to say that the #libranet.de instance seems to have some peculiarities that prior ~F instances did not have. I don't know whether this is just the way things are now, or whether this is the effect of configuration and other sysadmin decisions made for that specific instance.
For example, subbing to others is generally good, but there's enough hit and miss to make it a little frustrating. Outbound post propagation is not understandable. Sometimes they show up quickly, sometimes they show up hours later, sometimes multiple posts over a period of time all show up in a delayed batch.
I added the account in Fedilab (Android app). It is even more confusing what shows up and what doesn't show up there, and posting from the app is not allowed.
LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864}
All Federati Nu: Federated N-series GNU Social content and data are available under the