This is an interesting (pronounced like "frustrating") thread.

Emelia 👸🏻

I think it'd be neat to see a FEP for follow-time activity selection.

mx alex tax1a - 2020 (4)

@jenniferplusplus we're mutuals with one of the other people involved with the original spec, and they've had good humor about our criticism

and also yeah, you've seen us in full-on "yelling about oauth2" mode

Jenniferplusplus

@samsethi @julian
And there are solutions to that. But they take real work and coordination. We should have schemas. We should have a schema registry. We should have defined fallback mechanisms. We should have conformance profiles.

But none of these things exist, and it's killing us.

Jenniferplusplus

@mattly There is something happening that induces some deeply rooted and powerful magical thinking around this concept. But I have not figured out what it is or how to disrupt it.

Matthew Lyon

@jenniferplusplus I’ve been victim to it once before; I think it’s a thing that happens when one gets too into the abstract realm, and doesn’t do any actual implementing. It’s easy to forget the real world exists and has constraints when you don’t work in it.

hidden

@jenniferplusplus @julian If we'd remove Mastodon from the picture would the problem go away?

If we had 100% compliant ActivityPub app, whatever that means, would it work with another 100% compliant one? Say podcasting app, badge app, events app and blogging app...

The problem seems to be the undefined or open to interpretation protocol...

Overriding AS object to do something else because your app won't use it doesn't help either...

Noah Kennedy

@jenniferplusplus my hot take: AP is another example of how the W3C really isn't super useful as a standards body and tends to be actually counterproductive

having been involved with IETF standards processes before, there's such a big difference between a standards effort led by actual stakeholders which requires a diverse set of implementations to be accepted and what happens at the W3C with AP, JSON-LD, and RDF.

this is just laughably bad standards work

julian

@[email protected] @[email protected] that's exactly it.

I'm not going to go as far as using ivory tower imagery, but sometimes I've seen discussion occur around issues so abstract and theoretical that there is practically no way for me to implement it without having to throw everything away and start from scratch.

The real world is far messier, and the fact that we're able to talk to each other at all over ActivityPub is frankly a miracle... but that's actually par for the course if you look at practically any other protocol.

Email? Good god yes. DNS? Yup.

Jenniferplusplus

@hidden @julian
No. Mastodon is the worst offender, but the problem is that ActivityPub doesn't produce interoperability. There's no such thing as being AP compliant. That's not even a concept that makes sense. So we'd be right back here in a year or two, complaining about whatever other app ascended to popularity.

Hrefna (DHC)

@noah

One observation I've had previously is that:

W3C creates standards to solve problems that may or may not exist in reality. They charter groups to come together and solve problems in a way that aligns with their other standards, trying to get a consensus solution to a hypothetical (or niche) problems using consensus solutions to other hypothetical problems.

You can see this in the history of RDF, then in the history of JSON-LD, then in the history of AP.

@jenniferplusplus

Noah Kennedy

@hrefna @jenniferplusplus that is an incredibly good way of putting it

Michael T. Bacon, Ph.D.

@jenniferplusplus

Ooft, yeah. I've been doing a bunch with RDF and JSON-LD recently in non-AP contexts, and there's a huge amount of power there but HOLY PEAS it is NOT an interoperability standard, nor could it ever be one, I think. They are ontological data format and linking standards that REQUIRE a strong defining model for interop.

I'm a fossil from the old days of the IMAP and friends IETF standards. AP is so freakin' wobbly compared to those.

Hrefna (DHC)

@noah

Sometimes they hit on a core concern or problem, but then they keep asking "but what if" until people ignore 90% of the spec (XML I'm looking at you) and/or it gets applied to other specs that then get ignored (how many XML specs are there?). Many times the spec seems so abstract as to be unimplementable in a useful form (DIDs! you're up!)

But there's now a spec!

…that no one uses or can use. But it exists!

Specs for the sake of having specs.

@jenniferplusplus

Greg

@jenniferplusplus @julian discovered firsthand when working on my toy AP poster that Mastodon won't even do the "right" thing with an "image" object - instead of converting this to an embedded image in a post, it just shows it as a plain link! have to use their Attachments thing to a note activity to get that to work

Hrefna (DHC)

@noah

Heh, that's basically the thing I've been working on that I keep getting discouraged/overly frustrated by.

@jenniferplusplus @julian

Hrefna (DHC)

@MichaelTBacon

Yeah, that is one of the core points that BlueSky discussed in "why not AP":

Because if you want interoperability the RDF-isms just. don't. work. To the degree they do work, it is extremely expensive to validate and work with.

It's a model for describing things, not a model to be _understood_ about the things you are describing. That requires separate, out-of-band communication.

@jenniferplusplus

silverpill

@jenniferplusplus I think when it comes to objects, duck typing is a good solution. Look at properties instead of types

@julian

Jenniferplusplus

@silverpill @julian it's not a strong argument for activitypub if it can't be effectively implemented in languages with compile time type checking

silverpill

@jenniferplusplus @julian My project is written in Rust and for me duck typing AP objects is not a problem. I don't have experience with other languages, but there shouldn't be any problems with them either

Sir Alecks Gates

@silverpill @julian @jenniferplusplus

Yes, it's quite easy to parse JSON in rust at compile time. There's even a package to generate a struct from a JSON schema.