Kbin account replies made directly to a Kbin ‘Thread’ in a Magazine from another instance are not federating #90

New Issue

Open

opened 2023-06-12 01:57:15 +00:00 by techmagus · 3 comments

techmagus commented

2023-06-12 01:57:15 +00:00

Probably a bug, probably not.

What I did:

Created a new Kbin “Thread” in a Guppe group (or Kbin “Magazine”)

The new Kbin Thread was received by Guppe and pushed to its members.
Using a Kbin account, I replied to that Kbin Thread.

The reply was not seen by Guppe and thus no post/reply was pushed.
Using a non-Kbin account, I replied to that Kbin Thread.

Kbin itself received the reply and displays it as a Thread comment.
Using a Kbin account, I replied to the non-Kbin reply (see previous item).

Guppe received it and the reply was pushed to Guppe members.

So… it seems that a Kbin account replying to a Kbin Thread is not being received by Guppe (or Kbin is not pushing it).

Note: I have not tested if the Kbin “Magazine” is not from another instance. The steps would be slightly different as the non-Kbin account first have to subscribe/follo that “Magazine“.

Here is the test thread: https://fedia.io/m/test@a.gup.pe/t/969/Testing-how-posting-a-Kbin-thread-works

The “Ooh, I'm starting to” and “So, this is probably a” replies were from my Kbin account and were not seen by Guppe (thus can only be seen from Kbin itself).

(2023-06-16 EDIT: removed use of #-3, replace with “previous item”.)

Probably a bug, probably not. What I did: 1. Created a new Kbin “Thread” in a Guppe group (or Kbin “Magazine”) The new Kbin Thread was received by Guppe and pushed to its members. 2. Using a Kbin account, I replied to that Kbin Thread. The reply was not seen by Guppe and thus no post/reply was pushed. 3. Using a non-Kbin account, I replied to that Kbin Thread. Kbin itself received the reply and displays it as a Thread comment. 4. Using a Kbin account, I replied to the non-Kbin reply (see previous item). Guppe received it and the reply was pushed to Guppe members. --- So… it seems that a Kbin account replying to a Kbin Thread is not being received by Guppe (or Kbin is not pushing it). Note: I have not tested if the Kbin “Magazine” is not from another instance. The steps would be slightly different as the non-Kbin account first have to subscribe/follo that “Magazine“. Here is the test thread: https://fedia.io/m/test@a.gup.pe/t/969/Testing-how-posting-a-Kbin-thread-works The “Ooh, I'm starting to” and “So, this is probably a” replies were from my Kbin account and were not seen by Guppe (thus can only be seen from Kbin itself). (2023-06-16 EDIT: removed use of #-3, replace with “previous item”.)

sam_uk commented

2023-06-12 08:00:18 +00:00

I've read this is an issue with having Cloudflare enabled.

I suspect this is necessary for the next few days to keep the site online at all.

Once exponential growth has slowed I'd expect it will be disabled.

I've read this is an issue with having Cloudflare enabled. I suspect this is necessary for the next few days to keep the site online at all. Once exponential growth has slowed I'd expect it will be disabled.

👍 1

techmagus commented

2023-06-12 10:02:24 +00:00

Author

I've read this is an issue with having Cloudflare enabled.

I suspect this is necessary for the next few days to keep the site online at all.

Once exponential growth has slowed I'd expect it will be disabled.

Hmm… I'm not sure if fedia.io have Cloudflare enabled or not.

As far as I know, only the flagship server, kbin.social, is currently behind Cloudflare.

> I've read this is an issue with having Cloudflare enabled. > > I suspect this is necessary for the next few days to keep the site online at all. > > Once exponential growth has slowed I'd expect it will be disabled. Hmm… I'm not sure if fedia.io have Cloudflare enabled or not. As far as I know, only the flagship server, kbin.social, is currently behind Cloudflare.

👀 1