Yeah I'm on vacation at the moment so work is a bit stalled, but github.com/pterotype-project/a is something like 80% complete. At the very leastaybe it would be helpful as a reference resource.
@InspectorCaracal @dansup

Getting stoked for Johhnyswim concert at House of Blues Boston!

Jeremy boosted

S.O and I were talking about it earlier. It's pretty impressive considering the multigenerational Van Damme split they had to do to make it engaging for both the original fans and their kids.

Detective Pikachu is a way better movie than it has any right to be. Like, shockingly good. String acting, strong writing, good story, cool effects. Not at all what I expected.

Jeremy boosted
Jeremy boosted

From now on whenever someone asks what my "gender identity" is I'm going to say "f(x) = x".

Jeremy boosted

roses are red
violets are blue
Status: :gh_closed_1::gh_closed_2::gh_closed_3:
can't reproduce

I'm currently rewriting the core of how Pterotype handles federation, so any docs would be soon outdated. The short answer is, it handles all AP object types right now but there are likely bugs. Once I'm done with the rewrite, I plan on testing federation with a bunch of other services including plume, so I will revisit this then

It's uh. A little too hard-core for my tastes

@cj @bhaugen
And the expansion algorithm also handles what you are talking about earlier in the thread, where "as:actor" expands to "w3.org/ns/activitystreams#acto" given an @ context of { "as": "w3.org/ns/activitystreams#" }

@cj @bhaugen
So I get context about what type of node each field represents just by doing the expansion algorithm, and can e.g. lazy-load the actor field because i know it's a Resource node and handle the published field as a DateTime object.

Does that cover the use case you are talking about?

Depends what you mean by "context processing". I'm just doing expansion/compaction, but expansion is smart to understand that e.g. `{"actor": "foo"}` should expand to `{"w3.org/na/activitystreams#acto": [{"@ id": "foo"}]}` while `{"published": "theDate"}` should expand to {"w3.org/ns/activitystreams#publ": [{"@ type": "w3.org/2001/XMLSchema#dateTime", "@ value": "theDate"}]}`.

Yup! A little inconsistently right now apparently, since I replied to this from WordPress... Eh, that's the point of dogfooding software I suppose

What sort of privacy issues? JSON-LD is just a serialization format, it doesn't say what data you should be putting in it... I know @kaniini had some issues with linked data signatures preventing key rotation, is that what you're talking about?

Womp. Yeah, the beta version of Pterotype seems to totally thrash the database... Something which the v2 will be much better about 🙃

@pea it's really incredible how many problems opening emacs solves.

Jeremy boosted

More than JSON: ActivityPub and JSON-LD

In which our hero discovers the power of normalization and JSON-LD The problem with JSON I’ve been doing a lot of research for my current side project, Pterotype. It’s a new kind of social network built as a WordPress plugin that respects your freedom, encourages choice, and interoperates with existing social networks through the power […] jeremydormitzer.com/blog/more-

Show more
Mastodon for Tech Folks

This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either! We adhere to an adapted version of the TootCat Code of Conduct and follow the Toot Café list of blocked instances. Ash is the admin and is supported by Fuzzface, Brian!, and Daniel Glus as moderators. Hosting costs are largely covered by our generous supporters on Patreon – thanks for all the help!