#ActivityStreams

Here is my work-in-progress FEP for using JSON Resume with ActivityPub:

FEP-6158: ActivityPub 'Resume' Object: JSON Resume expressed as JSON-LD

https://codeberg.org/reiver/fep/src/branch/fep-6158/fep/6158/fep-6158.md

I prefer to write for clarity, so it still needs work.

#ActivityPub #ActivityStreams #FediDev #ProToGo #JSONLD #JSONResume #fep6158 #fep_6158

Here is my work-in-progress FEP for using JSON Resume with ActivityPub:

FEP-6158: ActivityPub 'Resume' Object: JSON Resume expressed as JSON-LD

https://codeberg.org/reiver/fep/src/branch/fep-6158/fep/6158/fep-6158.md

I prefer to write for clarity, so it still needs work.

#ActivityPub #ActivityStreams #FediDev #ProToGo #JSONLD #JSONResume #fep6158 #fep_6158

Here is my work-in-progress FEP for using JSON Resume with ActivityPub:

FEP-6158: ActivityPub 'Resume' Object: JSON Resume expressed as JSON-LD

https://codeberg.org/reiver/fep/src/branch/fep-6158/fep/6158/fep-6158.md

I prefer to write for clarity, so it still needs work.

#ActivityPub #ActivityStreams #FediDev #ProToGo #JSONLD #JSONResume #fep6158 #fep_6158

Here is my work-in-progress FEP for using JSON Resume with ActivityPub:

FEP-6158: ActivityPub 'Resume' Object: JSON Resume expressed as JSON-LD

https://codeberg.org/reiver/fep/src/branch/fep-6158/fep/6158/fep-6158.md

I prefer to write for clarity, so it still needs work.

#ActivityPub #ActivityStreams #FediDev #ProToGo #JSONLD #JSONResume #fep6158 #fep_6158

Here is my work-in-progress FEP for using JSON Resume with ActivityPub:

FEP-6158: ActivityPub 'Resume' Object: JSON Resume expressed as JSON-LD

https://codeberg.org/reiver/fep/src/branch/fep-6158/fep/6158/fep-6158.md

I prefer to write for clarity, so it still needs work.

#ActivityPub #ActivityStreams #FediDev #ProToGo #JSONLD #JSONResume #fep6158 #fep_6158

I may have written a JSON-LD schema for JSON Resume.

It is defined in terms of ActivityPub.
For example:

'Resume' is a sub-type of an ActivityPub 'Object'. There are some new fields defined. Etc.

...

Now the question is — where do I put it?

Do I create a pull-request to the JSON Resume resume-schema repo?

Do I create a FEP?

Do I put it somewhere else?

#ActivityPub #ActivityStreams #FediDev #ProToGo #JSONLD #JSONresume

I may have written a JSON-LD schema for JSON Resume.

It is defined in terms of ActivityPub.
For example:

'Resume' is a sub-type of an ActivityPub 'Object'. There are some new fields defined. Etc.

...

Now the question is — where do I put it?

Do I create a pull-request to the JSON Resume resume-schema repo?

Do I create a FEP?

Do I put it somewhere else?

#ActivityPub #ActivityStreams #FediDev #ProToGo #JSONLD #JSONresume

I may have written a JSON-LD schema for JSON Resume.

It is defined in terms of ActivityPub.
For example:

'Resume' is a sub-type of an ActivityPub 'Object'. There are some new fields defined. Etc.

...

Now the question is — where do I put it?

Do I create a pull-request to the JSON Resume resume-schema repo?

Do I create a FEP?

Do I put it somewhere else?

#ActivityPub #ActivityStreams #FediDev #ProToGo #JSONLD #JSONresume

My personal desire would be to create a format from scratch (because you are in control, you get something bespoke to your needs, and it is personally satisfying), but —

I think there is probably an advantage to using something (such as JSON resume) that already has wide adoption.

I guess that makes me inclined towards the latter.

...

So, if I go that way, I would have to decide: plain JSON or JSON-LD.

#ActivityPub #ActivityStreams #FediDev #ProToGo #JSONLD #JSONresume

More on a resume / CV on the Fediverse on Social Web.

Another option could be to use something like "JSON resume":

https://jsonresume.org/

https://github.com/jsonresume/resume-schema/blob/master/job-schema.json

It seems to be popular.

It isn't JSON-LD. Although I think it would be straightforward to translate it to JSON-LD, if that was desired.

#ActivityPub #ActivityStreams #FediDev #ProToGo #JSONLD #JSONresume

More on a resume / CV on the Fediverse on Social Web.

Another option could be to use something like "JSON resume":

https://jsonresume.org/

https://github.com/jsonresume/resume-schema/blob/master/job-schema.json

It seems to be popular.

It isn't JSON-LD. Although I think it would be straightforward to translate it to JSON-LD, if that was desired.

#ActivityPub #ActivityStreams #FediDev #ProToGo #JSONLD #JSONresume

More on a resume / CV on the Fediverse on Social Web.

Another option could be to use something like "JSON resume":

https://jsonresume.org/

https://github.com/jsonresume/resume-schema/blob/master/job-schema.json

It seems to be popular.

It isn't JSON-LD. Although I think it would be straightforward to translate it to JSON-LD, if that was desired.

#ActivityPub #ActivityStreams #FediDev #ProToGo #JSONLD #JSONresume

On Tags (including Hash-Tags) in ActivityPub.

1/

I think new developers coming to ActivityPub want to write something like:

"tag": ["apple", "banana", "cherry"]

It is unfortunate that that isn't valid ActivityPub. But, that it must instead be:

"tag": [
{
"type": "Hashtag",
"name": "#apple"
},
{
"type": "Hashtag",
"name": "#banana"
},
{
"type": "Hashtag",
"name": "#cherry"
}
]

...

#ActivityPub #ActivityStreams #FediDev #HashTag #HashTags #Tag #Tags

On Tags (including Hash-Tags) in ActivityPub.

2/

A new version of ActivityPub could extend the type of "tag" from:

Object | Link

to:

Object | Link | xsd:string

And that would make the following valid ActivityPub:

"tag": ["apple", "banana", "cherry"]

Of course, it would have to be specified how to interpret this. (Ex: as "type":"Hashtag", or whatever.)

#ActivityPub #ActivityStreams #FediDev #HashTag #HashTags #Tag #Tags

On Tags (including Hash-Tags) in ActivityPub.

1/

I think new developers coming to ActivityPub want to write something like:

"tag": ["apple", "banana", "cherry"]

It is unfortunate that that isn't valid ActivityPub. But, that it must instead be:

"tag": [
{
"type": "Hashtag",
"name": "#apple"
},
{
"type": "Hashtag",
"name": "#banana"
},
{
"type": "Hashtag",
"name": "#cherry"
}
]

...

#ActivityPub #ActivityStreams #FediDev #HashTag #HashTags #Tag #Tags

On Tags (including Hash-Tags) in ActivityPub.

2/

A new version of ActivityPub could extend the type of "tag" from:

Object | Link

to:

Object | Link | xsd:string

And that would make the following valid ActivityPub:

"tag": ["apple", "banana", "cherry"]

Of course, it would have to be specified how to interpret this. (Ex: as "type":"Hashtag", or whatever.)

#ActivityPub #ActivityStreams #FediDev #HashTag #HashTags #Tag #Tags

On Tags (including Hash-Tags) in ActivityPub.

1/

I think new developers coming to ActivityPub want to write something like:

"tag": ["apple", "banana", "cherry"]

It is unfortunate that that isn't valid ActivityPub. But, that it must instead be:

"tag": [
{
"type": "Hashtag",
"name": "#apple"
},
{
"type": "Hashtag",
"name": "#banana"
},
{
"type": "Hashtag",
"name": "#cherry"
}
]

...

#ActivityPub #ActivityStreams #FediDev #HashTag #HashTags #Tag #Tags

There is also the other question of — would the resume / CV be JSON-LD.

On one hand, if it was in JSON-LD, it would make it machine-legible similar to ActivityPub.

On the other hand, I don't think anyone is going to write JSON-LD (especially HTML embedded in a JSON string value) by hand. But, I do think some people will want to write their resume by hand.

It feels like user-experience is fighting with JSON-LD based machine-legibility.

#ActivityPub #ActivityStreams #FediDev #ProToGo #JSONLD

How could you represent a resume / CV on the Fediverse and Social Web? Where would you put it? Etc?

I think it is tempting to put the whole resume in the Actor document.

But, it is probably better for the Actor document to point (rather than include) it. And, have the resume / CV live somewhere else.

It should probably be done in a way that let's people have multiple resumes / CV. For example, for different roles / career tracks, etc.

#ActivityPub #ActivityStreams #FediDev #ProToGo #JSONLD

There is also the other question of — would the resume / CV be JSON-LD.

On one hand, if it was in JSON-LD, it would make it machine-legible similar to ActivityPub.

On the other hand, I don't think anyone is going to write JSON-LD (especially HTML embedded in a JSON string value) by hand. But, I do think some people will want to write their resume by hand.

It feels like user-experience is fighting with JSON-LD based machine-legibility.

#ActivityPub #ActivityStreams #FediDev #ProToGo #JSONLD

There is also the other question of — would the resume / CV be JSON-LD.

On one hand, if it was in JSON-LD, it would make it machine-legible similar to ActivityPub.

On the other hand, I don't think anyone is going to write JSON-LD (especially HTML embedded in a JSON string value) by hand. But, I do think some people will want to write their resume by hand.

It feels like user-experience is fighting with JSON-LD based machine-legibility.

#ActivityPub #ActivityStreams #FediDev #ProToGo #JSONLD

How could you represent a resume / CV on the Fediverse and Social Web? Where would you put it? Etc?

I think it is tempting to put the whole resume in the Actor document.

But, it is probably better for the Actor document to point (rather than include) it. And, have the resume / CV live somewhere else.

It should probably be done in a way that let's people have multiple resumes / CV. For example, for different roles / career tracks, etc.

#ActivityPub #ActivityStreams #FediDev #ProToGo #JSONLD

How could you represent a resume / CV on the Fediverse and Social Web? Where would you put it? Etc?

I think it is tempting to put the whole resume in the Actor document.

But, it is probably better for the Actor document to point (rather than include) it. And, have the resume / CV live somewhere else.

It should probably be done in a way that let's people have multiple resumes / CV. For example, for different roles / career tracks, etc.

#ActivityPub #ActivityStreams #FediDev #ProToGo #JSONLD

#ActivityPub #ActivityStreams #FediDev #SocialWeb #SocialWebIncubatorCommunityGroup
#swicg #w3c

Remote Inbox Architecture

1/

This, the Remote Inbox Architecture, is an architecture for a Fediverse back-end server that I think could be useful.

Here is how it works — there are (at least) 2 servers involved: (1) the main back-end server, and (2) a remote inbox server.

