post (@post@community.nodebb.org)
As of today, the NodeBB-ActivityPub implementation now supplies both context and audience properties with every post.
N.B. When I say context and audience, these are also terms used by the ForumWG that refer to "topic" and "category", in NodeBB parlance.
Early indications from the last ForumWG meeting indicate movement towards the inclusion of context in a low-level as:Note object (a federated NodeBB post), resolvable as an as:Collection or as:OrderedCollection. The latter is what NodeBB will send, ordered by post time.
Discussions with @angus@socialhub.activitypub.rocks also suggest that Discourse has the ability to parse an as:OrderedCollection context if provided, but currently does not if encountered as a property in a Note.
A minor change today also updates the audience property, which used to erroneously point to the context/topic, but now points to the audience/category. This change aligns usage of this property with FEP-1b12's expectations.
This change should allow other implementors to:
- automatically group objects together given a the provided context, and
- more thoroughly backfill a given object's context, without relying on
inReplyTotraversal
Show Original Post
grishka (@grishka@mastodon.social)
I made a FEP for an important part of my groups implementation: https://codeberg.org/fediverse/fep/src/branch/main/fep/db0e/fep-db0e.md
Show Original Post
nickdrawthing (@nickdrawthing@dice.camp)
Are there any #ActivityPub blogging services that automatically slice up long posts into 500-character (maximum), threaded posts when you publish? I like the idea of an ActivityPub compatible blog but I know a lot of people (myself included) aren't wild about huge, 10K character posts showing up on their feed.
I can imagine a service like this that provides a clean looking article when viewed on the originating site, but provides threaded posts on the federated TL.
Maybe this already exists?
Show Original Post
GualTRex (@GualTRex@mastodon.uno)
#ghost adotta #activitypub đ
https://activitypub.ghost.org/
Show Original Post
steve (@steve@social.technoetic.com)
Itâs crazy! The same terms for different concepts. Different terms for the same concept. So many inconsistencies. So many interoperability challenges. No, Iâm not talking about #ActivityPub development this time. Iâm learning French. đ Câest la vie dans le monde rĂ©el. đ·
Show Original Post
mapache (@mapache@hachyderm.io)
This is interesting, specially because they don't have a fediverse account
Show Original Post
paninid (@paninid@mastodon.world)
@mhoye are you thinking along the lines of a #PKM (Roam, Obsidian, Logseq) integration with #ActivityPub?
Because if so, I am also interested.
Show Original Post
davidbisset (@davidbisset@phpc.social)
Encrypted DMs Are Coming to #ActivityPub
https://wedistribute.org/2024/05/encrypted-dms-activitypub/
"At this point, E2EE DMs in the Social Web arenât a question of âifâ , but âwhenâ."
Show Original Post
JsonCulverhouse (@JsonCulverhouse@flipboard.social)
@dalias @evan @neptune22222 @tomcoates
Are we going to be able to register a additional public key to use for encrypted messages?
This way you can encrypt and send messages but we can decrypt on device?
Right now only the #activitypub server implementation holds your private key. So not really end to end.
Show Original Post
post (@post@community.nodebb.org)
Please see below for minutes from today's Forum and Threaded Discussions Task Force monthly meeting.
Apologies in advance if I misrepresented anybody or missed any crucial bits of information
Participants
in order of appearance
- Dmitri, @dmitri@social.coop
- Angus, @angus@socialhub.activitypub.rocks
- Julian, @julian@community.nodebb.org
- Rimu, @rimu@mastodon.nzoss.nz
- Evan, @evan@cosocial.ca
- Mattias, @pfefferle@mastodon.social
- Emelia: @thisismissem@hachyderm.io
- a: @trwnh@mastodon.social
- Dmitri invited participants to the regular SWICG call tomorrow; best place to be informed of upcoming events: SocialCG calendar â "please come by, it is free for everyone to join or listen in"
- Angus provided an update to the working group's inclusion under the banner of the Social Web Incubator Community Group (SWICG), revised name would be the Forums and Threaded Discussions Task Force, or "ForumWG" for short.
- Julian provided an update on this past month's usage of the fediverse to hold asynchronous discussion, a number of threads have been started on the respective forum categories (both of which federate out) for the working group pertaining to discussions re: agenda items, and have been fairly well received.
- Angus and Julian will update the respective handles of their categories to reflect the new working group name
"Lay of the Land" survey reports
- Angus: The general spirit of these surveys is 'these are the existing X approaches, the plurality may indicate the need to converge'
- Nomenclature
- Rimu: Document continues to be expanded upon
- Evan re-iterates that it is unlikely any implementors will change their nomenclature to match
- Angus asks whether participants find utility in the list
- Evan indicates that whatever is decided upon is best used "on-the-wire", Julian agrees and notes that the agreed-upon terminology would be used in the "Definitions" portion of any report written by ForumWG; suggests the list may be best kept as a living reference
- Rimu indicates that as the list grows, alternative ways to represent the data may be required
- Round of applause for Rimu for taking the initiative to start (and now maintain) the list
- Object Type (Article vs. Note vs. Page)
- Impetus for topic: WordPress sending out
as:Notewhenas:Articlewould be more suitable- @jupiter_rowland@hub.netzgemeinde.eu (in topic, paraphrased): Mastodon values microblogging UX and locked down their allowed html to satisfy this constraint, despite Hubzilla's pleas
- @mikedev@fediversity.site (in topic, paraphrased): Raised issue in 2017 to address issues with inline images being removed. Suggested a compromise: treat Article and Note differently (Note, text only with attachments; Article, full HTML) â Eugen 7 months later closed issue with change to further hamper treatment of Article, by showing only title and link back to source.
- @pfefferle@mastodon.social (in topic): "You can choose 'Note' if you want to have the best compatibility"
- Evan: Whether a note or article is federated, it shouldn't hamper implementation; but
as:Pageshould not be used - Mattias: Choice is given to user as to how WP maps the native Post object to ActivityPub. Historically sent out
Articlebut received a lot of pushback from early adopters. Difficult to reconcile UX with technical limitations - Evan: "An
as:Noteis a Tweet (we just couldn't call it that), anas:Articleis a blog post" - Emelia: "Should software publish different objects based on content length, even if using the same mechanism?"
- a: Big picture view â it doesn't seem complicated, but it is, because the line between them is completely arbitrary.
- Mattias: We try to autodetect (no headers, content length, etc.), would prefer different content types based on what users write, but the advantage is being able to read content natively on the user's platform of choice
- Dmitri: "I think we've got several questions in parallel:
- What SHOULD these things (Note & Article) be used for.
- What to do about Mastodon who only seems to consume Notes."
- Emelia: Don't Articles usually have titles?
- Everyone else: crickets (made us think!)
- a: https://wiki.trwnh.com/tech/spec/activitypub/confusion/note-vs-article/ (also indicates using title to discriminate Article vs. Post isn't 100%)
- a: The reason we're talking about this is because of various differring implementations - for example, in one implementor's mental model, you have a thread with a title and that is separate from the posts contained within; posts that may also have titles of their own. How do we reconcile this?
- Julian and Rimu note that @renchap@oisaur.com replied in-topic: "... we would like to improve how non-Note objects are processed/displayed in Mastodon."
- Julian mentions a compromise put forth by @mikedev@fediversity.site where Notes are smaller pieces of content with limited markup and attachments, and Articles are (sometimes) larger pieces with formatting, inline images. Additional survey/spreadsheet to be created, but we could as a group (Mastodon included) converge on a path forward and a report to the SocialCG could be authored. To be continued next month.
- Impetus for topic: WordPress sending out
- Group Actor characteristics
- 1b12 - announcing the activities of their actors, this is what Discourse and NodeBB do, other implementations have taken this approach
- @nutomic@lemmy.ml (paraphrased): "intent of 1b12 is to describe the existing status quo"
- 400e - Pubicly appendable collections; Picked up by a few other folks, also potentially Mastodon (with their new groups implementation)
- How do we treat group actors in forum/threaded implementations?
- a: 400e - Groups send Add activities, 1b12 - Groups send Announce activities, otherwise, a Group could even send regular Creates (editor's note: this is a dramatic simplication of the actual post here)
- Evan: announce style makes the most sense, understanding that folks use both - suggestion: document both but let consumers know they'll see one or both
- Rimu: Implementors can make opinionated decisions on how it should work, and adjust based on the reality of how the major players adopt
- Angus will continue collating responses into a spreadsheet re: group implementations
- Open item: feedback on desired UX (@trwnh@mastodon.social)
- Can a group be multiple different things? e.g. a context/thread has some recipients, a context could be an actor. How forums choose to (or could) represent these relationships via ActivityPub is what is currently being solicited
- a: Boils down to "Collections, please use them", but best to start foundationally: Notes in Collections, first.
- Due to lack of time discussion of this will take place asynchronously on the fediverse: https://community.nodebb.org/post/99491 (if this does not open in your client, paste it into the search box)
- Julian provided one user story: "If you want to share a context to others, one should share the higher-ordered collection, and not what we do today, which is to share the url/object uri for OP."
- A suitable implementation could see that and backfill the entire context locally, and redirect the user to the first object.
- Angus noted that Discourse already has some support for Collections, will provide details async on forum topic (linked above)
Action Items
- @angus@socialhub.activitypub.rocks and @julian@community.nodebb.org will update the respective handles of their categories to reflect the new working group name
- @julian@community.nodebb.org to collate responses to Article vs. Name among implementors, supply recommendation at next meeting.
- @angus@socialhub.activitypub.rocks to collate responses re: Group federation among implementors, continue discussion next meeting
- @trwnh@mastodon.social to solicit feedback asynchronously via the fediverse
Show Original Post
grishka (@grishka@mastodon.social)
After all these years, #Smithereen finally has this remote interaction thingy when you click a like or share button while logged out.
Show Original Post
post (@post@community.nodebb.org)
Unfortunately during today's ForumWG call, we did not have enough time to fully discuss @trwnh@mastodon.social's desire to solicit feedback regarding the Fediverse UX for forums.
The next best thing is to collect those user stories via the fediverse and discuss again at the next meeting, so here we are!
@trwnh@mastodon.social will start off the discussion with a reply here.
Show Original Post