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. PieFed Meta
  4. The default post type is now 'Link' instead of Discussion, with community override

The default post type is now 'Link' instead of Discussion, with community override

PieFed Meta
4 4 17
Log in to reply

Feed RSS
The default post type is now 'Link' instead of Discussion, with community override

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

    Labelling or hiding AI-generated content

    PieFed Meta fediverse piefed aislop
    1
    1
    0 Votes
    1 Posts
    4 Views
    rimu@piefed.socialundefined
    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.
  • rimu@piefed.socialundefined

    @ mention suggestions in PieFed

    PieFed Meta piefed
    1
    0 Votes
    1 Posts
    14 Views
    rimu@piefed.socialundefined
    Also works with !communityname@whatever.tld for communities.
  • rimu@piefed.socialundefined

    Use hashtags for greater visibility on Mastodon

    PieFed Meta fediverse piefed
    6
    0 Votes
    6 Posts
    24 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@community.nodebb.orgundefined

    Moving topics/contexts from one community to another

    Uncategorized piefed nodebb 1b12
    1
    0 Votes
    1 Posts
    20 Views
    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.