#social 2020-01-01
2020-01-01 UTC
maybefbi joined the channel
# 
maybefbi is id mandatory? where do i get a list of what is mandatory?
# nightpool[m] mandatory for what?
# nightpool[m] different software is going to require different things
# nightpool[m] imo it's more important to focus on what you need for your software
# nightpool[m] also happy new year :)
# maybefbi nightpool[m], happy new year. in https://www.w3.org/TR/activitystreams-vocabulary/#dfn-link there is no id field. could that be the case for all Objects and Links?
# maybefbi nightpool[m], im trying to make a reddit clone first.
# nightpool[m] the ActivityPub spec says that all objects must have an id (and that id should resolve to a copy of the object) unless they're "intentionally transient"
# nightpool[m] in practical terms, most people give unique IDs to actors and their main objects, and then they have hash-based IDs like "https://cybre.space/@nightpool#publicKey" for subsidiary objects that they need to reference. things like Links or images that are embedded in more complicated objects generally don't need IDs
# nightpool[m] since you don't need to reference them elsewhere
# maybefbi nightpool[m], if that is the case then Activity like this in Example 3 without an ID: https://www.w3.org/TR/activitystreams-vocabulary/#dfn-activity is incorrect?
# nightpool[m] again, depends on what you're using it for. that example is from the ActivityStreams Vocabulary spec, which ActivityPub builds on. when you're using AS2 outside of ActivityPub, IDs are often less important
# maybefbi interesting.
# nightpool[m] When you're using ActivitySteams for ActivityPub, then you have to follow the additional requirements ActivityPub imposes
# maybefbi makes sense
# maybefbi i didnt realize activitystreams is intended for a more general use case than activitypub
# maybefbi nightpool[m], the "type" field is another field which according to the AS vocabulary has a finite number of possible values.
# maybefbi e.g. a "Mention" is a "Link" with more fields.
# maybefbi in the future could there be more allowed values to types?
# maybefbi s/types/"type" field"/
# nightpool[m] hmm
# nightpool[m] not sure what you mean
# nightpool[m] the type of an object can be any URI, it just happens that ActivitySteams primarily talks about ActivitySteams-typed objects
# nightpool[m] Here's what the spec has to say:
# maybefbi nightpool[m], in https://www.w3.org/TR/activitystreams-vocabulary/#dfn-activity there is a json field/key called "type". according to the spec it seems like "type" has only a finite number of allowed values. e.g. "type" can be "Object" or "Link" or "Activity" or ....
# nightpool[m] > Furthermore, while implementations are free to introduce new types of Objects beyond those defined by the Activity Vocabulary, interoperability issues can arise when applications rely too much on extension types that are not recognized by other implementations. Care should be taken to not unduly overlap with or duplicate the existing Object types.
# maybefbi ah
# maybefbi i guess i will make implementation very strict then
# nightpool[m] Example 8, in the as2 core spec, has an example of this
# maybefbi nightpool[m], the "Note" type?
# maybefbi never mind
# maybefbi it is "type": ["Place", "gr:Location"],
# nightpool[m] no, this one: https://www.w3.org/TR/activitystreams-core/#fig-an-object-that-is-both-a-place-and-a-gr-location
# maybefbi got it
# nightpool[m] sorry, just took me a little bit to figure out the right link
# maybefbi no worries
sl007, maybefbi and cwebber2 joined the channel