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
  1. Home
  2. Categories
  3. Uncategorized
  4. Moving topics/contexts from one community to another

Moving topics/contexts from one community to another

Uncategorized
1 1 14
  • julian@community.nodebb.orgundefined

    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.

    1
    0
  • hongminhee@hollo.socialundefined hongminhee@hollo.social shared this topic on
Log in to reply

Feed RSS
Moving topics/contexts from one community to another

Gli ultimi otto messaggi ricevuti dalla Federazione
@pierobosio@soc.bosio.info
Post suggeriti
  • rimu@piefed.socialundefined

    Use hashtags for greater visibility on Mastodon

    PieFed Meta fediverse piefed
    6
    0 Votes
    6 Posts
    15 Views
    julian@activitypub.spaceundefined
    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.
  • julian@activitypub.spaceundefined

    Piefed community tags

    Technical Discussion piefed
    8
    0 Votes
    8 Posts
    37 Views
    rimu@piefed.socialundefined
    Another tricky aspect of this is different clients have all kinds of different designs and colors so depending on the situation the tags could look garish and crazy. But on the other hand a bit of crazy is fun.
  • pfefferle@mastodon.socialundefined

    @julian are there any plans to add #RSS support to #NodeBB?

    Fediverso rss nodebb
    9
    0 Votes
    9 Posts
    58 Views
    davew@mastodon.socialundefined
    @pfefferle https://github.com/scripting/Scripting-News/issues/329
  • abspecklog@fedimonster.deundefined

    Was mir an NodeBB gefällt, dass es komplett mit dem Fediverse föderiert.

    Fediverso nodebb discourse fediverse activitypub
    3
    0 Votes
    3 Posts
    48 Views
    pieroundefined
    @julian@activitypub.space It seems that NodeBB doesn't support the Mastodon API for polls. Since ActivityPub doesn't seem to support Poll natively, there needs to be an ActivityPub standard for poll voting. Otherwise, I suggest adopting the Mastodon API to improve compatibility with posts containing polls.