Home

I am outputting ActivityPub/ActivityStreams content for the listing of what is in a directory.

Think of it as the AP/AS version of output from the `ls` command

AP/AS has a whole bunch of stuff that can be used to represents files. Even sub-types of files

https://www.w3.org/TR/activitystreams-vocabulary/#object-types

And, while AP/AS has 'Collection' (and 'CollectionPage') —

https://www.w3.org/TR/activitystreams-vocabulary/#dfn-collection

AP/AS doesn't have a 'Directory' type (as a sub-type of 'Collection')

#ActivityPub #ActivityStreams #FediDev #FediDevs #Federation

@reiver Cool! Is this part of a larger project?

@maddyunderstars

Yes, I am creating a high performance read-only HTTP server for static files — that has built-in support for ActivityPub/ActivityStreams.

It also supports (the read operations of) WebDAV. So, it can be used as a shared read-only drive in operating-systems (OSes) that support WebDAV.

@reiver

This might be a misunderstanding.
Any property in ActivityPub can have multiple properties [except the few marked as 'functional'].
It does not need a special subtype.
If we have type ['CollectionPage', 'Collection', 'wd:Q201456'], it is a directory in a directory (?)
We have these nested structures in fedigeo anywhere, for example the UNESCO World Heritage or IATA Collection etc. We use wikidata (the data of wikipedia) so that anyone can use the label and infos for "directory" in any language …