@aaronwinstonsmith @rysiek @aral
Also bots, aren't people, but they may still have an account 8-)
Top-level
@aaronwinstonsmith @rysiek @aral Also bots, aren't people, but they may still have an account 8-) 7 comments
@oblomov @aaronwinstonsmith @rysiek @aral This was exactly what I was thinking 🤖 However, I do like the sentiment behind OP's toot. @rysiek @oblomov @aaronwinstonsmith @aral To be fair, people make bots and the accounts thereof. |
@oblomov @aaronwinstonsmith @aral @rysiek the ActivityPub spec specifically makes a distinction between “actors” (what we’re referring to as “users” here) and “human users” (people): https://www.w3.org/TR/activitypub/#actors.
ActivityPub does not dictate a specific relationship between "users" and Actors; many configurations are possible. There may be multiple human users or organizations controlling an Actor, or likewise one human or organization may control multiple Actors. Similarly, an Actor may represent a piece of software, like a bot, or an automated process. More detailed "user" modelling, for example linking together of Actors which are controlled by the same entity, or allowing one Actor to be presented through multiple alternate profiles or aspects, are at the discretion of the implementation.
I agree with the sentiment of the original post, but it’s going to be tricky when the tech has a different idea of reality.
@oblomov @aaronwinstonsmith @aral @rysiek the ActivityPub spec specifically makes a distinction between “actors” (what we’re referring to as “users” here) and “human users” (people): https://www.w3.org/TR/activitypub/#actors.
ActivityPub does not dictate a specific relationship between "users" and Actors; many configurations are possible. There may be multiple human users or organizations controlling an Actor, or likewise one human or organization may control multiple Actors. Similarly, an Actor...