The actor file on main back-end server "points" the inbox to the remote server.

It separates the user's content from the front-end related functionality

...

#ActivityPub #ActivityStreams #FediDev #RemoteInbox

Remote Inbox Architecture

2/

The Remote Inbox server deals with incoming activities, objects, etc, from other users..

The front-end can get the inbox (and other feeds') data from the Remote Inbox server.

(You'd probably want to store cached data from the Fediverse elsewhere from these two servers, as I've said before. But, that is a separate thread.)

#ActivityPub #ActivityStreams #FediDev #RemoteInbox

Remote Inbox Architecture

1/

This, the Remote Inbox Architecture, is an architecture for a Fediverse back-end server that I think could be useful.

Here is how it works — there are (at least) 2 servers involved: (1) the main back-end server, and (2) a remote inbox server.

The actor file on main back-end server "points" the inbox to the remote server.

It separates the user's content from the front-end related functionality

...

#ActivityPub #ActivityStreams #FediDev #RemoteInbox

On moving an actor's content.

4/

Or, instead of using the ActivityPub 'Update' activity —

Couldn't we use the ActivityPub 'Move' activity.

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

With the "origin" and "target" fields.

Where "origin" contains the old ID URL, and "target" contains the new ID URL.

.

#ActivityPub #ActivityStreams #FediDev

On moving an actor's content.

3/

There a many different conventions we could come up with to allow an ActvityPub 'Update' activity to be used to change an object's "id" field.

We (the Fediverse developer community) just need to pick one that everyone is willing to implement.

For example, perhaps the "origin", "result", or "target" field should be used:

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

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

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

Or —

...

#ActivityPub #ActivityStreams #FediDev

On moving an actor's content.

2/

Could an ActivityPub 'Update' activity be used to move objects from one server to another server?

Could an 'Update' activity be used to change an object's "id" field?

After all, the "id" is used to identity what is being changed. It is the targeting mechanism.

How can you provide the old "id" to target the (old) object you want to change the "id" of, while also providing a new "id"?

https://www.w3.org/TR/activitypub/#update-activity-inbox

...

#ActivityPub #ActivityStreams #FediDev

On moving an actor's content.

1/

One of the things that comes up on the Fediverse from time to time — is the ability for people to move their accounts.

For example, someone started off at:

＠joeblow＠example.com

But, now wants to "move" to:

＠misterx＠host.example

There is a mechanism to do that.

That mechanism moves their followers, their followees, BUT —

It does NOT move their content over!

That is a problem. Could we address this‽

...

#ActivityPub #ActivityStreams #FediDev

I think ActivityPub Partial Updates won't work well with attachments or tags.

Not unless there is a way to reliably just target the item in the attachments or tags array that you want to modify. AFAIK, there isn't.

You have to download the old version of the whole attachments or tags array first, update it locally, and then upload the whole (updated) thing. This creates a race-condition.

See also: https://mastodon.social/@reiver/116446675376417979

#ActivityPub #ActivityStreams #FediDev

In ActivityPub, these are all equivalent:

"type":"Banana"

"type":["Banana"]

"type":{"＠id":"Banana"}

"type":[{"＠id":"Banana"}]

"type":{"id":"Banana"}

"type":[{"id":"Banana"}]

"＠type":"Banana"

"＠type":["Banana"]

"＠type":{"＠id":"Banana"}

"＠type":[{"＠id":"Banana"}]

"＠type":{"id":"Banana"}

"＠type":[{"id":"Banana"}]

#ActivityPub #ActivityStreams #FediDev #JSONLD

In ActivityPub, these are all equivalent:

"type":"Banana"

"type":["Banana"]

"type":{"＠id":"Banana"}

"type":[{"＠id":"Banana"}]

"type":{"id":"Banana"}

"type":[{"id":"Banana"}]

"＠type":"Banana"

"＠type":["Banana"]

"＠type":{"＠id":"Banana"}

"＠type":[{"＠id":"Banana"}]

"＠type":{"id":"Banana"}

"＠type":[{"id":"Banana"}]

#ActivityPub #ActivityStreams #FediDev #JSONLD

ActivityPub specifications don't seem to provide a way to do Idempotent POSTs to your outbox.

That seems like a problem for C2S to me.

Networks are unreliable. You cannot tell the difference between an unreceived request vs an unreceived response. You'll get unwanted identical duplicate activities.

Although it isn't difficult to solve — a convention just needs to be picked.

For example, a new Idempotency field could be added to the JSON-LD payload.

#ActivityPub #ActivityStreams #FediDev

ActivityPub specifications don't seem to provide a way to do Idempotent POSTs to your outbox.

That seems like a problem for C2S to me.

Networks are unreliable. You cannot tell the difference between an unreceived request vs an unreceived response. You'll get unwanted identical duplicate activities.

Although it isn't difficult to solve — a convention just needs to be picked.

For example, a new Idempotency field could be added to the JSON-LD payload.

#ActivityPub #ActivityStreams #FediDev

ActivityPub specifications don't seem to provide a way to do Idempotent POSTs to your outbox.

That seems like a problem for C2S to me.

Networks are unreliable. You cannot tell the difference between an unreceived request vs an unreceived response. You'll get unwanted identical duplicate activities.

Although it isn't difficult to solve — a convention just needs to be picked.

For example, a new Idempotency field could be added to the JSON-LD payload.

#ActivityPub #ActivityStreams #FediDev

ActivityPub specifications don't seem to provide a way to do Idempotent POSTs to your outbox.

That seems like a problem for C2S to me.

Networks are unreliable. You cannot tell the difference between an unreceived request vs an unreceived response. You'll get unwanted identical duplicate activities.

Although it isn't difficult to solve — a convention just needs to be picked.

For example, a new Idempotency field could be added to the JSON-LD payload.

#ActivityPub #ActivityStreams #FediDev

@dahukanna

Yes. I think you are asking exactly the right question:"What does it mean in this context?"

Many replies to the #poll ponder related questions, or state an "it depends". It is clear there's a lot of nuance and edge cases.

Reformulated, how delete should work is solution-specific, depends on domain, use cases, and stakeholders in SX terms.

And Delete activity in #ActivityStreams is not the well-understood part of #ActivityPub it is treated as today. See also:

https://social.coop/@smallcircles/116543333306382246

@dahukanna

Yes. I think you are asking exactly the right question:"What does it mean in this context?"

Many replies to the #poll ponder related questions, or state an "it depends". It is clear there's a lot of nuance and edge cases.

Reformulated, how delete should work is solution-specific, depends on domain, use cases, and stakeholders in SX terms.

And Delete activity in #ActivityStreams is not the well-understood part of #ActivityPub it is treated as today. See also:

https://social.coop/@smallcircles/116543333306382246

4/

Related (in quote-boost).

#ActivityPub #ActivityStreams #FediDev

There is a comparison that can be made between ActivityPub and Event-Sourcing.

3/

With ActivityPub, Activities are often applied to an object. That object gets assigned an ID in the form of a URL.

(And, by URL I mean URL, URI, IRI, etc.)

One doesn't have to read through all the Activities in an inbox, outbox, etc to get the final state of an object.

One can just get the JSON-LD document from the object's ID URL to get the final state.

#ActivityPub #ActivityStreams #EventSourcing #FediDev

There is a comparison that can be made between ActivityPub and Event-Sourcing.

2/

With Event-Sourcing, you can "project" the events to get another (often more peformant) view of the data in the events.

Without having to incur the cost of having to read all the events to figure out the final state.

...

#ActivityPub #ActivityStreams #EventSourcing #FediDev

There is a comparison that can be made between ActivityPub and Event-Sourcing.

1/

With Event-Sourcing, your source-of-truth is an append-only series of events.

Ex: USER_REGISTERED, EMAIL_ADDRESS_VERIFIED, PASSWORD_CHANGED, etc.

In ActivityPub, this is similar to the inbox, outbox, etc being an append-only series of Activity.

Ex: Create, Like, Undo, etc.

...

#ActivityPub #ActivityStreams #EventSourcing #FediDev

Just thinking out loud —

If we wanted to support resumable uploads in C2S API, then — we probably need some URL to upload the file chunks to.

…

When a user POST to their own outbox, the HTTP "201 Created" response will have a "Location" header that provides a URL.

Maybe that could be used as the upload URL.

Or, maybe the JSON-LD document at that URL might contain a URL under the "object" field that could be used as the upload URL.

Other options too

#ActivityPub #ActivityStreams #FediDev

I can think of different ways to support resumable uploads with ActivityPub, but — just to see what others are doing —

PeerTube seems to have resumable uploads already.

PeerTube seems to use this protocol for it:

https://github.com/kukhariev/node-uploadx/blob/master/proto.md

I like that it uses Content-Range in the protocol. I would have done the similar.

#ActivityPub #ActivityStreams #FediDev

Just thinking out loud —

If we wanted to support resumable uploads in C2S API, then — we probably need some URL to upload the file chunks to.

…

When a user POST to their own outbox, the HTTP "201 Created" response will have a "Location" header that provides a URL.

Maybe that could be used as the upload URL.

Or, maybe the JSON-LD document at that URL might contain a URL under the "object" field that could be used as the upload URL.

Other options too

#ActivityPub #ActivityStreams #FediDev

It seems as if the uploadMedia ActivityPub extension does not provide a way to resume an upload that didn't previously compete.

https://www.w3.org/wiki/SocialCG/ActivityPub/MediaUpload

If, for example, you are working with large files (such as video files) this would matter.

Because if you uploaded 1GB, and the upload stopped, you would want to resume at where it stopped, and not have to upload from the beginning again.

This would be important for ActivityPub C2S adoption.

#ActivityPub #ActivityStreams #FediDev

I can think of different ways to support resumable uploads with ActivityPub, but — just to see what others are doing —

PeerTube seems to have resumable uploads already.

PeerTube seems to use this protocol for it:

https://github.com/kukhariev/node-uploadx/blob/master/proto.md

I like that it uses Content-Range in the protocol. I would have done the similar.

#ActivityPub #ActivityStreams #FediDev

It seems as if the uploadMedia ActivityPub extension does not provide a way to resume an upload that didn't previously compete.

https://www.w3.org/wiki/SocialCG/ActivityPub/MediaUpload

If, for example, you are working with large files (such as video files) this would matter.

Because if you uploaded 1GB, and the upload stopped, you would want to resume at where it stopped, and not have to upload from the beginning again.

This would be important for ActivityPub C2S adoption.

#ActivityPub #ActivityStreams #FediDev

What do you think about JSON-LD language maps for "preferredUsername"?

I.e., preferredUsernameMap.

"preferredUsernameMap": {
"en": "hello",
"fa": "درود",
"ko": "안녕하세요"
}

#FediDev #JSONLD #ActivityPub #ActivityStreams

I think it would be better if instead of Fediverse software outputting the following for ActivityPub/ActivityStreams Notes, Articles, etc:

"attributedTo": "https://mastodon.social/users/reiver",

It would instead output something more like:

"attributedTo": {
"id":"https://mastodon.social/users/reiver",
"type":"Person",
"name":"Charles",
"preferredUsername": "reiver",
"icon": {...},
"image": {...},
}

This way the Activity* document contains everything needed to render it.

#ActivityPub #ActivityStreams #FediDev

I think it would be better if instead of Fediverse software outputting the following for ActivityPub/ActivityStreams Notes, Articles, etc:

"attributedTo": "https://mastodon.social/users/reiver",

It would instead output something more like:

"attributedTo": {
"id":"https://mastodon.social/users/reiver",
"type":"Person",
"name":"Charles",
"preferredUsername": "reiver",
"icon": {...},
"image": {...},
}

This way the Activity* document contains everything needed to render it.

#ActivityPub #ActivityStreams #FediDev

Both Mastodon and Pixelfed seem to attach images as ActivityPub/ActivityStreams "type" = 'Document'.

I would have expected "type" = 'Image'.

'Document' isn't wrong. It is valid.

But, I would have expected the more specific type of 'Image'.

#ActivityPub #ActivityStreams #FediDev

Both Mastodon and Pixelfed seem to attach images as ActivityPub/ActivityStreams "type" = 'Document'.

I would have expected "type" = 'Image'.

'Document' isn't wrong. It is valid.

But, I would have expected the more specific type of 'Image'.

#ActivityPub #ActivityStreams #FediDev

Both Mastodon and Pixelfed seem to attach images as ActivityPub/ActivityStreams "type" = 'Document'.

I would have expected "type" = 'Image'.

'Document' isn't wrong. It is valid.

But, I would have expected the more specific type of 'Image'.

#ActivityPub #ActivityStreams #FediDev

Both Mastodon and Pixelfed seem to attach images as ActivityPub/ActivityStreams "type" = 'Document'.

I would have expected "type" = 'Image'.

'Document' isn't wrong. It is valid.

But, I would have expected the more specific type of 'Image'.

#ActivityPub #ActivityStreams #FediDev

I think it would be better if instead of Fediverse software outputting the following for ActivityPub/ActivityStreams Notes, Articles, etc:

"attributedTo": "https://mastodon.social/users/reiver",

It would instead output something more like:

"attributedTo": {
"id":"https://mastodon.social/users/reiver",
"type":"Person",
"name":"Charles",
"preferredUsername": "reiver",
"icon": {...},
"image": {...},
}

This way the Activity* document contains everything needed to render it.

#ActivityPub #ActivityStreams #FediDev

What if web-browsers could render the ActivityPub / ActivityStreams JSON-LD source-code into the document it represents?

Fediverse clients can do it — why can't browsers?

I previously created a small-net / small-web browser client named SpaceMonkey.

It supports protocols such as Gemini, HTTP, HTTPS, Mercury, etc. And, formats such as GemText, HTML, Markdown, etc.

It now supports the ActivityPub / ActivityStreams JSON-LD format, too.

#ActivitiyPub #ActivityStreams #FediDev #SpaceMonkey

What if web-browsers could render the ActivityPub / ActivityStreams JSON-LD source-code into the document it represents?

Fediverse clients can do it — why can't browsers?

I previously created a small-net / small-web browser client named SpaceMonkey.

It supports protocols such as Gemini, HTTP, HTTPS, Mercury, etc. And, formats such as GemText, HTML, Markdown, etc.

It now supports the ActivityPub / ActivityStreams JSON-LD format, too.

#ActivitiyPub #ActivityStreams #FediDev #SpaceMonkey

What if web-browsers could render the ActivityPub / ActivityStreams JSON-LD source-code into the document it represents?

Fediverse clients can do it — why can't browsers?

I previously created a small-net / small-web browser client named SpaceMonkey.

It supports protocols such as Gemini, HTTP, HTTPS, Mercury, etc. And, formats such as GemText, HTML, Markdown, etc.

It now supports the ActivityPub / ActivityStreams JSON-LD format, too.

#ActivitiyPub #ActivityStreams #FediDev #SpaceMonkey

Was the original intent of the ActivityPub / ActivityStreams "name" field to be a title?

(It seems as if some software is using it that way.)

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

#ActivityPub #ActivityStreams #FediDev

What should the file-extension for ActivityPub / ActivityStreams documents be?

I.e., for application/activity+json data?

I've been using .activity

Ex: filename.activity

(The extension cannot be .json or .jsonld if you want to be able to detect it just based on the file-extension.)

What do you think?

#ActivityPub #ActivityStreams #FediDev

What should the file-extension for ActivityPub / ActivityStreams documents be?

I.e., for application/activity+json data?

I've been using .activity

Ex: filename.activity

(The extension cannot be .json or .jsonld if you want to be able to detect it just based on the file-extension.)

What do you think?

#ActivityPub #ActivityStreams #FediDev

Can an ActivityPub 'Place' also be an Actor?

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

With followers, an outbox, etc.

That could be useful for both real-life places, and fictional places in stories, and in video games.

#ActivityPub #ActivityStreams #FediDev #FediFiction #FediGames

What makes an ActivityPub Actor an Actor?

I think it is probably a bad idea to just restrict it to things with 'type': "Application", "Group", "Organization", "Person", and "Service". Restricting it to just those would mean you couldn't have new actor types (and sub-types) in the future.

So then, do we do it in a duck-typing way? And if "yes", how?

Maybe if something has an "inbox" OR and "outbox" it is an Actor. I.e., it could have just one of those.

#ActivityPub #ActivityStreams #FediDev

And, if this is the case, then every ActivityPub / ActivityStreams library should be on the look-out for "inbox" and "outbox" fields on everything.

Doesn't matter what it is. An "Event", an "Image", a "Link", a "Place", a "Video", even things in other namespaces.

#ActivityPub #ActivityStreams #FediDev

If an ActivityPub Actor is something that has an "inbox" or an "outbox" (i.e., it could have just one or both) then —

Perhaps we should also be talking about "sources" and "sinks", too. Where —

An ActivityPub Source is an Actor with just an "outbox" (and no "inbox").

And, an ActivityPub Sink is an Actor with just an "inbox" (and no "outbox").

#ActivityPub #ActivityStreams #FediDev

What makes an ActivityPub Actor an Actor?

I think it is probably a bad idea to just restrict it to things with 'type': "Application", "Group", "Organization", "Person", and "Service". Restricting it to just those would mean you couldn't have new actor types (and sub-types) in the future.

So then, do we do it in a duck-typing way? And if "yes", how?

Maybe if something has an "inbox" OR and "outbox" it is an Actor. I.e., it could have just one of those.

#ActivityPub #ActivityStreams #FediDev

If an ActivityPub Actor is something that has an "inbox" or an "outbox" (i.e., it could have just one or both) then —

Perhaps we should also be talking about "sources" and "sinks", too. Where —

An ActivityPub Source is an Actor with just an "outbox" (and no "inbox").

And, an ActivityPub Sink is an Actor with just an "inbox" (and no "outbox").

#ActivityPub #ActivityStreams #FediDev

If an ActivityPub Actor is something that has an "inbox" or an "outbox" (i.e., it could have just one or both) then —

Perhaps we should also be talking about "sources" and "sinks", too. Where —

An ActivityPub Source is an Actor with just an "outbox" (and no "inbox").

And, an ActivityPub Sink is an Actor with just an "inbox" (and no "outbox").

#ActivityPub #ActivityStreams #FediDev

Can an ActivityPub 'Place' also be an Actor?

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

With followers, an outbox, etc.

That could be useful for both real-life places, and fictional places in stories, and in video games.

#ActivityPub #ActivityStreams #FediDev #FediFiction #FediGames

Can an ActivityPub 'Place' also be an Actor?

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

With followers, an outbox, etc.

That could be useful for both real-life places, and fictional places in stories, and in video games.

#ActivityPub #ActivityStreams #FediDev #FediFiction #FediGames

And, if this is the case, then every ActivityPub / ActivityStreams library should be on the look-out for "inbox" and "outbox" fields on everything.

Doesn't matter what it is. An "Event", an "Image", a "Link", a "Place", a "Video", even things in other namespaces.

#ActivityPub #ActivityStreams #FediDev

What makes an ActivityPub Actor an Actor?

I think it is probably a bad idea to just restrict it to things with 'type': "Application", "Group", "Organization", "Person", and "Service". Restricting it to just those would mean you couldn't have new actor types (and sub-types) in the future.

So then, do we do it in a duck-typing way? And if "yes", how?

Maybe if something has an "inbox" OR and "outbox" it is an Actor. I.e., it could have just one of those.

#ActivityPub #ActivityStreams #FediDev

Can an ActivityPub 'Place' also be an Actor?

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

With followers, an outbox, etc.

That could be useful for both real-life places, and fictional places in stories, and in video games.

#ActivityPub #ActivityStreams #FediDev #FediFiction #FediGames

Should an ActivityPub 'Place' be used to represent a fictional place?

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

Such as a fictional place in a story, or a video game?

#ActivityPub #ActivityStreams #FediDev #FediFiction #FediGames

Should an ActivityPub 'Place' be used to represent a fictional place?

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

Such as a fictional place in a story, or a video game?

#ActivityPub #ActivityStreams #FediDev #FediFiction #FediGames

Should an ActivityPub 'Place' be used to represent a fictional place?

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

Such as a fictional place in a story, or a video game?

#ActivityPub #ActivityStreams #FediDev #FediFiction #FediGames

Should an ActivityPub 'Place' be used to represent a fictional place?

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

Such as a fictional place in a story, or a video game?

#ActivityPub #ActivityStreams #FediDev #FediFiction #FediGames

2/

The game will be social.

Your player gains things in the game by being followed (and perhaps following back) Actors on the Fediverse.

For example, you would have a team. The characters on your team would be Fedivese Actors / accounts. This could be bot accounts, but could also be the accounts of other people playing the game.

Same with energy sources, special powers, etc — all Fedivese Actors / accounts.

#ActivitiyPub #ActivityStreams #FediDev #FediGames #Games #VideoGames

1/

I have been thinking about how to create a Fediverse Game using the ActivityPub 'Question' object.

I have some different ideas, but I think I want to try something simpler and quicker to make first — before attempting a magnum opus 🙂

Here is what I am thinking for a first game...

#ActivitiyPub #ActivityStreams #FediDev #FediGames #Games #VideoGames

I think Mastodon will strip image attachments from ActivityPub 'Question' objects.

That is too bad.

That means even if you create an 'Question' with 'Image' attachments elsewhere, you still won't see them in Mastodon (or in the Mastodon client-server API)

…

I guess the work-around is to post a 'Note' with an 'Image' attachment(s), and then reply to it with a 'Question'. That feels clunkier, but doable

#ActivitiyPub #ActivityStreams #FediDev #FediGames #Games #Mastodon #MastoDev #VideoGames

If one was to create a Fediverse Game using the ActivityPub 'Question' —

It would be nice if people could play it from a regular Fediverse client.

But, you could also offer a game-specific client that allows for a richer game experience.

#ActivitiyPub #ActivityStreams #FediDev #FediGames #Games #VideoGames

One decision to make if one was to create a Fediverse Game using the ActivityPub 'Question' —

Do you just create a bot that connect to a Fediverse server (such as a Mastodon server)?

Or, do you create the Fediverse server, too?

...

There are pros and cons each way.

The former is simpler to build in many ways.

The latter lets you add as many poll choices as you want, and even add extra JSON-LD name-spaces.

#ActivitiyPub #ActivityStreams #FediDev #FediGames #Games #VideoGames

Would you play a Fediverse game?

Would you play a Fediverse game about Meta Humans?

#ActivityPub #ActivityStreams #FediDev #FediGames #Fediverse #Games #VideoGames #MetaHumans

Would you play a Fediverse game?

Would you play a Fediverse game about Meta Humans?

#ActivityPub #ActivityStreams #FediDev #FediGames #Fediverse #Games #VideoGames #MetaHumans

I think you could create a (certain type of) video game using the ActivityPub 'Question'.

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

#ActivitiyPub #ActivityStreams #FediDev #FediGames #Games #VideoGames

@reiver

These are all conventions, and domain-specific conventions at that in my perspective, addressed in latest (long) blog post on grassroots #ActivityPub #fediverse evolution. In other words the choice depends on the domain you are modeling, and the solution requirements.

I am musing on a #Protosocial AP protocol extension, which acts as an overlay network, that operates more according to the Actor Model. Actors can be of many types, can be created on-the-fly, be part of supervision trees, have different lifetimes, etc.

Also they are decoupled from Identity. The have ActorId of course, but a Person actor does not relate directly to the person, and might as well be operated by a bot script. How exactly I'll model that remains open, but #ActivityStreams Profile may play a role, as an Identity visitor's card to exchange, kind of.

@argv_minus_one @pawv

Yea. The Tombstone object is available in #ActivityStreams but I think it is very tricky indeed to have a proper #prosocial wire implementation.

Suppose someone crosses the line in their conversation, receives harsh criticism, and decides to remove their post, now the wriggling tail of critique and judgment becomes detached from the popular originator toot in the thread. Unattached, floating freely in #social fabric, often without the context on why criticism was deserved. A harrasser comes off easy, one can say. They also have more chance to 'clean their slate', by showing better #behavior and re-earn lost respect if their comms violation wasn't too egregious.

A tombstone inserted in the deletion space, even when totally anonymised, still has mentions of the person in the following replies, which for a full-blown "right to be removed" would involve removing those too. Or else a respondent can make sure that the bad Monday someone had, remains carved in stone.

ActivityPub outboxes are the new RSS / Atom / WebFeed.

You can just read from them to get a JSON feed of someone's posts.

I.e., you do NOT have to implement the full suite of Fediverse protocols, or Follow, or run your own server, or anything else to get someone's posts on the Fediverse — just read from their outbox.

#ActivityPub #ActivityStreams #AtomFeed #AtomFormat #DeSe #FediDev #FediDevs #Fediverse #JSON #OpenSocial #RSS #SocialWeb

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 #Fediverse

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 #Fediverse

@reiver

Today "ActivityStreams: Where do you want to go to today?" might be a slogan we borrowed from Microsoft.

The question is whether #ActivityStreams should be used - besides all the things it is already being used for - to also map to file systems.

The #LinkedData nature of #ActivityPub is generally shunned in favor of plain #JSON. That in itself is fine, as long as:

a) information still represents valid #JSONLD.

