Quoted posts
-
@silverpill @trwnh @[email protected] Remember that one AI-based social network that said that they would never have follow relationships? Trying to imagine how to make that work with federation was a bit of a brain teaser. Their attempt at Mastodon interoperability fell apart for much simpler and much worse reasons though, so that experiment quickly turned into a nonstarter.
Maven Imported 1.12 Million Fediverse Posts (Updated) - We Distribute
A social network founded by a former OpenAI employee was caught importing public posts from Mastodon...and ran AI analysis to add tags to them.
We Distribute (wedistribute.org)
-
@[email protected] @silverpill @[email protected] i think the real question is what kind of world are we building here -- one limited to being a "social network"? that's so constrained. i don't want to live in that world. i don't want to "post" to "followers". i want to publish on my website and maybe syndicate to other websites of my explicit choosing. i want to be able to participate in discussions on various forums without having to make a new set of credentials for each one. neither of these require federation...
-
@trwnh @silverpill @[email protected] I guess we don't have to do pubsub if we don't want to.
But addressing conversations to a closed circle of people instead of having everything public is something that, broadly generalizing, people want, so we probably want some form of identity management and authentication and recipient addressing. My gut feeling is at that point we're in "social network" territory. But I've never been someone to dwell much on semantics and I don't feel strongly about it here. -
@[email protected] @silverpill @[email protected] that's basically just message passing. a message doesn't have to be a "post".
-
@[email protected] @silverpill @[email protected] to clarify: a message can also be a request, or a command, or a statement, or a query. we limit ourselves greatly when we think only in terms of “posts”. even within the limits of a “post”, we still have multiple contexts within which we can consider the message.
-
@infinite love ⴳ We already have different types of messages. Notes, articles, likes, etc. ActivityPub can handle those and more. How it typically works is that platforms ignore types they don't understand, which is expected behavior.
For example, Hubzilla has events and RSVPs. Other platforms don't. So only Hubzilla displays the post as an event. Everyone else displays it as a note.
Or a project management system might manage tasks over ActivityPub, but that doesn't mean other platforms will support it.
Platforms that understand posts and followers will interoperate. Project management systems will interoperate. But you have to get creative to get both of those to work together. -
@scott those are all posts
this isnt about activitypub
-
@scott i mean “message” in the sense that raw HTTP requests and responses are “messages”.
-
@infinite love ⴳ That can be anything you want to.
-
@infinite love ⴳ If it's a post, I'll use ActivityPub or Nomad Protocol. For everything else, I'll just use an API or something like that.
-
@scott i want an ecosystem of standardized APIs with semantics beyond just “posts”. does that help?
i want an API to talk to people and machines in equal measure
-
@infinite love ⴳ Sounds reasonable to me. I'm not sure how that's related to quoted posts (the topic of this thread), but I support the idea.
-
@scott the thread drifted a lot from “showing software icons” to “interoperability is the goal of software” to me disagreeing with that last bit
