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 22
  • 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
    14 Views
    This post did not contain any content.
  • 0 Votes
    6 Posts
    37 Views
    In general that's a good idea because you should never trust content coming from somewhere else (even in an S2S context) For reference, NodeBB literally sanitizes the bejeezus out of what it gets from anywhere. All classes are removed, all attributes are removed. I want it as close to semantic HTML as possible, and classes/attributes mean absolutely nothing because: I don't use the same CSS classes Attributes may not follow my own rules for when and where they are added. For example, Mastodon messes with any URL it federates out. It chops the anchor text in half, hides the rest behind invisible or something, and adds an ellipsis. invisible does something different in NodeBB, so there is a CSS conflict here. I strip everything and just show the URL as it was intended.
  • 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.
  • Topic removal from a category/community

    Technical Discussion piefed
    29
    0 Votes
    29 Posts
    126 Views
    Yes I'm fine with that. It doesn't make much difference in the end.