this post was submitted on 04 Oct 2024
0 points (NaN% liked)

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
0
Minutes from 3 October 2024 WG Meeting (community.nodebb.org)
submitted 1 month ago by [email protected] to c/[email protected]
23 comments fedilink hide all child comments
 

The minutes from yesterday's Forum and Threaded Discussions Task Force monthly meeting can be found at this Google Docs link

Apologies in advance if I misrepresented anybody or missed any crucial bits of information.

Of note:

Mastodon and its treatment of non-note items

  • Darius Kazemi (@[email protected]) reports that Hometown already supports improved conversion of non-note items (like as:Article) into statuses, and that this serves as a working proof-of-concept towards getting this merged upstream into Mastodon proper.
  • We discussed briefly the Mastodon PR approval process and how it sometimes drives away contributions
    • Darius emphasized the importance of showing real user support to facilitate the merging of pull requests.

Context Collections and FEP Convergence

  • Julian proposed consolidating various FEPs (7888, 400e, 171b) to publish a unified recommendation.
  • Evan (@[email protected]) objected to the use of the "context" property in FEP 7888, advocating for a new vocabulary instead.
  • The discussion included differing views on the utility of the context property and its historical usage.
  • Darius utilized his data observatory (TBD) data set to hopefully prove that context is not a properly currently seeing any usage.

"Convenings" and Collaboration Initiatives:

  • Darius, representing the Applied Social Media Lab, proposed organizing physical meetings to enhance interoperability in the fediverse.
  • He will provide a blog post detailing the ActivityPub Data Observatory and related goals.

ActivityPub Trust & Safety Task Force

  • A new task force will focus on protocol-level issues within ActivityPub, including proper content warnings and labeling.
  • Meetings are tentatively scheduled for the second Tuesday of each month (starting November), with a call for input on scheduling.
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 1 month ago (1 children)

@[email protected] @[email protected] @[email protected] Quick question, and forgive me for my ignorance: how is this different from the proposal for Conversation Containers?

https://codeberg.org/silverpill/feps/src/branch/main/171b/fep-171b.md

[–] [email protected] 1 points 1 month ago (1 children)

@deadsuperhero @julian @darius

  1. It defines a new property, thread, to identify the conversation thread of an object, instead of the context property, which can be used for other things besides threading.
  2. It uses an existing type, OrderedCollection, for the thread, instead of creating a new type.
  3. It defines a root property to quickly navigate from a thread collection to the root object.
  4. The thread contains objects that point to each other using the inReplyTo property.
[–] [email protected] 1 points 1 month ago* (last edited 1 month ago)

Having a separate thread property may be useful. One possible use case would be where threads or posts are labelled or categorized or placed in a list, and this is exposed as a context.

In that case, the thread and the context would be different.

cc: @Evan Prodromou @Sean Tilley @julian @Darius Kazemi