BDX-town / Mangane

Alternative frontend for Akkoma
https://bdx.town
GNU Affero General Public License v3.0
137 stars 28 forks source link

Disable Scheduled publication on Pleroma as they doesnt work #106

Closed bugsysop closed 1 year ago

bugsysop commented 1 year ago

Context:

Mangane goodcook-raccoon-b4be495
Pleroma 2.4.4

Problem:

1) Scheduled posts never published 2) Error message when suppressing failled scheduled toots

supp-error-mssg

Cl0v1s commented 1 year ago

Duplicate https://github.com/BDX-town/Mangane/issues/71

However, some of our users are already using scheduled posts, and I think they are working. cc @ymollard If it's the case, maybe it's an issue with pleroma ? Are scheduled posts working on the vanilla pleroma FE ?

bugsysop commented 1 year ago

Sorry for the duplicate...

I think nonody have tried to use this when we used Pleroma FE

bugsysop commented 1 year ago

Not exactly the same as #71 here scheduled posts are not published

Cl0v1s commented 1 year ago

If they arent published, I think it's more an issue with your backend than with Mangane itself. I'm waiting for Yann's answers since I know they are using scheduled posting on our instance :)

ymollard commented 1 year ago

Yes I've been using toot scheduling on bdx.town a couple of times, always successfully. And never met that error.

bugsysop commented 1 year ago

The problem is maybe from Pleroma part. There is an open issue about this.

Cl0v1s commented 1 year ago

This issue is to add the scheduling feature to the vanilla FE, if nobody is using it (since it's missing in front), there is maybe some problem with the backend implementation.

The Akkoma's changelog would tend in that direction:

image

https://akkoma.dev/AkkomaGang/akkoma/src/branch/develop/CHANGELOG.md Since it mention having added the endpoint allowing to schedule post, while pleroma just mention supporting the scheduled_at prop

bugsysop commented 1 year ago

On Pleroma FE and on Akkoma FE there is no front UI to use Scheduled posts.

I think as it's a Pleroma problem, maybe we can close this issue and just add a note somewhere in documentation about the problem (info for Pleroma users)

Cl0v1s commented 1 year ago

Based on the feature detection system, we can deactivate that option for pleroma directly. Do you think it would be a good idea ?

bugsysop commented 1 year ago

Yes, ist’s frustrating to have an unfunctional function