I wonder if @dansup could have an “anti-spam” assembly with the various software developers using #ActivityPub‽ We could also checkout what #WordPress is doing with Akismet too.
I've been in this industry long enough to see things constantly come & go. #React is no different - it'll be replaced by other frameworks soon & those will be hot for a bit. Then that one will be replaced & so on. Learn your basics! #HTML#CSS, plain#JS. Those are the only things that don't come & go & will take you through your entire career, regardless of what's cool right now. Will I still be coding #WordPress in 10 years? Who knows! But my knowledge of #PHP will carry me on.
ActivityPub is so neat! With all the new implementations coming out, it's slowly becoming my "one stop shop" internet aggregator.
For example, all from within my Mastodon instance I can:
Follow communities on Lemmy and Kbin, allowing me to interact with every post/comment and make my own post or comment to any community.
Follow my favorite podcasts and get new episodes directly in my feed via PodcastIndex.org
Follow WordPress blogs that have the ActivityPub plugin activated.
SOON enough I'll be able to:
Interact/follow accounts on Threads (and hopefully someday Instagram)
Follow/interact with comments/posts/communities from NodeBB forums.
This protocol is changing the internet and how I use it every day.
PS. If you want more information on how to do any of these things, just let me know and I will explain. Though please limit to asking about one or two at a time, as some are quite intricate in their implementations.
Edit: Nitter has been shut down 2 days after I posted this. Oh well. Fuck Xhitter
When writing the initial version of our project plan as signed and agreed with by NlNet we didn’t know yet about the dynamics of the community, specifically about how the cooperation between the maintainers of the #WordPress#ActivityPub plugin and #Mobilizon would be like. The level of collaboration with other #Fediverse developers would determine whether our project goals could only be achieved through a series of workarounds, or whether we could work together to strengthen interoperability and compatibility in the Fediverse.
Mobilizon was, until our project, the only Fediverse application with true event federation. #Gancio limits its ActivityPub capabilities to sending notes, but is working on a true federation of events, and other services like #Friendica have a very different approach to events: their implementation focuses on sending invitations rather than publishing events. As is usual with any software, you will find a lot of small bugs if you have not done any tests beforehand. In the case of Mobilizon, this was not possible since there were no alternative platforms to do the tests with, so the only option was to test the Federation with other Mobilizon servers. We seem to be the first and we are fascinated and incredibly grateful for the willingness and prioritization that such issues have among the other developers (thanks to tcit and les). The issues may seem small, but they have a big impact: #304#33#321#1509#1507#1392#1385#1388#1387#1378#1376.
The other deciding factor for us was that we didn’t know how close the interaction with the upstream WordPress AktivityPub project would be. The exchange of ideas and the desire for a joint solution is strong. We would like to thank @pfefferle again for the regular exchange, his ideas and inspiration, without his commitment to the community our project would be less sustainable.
Tasks done (almost)
We published a repository that aims to make it easy for other developers, including ourselves to start developing and debugging WordPress along with Mobilizon.
We have created a pull request to add management of various ActivityPub transformers to the admin interface. The current implementation basically works, but we have a lot to polish and improve on our roadmap.
Using that patched ActivityPub plugin we explored writing transformers for two popular event plugins, this gave us a lot insight on what is important. These transformers already have fundamental compatibility with Moblizon.
Updating our About us page showing some information who we are.
Implement the followers list of the application actor in the admin UI along with the ability to reject, approve, and remove followers. We are very inspired by how #PeerTube has solved this in the admin UI. This of course includes a an option as:manuallyApprovesFollowers that can be set for an ActivityPub actor within WordPress.
Write an initial draft of the user documentation informing about custom ActivityPub transformers and instance-to-instance federation with Mobilizon. The target audience will be non-tech people. Parts of this will also be used as a non-tech description of our project.
Improve the admin UI and propose a solution to handle the settings for each transformer, if there are any.
Write more transformers for other popular event plugins to discover common pitfalls.
If you have any questions, ideas, or would like to help us, for example by testing our progress yourself if your operate a WordPress site with events, please don’t hesitate to contact us. We don’t care if you have technical experience or what your background is: any kind of involvement is valuable to us.
Just read a bit of reactions about the #WordPress#ActivityPub plugin and there seems to be a sect of ppl who find it abhorrent that #fediverse posts might federate.
In their opinion, if they post “on Mastodon”, that post shouldn’t leave #mastodon. They think its understandable that a post may leave their own server and federate to other mastodon servers but federating outside of that is unacceptable. (I don’t know how they think about their posts federating to non-mastodon servers, especially non-microblogging servers like Friendica, kbin, etc)
Once again, I think the problem is caused by mastodon. They market mastodon as a Twitter-alternative and hype it as the platform instead of the fediverse. Now these users don’t understand the breadth of the fediverse and are “confused” that their posts could be “leaving” mastodon.
You’re not “on Mastodon”; you’re on the fediverse. Just like someone who runs a blog isn’t on Nginx or Apache, they’re on the web.
It looks like this "WordPress Security Team" impersonation scam is back, so please spread the word!
The #WordPress Security Team will never email you requesting that you install a plugin or theme on your site, and will never ask for an administrator username and password.
Oh man this is literally so amazing. Thanks to the #ActivityPub WP.com integration, my #CDrama#KDrama blog dramatea now has its own Mastodon profile. This is all kinds of cool. Theoretically I can literally use my blog as a #Fediverse instance. I wonder how this will change the Fediverse? How big will it grow? 🤔
You can check it out & follow me here @dramatea88.wordpress.com@dramatea88.wordpress.com
Let’s not forget #Drupal’s future depends on a healthy ecosystem for #PHP. When we have discussions about the future of Drupal or #WordPress or any other project that depends on PHP, we shouldn’t forget to also discuss how we can ensure a future for the programming language that powers these. https://mastodon.social/@palantir/112292234589621144
Quelqu'un connaît-il un moyen de forcer (provisoirement) le cache du browser des visiteurs à se vider quand ils arrivent sur votre site WP ? Via un plugin ou autre.
J'ai été piraté il y a quelques semaines, l'un de mes sites a été defacé, c'est corrigé, mais j'ai encore plein de visiteurs qui continuent d'arriver sur le site defacé à cause de leur cache... Si vous avez une solution, je suis preneur. J'ai essayé le plugin re-Busted, ça ne fonctionne pas.