It's wild that I was able to discuss federation/ActivityPub with other developers in person.
Uncategorized
6
Beiträge
4
Kommentatoren
0
Aufrufe
-
It's wild that I was able to discuss federation/ActivityPub with other developers in person.
This was my first conference and also the first time I ever met another developer IRL.
Sitting in a loud pub and hearing @julian backfilling proposal was iconic
When I asked about how to handle private/follower-only activities, he paused and said he only considered public activities, so I'll be working on that.
And @jesseplusplus and I will be working on Stories + Circles together!
Gosh it was fun
-
It's wild that I was able to discuss federation/ActivityPub with other developers in person.
This was my first conference and also the first time I ever met another developer IRL.
Sitting in a loud pub and hearing @julian backfilling proposal was iconic
When I asked about how to handle private/follower-only activities, he paused and said he only considered public activities, so I'll be working on that.
And @jesseplusplus and I will be working on Stories + Circles together!
Gosh it was fun
@dansup @julian@community.nodebb.org @jesseplusplus
Are there any circumstances under which context backfilling has to handle non-public posts? The way that ActivityPub delivery works, I would think that if a post has a recipient collection that doesn't include "as:Public", everyone who ought to be able to see it has already received a copy at time of creation.I guess depending on the internal data model you might need to "reconnect" them (if they are replies to posts you receive later via backfill).
-
@dansup @julian@community.nodebb.org @jesseplusplus
Are there any circumstances under which context backfilling has to handle non-public posts? The way that ActivityPub delivery works, I would think that if a post has a recipient collection that doesn't include "as:Public", everyone who ought to be able to see it has already received a copy at time of creation.I guess depending on the internal data model you might need to "reconnect" them (if they are replies to posts you receive later via backfill).
@dansup @julian@community.nodebb.org @jesseplusplus Maybe we want the option to backfill private contexts so you can join a group and then see its post history? Or follow someone and gain access to old followers-only posts? AFAIK Mastodon doesn't currently do the latter, so that might cause some friction around privacy expectations. Okay, I see there is room to think on this!
-
@dansup @julian@community.nodebb.org @jesseplusplus Maybe we want the option to backfill private contexts so you can join a group and then see its post history? Or follow someone and gain access to old followers-only posts? AFAIK Mastodon doesn't currently do the latter, so that might cause some friction around privacy expectations. Okay, I see there is room to think on this!
@julian@fietkau.social @dansup @julian@community.nodebb.org these are great questions, and I think this is where the interaction between the context field and the audience of the post will be interesting. A private/followers-only reply can copy the context, but right now since there is no way to set a collection besides public or followers as the audience, the reply cannot currently copy the audience of the original post, so it will still not be seen by anyone in the original audience who is not also in the replier’s followers
-
@dansup @julian@community.nodebb.org @jesseplusplus
Are there any circumstances under which context backfilling has to handle non-public posts? The way that ActivityPub delivery works, I would think that if a post has a recipient collection that doesn't include "as:Public", everyone who ought to be able to see it has already received a copy at time of creation.I guess depending on the internal data model you might need to "reconnect" them (if they are replies to posts you receive later via backfill).
julian@fietkau.social you're right about that. Backfilling is most beneficial in a public conversation context. I am sure there are some non-public applications (backfilling a private group discussion, as you point out), but for simplicity and ease of implementation I felt it was best to focus on the public-only aspect for now.
We aren't even at the point where we can specify recommendations for context inheritance and ownership, although we'll be working on those items next at the ForumWG!
-
@julian@fietkau.social @dansup @julian@community.nodebb.org these are great questions, and I think this is where the interaction between the context field and the audience of the post will be interesting. A private/followers-only reply can copy the context, but right now since there is no way to set a collection besides public or followers as the audience, the reply cannot currently copy the audience of the original post, so it will still not be seen by anyone in the original audience who is not also in the replier’s followers
jesseplusplus@mastodon.social yes and no! In the threadiverse it is actually quite common to reference a group actor in the to/cc. That actor is the second order context.
In regular parlance, that's the category/forum that the topic (context) is contained in.
Preferably it'd be in
audienceas well... and 1b12 does specify it's inclusion in that property.
Diese Artikel könnten Dich auch interessieren.
-
-
-
-
-
-
Fedicon 2025 is currently taking place. All the videos are being posted in this PeerTube account
Uncategorized
1
-
-
@julian diving into the hard problems of building for the Fediverse at #Fedicon, starting with hilariously talking about how those hard problems look like to average users 😅
Uncategorized
3
