Salta al contenuto

Piero Bosio Social Web Site Personale Logo Fediverso

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

Mondo

Discussioni esterne a questo forum. Le opinioni e i punti di vista qui espressi potrebbero non riflettere quelli di questo forum e dei suoi membri.

Un mondo di contenuti a portata di mano…

Consideralo come il tuo feed globale di scoperte. Riunisce in un unico posto discussioni interessanti da tutto il web e da altre comunità.

Mentre puoi sfogliare ciò che è di tendenza ora, il modo migliore per usare questo feed è farlo tuo. Creando un account, puoi seguire creatori e discussioni specifiche per filtrare i contenuti superflui e vedere solo ciò che conta per te.

Pronto a tuffarti? Crea un account per iniziare a seguire gli altri, ricevere notifiche quando qualcuno ti risponde e salvare i tuoi contenuti preferiti.

Registrati Accedi
  • apps@toot.fedilab.app

    More about how moderation will work on .

    FediHood is a way to talk with people near you without telling anyone who you are or where exactly you live. It uses the with the API for common endpoints, so it already works with most apps such as . Moderation is at the heart of this new app on the Fedi. The success of the project depends on it.
    (1/5)


    @samplerYes, this is similar to WoT but with a fundamental difference: you grant trust with human review of them.
  • stefano@littleone.littlefedi.social

    littleFedi: a Fediverse Server That Doesn't Need a Data Centre

    I was fifteen, and there were no BBSes in my city. So every call was long distance, once a day, sometimes twice. I'd start the dialer and wait for that sound - the handshake, the negotiation, the hiss settling into a carrier - and then I was connected to a computer sitting in somebody's bedroom, a few hundred kilometres away. I was a co-sysop of a local board and a national moderator of a FidoNet area. None of my friends understood what I was doing, and they'd stopped asking to avoid an incomprehensible monologue. But I liked it, and that was enough for me.

    Here's the thing about that computer in someone's bedroom. There was no data centre. No domain, no certificate authority, no hosting provider, no cloud. Just a machine, a phone line, and a person who'd decided to run it. If you wanted to reach it, you called it.

    Now look at what it takes today to put a small server on the network so other people can talk to it. A public address, which most home connections no longer have. A domain, which you rent. A certificate, which somebody has to issue you. And, increasingly, a VPS somewhere, because the software won't fit on the hardware you already own.

    We've added a lot of infrastructure between two people who just want to talk. That's what littleFedi is about.

    What it is

    A single Go binary. No Ruby, no Sidekiq, no Redis, no separate worker processes to babysit. You run init, answer a few questions, and you've got a working instance. It speaks ActivityPub, and it speaks the Mastodon client API well enough that existing apps just work.

    It also runs on hardware that would make Mastodon - or even Akkoma - struggle. Most software in this space assumes a VPS with a few gigabytes of RAM and a database server next to it. We assumed a Raspberry Pi Zero W behind a home router. There's a low_power mode that tunes memory use, image decoding and thumbnail generation for exactly that kind of box, and it's tested on that kind of box, not just on a fast dev machine.

    In spirit this puts littleFedi close to snac, which I've always liked a lot. Same conviction: a personal server shouldn't need a fleet of services behind it.

    Federating without a public address

    littleMesh is the part I'm most attached to, and it's the part that goes back to the modem.

    Your instance generates an Ed25519 key pair. That key is its identity - the node's address is derived from the public key, so reaching that address means reaching the holder of that key and nobody else. No registrar, no certificate authority, nobody to ask permission from.

    A small set of public lighthouse nodes help two instances find each other. Once they're introduced, the traffic runs over a second TLS session pinned to both node IDs. The lighthouse copies encrypted bytes back and forth. It never sees plaintext, and it can't impersonate either side. And if the two nodes can reach each other directly, they drop the relay after the introduction and talk peer to peer.

    Which is, more or less, calling the BBS directly. Just without the phone bill.

    The gateway into ordinary HTTPS

    Mastodon and other regular servers can't resolve a mesh address on their own. There's no domain and no certificate for them to find.

    That's what the optional HTTPS gateway is for. A lighthouse operator can run one alongside the relay, and it bridges the mesh into ordinary HTTPS for the rest of the web. The gateway has to terminate TLS to do that, so it can technically see the traffic passing through it. Which is exactly why it's a separate, opt-in piece and not something every node exposes by default.

    It has two independent settings: one controls what the gateway lets ordinary internet visitors reach at all, and a second one applies again at the destination node. Left at their defaults, both allow only federation traffic - ActivityPub delivery, discovery, public media. Web login, API and media proxy stay closed unless an operator deliberately opens them.

    Mesh peers talking to each other directly never touch the gateway at all. That exposure only applies to the bridge into the wider web. And all of this can be self-hosted.

    Chronological timelines

    Timelines are chronological. Nothing gets reordered by an engagement model.

    If you want something closer to "what did I miss", there's a separate /catchup page you visit on purpose. It ranks posts using signals your own instance already has - how many people you follow boosted something, whether it continues a conversation you took part in. No external popularity score, no telemetry, nothing leaves the machine. You press "mark as read", it moves a divider, and that's the only thing it remembers.

    Self-expiring posts

    You can set a post to expire, with its own timer, instead of a fixed instance-wide setting.

    This isn't a client-side trick that hides the post from view. The expiry goes on the same durable job queue that runs the rest of littleFedi's background work, so the deletion survives restarts and isn't lost if the process happens to be down at the moment the timer fires. When it does fire, the post is deleted and a real Delete activity goes out to everyone who received it - so it actually disappears from remote instances too, not just locally. Editing the post before then can push the timer back or cancel it.

    Static blogs, with real threaded replies

    littleFedi can take a Fediverse post and publish it as a page on a plain static blog, with its own Atom feed and permalinks that don't move even if you edit the post later. No JavaScript, no database hit on page load.

    The part I find more interesting is that the replies aren't left out. If the author turns the option on, littleFedi pulls the public replies that were actually federated to the post, threads them the same way the timeline does, and bakes the whole tree into the generated HTML at build time. So a blog post can show a real comment thread, in the same static file, with the same guarantee as the rest of the page - no JavaScript, no live queries. Only public and unlisted replies qualify, obviously. Anything followers-only or direct never enters the picture.

    Why it looks like this

    This isn't minimalism for its own sake. It's about how many people simply can't run their own server today, because the requirements are too steep. The hardware, the ops complexity, or just needing a domain and a public address before you can start. We're trying to remove those barriers one at a time, while still shipping a real, federating, reasonably complete server: polls, quotes, scheduled posts, MFA, PostgreSQL and S3 if you want to scale up later.

    I've written before about taking a semi-truck to buy salad. Hardware keeps getting more expensive and the software running on it keeps asking for more of it every year. That's backwards. If the machines cost more, the operational cost of what sits on them should go down, not up. Same with complexity: the default direction is to keep adding it, and we'd rather strip it out.

    And there's the other half, which is closer to why any of us are doing this at all. It's the same thing that drew me to snac and to the way grunfink works on it, and the same thing that had me dialing a stranger's computer at fifteen. People building tools so that people can talk to each other. Nothing more dressed up than that. We'd rather show the servers running, talk about the Pi sitting in the corner, share a tiramisu photo if it comes up. The joy in this was never about the money it brings in. It's about what we end up building, humanly, because of it.

    It's beta software, still short of a first release, and I'd rather say that plainly than oversell it. But it runs, and it federates. That's the part I wanted to write about.

    #littleFedi #Fediverse


  • stefano@littleone.littlefedi.social

    Update since yesterday:

    New

    • Opt-in federated RSS feed for your account
    • Threaded federated replies now show up on static blog posts (merged from an experimental branch - works but not pretty yet, it's a start, watching it closely)
    • New followers can require your approval before they're accepted - it was there, just hidden
    • Default language, Markdown, and audience settings for new posts (replies/edits/redrafts keep original settings)
    • DM button and blog badge on profile pages

    Fixed

    • Follow/unfollow path
    • Video playback
    • Search now resolves pasted remote status URLs directly
    • RSS/blog reply preferences carry over on account export/import
    • Profile pane improvements

    All live now. Let us know if anything looks off!

    #littleFedi #Fediverse


  • staff@mastodon.social

    We published two new resources on our Help Centre today.

    To bring you more transparency about how our moderation team makes decisions, actions they might take against rule-violating behaviour, and the pathways available to you for appealing our decisions: https://help.joinmastodon.org/article/20-moderation-decisions-and-appeals

    Plus, learn how to use one of our newest features, Collections, and help people across the find new accounts to follow: https://help.joinmastodon.org/article/19-creating-a-collection


  • free_press@mstdn.social

    CLIMATE CHANGE 2026

    Record High Temperatures
    Droughts
    Flash Floods
    Wildfires

    2026 is far exceeding worst case scenario forecasts from years' past

    The iconic green lawns of Hyde Park in London have turned brown, leaving parts of the historic park resembling a parched desert landscape


  • elettrona@poliversity.it

    I was just wondering how many HIV advocates are here on Fediverse. I feel like howling to the moon!


    @ajayiyer Every context has its space of advocacy. I am wondering, as all sex education, HIV awareness advocates, event organizers, stay on commercial platforms. With all the risks we all know about.To talk about healthcare, medicine, etc. another kind of movement is needed. Many folks I know, have been in Rio de Janeiro conference. I don't understand anything of medicine, my field is awareness. Think that in my area (Italy) U=U is almost unknown, despite associations do their best to inform about it. But media never mention it properly.
  • badgefed@badges.vocalcat.com

    First 100: BadgeFed Explorer

    The verified Badge was issued to @MIchael S. Manley

    You ventured into uncharted territory and helped shape the BadgeFed project from the start. As one of the first 100 testers, your curiosity, feedback, and bug-finding instincts helped stabilize the platform. The fediverse will always remember your role in getting us off the ground—one crash, typo, and glorious bug report at a time.

    Earning Criteria: Awarded to the first 100 individuals who actively participated in the early testing phase of BadgeFed. This includes exploring the platform, submitting feedback or bug reports, and generally poking around where things probably weren’t ready yet. These badges are limited—no retroactive claims, no reruns, no exceptions. You were here. You mattered..
    Issued on: 04/11/2025 20:45:42
    Accepted On: 04/11/2025 22:32:22

    Verify the Badge here.


  • stefano@littleone.littlefedi.social

    littleFedi works like a real app on your phone

    A few people have asked me how to actually use littleFedi on mobile, so let's clear this up. I use MastoBlaster, for obvious reasons. But you don't need to build anything native - littleFedi is a Progressive Web App (PWA), and that means it behaves like a proper installed app once you set it up.

    • You add littleFedi to your home screen like any other app
    • It opens full screen, no browser address bar, no tabs cluttering things up
    • It works offline for the shell of the app, so a dead connection doesn't just throw a blank error page at you
    • You get real push notifications, even when the app isn't open
    • Static assets load instantly on repeat visits because they're cached on the device

    Just your browser doing what browsers are supposed to do.

    Installing it

    On Android (Chrome or most Chromium-based browsers): open your instance, tap the menu, and choose "Add to Home screen" or "Install app". On iOS (Safari): tap the Share button, then "Add to Home Screen". That's it - the icon lands on your home screen and from then on littleFedi launches like a native app, in its own window, with its own icon and theme color.

    Notifications that actually work

    This is the part people are usually most surprised by. littleFedi uses Web Push, so once you enable notifications from the settings page, you get real-time alerts for mentions, boosts, favourites, quotes, follows, follow requests, polls ending, and a few other events - each with its own icon so you can tell at a glance what happened without opening the app. Tap a notification and it takes you straight to the right place, or focuses the app if it's already open in another tab.

    This works the same whether the app is in the foreground, in the background, or fully closed. The browser's service worker handles delivery even when littleFedi itself isn't running.

    Why it feels fast

    Static files - the JavaScript, the icons, the stylesheets - get cached on your device the first time you load the app. On every visit after that, they load instantly from local storage instead of going over the network again, and the cache quietly checks for updates in the background so you're never stuck on stale code. Your actual content - posts, notifications, everything tied to your session - always comes fresh from the server, since that's the stuff that has to be accurate and can't be cached.

    If your connection drops entirely, you'll see an offline page instead of a browser error, so it's clear what's going on rather than looking broken.

    No extra app needed

    If you're on mobile and haven't installed littleFedi yet, this is really the way to use it day to day. It's lighter than many native apps, updates itself automatically, and you're not waiting on anyone to approve a release in an app store. Just add it to your home screen and it stays there, working like any other app on your phone.

    #littleFedi #PWA #OwnYourData #Fediverse


  • gina@fosstodon.org

    I'm so excited to organize this with @elena 🥳🥳

    This years @oscl has a new track named “Decentralized Technologies for Digital Sovereignty!" 👏

    🔗: https://conference.opensource.lu

    We are looking for speakers interested in discussing these topics:

    • Federated technologies in the public sector
    • Decentralized platforms
    • Fediverse successes and challenges
    • Self-hosted solutions
    • Interoperability

    Apply here:
    🔗: https://pretalx.com/open-source-conference-luxembourg-2026/cfp

    Please boost 🚀


    per saperne di più →
    @krisfreedain 🥲❤️ @Gina @oscl
  • canvasesbypeter@mementomori.social

    New Mexico sues justice department for ‘stonewalling’ Epstein investigation

    "New Mexico filed a lawsuit against the US Department of Justice and the acting attorney general, Todd Blanche, on Wednesday for “stonewalling” its criminal investigation into the activities of the late financier and sex offender Jeffrey Epstein at a remote ranch in the state.

    Raúl Torrez, the New Mexico attorney general, had said he was mulling the possibility of legal action if the justice department did not share with him by 31 July information about the alleged historical abuse of girls and young women at Epstein’s Zorro ranch about 30 miles south of Santa Fe.

    Wednesday’s filing, seen by the Guardian, delivers on that threat after the justice department appeared to ignore last Friday’s deadline."

    https://www.theguardian.com/us-news/2026/aug/05/new-mexico-sues-doj-epstein-investigation


  • canvasesbypeter@mementomori.social

    Lesser-well-known israeli occupation in Southern Syria is destroying farmland and lives

    "Across southern Syria, israelis have bulldozed trees, killed crops with chemicals, and set up a separation line that keeps farmers from their fields. Around 100 families are completely barred from accessing their land. Most of the agricultural roads have been destroyed by israeli tanks.."

    [Video link] - https://www.aljazeera.com/#flips-6402869604112


  • stefan@stefanbohacek.online

    Nice!

    "Mastodon is currently considered *the* alternative to Twitter. SURF [the IT cooperative of Dutch education and research] and Universities of the Netherlands are therefore jointly exploring how a Mastodon environment for education and research in the Netherlands can take shape."

    https://www.surf.nl/en/mastodon-pilot-for-research-and-education


    per saperne di più →
    @Bradley_JF @rejzor @stefan Few actually have, @hetzner for example.