b) information models still follow data modeling best practices.

c) information models are designed with #interoperability in mind.

Not saying your approach is good or bad, just observing that everyone mapping and overloading their own app-specific semantics to the poor AS vocab looks to me a worst-practice. We can get away with it, as we made post-facto interop the poor man's accepted practice, lacking more rigorous extension process and guidance.

There are likely existing standardized ontologies.

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 #Fediverse

I've seen an ongoing debate between "Note" versus "Article" in ActivityPub / ActivityStreams.

When is something a "Note"‽
When is something an "Article"‽

Personally — I would probably have made the distinction this way.

An "Article" has a title.
A "Note" doesn't have a title.

(In ActivityPub / ActivityStreams, a 'title' seems to tend to get represented in the "name" field.)

#ActivityPub #ActivityStreams #FediDev #FediDevs #Fediverse

So, an interesting issue came up in the #Fedify repo that I've been thinking about: #629.

You know how every #fediverse server uses schema:PropertyValue in actor attachment for profile metadata fields (like “Website”, “GitHub”, etc.)? Turns out, strict #AS2 validators like browser.pub reject it, because the AS2 spec says attachment should only contain Object or Link—and PropertyValue is a schema.org type, not an Activity Streams 2.0 type.

The thing is, we can't just drop the type like we did with Endpoints (#576), because Mastodon and others rely on seeing "type": "PropertyValue" to render profile fields. But at the same time, it's technically not spec-compliant.

