I sat down with @snarfed.org to talk about his work around the #fediverse, the #indieweb and the #atmosphere including (fed.)brid.gy and @anewsocial
https://openchannels.fm/connecting-decentralized-social-networks-and-rethinking-interoperability/
@quillmatiq you should post about this on the @anewsocial account!
@liaizon Tysm for the heads up!
@janeckhoff 😉
@seindal true, but not properly handling "novels" as a client is hostile to the reader too... the fediverse is not only microblogging!
I will work on improving the handling, but I plugins do unpredictable things sometimes. like for example adding trasnscripts to the content through a filter.
@janeckhoff I will check with them to maybe truncate the quotes!
the weird JS output is already fixed and will be published with the next release. I will also how to limit the podcast episode to the summary!
sorry about that!
@ted you're welcome :)
It is not always easy to deal with the WordPress beast ;)
@ted wordpress caching does not support content negotiation by default. it caches what was requested and returned. if mastodon requests the page content in JSON after it was federated, the cache would take this response and cache it. so either you disable caching or you disable content negotiation for user facing sites.
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
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
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" and "sameAs" would be a poor choice. And, 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
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
@macgirvin
I thought Punycode was only for domain names. Are you saying you also use it for the user part?