Conversation

Notices

1. Embed this notice
   LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} (lnxw48a1@nu.federati.net)'s status on Friday, 04-Aug-2023 03:32:02 JST LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864}

   • fu
   @fu "Forbidden. Only logged in users are permitted to perform a search.
   • Embed this notice
     LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} (lnxw48a1@nu.federati.net)'s status on Tuesday, 08-Aug-2023 15:42:55 JST LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864}

     • fu
     @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.