I'm leaning towards writing a #FEP to formalize this existing practice rather than trying to invent a new type (like toot:PropertyValue extending Object), which would be a nightmare to migrate across the whole fediverse.

What do you all think? Has anyone else run into this? Would love to hear thoughts from implementers and spec folks.

#fedidev #ActivityPub #ActivityStreams #ActivityStreams2 #AS2 #PropertyValue

So, an interesting issue came up in the #Fedify repo that I've been thinking about: #629.

You know how every #fediverse server uses schema:PropertyValue in actor attachment for profile metadata fields (like “Website”, “GitHub”, etc.)? Turns out, strict #AS2 validators like browser.pub reject it, because the AS2 spec says attachment should only contain Object or Link—and PropertyValue is a schema.org type, not an Activity Streams 2.0 type.

The thing is, we can't just drop the type like we did with Endpoints (#576), because Mastodon and others rely on seeing "type": "PropertyValue" to render profile fields. But at the same time, it's technically not spec-compliant.

I'm leaning towards writing a #FEP to formalize this existing practice rather than trying to invent a new type (like toot:PropertyValue extending Object), which would be a nightmare to migrate across the whole fediverse.

What do you all think? Has anyone else run into this? Would love to hear thoughts from implementers and spec folks.

#fedidev #ActivityPub #ActivityStreams #ActivityStreams2 #AS2 #PropertyValue

So, an interesting issue came up in the #Fedify repo that I've been thinking about: #629.

You know how every #fediverse server uses schema:PropertyValue in actor attachment for profile metadata fields (like “Website”, “GitHub”, etc.)? Turns out, strict #AS2 validators like browser.pub reject it, because the AS2 spec says attachment should only contain Object or Link—and PropertyValue is a schema.org type, not an Activity Streams 2.0 type.

The thing is, we can't just drop the type like we did with Endpoints (#576), because Mastodon and others rely on seeing "type": "PropertyValue" to render profile fields. But at the same time, it's technically not spec-compliant.

I'm leaning towards writing a #FEP to formalize this existing practice rather than trying to invent a new type (like toot:PropertyValue extending Object), which would be a nightmare to migrate across the whole fediverse.

What do you all think? Has anyone else run into this? Would love to hear thoughts from implementers and spec folks.

#fedidev #ActivityPub #ActivityStreams #ActivityStreams2 #AS2 #PropertyValue

So, an interesting issue came up in the #Fedify repo that I've been thinking about: #629.

You know how every #fediverse server uses schema:PropertyValue in actor attachment for profile metadata fields (like “Website”, “GitHub”, etc.)? Turns out, strict #AS2 validators like browser.pub reject it, because the AS2 spec says attachment should only contain Object or Link—and PropertyValue is a schema.org type, not an Activity Streams 2.0 type.

The thing is, we can't just drop the type like we did with Endpoints (#576), because Mastodon and others rely on seeing "type": "PropertyValue" to render profile fields. But at the same time, it's technically not spec-compliant.

I'm leaning towards writing a #FEP to formalize this existing practice rather than trying to invent a new type (like toot:PropertyValue extending Object), which would be a nightmare to migrate across the whole fediverse.

What do you all think? Has anyone else run into this? Would love to hear thoughts from implementers and spec folks.

#fedidev #ActivityPub #ActivityStreams #ActivityStreams2 #AS2 #PropertyValue

So, an interesting issue came up in the #Fedify repo that I've been thinking about: #629.

You know how every #fediverse server uses schema:PropertyValue in actor attachment for profile metadata fields (like “Website”, “GitHub”, etc.)? Turns out, strict #AS2 validators like browser.pub reject it, because the AS2 spec says attachment should only contain Object or Link—and PropertyValue is a schema.org type, not an Activity Streams 2.0 type.

The thing is, we can't just drop the type like we did with Endpoints (#576), because Mastodon and others rely on seeing "type": "PropertyValue" to render profile fields. But at the same time, it's technically not spec-compliant.

I'm leaning towards writing a #FEP to formalize this existing practice rather than trying to invent a new type (like toot:PropertyValue extending Object), which would be a nightmare to migrate across the whole fediverse.

What do you all think? Has anyone else run into this? Would love to hear thoughts from implementers and spec folks.

#fedidev #ActivityPub #ActivityStreams #ActivityStreams2 #AS2 #PropertyValue

So, an interesting issue came up in the #Fedify repo that I've been thinking about: #629.

You know how every #fediverse server uses schema:PropertyValue in actor attachment for profile metadata fields (like “Website”, “GitHub”, etc.)? Turns out, strict #AS2 validators like browser.pub reject it, because the AS2 spec says attachment should only contain Object or Link—and PropertyValue is a schema.org type, not an Activity Streams 2.0 type.

The thing is, we can't just drop the type like we did with Endpoints (#576), because Mastodon and others rely on seeing "type": "PropertyValue" to render profile fields. But at the same time, it's technically not spec-compliant.

I'm leaning towards writing a #FEP to formalize this existing practice rather than trying to invent a new type (like toot:PropertyValue extending Object), which would be a nightmare to migrate across the whole fediverse.

What do you all think? Has anyone else run into this? Would love to hear thoughts from implementers and spec folks.

#fedidev #ActivityPub #ActivityStreams #ActivityStreams2 #AS2 #PropertyValue

So, an interesting issue came up in the #Fedify repo that I've been thinking about: #629.

You know how every #fediverse server uses schema:PropertyValue in actor attachment for profile metadata fields (like “Website”, “GitHub”, etc.)? Turns out, strict #AS2 validators like browser.pub reject it, because the AS2 spec says attachment should only contain Object or Link—and PropertyValue is a schema.org type, not an Activity Streams 2.0 type.

