-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
support block lists #40
Comments
Regarding AS markup, one can expose blocking as a list of blocking and unblocking activities – but that would make it hard for clients to fully resolve the full state of things, so not really sure how to express this in AS. In mf2 I would say an extended XFN-like list with pagination rather than h-entries. Just wanted to note this as early as possible before anyone goes down the activity representation route :) |
thanks @voxpelli! granary uses AS as its common base format, so we need something there. most users will probably consume mf2, though, so I'm fine with any AS representation that works. |
AS2 Block activity type: https://www.w3.org/TR/activitystreams-vocabulary/#dfn-block i didn't see an AS1 Block activity or object type or verb. |
tentative proposed mf2: based on http://microformats.org/wiki/block-list-brainstorming#simple_container_of_hCards (the |
Small note on markup of this: It makes sense I think to have a format that allows for creation and modification of blocks over Micropub and that means that a block entity in itself needs to convey that it is a blocking of something and not just have that be conveyed through the context in which it exists, such as a list of h-card getting the meaning of blocking something by being part of a h-blocklist rather than them being a h-block or some other property of an individual block. |
ok, granary now fetches and converts twitter blocklists. no explicit mf2 yet, just a list of |
sounds like we're nixing the explicit ...which means this is done! closing. |
... both fetching them and covering then to mf2. lots of details in snarfed/bridgy#473.
first step is to catalog each silo's feature(s), API support, and link(s) to docs. twitter is the main (only) silo people like @voxpelli @kevinmarks @kylewm have been asking for so far.
another first step is to nail down the AS and mf2 representations we want.
The text was updated successfully, but these errors were encountered: