NodeBB

@steve @hongminhee I mentioned this thread in the #ActivityPub #C2S tracking issue. I think there's a fundamental risk that C2S is going sideways because of misconceptions between devs on where things are / should be headed.https://codeberg.org/fediverse/delightful-fediverse-experience/issues/130#issuecomment-11737818

@hongminhee @kopper I'm too stupid to understand AP specifically (but I have a deep CS background).. I've always wondered why this wasn't the model by default? Using UUIDv7 you could mark every in order of timetime.I think you could push the separation of intents further. Make a "AP post" hold all of the metadata, but make the actual text an attachment like an image, video, audio etc.. then you could just store all of the text in blobs in storage to be easily replicated/mirrored and deleted on bulk... "even as ciphertext" requiring the original toot to fetch and decrypt.also. I think the idea of attaching a user to an instance (domain) was always a mistake. A user should be whoever owns the key material on a frontend (endpoint), and it should be able to ask any "client in your meaning" to be it's new primary location (they can be AP broadcast... user with public key X is now defaulting to client Y)... BUT all of this is fan fiction, nobody has even solved the storage problem. We're still defaulting to 10,000 S3 buckets.Turning media URIs from dedicated single URLS to magnet:<hashes> that can be pulled down from multiple locations incase the original dies feels like REALLLLLY low hanging fruit that nobody has touched (and It kind of annoys me nobody has).

@trwnhthe type information is largely unnecessary and shouldn't factor into handling CRUDServers needs to know the core type / class in order to determine the "owner" of an object (actor, attributedTo, etc).how does the server know which ids to assign and which ones not to?The result property could be declared as special in the FEP. Servers will be required to assign IDs to embedded activities. What is a blank node identifier, id: null? Using this to indicate a need for ID is a good idea too.I don't think side effect activities should be fragments.lastly as:result itself maybe doesn't have these semantics defined, so should a subproperty or different property be used, or do we skip non-CRUD results?Why skip non-CRUD results? I think side effects shouldn't be limited to basic activities like Create/Update/Add/Remove.@steve

@naturzukunft2026@mastodon.social yes that's correct, it's just a flat list for ease of processing. The tree building takes place after all of the objects are received and processed.

I opened a issue in the swicg ActivityPub API repo about a gap i keep running into: how does a C2S client access server-local metadata about foreign objects?Thread collections, read status, notifications — your server knows things about remote objects that the client needs, but AP has no vocabulary for it.https://github.com/swicg/activitypub-api/issues/60#ActivityPub #Fediverse #C2S@evanprodromou

Bring it on!#ActivityPub Social API is getting a lot of attention and traction on the implementation side! Join the fun, in this area where there's a fine future for the #fediverse social networking.Some new updates to the list of client-to-server #C2S parts of the AP open standard:https://codeberg.org/fediverse/delightful-fediverse-experience/issues/130 Added the projects of @kopper and a new C2S article by @mediaformat

I end the talk with an invitation for devs and non-developers alike to submit some user-stories about what they would want from a general AP clienthttps://github.com/swicg/activitypub-api

@julian i recognize we are not there yet, but i do think we need to broadly move toward an architecture where a server going down isn’t as catastrophic as it currently is.