FACT: 02/12/2020 is the last date in our calendar system that can be written in mm/dd/yyyy format using 02 for the month, 12 for the day, and 2020 for the year! Enjoy it while it lasts!!


Might fuck around and turn this into a bot

· · Web · 2 · 0 · 10

@darius in this post truth world, you're the hero we need and deserve.

With some of the AP stuff you've done in Node, have you ever attempted or stumbled upon any attempts at an AP C2S client library?

@yaaps no to both. I've *thought* about C2S but I can't imagine an implementation that isn't ultimately a UX nightmare (imo c2s is based on the flawed premise that AP activities and objects of the same technical type across different servers and services will have similar semantic (in the human communication sense) meaning)

Right. ActivityStreams 2.0 may be a semantic vocabulary, but that doesn't translate into reusable expectations of behavior for the content. Working in Lua, which also has prototype based inheritance and first class functions, I created an object hierarchy and some convenience functions and I've done some work towards APIs for what @cwebber refers to as drivers in his project (likely a term derived from another source, but I'm not good at remembering details out of their immediate context)

That's the unopinionated approach, which is reusable at the expense of being useful. That's fine in Lua, but JavaScript programmers probably expect an opinionated library

I think the API should look like an object store, preferably an in memory store with write ahead logging as a progressive enhancement when local storage is available. Do you have any opinions about libraries providing this capability and/or a nice API in this area?

@yaaps @cwebber I mean I usually just use redis and its Node.js library as an object store on the backend and localStorage (just the basic API, no library) on the frontend, but maybe I'm missing some context because I don't know the details of Chris' project (so I do not know what you are working toward)

No, you're not missing anything. It really is as simple as creating a wrapper over Redis or some other storage to cache objects from the outbox and to replicate objects so they're created in the inbox. A library is just a shim to conform to the expectations of the developer community. If it happens to hide some common pain points, that's a bonus, but the main point is simply to have support for the protocol found when someone searches for it

Sign in to participate in the conversation
Friend Camp

Hometown is adapted from Mastodon, a decentralized social network with no ads, no corporate surveillance, and ethical design.