I am using #activitypub to federate my #WordPress blog(s).
General Discussion
5
Post
2
Autori
1
Visualizzazioni
-
I am using #activitypub to federate my #WordPress blog(s). It works basically - just not on mastodon.social.
In this case it is (at)micha(at)www.mikapi.de.
As you can see, it knows of 5 posts, but shows none. Weird.
That looks very different on other instances.
-
Sistema ha condiviso questa discussione
-
I am using #activitypub to federate my #WordPress blog(s). It works basically - just not on mastodon.social.
In this case it is (at)micha(at)www.mikapi.de.
As you can see, it knows of 5 posts, but shows none. Weird.
That looks very different on other instances.
-
@pfefferle Only to instances of my Mastodon-followers? Or my WP-followers?
-
@pfefferle Only to instances of my Mastodon-followers? Or my WP-followers?
@os112 Both. I just wanted to say that the plugin can only send activities to known instances (the servers of your followers). So you need at least one follower on mastodon.social. And the plugin only federates new posts (the posts that were created after someone follows you).
-
@os112 Both. I just wanted to say that the plugin can only send activities to known instances (the servers of your followers). So you need at least one follower on mastodon.social. And the plugin only federates new posts (the posts that were created after someone follows you).
@pfefferle Thanks, Mr. ActivityPub. I'll have an eye on that.
Gli ultimi otto messaggi ricevuti dalla Federazione
-
@tom I'm slowly working on one, but it's completely unpaid work.
-
@tom if it doesn't work out I'd also be interested in learning why not. :D
-
@mariusor thanks! (Looks like I had already starred this one awhile ago haha) I'll check it out and see if it's what I'm looking for
-
You also cannot separate the success of AT Protocol in it's developer engagement from the existence of the Personal Data Server (or, Personal Data Storage), building applications is much easier when you don't need to deal with user registration, authentication and authorization, data storage, etc. When all you need to concern yourself with as an application developer is "I write data to the personal data server for the authenticated account, using this lexicon", development is much much easier.
Right now in the ActivityPub ecosystem, we see all the same problems as those that the Solid ecosystem sees (both rely on JSON-LD and data effectively being schemaless), but on top of that, the current architecture of the Fediverse is these huge monolithic servers with their own proprietary APIs. If you spend enough time in the ATmosphere looking at AT Protocol, you'll note that they just don't have that issue. Sure, there's lexicon clashes where someone extends someone else's lexicon, and there's all the problems of schema design, but you don't need to think about so much lower level infrastructure — it just exists.
Only a relatively small handful of people end up needing to think about that lower level infrastructure: the people implementing custom PDSes, Relays, and AppViews, but that last one is changing with the advent of https://slices.network which makes it trivial to build an AppView for your application.
-
@tom check if this one I wrote can be of use:
https://github.com/mariusor/oni
PS: Any feedback about setting it up and configuring it for your use case will be appreciated, either here, or on github/mailing list.
-
If I wanted to mess around with ActivityPub c2s clients what's a server I can host that has support for it?
-
You'd also need automatically generated SDKs that actually understand the data in a way that is useful to people. In ActivityPub, we have JSON-LD which is based on RDF which is effectively schemaless. Sure, we have object types, but every property is technically optional, or may be a single value of the type indicated, or be an array of the type indicated.
AT Protocol uses lexicons which have a much stricter schema; with the ability to have those be open or closed schemas. That gives you a lot of power in being able to generate SDKs and tooling that can handle all this data, because you don't need to think about all the edge cases.
I can of course still write data to my repository that says it's one lexicon (schema) when it's really not, and the default logic is to just drop the item as unprocessable and move on, however, that can lead to some unexpected behaviour for users and developers.
Fedify's work to split out the vocabulary tooling is a step in the right direction, but we've still a long way to go.
Also, ActivityPub is absolutely not "Simple, JSON-native", in any sense of those words, because it's JSON-LD, yes, it uses JSON encoding, but there's so many more rules and logic in order to correctly handle it.
-
@pfefferle Thanks, Mr. ActivityPub. I'll have an eye on that.