The thing is, we can't just drop the type like we did with Endpoints (#576), because Mastodon and others rely on seeing "type": "PropertyValue" to render profile fields. But at the same time, it's technically not spec-compliant.

I'm leaning towards writing a #FEP to formalize this existing practice rather than trying to invent a new type (like toot:PropertyValue extending Object), which would be a nightmare to migrate across the whole fediverse.

What do you all think? Has anyone else run into this? Would love to hear thoughts from implementers and spec folks.

#fedidev #ActivityPub #ActivityStreams #ActivityStreams2 #AS2 #PropertyValue

So, an interesting issue came up in the #Fedify repo that I've been thinking about: #629.

You know how every #fediverse server uses schema:PropertyValue in actor attachment for profile metadata fields (like “Website”, “GitHub”, etc.)? Turns out, strict #AS2 validators like browser.pub reject it, because the AS2 spec says attachment should only contain Object or Link—and PropertyValue is a schema.org type, not an Activity Streams 2.0 type.

The thing is, we can't just drop the type like we did with Endpoints (#576), because Mastodon and others rely on seeing "type": "PropertyValue" to render profile fields. But at the same time, it's technically not spec-compliant.

I'm leaning towards writing a #FEP to formalize this existing practice rather than trying to invent a new type (like toot:PropertyValue extending Object), which would be a nightmare to migrate across the whole fediverse.

What do you all think? Has anyone else run into this? Would love to hear thoughts from implementers and spec folks.

#fedidev #ActivityPub #ActivityStreams #ActivityStreams2 #AS2 #PropertyValue

So, an interesting issue came up in the #Fedify repo that I've been thinking about: #629.

You know how every #fediverse server uses schema:PropertyValue in actor attachment for profile metadata fields (like “Website”, “GitHub”, etc.)? Turns out, strict #AS2 validators like browser.pub reject it, because the AS2 spec says attachment should only contain Object or Link—and PropertyValue is a schema.org type, not an Activity Streams 2.0 type.

The thing is, we can't just drop the type like we did with Endpoints (#576), because Mastodon and others rely on seeing "type": "PropertyValue" to render profile fields. But at the same time, it's technically not spec-compliant.

I'm leaning towards writing a #FEP to formalize this existing practice rather than trying to invent a new type (like toot:PropertyValue extending Object), which would be a nightmare to migrate across the whole fediverse.

What do you all think? Has anyone else run into this? Would love to hear thoughts from implementers and spec folks.

#fedidev #ActivityPub #ActivityStreams #ActivityStreams2 #AS2 #PropertyValue

So, an interesting issue came up in the #Fedify repo that I've been thinking about: #629.

You know how every #fediverse server uses schema:PropertyValue in actor attachment for profile metadata fields (like “Website”, “GitHub”, etc.)? Turns out, strict #AS2 validators like browser.pub reject it, because the AS2 spec says attachment should only contain Object or Link—and PropertyValue is a schema.org type, not an Activity Streams 2.0 type.

The thing is, we can't just drop the type like we did with Endpoints (#576), because Mastodon and others rely on seeing "type": "PropertyValue" to render profile fields. But at the same time, it's technically not spec-compliant.

I'm leaning towards writing a #FEP to formalize this existing practice rather than trying to invent a new type (like toot:PropertyValue extending Object), which would be a nightmare to migrate across the whole fediverse.

What do you all think? Has anyone else run into this? Would love to hear thoughts from implementers and spec folks.

#fedidev #ActivityPub #ActivityStreams #ActivityStreams2 #AS2 #PropertyValue

1/

AFAIK, there isn't a way for an ActivityPub Actor (such as a Person actor) to specify a list of Service actors associated with it.

...

For example, imagine that there is a Service actor that represents a way to make a video call to me.

And, for example, I have my Mastodon Person actor.

And, I want to let people know about it (and other Service actors associated with me).

How do I do that using AP, etc‽

...

#ActivityPub #ActivityStreams #AudioCall #Call #FediDev #Fediverse #VideoCall

7/

Continuing to look for an alternative to "attachment" (for properly supporting an Actor specifying a list of CALL Service actors associated with it) —

Maybe a call specific custom top-level attribute would be useful.

Maybe something like:

"call": [
{
"rel":"callpub",
"href":"https://videocalls.example/users/joeblow"
}
]

Or even:

"call": [
"href":"https://videocalls.example/users/joeblow"
]

.

#ActivityPub #ActivityStreams #AudioCall #Call #FediDev #Fediverse #VideoCall

6/

Continuing to look for an alternative to "attachment" (for properly supporting an Actor specifying a list of Service actors associated with it) —

Maybe a custom top-level attribute would be useful.

Maybe something like:

"service": [
{
"rel":"callpub",
"href":"https://videocalls.example/users/joeblow"
}
]

Although perhaps that is not much better than "attachment", if you just care about calls

So —

#ActivityPub #ActivityStreams #AudioCall #Call #FediDev #Fediverse #VideoCall

5/

Continuing to look for an alternative to "attachment" (for properly supporting an Actor specifying a list of Service actors associated with it) —

I think "endpoints" would also be a poor choice, too. Again, the semantics are wrong, or at least lacking.

So —

#ActivityPub #ActivityStreams #AudioCall #Call #FediDev #Fediverse #VideoCall

4/

Looking for an alternative to "attachment" (for properly supporting an Actor specifying a list of Service actors associated with it) —

I think using "alsoKnownAs" or "sameAs" would be a poor choice. The semantics are wrong.

For example: a Service actor might represent my mobile phone (or software on it). My phone is not me. It is something I have.

So —

#ActivityPub #ActivityStreams #AudioCall #Call #FediDev #Fediverse #VideoCall

3/

But, what about the non- fall-back situation where software could properly support this (when an Actor specifies a list of Service actors associated with it)‽

I think some might say, put the associated Service actors in "attachment". And, semantically I think that would work with ActivityPub, but — I have a very strong dislike with putting everything in "attachment" (and "tag"). It makes parsing difficult.

So —

#ActivityPub #ActivityStreams #AudioCall #Call #FediDev #Fediverse #VideoCall

2/

Because most people wouldn't be able to add custom attributes or custom values to most Fediverse software (including Mastodon) —

Most supporting software would probably want to support a "PropertyValue" link in "attachment" field as a fall-back

For example:

