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

Cos'è il Fediverso? (doppiaggio originale ENG)

General Discussion
1 1 7

Gli ultimi otto messaggi ricevuti dalla Federazione
  • @benjohn it's not a peer to peer protocol. It's federated - meaning you can pick a provider - like email or the Fediverse.

    read more

  • @daniel I was just checking out the Wikipedia page, thanks for the pointer. … does it work well peer to peer? Identifies seem to be tied to a domain?

    https://en.wikipedia.org/wiki/XMPP

    read more

  • @daniel@gultsch.social absolutely, the same naive expectations happen often when people think forums are easy to build :smile:

    @pixelschubsi@troet.cafe is definitely on to something about re-using an existing XMPP server in order to avoid the heavy lift. The less the maintenance burden for me, the better as far as I'm concerned.

    read more

  • @julian @pixelschubsi I understand the instinct of wanting to reuse the parts you already have. Protocol parsing, identities, profiles etc. However those will very quickly become extremely minor building blocks in the complexity of instant messaging.
    It's very easy to underestimate the scope and feature creep of IM. I've seen this happening in other places where people initially think that IM is just passing some messages around. And then users demand more features and then you reinvent XMPP.

    read more

  • @julian @daniel so in practice it would probably be the other way round: that heavy lifting you're rightfully afraid of has already been done and even the large tail of the remaining 20% (that in reality need 80% of the effort) are largely done.

    If we were to agree to go the XMPP route, we could have fully-featuered deployment-ready implementations of instant messaging on top of AP identities in weeks to months. If it's something entirely new on top of AP, it's going to take years.

    read more

  • @julian @daniel I'm looking at it from a different perspective. IMO the Mastodon server (as an example) doesn't need to implement XMPP itself (it could, but it doesn't need to). Just like it doesn't implement HTTP itself.

    It could instead rely on existing implementations. Take an existing XMPP server, reverse proxy its websocket endpoint, use the existing Mastodon auth to sign in, and embed an existing XMPP web client in the web frontend.

    read more

  • @silverpill @pixelschubsi @tris you can have a single account (or as I phrased it 'identity and login credentials') across different protocols.
    For example your Google account works across multiple protocols. And even in the federated world we have several cases where email address == xmpp address.
    So to repeat myself: using the same identity is good. Doesn't mean you are locked into ActivityPub if you want to build instant messaging.

    read more

  • To preface — I'm in agreement that ActivityPub probably isn't the best protocol to use for instant messaging. There's a lot of FUD still being spread about XMPP and I am outside of most of those discussions. NodeBB only supports AP at current.

    That said, there's interest in pursuing AP as a delivery protocol for instant messaging because integrating a separate protocol is a heavy lift for everybody involved. It's a heavy lift if you already support AP, and it's a heavy lift when you support no federating protocols at all. Imagine a site looking to federate... now they have to use AP+XMPP? AP+Delta? etc...

    Setting aside all the existing reasons why AP isn't ideal, I will say this... It clears the baseline expectations:

    Messages can get sent via AP :heavy_check_mark: Messages can be privately addressed via existing AP addressing mechanisms :heavy_check_mark:

    That's it. The rest is icing. Really important icing, but for 99% of conversations, icing.

    @daniel@gultsch.social @pixelschubsi@troet.cafe

    read more
Post suggeriti
  • 0 Votes
    1 Posts
    1 Views
    We're very excited to announce that we're sponsoring Protocols for Publishers - @team - in London.As well as helping support the event, @saskia will be joined by Siddhartha from The Bristol Cable to talk about building a social app for a local community, with their local news publisher.Find out more here: https://protocolsforpublishers.com/london-2026/#ProtocolsForPublishers #ActivityPub #SocialWeb #Fediverse #SocialMedia #Mastodon #Event #London
  • 0 Votes
    1 Posts
    5 Views
    Parenting done right.(It's #HootinTootinTuesday again! Post some jokes or funny memes under this hashtag today, and bring lots of smiles to #Mastodon.)#Humor #Humour #FunnyMeme #Turkey #TurkeyDay #Dogstodon #Thanksgiving #ThanksgivingDinner #Holidays #Dogs #DogsOfMastodon #Puppies #GSDs #GSDsOfMastodon #GermanShepherds
  • 0 Votes
    1 Posts
    12 Views
    Non tutti sanno che... E' semplicissimo fare un post (toot) sul proprio profilo #mastodon con un semplice comando, ad esempio utilizzando #curl. Vediamo come fare. Abilitazione e creazione token Accedere, con il vostro account, al l'istanza mastodon di riferimento. Andare su Preferenze (menù a destra) Andare su Sviluppo (menù a sinistra) Fare click su Nuova applòicazione Compilare tutti i campi e concedere almeno i permessi di scrittura post. Salvare in un luogo sicuro (password manager) quanto generato. Comando curl di esempio curl -s -X POST https://mastodon.uno/api/v1/statuses \ -H "Authorization: Bearer TOKEN_DI_ACCESSO" \ -d "status=Ciao mondo" \ -d "visibility=public" \ Semplice Script di invio A questo punto possiamo farci un semplice script che prende in input, come parametro, del testo e lo invia per noi. cat toot.sh #!/bin/bash # Verifica che sia stato passato almeno un argomento if [ -z "$1" ]; then echo "Errore: devi passare il testo del toot come parametro." echo "Uso: $0 \"Testo del toot\"" exit 1 fi # Salva il parametro in una variabile TOOT="$1" # Esegui la richiesta POST curl -s -X POST https://mastodon.uno/api/v1/statuses \ -H "Authorization: Bearer TOKEN_DI_ACCESSO" \ -d "status=$TOOT" \ -d "visibility=public" \ -H "Authorization: Bearer TOKEN_DI_ACCESSO" \ | jq '.uri' Ho inserito #jq in fondo con un filtro (che possiamo modificare a nostro piacimento), perché l'output in formato json è abbastanza prolisso Perché? A parte che è bello fare il nerd è usare #mastodon da command line, ma la cosa può essere molto utile se la usiamo in abbinata ad altre azioni/comandi. Pensiamo ad esempio ad un integraszione con #forgejo, ad esempio potremmo fare un post (tramite #webook) al termine del nostro workflow. Un altro esempio è il collegare l'account ad un servizio di monitoraggio come #uptimekuma in questo modo si avrà una pagina che indica ai follower lo stato dei nostri servizi. Oppure usarlo al termine di un nostro script che preleva i prossimi appuntamenti da un caledario ics. Insomma, potete integrare l'invio di un toot alla fine di un vostro script custom, il limite a questo punto è solo la fantasia! E voi come lo usate? Seguimi su mastodon: @magostinelli@mastodon.uno Articolo pubblicato con licenza CC BY-NC-SA
  • 0 Votes
    2 Posts
    14 Views
    @firesidefedi oh well since you ask... @philipkristians take a note here! (bye, I'm off on holiday!)