Developers building ActivityPub applications picking what AS2 object type to use when doing ActivityPub federation:
General Discussion
8
Posts
3
Posters
2
Views
-
Developers building ActivityPub applications picking what AS2 object type to use when doing ActivityPub federation:
-
Developers building ActivityPub applications picking what AS2 object type to use when doing ActivityPub federation:
@thisismissem Yeah, I'm curious about this. What is the blocker for federating other object types? Is it that there isn't agreement around how to display objects that aren't Notes? Or are some objects less well defined?
-
@thisismissem Yeah, I'm curious about this. What is the blocker for federating other object types? Is it that there isn't agreement around how to display objects that aren't Notes? Or are some objects less well defined?
@FreddieJ its just Mastodon doesn't support many other object types, and everyone wants compatibility with Mastodon.
-
undefined julian shared this topic
undefined ζ΄ͺ ζ°ζ (Hong Minhee) shared this topic
-
Developers building ActivityPub applications picking what AS2 object type to use when doing ActivityPub federation:
thisismissem@hachyderm.io Not to worry, in maybe a decade we'll upgrade to handling square objects and squircle objects too!
-
@FreddieJ its just Mastodon doesn't support many other object types, and everyone wants compatibility with Mastodon.
@thisismissem I see, thanks. So in theory, "Event" objects as defined in ActivityStreams should be easy to federate if two platforms actually support it?
-
System shared this topic
-
@thisismissem I see, thanks. So in theory, "Event" objects as defined in ActivityStreams should be easy to federate if two platforms actually support it?
freddiej@newsmast.social yes (sorry to butt in) β an example would be
as:Pageandas:Article. Threadiverse softwares like Lemmy, Piefed, and NodeBB handle this fine, showing title and content with the appropriate attachments, but in Mastodon they currently get collapsed into just the title and URL, as that is the current fallback handler for objects that are not notes. -
@julian @thisismissem Hi Julian, no worries, thanks for the clarification. I had thought this was the case from when I attended the early Threadiverse meetups. Looking at the AS spec, they support loads of complex objects it would be great to see supported more widely in the Fediverse (like events) and just wondered what the barrier to adoption might be?
-
@thisismissem I see, thanks. So in theory, "Event" objects as defined in ActivityStreams should be easy to federate if two platforms actually support it?
@FreddieJ yes. As long as you agree on what the properties mean, and activities performed on them, then you'd be fine.
Gli ultimi otto messaggi ricevuti dalla Federazione
-
@FreddieJ yes. As long as you agree on what the properties mean, and activities performed on them, then you'd be fine.
-
@julian @thisismissem Hi Julian, no worries, thanks for the clarification. I had thought this was the case from when I attended the early Threadiverse meetups. Looking at the AS spec, they support loads of complex objects it would be great to see supported more widely in the Fediverse (like events) and just wondered what the barrier to adoption might be?
-
freddiej@newsmast.social yes (sorry to butt in) β an example would be as:Page and as:Article. Threadiverse softwares like Lemmy, Piefed, and NodeBB handle this fine, showing title and content with the appropriate attachments, but in Mastodon they currently get collapsed into just the title and URL, as that is the current fallback handler for objects that are not notes.
-
@thisismissem I see, thanks. So in theory, "Event" objects as defined in ActivityStreams should be easy to federate if two platforms actually support it?
-
thisismissem@hachyderm.io Not to worry, in maybe a decade we'll upgrade to handling square objects and squircle objects too!
-
@FreddieJ its just Mastodon doesn't support many other object types, and everyone wants compatibility with Mastodon.
-
@thisismissem Yeah, I'm curious about this. What is the blocker for federating other object types? Is it that there isn't agreement around how to display objects that aren't Notes? Or are some objects less well defined?
-
Developers building ActivityPub applications picking what AS2 object type to use when doing ActivityPub federation:
