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

Dedicated community for Piefed announcements?

Uncategorized
5 3 32

Gli ultimi otto messaggi ricevuti dalla Federazione
  • Oltre le macerie
    @anarchia
    Eccoci di nuovo qui. Riprendiamo le pubblicazioni dopo le consuete settimane di pausa, ma per le lotte non c’è stata sosta nella crescente stretta autoritaria e militarista. Multe, denunce, sgomberi. Questi sono i regali che si sono scambiati governo e...

    Vedi l'articolo
    https://www.rivoluzioneanarchica.it/oltre-le-macerie/

    read more

  • Ha finito di vedere Un film Minecraft

    read more

  • @tasket@infosec.exchange an official protocol handler would help a lot. Today there is the option of introducing a web protocol handler but the UX for it is pretty dogshit (Piefed recently implemented it, and the number of dialogues was too damn high!)

    That said I don't know if PWAs can register against non-web protocol handlers. That would be useful for sites like NodeBB.

    read more

  • @wgwz @IceClimate comes to mind.

    read more

  • Testing a Continuous Printing Mod for the Bambu Lab A1 Mini

    There are a few types of continuous 3D printing with FDM printers, with a conveyer belt and automatic build plate swapping the most common types. The advantage of build plate swapping is that it automates the bit where normally a human would have to come in to remove finished parts from the build plate. A recent entry here is the Chitu PlateCycler C1M which the [Aurora Tech] YouTube channel had over for a review. This kit bolts onto the Bambu Lab A1 Mini FDM printer and comes with four extra PEI build plates for a not unreasonable $79 (€69).

    As also noted in the review video, this is effectively a clone of the original swapmod A1m kit, but a big difference is that the Chitu kit comes with all of the parts and doesn’t require you to print anything yourself.

    The different plates are prepared using a special tool that inserts G-code between the plate changes. Moving the bed in a specific way triggers the switch that lifts the finished plate off the magnetic bed by the plastic grip on the plate and loads a fresh plate from the stack. Here it was found that a small tolerance issue prevented the last plate from being used, but some sandpaper fixed this. Other than that it was a fairly painless experience, and for e.g. multi-color prints with separated colors – as demonstrated – it would seem to be a great way to churn out the entire model without manual intervention or a lot of wasted filament.

    Perhaps the main issue that is central to all of these build plate swap mods is where the plates go after they’re pulled off the magnetic bed: the padded box is a great idea for the first one or two plates, but after that you get your PEI build plates with parts on them crashing on top of each other.

    This is where perhaps something like a passive roller conveyer system could provide a nice gentle off-ramp, though this too would increase the footprint of the system. Regardless, the overall system seems to work well enough, allowing one to stack fresh plates in the chute and if you turn on build plate detection in the A1 you can even prevent the printer from trying to print on the magnetic bed.

    youtube.com/embed/5Ev57r4ikBg?…

    hackaday.com/2026/01/16/testin…

    read more

  • > 'Veterans GO BALLISTIC on ICE: “Fight These Motherf*ckers!”'

    https://youtube.com/watch

    read more

  • @fediversereport If they are smart they will fix a raft of fundamental UX pitfalls in current ActivityPub by defining a protocol handler for it.

    Email needed its protocol handler spec while it was getting established – and arguably still does – and I do think this is one of the ways in which ActivityPub is "like email".

    read more

  • C’era una volta Repubblica – Intervista con Franco Recanatesi


    @giornalismo
    articolo21.org/2026/01/cera-un…
    Cinquant’anni di Repubblica, con tanta nostalgia e un certo dolore. Nostalgia per lo straordinario quotidiano che fu, fondato e diretto da Eugenio Scalfari; dolore per ciò che ha smesso da tempo

    read more
Post suggeriti
  • 0 Votes
    1 Posts
    3 Views
    This is our biggest release yet, including more finished tasks than any of our previous ones. Below is a summary of the highlights: What's new Posts & communities can be labelled as AI-generated and people can choose to hide all posts tagged that way. Very similar to how NSFW works. Comments can be marked as an Answer, like on StackOverflow. React to posts and comments with an emoji. Hide an individual post from yourself, without blocking the author. PieFed is now in the Yunohost app store, making initial setup easier. When banned from a remote instance you cannot make local-only posts in their communities. Honeypot to automatically IP ban badly-behaved crawlers. https://lemmy-federate.com integration, making PieFed communities get more exposure. "Share on Mastodon" menu item on posts. Vastly improve docs for new developers, see https://codeberg.org/rimu/pyfedi/src/branch/main/docs/developer_docs. Language selection is more visible during post creation. Tag clouds can also be viewed as a list of tags. View post/comment markdown. Bot accounts are not included in community statistics. Footnote support in markdown. Polish translation. Better HTTP caching, which reduces dependence on Cloudflare. Bugs Passkey fixes. Polls can now have up to 15 options. User profile performance improved. Don't allow bypassing minimum username length and post title with whitespace. Polls and Events can no longer be posted into Lemmy communities. API Additional user settings can be set through the api, including Extra Fields. Fetch url metadata. Sort comments by controversial. Comment search now works. Hashtags. Events. Polls. Emoji reactions on posts and comments. See https://piefed.social/c/piefed_api for more details. To upgrade To upgrade from 1.3.x: git pull git checkout v1.4.x ./deploy.sh or ./deploy-docker.sh There is a big database migration that will take a few minutes to run. How long will vary depending on how old your instance is - older instances will have more content to process. It took ~25 minutes on piefed.social so expect it to be less than that. Donations PieFed is free and open-source software while operating without any advertising, monetization, or reliance on venture capital. Your donations are vital in supporting the PieFed development effort, allowing us to expand and enhance PieFed with new features. Donations can be made via Patreon, Liberapay or Ko-fi.
  • 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
    4 Posts
    20 Views
    I'm looking to seeing this will bugger up Piefed <> NodeBB interop :laughing: Keep it up!
  • 0 Votes
    1 Posts
    21 Views
    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.