@FinchHaven @strypey I do not think that @naturzukunft2026 misunderstands this.There's a difference between #ActivityPub the protocol and #fediverse the on-the-wire reality, and in the latter #Mastodon is the post-facto interoperability leader.For there to be interoperabiity in a particular domain there needs to be agreement on data formats and msg exchanges, and the specs don't provide full coverage nor clear guidance on this. Though #ActivityStreams has a section on use cases it was designed to handle, they aren't fully specified.Of course it is perfectly fine, and highly encouraged to model a domain in the best possible way, but you won't be "part of the fediverse" until you implement enough of the post-facto Mastodon microblogging interop quirks.We don't have a good ecosystem-level extension approach, and the #FEP constitutes a best-effort. A bandaid that allows to present a best-practice in hopes it gets further adoption.I'm not sure that JSON-LD offers solace though.

We support that, with the caveats that if it's less than 15 minutes into the future we'll just assume your clock is off and send it anyway. And we make a good faith effort to deliver within 15 minutes after its scheduled time; as this is how often our scheduled tasks run. Otherwise, this has very little to do with the protocol.

@reiver I don't remember seeing those without content.But my software also parses name and summary, so it should be able to present objects without content as posts.

agreed, use syncthing (which I think @[email protected] also works on!) and call it a day. @[email protected] @[email protected]

@liaizon the service where that is hosted knows to serve either ActivityPub or a regular image depending on the Accept header.@reiver

@[email protected] cool! TIL, although I don't think it's applicable for me.

@oranadoz @reiver @hongminhee I believe the ActivityPub spec requires json-ld compaction if I'm not mistaken. (Section 7.1)

@dariusk I may be overly optimistic, but I'd like to move forward thinking that perhaps that was then and this is now. Let's chat tomorrow (?) about the merits of your implementation and see whether we can make some waves!

@[email protected] thanks for the kind words, appreciate it! I feel like we're almost in an exploratory phase of ActivityPub development, where we're still figuring out some best practices for some things. It'll only get better!

@[email protected] there was some talk about it awhile back which summarized reply chain traversal as essentially being decently reliable but exploitable (infinite loops, etc.) So chain traversal should have a hard cap for that reason, but ForumWG is also looking into recommending an alternative — resolvable context collections, in order to achieve backfill in a more performant manner. The same security implications apply, however, so that's something that ought to be discussed as well.

Thanks @[email protected]! That's good feedback and it's really exciting to know that there exist implementors out there whose default is not Note. I think at this point a real-time discussion at the next ForumWG re: the distinction between Article vs. Note would be beneficial. It'd be a continuation of the discussion we had last month. It's clear there are varied opinions on it, but as intimated by others, this might not actually be a problem that has technical solution.

@[email protected] said in Article vs. Note vs. Page: Since then WordPress has joined the Fediverse, and now Ghost is about to join as well. I think the ability to display rich content may soon become a serious competitive advantage. Completely agreed. The best time to consider a different approach is now, so I am hoping we can make some headway here at the WG meeting. Stay tuned... cc @[email protected] @[email protected]

@[email protected] @deadsuperhero Nice Article!

@hazelnoot @KevinMarks @risottobias That's not necessarily true.Anyway, the question was why shouldn't a server do this. The answer is because it makes many problems worse, and the benefits are tiny.