Conversation

Notices

1. Jacky Alciné (jalcine)'s status on Monday, 18-Feb-2019 00:45:42 CET Jacky Alciné

   #activitypub #activitypubdev #apdev

   (this is more about ActivityStreams)

   So I refuse to 'define' a type at build-time for each object/link type. I'm going to resolve it on start from the schema and use that for 'assertion' and property discovery.

   (This is for an Elixir project).

   I think this approach would also allow for automatic support of custom types too. I'd have to figure out a good caching mechanism (maybe relying on Cache headers + HTTP?) to make things easier.

   • Jacky Alciné (jalcine)'s status on Monday, 18-Feb-2019 00:50:50 CET Jacky Alciné

     in reply to

     Now looking at the #ActivityPub spec; things make a lot more sense in terms of resolving collections (those are those timelines!) and what not. This is probably the most 'important' part of the spec if you're attempting to fetch information and the like about a user using AP only: https://www.w3.org/TR/activitypub/#actor-objects

   • Jacky Alciné (jalcine)'s status on Monday, 18-Feb-2019 01:01:01 CET Jacky Alciné

     in reply to

     My goal? To have a "simple"/flexible #ActivtyStreams + #ActivityPub library for #Elixir so I can make toy services on top of it.

     Like a polling platform that can federate! Or even a simpler scrobbling platform. All of the actions are there in AP and one can define new ones if ever needed.