silverpill

Results 56 comments of silverpill

Are there any use cases where unordered set might be desirable? Media attachments and key-value pairs in profiles are assumed to be ordered by many implementations (and users), so I'd...

All popular implementations use `Application` type for instance actors and `Service` type for automated accounts (aka bots). The role of Application actor is also described in [FEP-2677: Identifying the Application...

@evanp Thanks. I can see the new revision of "Service type" page which adds information about bots. But it seems that general recommendations haven't been changed? I think it could...

>OK, based on your feedback, it sounds like you think the types defined in the spec should reflect FEP definitions. I'm not sure that's the case. It's also not particularly...

>Another thing I would probably consider is a property like automated: true that can be used to signal "bot accounts" regardless of the actor type @trwnh Good idea

@samscott89 Thanks for update. Another place where MSRV is mentioned is Installation section of `README.md`

We have two new FEPs focused on machine readable indicators: - https://codeberg.org/fediverse/fep/src/branch/main/fep/6481/fep-6481.md ([SocialHub topic](https://socialhub.activitypub.rocks/t/fep-6481-specifying-activitypub-extension-support-with-nodeinfo/3993)). - https://codeberg.org/fediverse/fep/src/branch/main/fep/9fde/fep-9fde.md ([SocialHub topic](https://socialhub.activitypub.rocks/t/fep-9fde-mechanism-for-servers-to-expose-supported-operations/3999))

@yretenai >The issue is that we'd need to add a scope (or similar) term on top of this key class, and hope that major instances refactor their codebase to support...

I wrote a FEP that introduces two endpoints similar to `provideClientKey` and `signClientKey`: https://codeberg.org/fediverse/fep/src/branch/main/fep/ae97/fep-ae97.md The endpoints are `registerIdentity` and `verifyIdentity`, and they are meant to be discovered using well-known URL,...

At the beginning actor doesn't exist, and client should use `registerIdentity` endpoint (discovered via .well-known URL) to create it (per FEP-ae97). Is there a better way?