@cwebber @puppygirlhornypost2 yeah Mastodon & GoToSocial only send it to the author but IMO they’re maybe being a little too… anxious? about it.

@erincandescent @cwebber @puppygirlhornypost2 it should be an option but people want it to be a one-click button

i think they don't go far enough tbh, if i send a private Like it shouldn't be publicly visible in the list of likes. at most, its uri might end up in the collection's items.

@trwnh@mastodon.social @erincandescent@akko.erincandescent.net @cwebber@social.coop usually you have object | link and if you're emitting an activity on another post people tend to link the remote object so that implementations have to fetch from that server instead of relaying

@puppygirlhornypost2 @trwnh @cwebber Object already permits just putting an Object-ID-URI there, Object | Link is a horrible overcomplicated mess (IMO) that should never have made it into the standard >_<

Oh well

@erincandescent @cwebber @puppygirlhornypost2 i'm like 60% convinced that either Link should not have been part of AS2 or otherwise most instances of range=(Object|Link) are in fact a mistaken attempt to describe jsonld's type:id construct

i actually recently tried to think about where you would *actually* want to use a Link node and i cannot think of any. there's like one or two examples and none of them make sense. in most cases why would you need to reify a Link when you can use a property?

@trwnh @cwebber @puppygirlhornypost2 The one case I can think of is the “url” property and there its basically performing an analogous role to HTML <link rel=X> tags.

@erincandescent @cwebber @puppygirlhornypost2 as:url is a bit cursed because sometimes it seems like people stuff a string href in there? but the jsonld context defines it as type:id. so the only "correct" way to use `url` is to *always* have it be a Link and never anything else. to get around this you would need to define a `urlValue` term which is as:url but without the type:id in the definition. but this is still kinda bad design because as:url should either be object prop or datatype prop...

@trwnh@mastodon.social @erincandescent@akko.erincandescent.net @cwebber@social.coop I don't know. most of the time you will actually see URIs like erin said above. I don't think I've ever seen anyone actually sit there with a full link object for the id of another object (although you could. https://www.w3.org/TR/activitystreams-vocabulary/#dfn-id)

@erincandescent @cwebber @puppygirlhornypost2 i mean in an RDF sense it's unclear whether as:url points to a "thing" or a "string". the synthesis answer that makes the least errors is to say that it is always a "thing", and that "thing" is always a Link... but i kinda wonder if the better model would've been to do something like HAL's _links or define a property specifically for links, but without the semantics of as:url (so links to things which aren't representations of the resource)

@trwnh@mastodon.social @erincandescent@akko.erincandescent.net @cwebber@social.coop if i see

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "summary": "Sally offered the Foo object",
  "type": "Offer",
  "actor": {
    "type": "Person",
    "id": {
      "type": "Link",
      "href": "http://sally.example.org"
    },
    "summary": "Sally"
  },
  "object": "http://example.org/foo"
}

@puppygirlhornypost2 @trwnh @cwebber that’s flatly illegal. id must be a string that encodes a URI.

@erincandescent@akko.erincandescent.net @trwnh@mastodon.social @cwebber@social.coop OH I know why i am confusing this i am using AS logic not AP

@puppygirlhornypost2 @trwnh @cwebber no its flat out illegal AS2 (and indeed flat out illegal JSON-LD), AP imposes no additional requirements here.

@erincandescent@akko.erincandescent.net @trwnh@mastodon.social @cwebber@social.coop im so confused to why it specifies Object | Link here then unless I am misinterpreting what that means which is always possible

@puppygirlhornypost2 @trwnh @cwebber Domain is the types this property applies to

Range is the type of the value(s) of this property

@puppygirlhornypost2 @erincandescent could, but it doesn't make for semantics. what does it mean to reply to a Link instead of replying to a Note? like what's the link context there. we know the link target is the as:href and we might have some link relation declared as the as:rel, but what does the arc of that graph edge look like? can you even draw such an edge? technically you are not relating A to B, you are relating A to an intermediate blank node whose href is B. how to reason around that?

@puppygirlhornypost2 @cwebber @trwnh Anyway the explainers for “id” and “type” are a bit wonky because they’re special magical RDF terms unlike anything else and so their domain is actually everything and their range is always a URI (or in the case of type: one or more URIs).

@erincandescent@akko.erincandescent.net @cwebber@social.coop @trwnh@mastodon.social well that certainly doesn't help with confusion lol

@erincandescent@akko.erincandescent.net @cwebber@social.coop @trwnh@mastodon.social Here we are I have found a much more valid example. https://www.w3.org/TR/activitystreams-vocabulary/#dfn-subject a subject can be either.

@puppygirlhornypost2 @erincandescent in rdf you have the concept of "type" which points to a Class. if everything is a triple of the form "alice knows bob", then we can start to describe each term individually:

- alice isA Person
- bob isA Person
- knows isA Property
- Person isA Class

as2.0 "id" is just a straight alias for jsonld `@\id` and that basically just indicates the subject for that node. you can reconstruct statements of the form "id property value"

as2.0 "type" is rdf:type p much.