If I wanted to mess around with ActivityPub c2s clients what's a server I can host that has support for it?
General Discussion
25
Posts
6
Posters
65
Views
-
@thisismissem is that related to the stuff you were doing w/ PDSes a few weeks ago or are those separate projects?
@tom yeah, activitypds is the research project name, but there's a bunch of upstream work in Fedify to enable C2S in Fedify, and then also to enable reusing the Fedify vocabularies (they take JSON-LD and convert into classes that Fedify understands, and handles serialisation to JSON-LD)
-
@tom yeah, activitypds is the research project name, but there's a bunch of upstream work in Fedify to enable C2S in Fedify, and then also to enable reusing the Fedify vocabularies (they take JSON-LD and convert into classes that Fedify understands, and handles serialisation to JSON-LD)
@tom basically the things I'm trying to solve in ActivityPDS are:
- an OAuth profile (based on AT Proto's OAuth profile)
- webfinger & DIDs & Handles
- what should a "PDS" do in the context of ActivityPub C2S, how much logic does it implement, or is it just a simple pipe? -
undefined andypiper@macaw.social shared this topic on
-
If I wanted to mess around with ActivityPub c2s clients what's a server I can host that has support for it?
-
@evan oh yeah this should be perfect
-
@evan oh yeah this should be perfect
@tom I can also send you an invite code.
There's a chapter on the social API in the ActivityPub book.
-
@tom I see others are pointing you in a similar direction, but funnily enough I tinkered with Social Web's ap-component test instance this afternoon!
Look at the sample client "acct-handler", too. That's what I tried today.
-
@tom I can also send you an invite code.
There's a chapter on the social API in the ActivityPub book.
@evan I signed up to get notified for the print edition a few months ago, still prefer actually holding physical books haha
-
@evan I signed up to get notified for the print edition a few months ago, still prefer actually holding physical books haha
@tom OK!
-
@mariusor I got it running w/o many issues (maybe I missed it but I didn't see any wiki pages on building Box? I got that working as well regardless)
Is there an active issue w/ fetching oni content in Mastodon? I can't seem to grab my user or any statuses from my server or from activitypub.academy. I also tried fetching your posts (because it sounded like it at least worked last year, https://metalhead.club/@mariusor/113708953874760675) but that didn't work either so maybe I'm missing something.
@tom I basically follow actors and that's how seeing posts by others in your /inbox works.
The frontend loads stuff directly through JavaScript fetch and needs all the mechanisms of that to work (and I imagine what you see might be things failing to load due to CORS rules being too restrictive on remote Mastodon instances)
I am not aware of any issues with receiving activities though, and in this process the objects themselves should be fully dereferenced to local copies.
I'll add a note about BOX compilation. Thanx.
-
@tom I basically follow actors and that's how seeing posts by others in your /inbox works.
The frontend loads stuff directly through JavaScript fetch and needs all the mechanisms of that to work (and I imagine what you see might be things failing to load due to CORS rules being too restrictive on remote Mastodon instances)
I am not aware of any issues with receiving activities though, and in this process the objects themselves should be fully dereferenced to local copies.
I'll add a note about BOX compilation. Thanx.
@tom looking at the post of mine you linked, I realize you're probably thinking of regular object discovery, and there isn't any mechanism for it yet, or for viewing remote objects that haven't reached your inbox.
-
@julian yes, two of them:
https://rattlehead.bruta.link < where a bot posts daily metal releases scraped from the internet
https://marius.federated.id < where I write a bit about stuff and play with more expressive ActivityPub objects.
-
@tom looking at the post of mine you linked, I realize you're probably thinking of regular object discovery, and there isn't any mechanism for it yet, or for viewing remote objects that haven't reached your inbox.
@mariusor sorry I meant the reverse behavior, viewing Oni users/activities from my mastodon instance (or from mastodon.social) not viewing remote activities from oni
I.e. searching for https://marius.federated.id/outbox/1725894299052/object doesn't pull up the object in mastodon (and searching for the user doesn't bring that up either)
-
@mariusor sorry I meant the reverse behavior, viewing Oni users/activities from my mastodon instance (or from mastodon.social) not viewing remote activities from oni
I.e. searching for https://marius.federated.id/outbox/1725894299052/object doesn't pull up the object in mastodon (and searching for the user doesn't bring that up either)
@mariusor actually nevermind ignore me, searching for your federated id user seems to work so I must have something wrong with my network configuration, I'll do some debugging later
-
@mariusor sorry I meant the reverse behavior, viewing Oni users/activities from my mastodon instance (or from mastodon.social) not viewing remote activities from oni
I.e. searching for https://marius.federated.id/outbox/1725894299052/object doesn't pull up the object in mastodon (and searching for the user doesn't bring that up either)
@tom I understand.
Indeed in the past two/three weeks I must have deployed something (or Mastodon made some changes) that regular objects posted by ONI aren't findable any more. The problem is that I don't have a development setup for mastodon on which to test what the problem is. :(
However the actors should still be available.
-
@mariusor actually nevermind ignore me, searching for your federated id user seems to work so I must have something wrong with my network configuration, I'll do some debugging later
@tom a quick check list for you:
1. Check if the actor is publicly accessible from the internet.
2. Check if it has a RSA private/public key.
3. Check that if you have a proxy in front of ONI it doesn't mangle Accept/Vary/Content-Type headers.
4. Check that if you have a proxy the `/.well-known/webfinger` route is handled by ONI. (your proxy should forward all routes to ONI directly as a start)
-
@tom a quick check list for you:
1. Check if the actor is publicly accessible from the internet.
2. Check if it has a RSA private/public key.
3. Check that if you have a proxy in front of ONI it doesn't mangle Accept/Vary/Content-Type headers.
4. Check that if you have a proxy the `/.well-known/webfinger` route is handled by ONI. (your proxy should forward all routes to ONI directly as a start)
mariusor@metalhead.club Can you use ActivityPub.academy? There is a logger built in so you can see the activities coming and going. It might help you debug why the ONI activities aren't being processed.
Gli ultimi otto messaggi ricevuti dalla Federazione
-
Yes, very likely.
When I built the core software for a bank more than a decade ago, I did the same.
-
There isn’t anything that says my server should return the latest known state of a post, including my interactions with it.
And sure, I can refetch any activity from the inbox via proxyUrl (except non-public), but nothing guarantees my server will add the current remote state of a post to its internal representation and return this.
So this forces a thick client situation, to have what should be fairly standard User Experience.
-
Of course implementations may vary but the spec isn’t clear, so let’s improve this, yeah! https://github.com/swicg/activitypub-api/issues/52
-
ActivityPub client developer experience is something like this.
Building a coherent feed with stateful objects requires comparing an Activity from the inbox, with what’s in your outbox.
-
@reiver@mastodon.social pretty sure this kind of ambiguios why Stripe represents everything in cents, no? 😏
-
AFAIK, it is an IETF JSON thing, and wasn't part of the original (pre-IETF) JSON.
Here's the oldest version of the JSON spec I could find:
https://web.archive.org/web/20030228034147/http://www.crockford.com/JSON/index.html
It defines "number" as in the screen-shot, and doesn't say anything about floating-point numbers.
...
I do agree with you that the reason IETF JSON talked about floating-point numbers is almost certainly because of JavaScript.
-
@reiver that's a json thing, which is itself a JavaScript thing. JS doesn't have an integer type, only number, which is a double precision floating point. Json is a serialization spec for JavaScript objects, and jsonld is spec for pretending that adding one property to a json document makes it a collection of rdf triples and then getting mad about it when the rest of the world just wants things to be parseable
-
@silverpill @sabrinkmann @naturzukunft2026 @julian
i should use socialhub more... i'll catchup on the dicussion, soon
