André Menrath

Thanks for reporting. A fix will be shipped with the next release: https://codeberg.org/Event-Federation/wordpress-event-bridge-for-activitypub/pulls/142

If anyone can help me learn how to link from a web site to open a WP federated post in Mastodon… I’d buy them a drink.

You will not be able to do that, thats up to the each individual, as you do not know each persons Mastodon instance, and moreover one could have several. However, browser plugins could do such things, to show a “open this site in Mastodon” if the current page has an ActivityStreams representation. But I do not know if such a things exists.

FYI: I followed your events for demonstration purposes: https://gancio-test.event-federation.eu/

If you use the Gutenberg block editor select -> Preview -> ActivityPub Preview. If you use the classic editor under the event posts list if you hover over an event you see an “ActivityPub preview” link. Just save the Event as draft before in that case.

Resolved with HotFix in version 1.0.0.

Should be resolved with version 1.0.0.

Thanks for reporting this one. It should be fixed in the upcoming 1.0.0 release.

It contains plenty of improvements, and I am curious of receiving feedback again. Please be patient maybe one or two more days! ??

What you are encountering is likely a bug in the ActivityPub plugin, it federated the event before all meta-data of the event is processed and ready. The upstream plugin is informed about this issue, but the 1.0.0 version of the Event Bridge for ActivityPub contains a hotfix to solve it meanwhile. The start-date being the created time is just currently the very last fallback before not sending malicious event, it should never occur anyway.

• This reply was modified 1 month, 1 week ago by André Menrath.

Hello!

Thanks a lot for your detailed report.

HTML in summary: Fediverse application should parse the summary as HTML, Mastodon does it since version 4.3.0. That means if your instance received the last update of an Event before being upgraded to version 4.3.0+ still the HTML markup will be shown. Many other Fediverse application sadly still handle this the wrong way. What I could offer in meanwhile is adding a config option to send the summary as plain text, until other more other Mastodon servers are updates and other applications have fixed this. What do you think?

Events not showing up on Mastodon: Which version of the ActivityPub plugin do you use? Because almost all federation logic is handled by that plugin and the most recent release 5.0.0 a few days ago has some severe issues which I reported – I am currently working together with its developers on solving these as fast as possible. I will notify you here once this should be resolved.

Note that I afterwards will release the 1.0.0 version of the “Event Bridge for ActivityPub”. As there are plenty of improvements done since 0.3.5 I would kindly to ask you to be patient and investigate again if any issues should still persist then!

Kind regards,

André

• This reply was modified 1 month, 2 weeks ago by André Menrath.
• This reply was modified 1 month, 2 weeks ago by André Menrath.

Thanks for your Feedback. Yes you are right, most of the stuff happens under the hood, but more features that touch the admin UI will come soon.

Indeed, we had long discussions about RSVP in the Fediverse and I am working on unifying the behaviour of it.

The problem here is: the event plugin itself should offer a way to handle RSVP already. And it should do so in a way flexible enough to include it. But including it here in a generic way is almost impossible, or would end up being very clunky, having lots of confusing edge-cases. The RSVP solutions present in the supported event plugins are just too different.

That’s where the idea came up of developing an Event-Plugin with built-in ActivityPub support. Note that I am in contact with the developers of GatherPress, a community first event plugin.

On the other hand what would be easier is doing an independent RSVP –ignoring what an event plugin might already provide.

To edit the mirrored events in the admin user interface, you can change this: https://codeberg.org/linos/mobilizon-mirror/src/commit/a09fe0661a8ea41c3d88dec8bb2c9c2b97990263/includes/class-mobilizon-mirror-post_types.php#L349

Note that I have been working on a v2.0.0 which also had duplication issues. See the alpha releases: https://codeberg.org/linos/mobilizon-mirror/releases

Short summary of what happens and had been the error back then:

The information which events are already mirrored gets stored in a transient called mobilizon_mirror_cached_events_list (like a cache): it is an array which holds information about the mobilizon event UUID, the last known updatedAt and the WordPress post id. In case this transient gets lost it is regenerated in the get_local_mobilizon_events() function. We had the problem that this get_local_mobilizon_events() only returned a finite number of the already mirrored events: like the first page of a pagination. So all events that were on the latter pages got mirrored again.

Another point of failure is the update_mobilizon_events() function. There it does deletions, updates and new creations. Note that if any changes have been made during the sync, the transient gets regenerated by calling the get_local_mobilizon_events() again. So the issue kind of must be there. Or your mobilizon events always come in with a new UUID.

• This reply was modified 1 year, 3 months ago by André Menrath.

Seems like https://codeberg.org/linos/mobilizon-mirror/src/commit/a09fe0661a8ea41c3d88dec8bb2c9c2b97990263/includes/class-mobilizon-mirror-api.php#L354 is not returning all posts on your website.

But at the moment I can think of why, and sadly I don’t have any time to test and debug this further at the moment. I would start by writing some log information during the sync-cycles, this could help to see where things go wrong.

@ravanh In order to investigate what might cause this behaviour, could you maybe share the WordPress version you have been using and the Mobilizon group/instance you have been mirroring.

Have all these duplicated posts been really linking to the same event with the same UUID (the part after mobilizon.instance.tld/events/<uuid>)?

Thanks for reaching out.

Both have an open issue now on the code repository.

https://codeberg.org/linos/mobilizon-mirror/issues/8

https://codeberg.org/linos/mobilizon-mirror/issues/18

I will try to enhance both with the next minor release with I can start working on in September.

Like the description says, the integrated card view is deprecated. But you can still make it work in your case, if you manually proper custom css to your site like:

div#event-card-list div.event-columns div.event-card-container a.event-card div.card-content h4.event-title { color: #333 }

• This reply was modified 1 year, 12 months ago by André Menrath.

Sorry for the late reply. Even looking at the new debug logs, I could not see what could be going wrong as there are no warnings or errors from files related to mobilizon_mirror. Perhaps the cronjob that triggers the mirroring isn’t registered/enabled. Cronjobs are tasks that are executed at specified intervals.

The WordPress plugin Wp Control lets you view and run all present cron jobs.

So the next think to look for now is whether a cronjob called mobilizon_mirror_cron_refresh_events is registered on your site.

If not the error your site maybe fails registering new cronjobs or there is some error in the logic which is registering the cronjob in mobilizon mirror: https://codeberg.org/linos/mobilizon-mirror/src/commit/a09fe0661a8ea41c3d88dec8bb2c9c2b97990263/admin/class-mobilizon-mirror-admin.php#L323

Regards, André

• This reply was modified 2 years, 1 month ago by André Menrath.
• This reply was modified 2 years, 1 month ago by André Menrath.

@ecollart But these errors would be exactly what I would need to help you out or fix the problem. Please re-enable WP Debugging plugin, wait at least x minutes for the Mobilizon mirror sync to start at least once, then copy the PHP errors and paste them somewhere/send them to me. I can do the work to find the right place. Without them errors it is almost impossible to tell. Thank you very much in advance.