ether+nick

@evan then what's with all the parsing issues like the ones people are complaining about in this very thread?

@deborahh
I must be out of touch. I've never used "y'all", nor have I heard it used in Canada unironically.

@Profpatsch "Most implementations" treat it like it is -- JSON-LD. They might use different kinds of processors for publishing or consuming it, but on the wire, it's compliant JSON-LD, according to the ActivityPub and Activity Streams 2.0 specs.

@evan cause most Implementations already treat it as if it was plain JSON with a subset of ActivityPub semantics

on the atmosphere, there is an incentive to implement better functionalities because any user can change service at zero cost; on the fediverse i feel like it's the opposite: there is no real incentive in embracing new software because it's more a risk than anything else and it's not like you can bring your own instance data on another software without costs.

@Profpatsch what makes you think that's going to happen? It's unlikely. It would require a massive backwards-incompatible change. Why would we do that to a network that has tens of thousands of nodes, 100+ implementations?