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
 

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 (7 children)

@erincandescent @julian @darius it's covered in the doc, which is free to read!

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

@evan @julian @darius That doesn’t really cover the why other than “context is vaguely defined” (maybe, but its’ been used in this exact way for… 7 years now? And is being used in this way by multiple interoperating implementations)

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

@erincandescent @julian @darius great. You can definitely use both.

context is fine for any kind of grouping of objects, as is noted in AV.

https://www.w3.org/TR/activitystreams-vocabulary/#dfn-context

If you want to specifically talk about a conversation tree, a more specific property is better.

[–] [email protected] 1 points 1 month ago

@evan @julian @darius I don’t really have a horse in this race but we’ll probably never get rid of the existing use of context so I mostly question the advantage of us having to deal with three conversation grouping properties for the indefinite future

load more comments (3 replies)
load more comments (4 replies)
load more comments (4 replies)