November 2025 ForumWG Meeting
Uncategorized
3
Posts
1
Posters
1
Views
-
Monthly meetings are held on the first Thursday of each month, at 13h00 to 14h00 Eastern Time (currently 18h00 to 19h00 UTC). You can find them listed in the SocialCG Calendar. The next meeting will be held (today) on 6 November 2025.
Please note the time difference if applicable, ForumWG meeting times follow Eastern (± Daylight) Time Zone.
Meeting link: https://meet.jit.si/ap-forum-wg
Discussions will continue re:
- Context (topic/thread) deletion and moving between audiences (communities/categories)
-
undefined NodeBB shared this topic on
-
Apologies, I had the date wrong, the next meeting will be held on 6 November 2025
-
A reminder that the WG meeting is coming up in 15 minutes.
Feed RSS
Gli ultimi otto messaggi ricevuti dalla Federazione
-
-
A jury of your peers is lowkey goated when defending against prosecutorial overreach is the vibe.
-
@darth_biomech yes because I follow the RSS 8-)
-
Apologies in advance if I misrepresented anybody or missed any crucial bits of information.
Julian (myself) and Ted (tallted@mastodon.social) began the session discussing moderation tools in USENET There are comparable systems to how the threadiverse propagates content. Messages are sent to a remote server who is then responsible for distribution. In relation to moderation, there was more ambiguity. Local users could set up their own kill file but whether moderation could be done from the remote server was not discussed. We discuss more about actions done to contexts (aka topics, threads) Ted recommends a read through RFCs 2821 (SMTP) and 2822 (Internet Message Format) Dmitri (dmitri@social.coop) joins at or before this point, and points out that there continues to be confusion over the context property and @context. Example actions are offered: Removing a context from an audience, and locking a context from new contributions Re: crossposting, Ted discusses the need for implementor changes to allow for contexts to be a part of multiple audiences ed: much of the discussion at this point shifts away from ForumWG terminology and toward email nomenclature for ease of understanding. ForumWG nomenclature is used for these minutes Dmitri points out that a breaking change to AP might be needed in order to break apart header (addressing/recipients) and body Julian asks why, and Dmitri mentions signing difficulties wrt bto and bcc. Julian asks if anybody uses bto and bcc, and Dmitri says "yes, absolutely", and said we should check out darius@friend.camp's Fediverse Observatory for the answer Julian says that as currently implemented, resolvable contexts do not necessarily need to be inherited. Lemmy explicitly does not want to inherit contexts, and their published contexts always refer to a local representation (ping nutomic) Julian steps through an example. NodeBB A federates context /topic/1, NodeBB B receives the topic and assigns it /topic/4bdffa. A later Removes the context. B doesn't know what A/topic/1 is so needs to resolve it, get its' root post, and see if it matches any know context on B, then act on it. Ted and Dmitri caution that this is difficult and messy, and strongly recommend that the root-level context must be inherited
-
@lorenzo jazz?
-
This post did not contain any content.
-
@informapirata bisognerebbe smettere di chiamarli Hackers, almeno noi che sappiamo chi erano gli hackers del MIT, degli Altair, degli Apple I, usiamo i termini corretti. @informatica
-
Se non li conoscete. Note Bandite: Resistenza 12
@anarchia
È passato più di un secolo dalla Marcia su Roma. Le canzoni hanno seguito, e segnato, ogni passo delle lotte contro Mussolini e i suoi successori. Anche in piena dittatura la satira era un dardo appuntito nella faretra degli antifascisti,...https://www.rivoluzioneanarchica.it/se-non-li-conoscete-note-bandite-resistenza-12/
