home.social

#socialnetworking — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #socialnetworking, aggregated by home.social.

  1. It’s time for Mark Zuckerberg to resign from Meta | Joan Donovan
    By Joan Donovan

    The CEO is the throughline in a history of billion-dollar blunders that have caused real harm, culminating in last week’s settlement

    theguardian.com/technology/com

    #MarkZuckerberg #Technology #Meta #Facebook #Socialnetworking #Media #TheGuardian #JoanDonovan

  2. It’s time for Mark Zuckerberg to resign from Meta | Joan Donovan
    By Joan Donovan

    The CEO is the throughline in a history of billion-dollar blunders that have caused real harm, culminating in last week’s settlement

    theguardian.com/technology/com

    #MarkZuckerberg #Technology #Meta #Facebook #Socialnetworking #Media #TheGuardian #JoanDonovan

  3. It’s time for Mark Zuckerberg to resign from Meta | Joan Donovan
    By Joan Donovan

    The CEO is the throughline in a history of billion-dollar blunders that have caused real harm, culminating in last week’s settlement

    theguardian.com/technology/com

    #MarkZuckerberg #Technology #Meta #Facebook #Socialnetworking #Media #TheGuardian #JoanDonovan

  4. It’s time for Mark Zuckerberg to resign from Meta | Joan Donovan
    By Joan Donovan

    The CEO is the throughline in a history of billion-dollar blunders that have caused real harm, culminating in last week’s settlement

    theguardian.com/technology/com

    #MarkZuckerberg #Technology #Meta #Facebook #Socialnetworking #Media #TheGuardian #JoanDonovan

  5. It’s time for Mark Zuckerberg to resign from Meta | Joan Donovan
    By Joan Donovan

    The CEO is the throughline in a history of billion-dollar blunders that have caused real harm, culminating in last week’s settlement

    theguardian.com/technology/com

    #MarkZuckerberg #Technology #Meta #Facebook #Socialnetworking #Media #TheGuardian #JoanDonovan

  6. #Fediverse today consists of apps and app platforms. It is entirely app-centric.

    Since fediverse (luckily) didn't attract much corporate attention yet, it is dominated by #FOSS culture, where people on the #SocialWeb are all "users" that are dependent on FOSS developers to serve their needs. Every dev focuses on their app features first and #interoperability second, leading to a patchwork of poorly integrated apps, and a janky overall experience. The app delivery model is not much different than Web 2.0.

    A paradigm shift is possible, to a #SocialNetwork of apps and services, a service-oriented #fedi. The efforts around the #ActivityPub API can be the enabler of this shift.

    In this new paradigm devs introduce solutions to a unified #SocialNetworking space, delivering new services to participants on the network. On top of a robust Protocol Layer they model social use cases in the Data Layer, integrating with services and building blocks already available.

    coding.social/blog/prosocial-w

  7. #Fediverse today consists of apps and app platforms. It is entirely app-centric.

    Since fediverse (luckily) didn't attract much corporate attention yet, it is dominated by #FOSS culture, where people on the #SocialWeb are all "users" that are dependent on FOSS developers to serve their needs. Every dev focuses on their app features first and #interoperability second, leading to a patchwork of poorly integrated apps, and a janky overall experience. The app delivery model is not much different than Web 2.0.

    A paradigm shift is possible, to a #SocialNetwork of apps and services, a service-oriented #fedi. The efforts around the #ActivityPub API can be the enabler of this shift.

    In this new paradigm devs introduce solutions to a unified #SocialNetworking space, delivering new services to participants on the network. On top of a robust Protocol Layer they model social use cases in the Data Layer, integrating with services and building blocks already available.

    coding.social/blog/prosocial-w

  8. #Fediverse today consists of apps and app platforms. It is entirely app-centric.

    Since fediverse (luckily) didn't attract much corporate attention yet, it is dominated by #FOSS culture, where people on the #SocialWeb are all "users" that are dependent on FOSS developers to serve their needs. Every dev focuses on their app features first and #interoperability second, leading to a patchwork of poorly integrated apps, and a janky overall experience. The app delivery model is not much different than Web 2.0.

    A paradigm shift is possible, to a #SocialNetwork of apps and services, a service-oriented #fedi. The efforts around the #ActivityPub API can be the enabler of this shift.

    In this new paradigm devs introduce solutions to a unified #SocialNetworking space, delivering new services to participants on the network. On top of a robust Protocol Layer they model social use cases in the Data Layer, integrating with services and building blocks already available.

    coding.social/blog/prosocial-w

  9. #Fediverse today consists of apps and app platforms. It is entirely app-centric.

    Since fediverse (luckily) didn't attract much corporate attention yet, it is dominated by #FOSS culture, where people on the #SocialWeb are all "users" that are dependent on FOSS developers to serve their needs. Every dev focuses on their app features first and #interoperability second, leading to a patchwork of poorly integrated apps, and a janky overall experience. The app delivery model is not much different than Web 2.0.

    A paradigm shift is possible, to a #SocialNetwork of apps and services, a service-oriented #fedi. The efforts around the #ActivityPub API can be the enabler of this shift.

    In this new paradigm devs introduce solutions to a unified #SocialNetworking space, delivering new services to participants on the network. On top of a robust Protocol Layer they model social use cases in the Data Layer, integrating with services and building blocks already available.

    coding.social/blog/prosocial-w

  10. #Fediverse today consists of apps and app platforms. It is entirely app-centric.

    Since fediverse (luckily) didn't attract much corporate attention yet, it is dominated by #FOSS culture, where people on the #SocialWeb are all "users" that are dependent on FOSS developers to serve their needs. Every dev focuses on their app features first and #interoperability second, leading to a patchwork of poorly integrated apps, and a janky overall experience. The app delivery model is not much different than Web 2.0.

    A paradigm shift is possible, to a #SocialNetwork of apps and services, a service-oriented #fedi. The efforts around the #ActivityPub API can be the enabler of this shift.

    In this new paradigm devs introduce solutions to a unified #SocialNetworking space, delivering new services to participants on the network. On top of a robust Protocol Layer they model social use cases in the Data Layer, integrating with services and building blocks already available.

    coding.social/blog/prosocial-w

  11. @bob

    I'm happy with this #MLS #e2ee development.

    Just not with the way in which the #ActivityPub #fediverse now evolves, i.e. on the basis of protocol decay, tech debt, and whack-a-mole development. Which have been my #sighs and frustration in the past years of #SocialHub facilitation and #SocialWeb advocacy.

    Where I have use cases is in Personal #SocialNetworking, to enable #DelightfulCommons participation, and subsequently work collectively on #GrassrootsStandards

    coding.social/introduction/#pe