silverpill

@julian

No, that's for target property. Here's an example of Add.target from Streams:

"target": {
  "id": "https://streams.lndo.site/conversation/ed4775f8-18ee-46a5-821e-b2ed2dc546e8",
  "type": "Collection",
  "attributedTo": "https://streams.lndo.site/channel/red"
},

In my code I have a handler for Add activity, which then sends activity to one of the other handlers:

- Add{target: featured}
- Add{target: subscribers}
- Add{target: context}

Currently I use heuristics to determine which one to use. But with Add.target.type == <meaningful type name> the code would be simpler and less fragile.

Do you have something like that in NodeBB? I wonder how others solve this "routing" problem

@julian @evan @jenniferplusplus @mikedev @erincandescent @evan @trwnh

>7888/171b use context whereas 76ea uses a new property thr:thread

I think context is good enough. Streams and NodeBB already provide this collection and Mitra will too.

>171b specifies a new object type Context

It is for easier identification of conversation-Add activities. My server may receive many different kinds of Add activities, and it would be nice to have some indication of what collection is being modified.

This is just an idea though. Streams uses Collection type

>Collection items:

My use case requires items to be activities, but I can support both variants of context collection. Conversation activities can be also put into a different collection.

@julian @trwnh @thisismissem

>How that is represented via ActivityPub is probably detailed in some FEP

FEP-e232? I think you can add content or summary property to FEP-e232 link to represent HTML content of a quote

@5dh @fediverse Financial incentive is not the only possible cause. If project leaders stop listening to their users for some other reason, you'll get the same result.
And there is another, more subtle problem: protocol bloat. Fediverse services are getting more and more complicated, and the cost of creating a new platform is constantly increasing. If this problem is not addressed, at some point Fediverse will start looking like a web browser market, where new players can't compete due to an immense implementation complexity.

@evan @darius @julian Merged: https://codeberg.org/fediverse/fep/src/branch/main/fep/76ea/fep-76ea.md

@trwnh @mikedev @julian This object design pattern (partial embeddings) can be used in other situations too. We can use a new property like partial: true do indicate partial representations:

https://socialhub.activitypub.rocks/t/partially-embedded-objects/4450

@mikedev @trwnh @julian

Context helps with identifying the target. When I receive an Add activity, I need to know what collection is being modified. Is it a featured collection, a context, or something else?

One solution is to keep an index of all known collections and search through it every time Add is received.
Another solution would require cooperation from producers, but I think it is a bit cleaner: embed partial representation of a target and use specific type there, like Context, instead of Collection. Then, as a consumer, I can simply check target.type instead of searching for target.id in my collection index.

@julian @mikedev Yes, this is a new requirement, but I can't comment on that part yet. The FEP is very much work in progress

@julian @trwnh @mikedev

There is a draft of Conversation Containers FEP: https://codeberg.org/silverpill/feps/src/branch/main/171b/fep-171b.md
And I've come up with a plan for FEP-400e and FEP-1b12 convergence: https://socialhub.activitypub.rocks/ap/object/e9b7fb34c4af9291b9b98095e661789d

@monerobull @monero @owe_addams

>their garbage tier mascot

Wait, zcash has a mascot?

@deadsuperhero @fediverse @quillmatiq Protocols described in these FEPs are currency-agnostic and developers can build actual platforms and solutions on them (as I did). This is the only ongoing effort to bring a payment layer to the Fediverse - there are no alternative proposals. FEP-8c3f was withdrawn in favor of FEP-0ea0.

Okay, you didn't know about it. But now you do and it would be nice to include at least some of that information in the article.

@deadsuperhero @fediverse You cite an abandoned project and withdrawn WebMonetization FEP and then say "most efforts have not advanced beyond the planning stages". This statement is misleading because those planning stages are far behind us. Mitra had subscriptions since 2022 and there are other projects that provide monetization options, like PeerTube Lightning plugin and PeerTube Premium Users plugin. FEP-0ea0 and FEP-0837 were published and implemented. Your co-author @quillmatiq should be well aware of these developments because we talked about it