Forums and Threaded Discussions Task Force

0 readers

1 users here now

Discussion and announcements related to the SWICG Forums and Threaded Discussions Task Force.

This profile is a discussion forum category and shares content from users who post in its discussions.

founded 4 months ago

FEP Convergence (400e, 7888, 171b/Conversation Containers, 76ea) (community.nodebb.org)

submitted 3 weeks ago by [email protected] to c/[email protected]

25 comments fedilink hide all child comments

Related to the ForumWG topic of resolvable context collections, there are four FEPs that are currently in consideration:

@[email protected] made a suggestion last month to hopefully reduce the number of moving parts:

Both FEP-400e and FEP-1b12 implementations: support FEP-7888 (context collection)

FEP-400e implementations: upgrade to Conversation Containers

FEP-1b12 implementations: add target property to Announce activity that points to context collection.

This takes FEP 400e out of the running (potentially). But the day after that last meeting, @[email protected] put together FEP 76ea, and now we're back to three.

My concern is that all three FEPs (7888, 171b, and 76ea) all share these distinct qualities:

They establish a conversational context for a given object
They federate out an Add on collection addition. (76ea also sends Remove)
They contain some concept of a context owner (attributedTo)

They differ on the following qualities:

7888/171b use context whereas 76ea uses a new property thr:thread
171b specifies a new object type Context
Collection items:
- 7888 sends objects in chronological order
- 171b sends activities in chronological order
- 76ea sends objects in reverse chronological order

In the lead up to the November WG meeting I'd like to address those differences. All three FEPs are in pre-draft or draft stages, and so I am hoping we can find some common ground and compromise.

Pinging interested parties (who were not already mentioned above) for comment:

@[email protected] @[email protected] @[email protected] @[email protected]

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 2 weeks ago

@julian

If, for example, someone were to see my context and say "I'd like to map this context's objects out into a word cloud and do sentiment analysis on it", I think that's a perfectly cromulent use of the data. For me to say "this here is a thread, and you better treat it as a thread" is contrary to the spirit of ActivityPub and fedidevs in general.

Simply declaring a collection to be a thread does not force people to display it as a thread. But it does provide valuable information to people who do want to display it as a thread.

So you are not removing people's choice by simply stating that on your platform, this is considered a thread.