"attachment": [
{
"type": "PropertyValue",
"name": "Video Calls (callpub)",
"value": "https://videocalls.example/users/joeblow"
}

But —

...

#ActivityPub #ActivityStreams #AudioCall #Call #FediDev #Fediverse #VideoCall

1/

AFAIK, there isn't a way for an ActivityPub Actor (such as a Person actor) to specify a list of Service actors associated with it.

...

For example, imagine that there is a Service actor that represents a way to make a video call to me.

And, for example, I have my Mastodon Person actor.

And, I want to let people know about it (and other Service actors associated with me).

How do I do that using AP, etc‽

...

#ActivityPub #ActivityStreams #AudioCall #Call #FediDev #Fediverse #VideoCall

@steve

Have there been any further discussions on this? I think it’s becoming increasingly important!

https://github.com/steve-bate/activitypub-ontology/blob/main/activitystreams2.ttl

#activitystreams #activitypub #rdf

@steve

Have there been any further discussions on this? I think it’s becoming increasingly important!

https://github.com/steve-bate/activitypub-ontology/blob/main/activitystreams2.ttl

#activitystreams #activitypub #rdf

I used to not like JSON-LD. And then I got exposed to CBOR. And, since then, I ended up liking JSON-LD more than I did before.

https://j12t.social/@j12t/114581086678041245

...

I was looking for performant ways of storing JSON-LD data, so that it can be looked up, queried, etc.

CBOR might actually be a way of doing that.

...

For me that is an odd realization given me liking JSON-LD is a reaction to CBOR.

#ActivityPub #ActivityStreams #CBOR #CBORLD #FediDev #JSONLD

I used to not like JSON-LD. And then I got exposed to CBOR. And, since then, I ended up liking JSON-LD more than I did before.

https://j12t.social/@j12t/114581086678041245

...

I was looking for performant ways of storing JSON-LD data, so that it can be looked up, queried, etc.

CBOR might actually be a way of doing that.

...

For me that is an odd realization given me liking JSON-LD is a reaction to CBOR.

#ActivityPub #ActivityStreams #CBOR #CBORLD #FediDev #JSONLD

FWIW, I have been storing Linked Data (including ActivityPub) in an INI like format — because I find INI-like formats more human-friendly (to both read and write) than JSON.

YAML is probably better than JSON, too, in that respects. But I think INI-like formats are better than YAML.

#ActivityPub #ActivityStreams #JSONLD #LinkedData #RDF #YAML #YAMLLD

FWIW, I have been storing Linked Data (including ActivityPub) in an INI like format — because I find INI-like formats more human-friendly (to both read and write) than JSON.

YAML is probably better than JSON, too, in that respects. But I think INI-like formats are better than YAML.

#ActivityPub #ActivityStreams #JSONLD #LinkedData #RDF #YAML #YAMLLD

With ActivityPub / ActivityStreams...

To me, it feels like there should have been something that is a common parent of both 'Object' and 'Link'.

That just had the "name", "nameMap", and "preview" fields (along with "id" and "type, of course) — since that is what 'Object' and 'Link' share in common.

I'll just call this common parent: 'Entity'.

...

It could have even been an opportunity to talk about how to handle unknown types.

#ActivityPub #ActivityStreams #FediDev #Fediverse

"A guide to implement ActivityPub in a static site (or any website)" by @mapache

https://maho.dev/2024/02/a-guide-to-implement-activitypub-in-a-static-site-or-any-website/

#ActivityPub #ActivityStreams #FediDev #FediDevs #Fediverse

"A guide to implement ActivityPub in a static site (or any website)" by @mapache

https://maho.dev/2024/02/a-guide-to-implement-activitypub-in-a-static-site-or-any-website/

#ActivityPub #ActivityStreams #FediDev #FediDevs #Fediverse

"A guide to implement ActivityPub in a static site (or any website)" by @mapache

https://maho.dev/2024/02/a-guide-to-implement-activitypub-in-a-static-site-or-any-website/

#ActivityPub #ActivityStreams #FediDev #FediDevs #Fediverse

I suspect that there is an error in the Turtle specification, in the section shown in the screen-shot.

(It relates to JSON-LD, which ActivityPub / ActivityStreams is built on.)

I suspect that "PN_CHARS_BASE" is an error.

Because other parts of other specifications seem to not make sense if it is.

I suspect that maybe it should have been "PN_PREFIX" instead.

#ActivityPub #ActivityStreams #RDF #JSONLD

This is from the JSON-LD spec.

ActivityPub / ActivityStream are based on JSON-LD.

I think it was a very bad idea for JSON-LD to define "number" this way!

It makes it so numbers with fractional values are inexact & lossy.

This include values that are common for money.

For example, neither 0.10 and 0.20 can be represented exactly. So, 0.10 + 0.20 does NOT equal 0.30!

It should have used FIXED-point numbers rather than FLOATING-point.

#ActivityPub #ActivityStreams #JSONLD #RFC7159 #RFC8259

There is a larger discussion about fixed-point numbers versus floating-point numbers.

And that, ALL programming-languages should have fixed-point numbers built into them.

And that, programmers should be warned against using floating-point numbers in all but a set of very specialized situations — where inexact math is OK.

For most programmers in most situations inexact math is NOT OK. And, they should NOT use floating-point numbers.

#ActivityPub #ActivityStreams #JSONLD #RFC7159 #RFC8259

This is from the JSON-LD spec.

ActivityPub / ActivityStream are based on JSON-LD.

I think it was a very bad idea for JSON-LD to define "number" this way!

It makes it so numbers with fractional values are inexact & lossy.

This include values that are common for money.

For example, neither 0.10 and 0.20 can be represented exactly. So, 0.10 + 0.20 does NOT equal 0.30!

It should have used FIXED-point numbers rather than FLOATING-point.

#ActivityPub #ActivityStreams #JSONLD #RFC7159 #RFC8259

I've seen an ongoing debate between "Note" versus "Article" in ActivityPub / ActivityStreams.

When is something a "Note"‽
When is something an "Article"‽

Personally — I would probably have made the distinction this way.

An "Article" has a title.
A "Note" doesn't have a title.

(In ActivityPub / ActivityStreams, a 'title' seems to tend to get represented in the "name" field.)

#ActivityPub #ActivityStreams #FediDev #FediDevs #Fediverse

@thisismissem

@reiver it is a good question. It is also a question that is formulated from the perspective on how we currently see the AS/AP fediverse.

> I've seen an ongoing debate between "Note" versus "Article" in #ActivityPub / #ActivityStreams.
> When is something a "Note"‽
> When is something an "Article"‽

The question makes sense from the notion of what the current #fediverse is. It makes less sense from the context of AS/AP as described in the protocol specs.

Background to my post is this observation: https://social.coop/@smallcircles/116109447243110037

Then the answer to when is something a Note or an Article is: Always. Note is Note in ActivityStreams and Article is Article.

The question that you would be asking, if only we had a fediverse that followed the original promise of the open standards, is:

> "When is something a Note or an Article in a Microblogging domain?"

For instance.. types you have in any domain depend on your model preferences. Could be anything that serves needs of a solution.

I've seen an ongoing debate between "Note" versus "Article" in ActivityPub / ActivityStreams.

When is something a "Note"‽
When is something an "Article"‽

Personally — I would probably have made the distinction this way.

An "Article" has a title.
A "Note" doesn't have a title.

(In ActivityPub / ActivityStreams, a 'title' seems to tend to get represented in the "name" field.)

#ActivityPub #ActivityStreams #FediDev #FediDevs #Fediverse

In the old blogging software I created back in the 1990s, I had a handful of posts types

There was a type of rich-text oriented post that had a title. (Article)

And, there way another type of rich-text oriented post that did not have a title. (Note)

(There were also other types of posts, but they aren't relevant here)

These 2 types of posts were rendered / displayed differently

I.e., my 1990s software already had this distinction

#ActivityPub #ActivityStreams #FediDev #FediDevs #Fediverse

I've seen an ongoing debate between "Note" versus "Article" in ActivityPub / ActivityStreams.

When is something a "Note"‽
When is something an "Article"‽

Personally — I would probably have made the distinction this way.

An "Article" has a title.
A "Note" doesn't have a title.

(In ActivityPub / ActivityStreams, a 'title' seems to tend to get represented in the "name" field.)

#ActivityPub #ActivityStreams #FediDev #FediDevs #Fediverse

@trwnh @evan @julian

Yes, for the ideation on Protosocial as an #ActivityPub compliant extension (going back to the roots with blank slate W3C specs) I imagined mapping the AS primitives to consistent protocol capabilities and thereby define a set of normative architecture patterns, like "this is how we do CRUD, this is Publish/Subscribe, this is an Event stream and this a Collection", etc.

Then Protosocial library and SDK implementers would need to deal with #ActivityStreams at a low-level plumbing impl detail, while solution developers would have a higher-level API to invoke these patterns. And other than that would not need to touch #ActivityStreams which is now entirely reserved to making AP work on the wire.

A combination of linked data practices and schema-based design would be used for both open-world and closed-world extension modeling. But here too the solution developer should be shield from the nitty gritty internal mechanics.

@steve @evan

I agree with what you say.

On the use of "stream(s)" I did a search in both specs, and it is only very sparsely used in the meaning of a stream rather than an Activity Streams document or object.

One time mentioned as "Activity Streams consumer" in #ActivityStreams core and another mention in the Security considerations section.

> Publishers or Consumers implementing Activity Streams as a stream of public data ..

And twice in #ActivityPub where it says both inbox and outbox where it mentions "the outbox stream", "the inbox stream", and one other mention in definition of "Social API" where it is said to provide a "social stream of the user's actor".

So I would not consider this formal language terminology right now. That said, it would be good to further formalize the concept of a Stream, as it is a higher-order concept that'll help lift discussions out of nitty gritty impl detail territory.

#ActivityPub, a *great start* providing the key ingredients.

#Fediverse, where things are cooked into a mush, by pragmatic though unsustainable fast-food preparation.

Recipe:

- Mash everything into #ActivityStreams
- Overload the semantic frying pan
- Sprinkle in combinatorial complexities
- Cook until too hot

Then simply keep stirring with increasing whack-a-mole maintenance burdens until project phased out.

Or become the post-facto #interoperability leader and dominate the restaurant chain.

Recipe improvement tips:

- Add #FEP spice to the mix where you can!
- Participate in #SocialCG collective cooking.

@evan @julian

#ActivityPub builds on top of #ActivityStreams in the sense that it adopted a number of its 'social primitives' defined in its vocabulary, and Collection being among those. These particular uses become 'protocol space', but other than that AS from the perspective of AP solution development is purely a set of social primitives, granular building blocks that one *may* use in a solution. AS is a utility library of sorts then. Or is that a wrong perception?

A 'feed' is something that lives in solution space, and I would only choose Collection to model it, if it offers a perfect fit in functionality. And aboveall.. does not assign some new app-specific use along the way.

I tooted today that I feel the biggest folly of the fedi is that everyone tries to cram their domain into the AS namespace. The AS primitives should not be Swiss army knives and have only singular well-defined meaning and purpose, yet they have become that along the way.

https://social.coop/@smallcircles/116096886732404993

@trwnh @evan @julian

Yes, for the ideation on Protosocial as an #ActivityPub compliant extension (going back to the roots with blank slate W3C specs) I imagined mapping the AS primitives to consistent protocol capabilities and thereby define a set of normative architecture patterns, like "this is how we do CRUD, this is Publish/Subscribe, this is an Event stream and this a Collection", etc.

Then Protosocial library and SDK implementers would need to deal with #ActivityStreams at a low-level plumbing impl detail, while solution developers would have a higher-level API to invoke these patterns. And other than that would not need to touch #ActivityStreams which is now entirely reserved to making AP work on the wire.

A combination of linked data practices and schema-based design would be used for both open-world and closed-world extension modeling. But here too the solution developer should be shield from the nitty gritty internal mechanics.

@evan @julian

#ActivityPub builds on top of #ActivityStreams in the sense that it adopted a number of its 'social primitives' defined in its vocabulary, and Collection being among those. These particular uses become 'protocol space', but other than that AS from the perspective of AP solution development is purely a set of social primitives, granular building blocks that one *may* use in a solution. AS is a utility library of sorts then. Or is that a wrong perception?

A 'feed' is something that lives in solution space, and I would only choose Collection to model it, if it offers a perfect fit in functionality. And aboveall.. does not assign some new app-specific use along the way.

I tooted today that I feel the biggest folly of the fedi is that everyone tries to cram their domain into the AS namespace. The AS primitives should not be Swiss army knives and have only singular well-defined meaning and purpose, yet they have become that along the way.

https://social.coop/@smallcircles/116096886732404993

@thisismissem @eyeinthesky

The biggest folly imho is this idea of "let's cram every domain into #ActivityStreams somehow". Flatten everything and project it onto this small set of social primitives that AS defines.

It is once more a choice of pragmatism: "Hey, I've seen it working with Mastodon, so I copied that. And #LinkedData extension mechanism is a handwaved horror show".

So understandable perhaps that we did it. But now we must overcome this trend which has taken stubborn root and drags the ecosystem down.

@FinchHaven @strypey

I do not think that @naturzukunft2026 misunderstands this.

There's a difference between #ActivityPub the protocol and #fediverse the on-the-wire reality, and in the latter #Mastodon is the post-facto interoperability leader.

For there to be interoperabiity in a particular domain there needs to be agreement on data formats and msg exchanges, and the specs don't provide full coverage nor clear guidance on this. Though #ActivityStreams has a section on use cases it was designed to handle, they aren't fully specified.

Of course it is perfectly fine, and highly encouraged to model a domain in the best possible way, but you won't be "part of the fediverse" until you implement enough of the post-facto Mastodon microblogging interop quirks.

We don't have a good ecosystem-level extension approach, and the #FEP constitutes a best-effort. A bandaid that allows to present a best-practice in hopes it gets further adoption.

I'm not sure that JSON-LD offers solace though.

@eyeinthesky I am genuinely curious. What do you mean by a "real" schema language? What criteria should it meet?

More specifically, what would constitute successful interoperability for #ActivityPub in line with the aims of #SocialWeb?

#JSONLD is not a schema language. It is used to serialise #ActivityStreams as the primary vocab for exchanging social activities, providing a foundation, and leaves room for extensibility for broad human needs to express social matters.

@eyeinthesky I am genuinely curious. What do you mean by a "real" schema language? What criteria should it meet?

More specifically, what would constitute successful interoperability for #ActivityPub in line with the aims of #SocialWeb?

#JSONLD is not a schema language. It is used to serialise #ActivityStreams as the primary vocab for exchanging social activities, providing a foundation, and leaves room for extensibility for broad human needs to express social matters.

@steve @jerger @mariusor @HolosSocial

An interesting document that was created for #ActivityStreams primer details "motivating use cases" for the specification, and these are categorized by domain.

https://www.w3.org/wiki/Activity_Streams/Primer/Motivating_Use_Cases

The primer also uses "domain" as terminology, and in Extensibility page reads:

> Activity Streams 2.0 extensions aren't self-explanatory or self-executing. It takes documentation and software to turn a pet-adoption schema into actual adoption of dogs and cats. However, ideally, the schema for pet adoptions could (and should) run over existing distribution infrastructure like ActivityPub.

https://www.w3.org/wiki/Activity_Streams/Primer/Extensions

It takes a schema and docs, which describe formats, validation, logic, msg exchanges to define what "app" means. These constitute a 'contract' whenever interoperability comes into play, and must be maintained somewhere discoverable, or all interoperability bets are off (and you get whack-a-mole development, app-by-app).

5/

So, not just Decentralized Social (DeSo), but instead —

Decentralized Social (DeSo), Federated Social (FeSo), Localized Social (LoSo)

The goal is 'social' that is simultaneously — 'Decentralized', 'Federated', and 'Localized', all at the same time.

RE: https://mastodon.social/@reiver/114551725757671167

#ActivityPub #ActivityStreams #Decentralization #DeSo #Federation #FeSo #Fediverse #governance #Localization #LoSo

4/

Federation is the word we use to describe that act of bringing together and connecting these separate Decentralized, Localized communities.

This is where protocols such as ActivityPub, ActivityStreams, etc come into play.

Federation is a voluntary choice.
But, so too is Defederation, if desired.

#ActivityPub #ActivityStreams #Decentralization #DeSo #Federation #FeSo #Fediverse #governance #Localization #LoSo

9/

[Fediverse BackUp]

So, I think an (ActivityPub / ActivityStreams) Activity File COULD be a "good" format for backing-up a single post on the Fediverse, but —

Most (maybe all) extant Fediverse software would need to change a bit. Fediverse software would need to support embedding "everything" in a single Activity File (rather than referring to "everything" else by URLs).

.

#ActivityPub #ActivityStreams #BackUp #BackUps #FediBackUp #FediDev #FediDevs #Fediverse

8/

[Fediverse BackUp]

Also — what about comments / replies —

Someone people (including me) would want at least some of the comments / replies to be included in a BackUp for a post.

So, for an Activity File to be a "good" format for a BackUp, a single Activity File would also need to contain (all or selected) the comments / replies to the post.

...

#ActivityPub #ActivityStreams #BackUp #BackUps #FediBackUp #FediDev #FediDevs #Fediverse

1/

[Fediverse BackUp]

Could an ActivityPub / ActivityStreams file be a "good" format for backing up a post?

(I.e., what I call an "Activity File". I.e., the file that has a media-type of "application/activity+json".)

...

#ActivityPub #ActivityStreams #BackUp #BackUps #FediBackUp #FediDev #FediDevs #Fediverse

7/

[Fediverse BackUp]

Also — we would need to consider Threads / Storms —

Where people reply to their own post to make a larger post made up of smaller posts.

(I.e., what I have been doing here 🙂 )

For an Activity File to be a "good" format for a BackUp, a single Activity File would need to contain all the posts in the Thread / Storm.

Also —

...

#ActivityPub #ActivityStreams #BackUp #BackUps #FediBackUp #FediDev #FediDevs #Fediverse

6/

[Fediverse BackUp]

Also — we would need to consider Threads / Storms —

Where people reply to their own post to make a larger post made up of smaller posts.

(I.e., what I have been doing here 🙂 )

for an Activity File to be a "good" format for a BackUp, a single Activity File would need to contain all the posts in the Thread / Storm.

Also —

...

#ActivityPub #ActivityStreams #BackUp #BackUps #FediBackUp #FediDev #FediDevs #Fediverse

5/

[Fediverse BackUp]

But — for an Activity File to be a "good" format for a BackUp, there would need to be a way to get the Fediverse software to embed the (non-text) media (such as images, audio, video, etc) into an Activity File.

Also —

...

#ActivityPub #ActivityStreams #BackUp #BackUps #FediBackUp #FediDev #FediDevs #Fediverse

5/

[Fediverse BackUp]

But — for an Activity File to be a "good" format for a BackUp, there would need to be a way to get the Fediverse software to embed the (non-text) media (such as images, audio, video, etc) into an Activity File.

Also —

...

#ActivityPub #ActivityStreams #BackUp #BackUps #FediBackUp #FediDev #FediDevs #Fediverse

4/

[Fediverse BackUp]

Now, having said that, I don't think there is anything about ActivityPub / ActivityStreams that "prevents" Fediverse software from not embedding (non-text) media (such as images, audio, video, etc) into an Activity File —

For example, an "Image" Object can contain a ("mediaType" and a) "content" field (rather than an "href" field).

But —

...

#ActivityPub #ActivityStreams #BackUp #BackUps #FediBackUp #FediDev #FediDevs #Fediverse

4/

[Fediverse BackUp]

Now, having said that, I don't think there is anything about ActivityPub / ActivityStreams that "prevents" Fediverse software from not embedding (non-text) media (such as images, audio, video, etc) into an Activity File —

For example, an "Image" Object can contain a ("mediaType" and a) "content" field (rather than an "href" field).

But —

...

#ActivityPub #ActivityStreams #BackUp #BackUps #FediBackUp #FediDev #FediDevs #Fediverse

3/

[Fediverse BackUp]

If you wanted to BackUp a post on the Fediverse, and all you download was the Activity File (with URLs pointing to the non-text media), then — you lost all the (non-text) media (such as images, audio, video, etc) that were part of the post.

Which would be bad.

...

#ActivityPub #ActivityStreams #BackUp #BackUps #FediBackUp #FediDev #FediDevs #Fediverse

3/

[Fediverse BackUp]

If you wanted to BackUp a post on the Fediverse, and all you download was the Activity File (with URLs pointing to the non-text media), then — you lost all the (non-text) media (such as images, audio, video, etc) that were part of the post.

Which would be bad.

...

#ActivityPub #ActivityStreams #BackUp #BackUps #FediBackUp #FediDev #FediDevs #Fediverse

2/

[Fediverse BackUp]

I think one challenge, in practice, with using an Activity File as a BackUp Format is that — a lot of Fediverse software does NOT embed (non-text) media (such images, audio, video, etc) in the Activity File.

But, instead references them using URLs.

(And, by "URL" I mean "URI", "IRI", etc.)

Usually this is probably a good thing, but —

...

#ActivityPub #ActivityStreams #BackUp #BackUps #FediBackUp #FediDev #FediDevs #Fediverse

2/

[Fediverse BackUp]

I think one challenge, in practice, with using an Activity File as a BackUp Format is that — a lot of Fediverse software does NOT embed (non-text) media (such images, audio, video, etc) in the Activity File.

But, instead references them using URLs.

(And, by "URL" I mean "URI", "IRI", etc.)

Usually this is probably a good thing, but —

...

#ActivityPub #ActivityStreams #BackUp #BackUps #FediBackUp #FediDev #FediDevs #Fediverse

1/

[Fediverse BackUp]

Could an ActivityPub / ActivityStreams file be a "good" format for backing up a post?

(I.e., what I call an "Activity File". I.e., the file that has a media-type of "application/activity+json".)

...

#ActivityPub #ActivityStreams #BackUp #BackUps #FediBackUp #FediDev #FediDevs #Fediverse

1/

[Fediverse BackUp]

Could an ActivityPub / ActivityStreams file be a "good" format for backing up a post?

(I.e., what I call an "Activity File". I.e., the file that has a media-type of "application/activity+json".)

...

#ActivityPub #ActivityStreams #BackUp #BackUps #FediBackUp #FediDev #FediDevs #Fediverse

If you're trying to dereference all RDF namespaces found in the #ActivityStreams JSON-LD document you must first download the internet.

Now downloading google.com...

#ActivityPub #ActivityPubDev

If you're trying to dereference all RDF namespaces found in the #ActivityStreams JSON-LD document you must first download the internet.

Now downloading google.com...

#ActivityPub #ActivityPubDev

I wish there was a facility (native or in any app, ideally as part of the #ActivityStreams objects) where I could make #notes on #toots, like we can make notes about particular accounts.

I have a bunch of stuff #bookmarked; I have a tool that exports and sorts my bookmarks.. but by the time I get around to curating them, half the time I can't remember why I bookmarked something.

I wish there was a facility (native or in any app, ideally as part of the #ActivityStreams objects) where I could make #notes on #toots, like we can make notes about particular accounts.

I have a bunch of stuff #bookmarked; I have a tool that exports and sorts my bookmarks.. but by the time I get around to curating them, half the time I can't remember why I bookmarked something.

"＠context": [
"https://www.w3.org/ns/activitystreams",
{
"Quotation": "as:Quotation",
"citation": "as:citation",
"quotation": "as:quotation"
},
],

#ActivityPub #ActivityStreams #FediDev #Fediverse #JSONLD #ObjectTypeQuotation #retejo

4/

Apparently, Bookwyrm stores quotations with:

type="Quotation"

And if one Bookwyrm server talks to another Bookwyrm server, then — the ActivityPub / ActivityStreams representation of the quotation will have:

type="Quotation"

...

BUT — if a non-Bookwyrm server talks to a Bookwyrm server, then — the ActivityPub / ActivityStreams representation of the quotation will have:

type="Note"

#ActivityPub #ActivityStreams #FediDev #Fediverse #ObjectTypeNote #ObjectTypeQuotation #retejo

3/

Apparently the Bookwyrm developer had the exact same idea!

(Which isn't too surprising.)

Here is how it works —

...

#ActivityPub #ActivityStreams #FediDev #Fediverse #ObjectTypeNote #ObjectTypeQuotation #retejo

2/

How could you represent a quotation in ActivityPub‽

...

I suppose there are 2 major approaches.

Either use an existing Object Type. Maybe:

type="Note"

Or create a new Object Type:

type="Quotation"

...

Here is the interesting thing though —

#ActivityPub #ActivityStreams #FediDev #Fediverse #ObjectTypeNote #ObjectTypeQuotation #retejo

Quotations & the Fediverse / ActivityPub

1/

One thing I used to do a lot on social-media is — post quotations.

Sometimes I was reading a book. And, I would quote things from the book and post it on social-media.

Or I was reading a scholarly paper, or reading a blog post, or watching a video, or listening to a podcast, etc.

...

I was thinking — how could you represent a quotation in ActivityPub‽

#ActivityPub #ActivityStreams #FediDev #Fediverse #ObjectTypeNote #ObjectTypeQuotation #retejo

4/

Apparently, Bookwyrm stores quotations with:

type="Quotation"

And if one Bookwyrm server talks to another Bookwyrm server, then — the ActivityPub / ActivityStreams representation of the quotation will have:

type="Quotation"

...

BUT — if a non-Bookwyrm server talks to a Bookwyrm server, then — the ActivityPub / ActivityStreams representation of the quotation will have:

type="Note"

#ActivityPub #ActivityStreams #FediDev #Fediverse #ObjectTypeNote #ObjectTypeQuotation #retejo

Quotations & the Fediverse / ActivityPub

1/

One thing I used to do a lot on social-media is — post quotations.

Sometimes I was reading a book. And, I would quote things from the book and post it on social-media.

Or I was reading a scholarly paper, or reading a blog post, or watching a video, or listening to a podcast, etc.

...

I was thinking — how could you represent a quotation in ActivityPub‽

#ActivityPub #ActivityStreams #FediDev #Fediverse #ObjectTypeNote #ObjectTypeQuotation #retejo

4/

Apparently, Bookwyrm stores quotations with:

type="Quotation"

And if one Bookwyrm server talks to another Bookwyrm server, then — the ActivityPub / ActivityStreams representation of the quotation will have:

type="Quotation"

...

BUT — if a non-Bookwyrm server talks to a Bookwyrm server, then — the ActivityPub / ActivityStreams representation of the quotation will have:

type="Note"

#ActivityPub #ActivityStreams #FediDev #Fediverse #ObjectTypeNote #ObjectTypeQuotation #retejo

3/

Apparently the Bookwyrm developer had the exact same idea!

(Which isn't too surprising.)

Here is how it works —

...

#ActivityPub #ActivityStreams #FediDev #Fediverse #ObjectTypeNote #ObjectTypeQuotation #retejo

2/

How could you represent a quotation in ActivityPub‽

...

I suppose there are 2 major approaches.

Either use an existing Object Type. Maybe:

type="Note"

Or create a new Object Type:

type="Quotation"

...

Here is the interesting thing though —

#ActivityPub #ActivityStreams #FediDev #Fediverse #ObjectTypeNote #ObjectTypeQuotation #retejo

Quotations & the Fediverse / ActivityPub

1/

One thing I used to do a lot on social-media is — post quotations.

Sometimes I was reading a book. And, I would quote things from the book and post it on social-media.

Or I was reading a scholarly paper, or reading a blog post, or watching a video, or listening to a podcast, etc.

...

I was thinking — how could you represent a quotation in ActivityPub‽

#ActivityPub #ActivityStreams #FediDev #Fediverse #ObjectTypeNote #ObjectTypeQuotation #retejo

9/

A regular users might write Markdown like this:

"""
# Hello!

How do you do?
"""

Or write HTML like this:

"""
<article>
<h1>Hello!</h1>
<p>How do you do?</p>
</article>
"""

#ActivityPub #ActivityStreams #FediDev #Fediverse #Markdown #retejo #RDFa

8/

REMEMBER: this is for power-users, not regular users

How would you get ActivityPub / ActivityStreams into HTML using RDFa‽

Like this:

<div vocab="https://www.w3.org/ns/activitystreams#" typeof="Note">
<p property="name">Hello!</p>
<p>How do you do?</p>
</div>

AGAIN, REMEMBER: this is for power-users, not regular users.

Regular users can just write Markdown or HTML and Retejo will figure this out automatically for you

#ActivityPub #ActivityStreams #FediDev #Fediverse #Markdown #retejo #RDFa

7/

If you are wondering what RDFa is —

You might be more familiar with OpenGraph.

https://ogp.me/

OpenGraph is usually the thing that causes "preview cards" to be showed for links shared on social-media.

OpenGraph is written in RDFa. Which, in practice, is some special HTML elements added to the page.

For example:

<meta property="og:image" content="https://example.com/img/preview.png" />

So what about ActivityPub‽ —

#ActivityPub #ActivityStreams #FediDev #Fediverse #Markdown #retejo #RDFa

1/

I have spending time thinking of ways you could automatically create ActivityPub / ActivityStreams data from HTML and Markdown

Most people will probably write in plain UTF-8 text, or Markdown, or HTML

How to do you take that and get it onto the Fediverse and Social Web‽

This isn't just a question of how to technically do it — but also a question of user-experience (UX)

I.e., what are "good" ways of doing it‽

...

#ActivityPub #ActivityStreams #FediDev #Fediverse #Markdown #retejo #RDFa

6/

Obviously, beginners are NOT going to do this, but — some power-users may want this level of control.

There are different way this could be done, but — one way might be that power-users could use RDFa to explicitly specify what data from the HTML gets into the ActivityPub / ActivityStreams data.

Again, beginners and typical users would NOT do this.

But a power-user might want to.

Here is an example —

#ActivityPub #ActivityStreams #FediDev #Fediverse #Markdown #retejo #RDFa

5/

So, what would be a good user-experience (UX) for power-users be — in a system that automatically creates ActivityPub / ActivityStreams data from HTML and Markdown‽

One thought I had is that power-users could explicitly mark what data from their HTML gets into the ActivityPub / ActivityStreams data (if they want to).

I'll explain —

#ActivityPub #ActivityStreams #FediDev #Fediverse #Markdown #retejo #RDFa

1/

I have spending time thinking of ways you could automatically create ActivityPub / ActivityStreams data from HTML and Markdown

Most people will probably write in plain UTF-8 text, or Markdown, or HTML

How to do you take that and get it onto the Fediverse and Social Web‽

This isn't just a question of how to technically do it — but also a question of user-experience (UX)

I.e., what are "good" ways of doing it‽

...

#ActivityPub #ActivityStreams #FediDev #Fediverse #Markdown #retejo #RDFa

4/

I think one mistake some software does is — they create a good experience for beginners, but have a poor experience for power-users.

And keep in mind that — some beginners become power-users later on.

I think it is important to design for power-users, too, in addition to beginners.

...

#ActivityPub #ActivityStreams #FediDev #Fediverse #Markdown #retejo #RDFa

3/

If a typical user is writing in Markdown, and their Markdown file has a level-1 heading right at the beginning, then —

That could go into the ActivityPub "name" field.

And, similar could be done for HTML, too.

...

But what about power users —

#ActivityPub #ActivityStreams #FediDev #Fediverse #Markdown #retejo #RDFa

2/

What are "good" ways of automatically creating ActivityPub / ActivityStreams data from HTML and Markdown‽

I think the answer depends on who, for example, is writing HTML, and how they are writing it.

For example, is this a typical user? Is this a power-user? Do they know HTML? And if they do know HTML, how well do they know it? Etc?

I will show you what I mean —

...

#ActivityPub #ActivityStreams #FediDev #Fediverse #Markdown #retejo #RDFa

1/

I have spending time thinking of ways you could automatically create ActivityPub / ActivityStreams data from HTML and Markdown

Most people will probably write in plain UTF-8 text, or Markdown, or HTML

How to do you take that and get it onto the Fediverse and Social Web‽

This isn't just a question of how to technically do it — but also a question of user-experience (UX)

I.e., what are "good" ways of doing it‽

...

#ActivityPub #ActivityStreams #FediDev #Fediverse #Markdown #retejo #RDFa

1/

I have spending time thinking of ways you could automatically create ActivityPub / ActivityStreams data from HTML and Markdown

Most people will probably write in plain UTF-8 text, or Markdown, or HTML

How to do you take that and get it onto the Fediverse and Social Web‽

This isn't just a question of how to technically do it — but also a question of user-experience (UX)

I.e., what are "good" ways of doing it‽

...

#ActivityPub #ActivityStreams #FediDev #Fediverse #Markdown #retejo #RDFa

Retejo

I have been working on a new type of web-server for serving static web-sites.

I started working on it recently — on August 23rd. But, have had the idea for it for a number of years.

...

What is different about this web-server for static web-sites‽

Well, of course, it supports HTML.

But, it also supports Markdown, and ActivityPub natively!

https://codeberg.org/reiver/retejo

#ActivityPub #ActivityStreams #codeberg #forgejo #gitea #markdown #retejo #StaticSite #StaticWeb #StaticWebSite

1/

If you are curious about where the "Retejo" name comes from —

The way the name "retejo" was chosen was inspired by how the name "forgejo" chosen.

...

RE: https://mastodon.social/@reiver/115203527761462559

#ActivityPub #ActivityStreams #codeberg #forgejo #GeminiProtocol #gitea #markdown #retejo #SmallNet #SmallWeb #StaticSite #StaticWeb #StaticWebSite

2/

"forgejo" comes from the Esperanto word "forĝejo".

"retejo" is (also) an Esperanto word.

The meaning of the Esperanto word "retejo" can be understood as follows:

ret-: The root for "net" or "web".
-ej-: A suffix meaning "place" or "site".
-o: The noun ending.

https://codeberg.org/reiver/retejo

RE: https://mastodon.social/@reiver/115203527761462559

#ActivityPub #ActivityStreams #codeberg #forgejo #GeminiProtocol #gitea #markdown #retejo #SmallNet #SmallWeb #StaticSite #StaticWeb #StaticWebSite

1/

If you are curious about where the "Retejo" name comes from —

The way the name "retejo" was chosen was inspired by how the name "forgejo" chosen.

...

RE: https://mastodon.social/@reiver/115203527761462559

#ActivityPub #ActivityStreams #codeberg #forgejo #GeminiProtocol #gitea #markdown #retejo #SmallNet #SmallWeb #StaticSite #StaticWeb #StaticWebSite

1/

Probably the biggest thing that motivated me to create Retejo now (as I've had the idea for this for a number of year) is —

...

RE: https://mastodon.social/@reiver/115203482817088160

#ActivityPub #ActivityStreams #codeberg #forgejo #GeminiProtocol #gitea #markdown #retejo #SmallNet #SmallWeb #StaticSite #StaticWeb #StaticWebSite

4/

So, I thought — what if I just ran my own web-server to server files from Codeberg.

And thus, Retejo was born.

https://codeberg.org/reiver/retejo

...

But, while I am at it, I can also add automatic ActivityPub / ActivityStreams support to it.

RE: https://mastodon.social/@reiver/115203482817088160

#ActivityPub #ActivityStreams #codeberg #forgejo #GeminiProtocol #gitea #markdown #retejo #SmallNet #SmallWeb #StaticSite #StaticWeb #StaticWebSite

3/

№1:

The software powering Codeberg Pages seems like it isn't being maintained anymore beyond minor fixes

№2:

Although Codeberg is pretty reliable, Codeberg Pages doesn't that reliable.

...

So, I thought —

...

RE: https://mastodon.social/@reiver/115203482817088160

#ActivityPub #ActivityStreams #codeberg #forgejo #GeminiProtocol #gitea #markdown #retejo #SmallNet #SmallWeb #StaticSite #StaticWeb #StaticWebSite

2/

Although I've had a Codeberg account for a number of years — I recently started the process of migrating over to Codeberg (from GitHub).

Codeberg has something similar to GitHub Pages — called Codeberg Pages

https://codeberg.page/

However —

...

RE: https://mastodon.social/@reiver/115203482817088160

#ActivityPub #ActivityStreams #codeberg #forgejo #GeminiProtocol #gitea #markdown #retejo #SmallNet #SmallWeb #StaticSite #StaticWeb #StaticWebSite