Skip to content

Piero Bosio Social Web Site Personale Logo Fediverso

Social Forum federato con il resto del mondo. Non contano le istanze, contano le persone

Moving topics/contexts from one community to another

Uncategorized
1 1 21
  • At Piefed office hours, rimu@piefed.social and I got to talking about what's next for Piefed and the Threadiverse WG.

    One of those things is moving stuff between communities (or in bbs parlance: moving topics between categories/forums).

    Rimu suggested we use the already-existing as:Move activity, sent by the community (a group actor), with origin and target set, and with object being the post id itself.

    I suggested we update this to use the resolvable context collection as object instead, which Piefed has supported since v1.2.

    That should be enough to get a proof-of-concept implementation going between Piefed and NodeBB... a question remained as to whether this should be Announce(Move(Object)) or simply Move(Object).

    Argument for former was that it was similar verbiage to other 1b12 actions.

    Argument for the latter was that this is merely 1b12 adjacent and needn't follow prior art.

    We'll likely put together an FEP for this.

  • hongminhee@hollo.socialundefined hongminhee@hollo.social shared this topic on

Gli ultimi otto messaggi ricevuti dalla Federazione
Post suggeriti
  • 0 Votes
    1 Posts
    6 Views
    In PieFed v1.4 it will be possible to label posts as having AI generated content. Labelled posts will get a little badge near their title, similar to how nsfw and nsfl content is labelled. Mods and authors can change this value on a post in the same way they do flair and nsfw, using the little tags button in the bottom right or in 'More options' when editing their post. Account settings for blocking: [image: rIJ6kQKrU9ygU9p.png] Similar to how NSFW works, each user can control how those posts are listed on the home page, etc. The default is 'Label as AI', which just adds the badge. People averse to AI-generated content might want to change this to 'Hide completely'. Also similar to NSFW, entire communities can be assigned as 'AI content' and that will auto-tag every post inside as being AI generated. If the community mods have this value unset (e.g. Lemmy communities, which don't have this functionality) then the instance admin can manually override the community's AI Generated setting.
  • 0 Votes
    5 Posts
    32 Views
    Thanks Rimu. I'd link this one directly (and I do, under "Related Communities") but I was hoping for one dedicated to announcements only. No matter, it will work fine :)
  • 1 Votes
    1 Posts
    15 Views
    We have just released v4.6.0 of NodeBB, containing fixes to our ActivityPub integration, minor fixes with SCSS, and some new functionality with topic templating. :globe_with_meridians: ActivityPub Fixes WordPress blogs can be properly pulled into NodeBB (via their URL) now Fixed an error when moving a remote topic to another category This also fixed the issue where moved topics didn't update topic/post counters Fixed bug where NodeBB could not properly process Link headers when it contained the standalone crossorigin directive Notifications for replies to topics made in remote categories now show the appropriate user Fixed bug where remote users were not able to post to a local category if registered-users privilege was removed (now checks fediverse pseudo-user) Nested remote categories can now be removed from the ACP Remote categories can be renamed for de-duplication purposes Improved title generation for quote-posts Core fixes Persona theme now shows hidden (zero-character) links in post content _variables.scss page in ACP > Appearance can now override Bootstrap variables A template can be provided in a category's settings. This template is auto-populated in the composer when a new topic is being authored.
  • 0 Votes
    9 Posts
    74 Views
    @pfefferle https://github.com/scripting/Scripting-News/issues/329