GNU social JP
  • FAQ
  • Login
GNU social JPは日本のGNU socialサーバーです。
Usage/ToS/admin/test/Pleroma FE
  • Public

    • Public
    • Network
    • Groups
    • Featured
    • Popular
    • People

Conversation

Notices

  1. Embed this notice
    The Spritely Institute (spritely@social.coop)'s status on Saturday, 21-Dec-2024 05:25:55 JST The Spritely Institute The Spritely Institute

    Many new people are discovering us since the launch of our supporter campaign (thanks to all who have supported us so far!) https://spritely.institute/donate/

    For the next few days we're going to go through each of our Technical Values and Design Goals. https://spritely.institute/about/

    Today's is "Secure collaboration". Let's talk about what that means to us!

    In conversation about 6 months ago from social.coop permalink

    Attachments


    1. https://social-coop-media.ams3.cdn.digitaloceanspaces.com/media_attachments/files/113/686/964/278/010/326/original/88347f0031b8ba03.png


    • Christine Lemmer-Webber repeated this.
    • Embed this notice
      The Spritely Institute (spritely@social.coop)'s status on Saturday, 21-Dec-2024 05:26:16 JST The Spritely Institute The Spritely Institute
      in reply to

      People collaborate in many different ways; one way is in communication and discourse. But we also want to build the worlds we want to live in together.

      Why should we have only certain categories of software which are considered "social"? Our day to day lives involve social collaboration!

      The goal of Spritely's tech is to allow *all* software to be able to be easily social and distributed. This requires new foundational work.

      In conversation about 6 months ago permalink
      Christine Lemmer-Webber repeated this.
    • Embed this notice
      The Spritely Institute (spritely@social.coop)'s status on Saturday, 21-Dec-2024 05:26:17 JST The Spritely Institute The Spritely Institute
      in reply to

      Our About page defines "secure collaboration" as:

      > *Secure collaboration:* Spritely's work is to enable safe cooperation between individuals and communities in an unsafe world. We are building tools to make this possible.

      This includes decentralized social networks. But that's just a start!

      In conversation about 6 months ago permalink
      Christine Lemmer-Webber repeated this.
    • Embed this notice
      The Spritely Institute (spritely@social.coop)'s status on Saturday, 21-Dec-2024 05:26:46 JST The Spritely Institute The Spritely Institute
      in reply to

      Tomorrow we'll talk about the high level conceptual model for secure collaboration we use in Spritely's technology.

      Talk to you then, and thanks to everyone who's supported us so far! 💜 https://spritely.institute/donate

      In conversation about 6 months ago permalink

      Attachments

      1. Domain not in remote thumbnail source whitelist: files.spritely.institute
        Support Spritely! — Spritely Institute
    • Embed this notice
      Christine Lemmer-Webber (cwebber@social.coop)'s status on Tuesday, 24-Dec-2024 00:04:45 JST Christine Lemmer-Webber Christine Lemmer-Webber
      in reply to
      • Outfrost

      @outfrost @spritely Well, that's the first time our work has been described as too buzzword'y... usually it's described as too technically complex, if anything. :) And I think the reason for that is probably that this is the first time we're describing our organization in a very non-technical level: talking about the values that grow out of the mission of the organization.

      If you're wondering what we're doing, I'll explain it simply: building the foundations for the next generation of net tech

      In conversation about 6 months ago permalink
    • Embed this notice
      Outfrost (outfrost@mastodon.social)'s status on Tuesday, 24-Dec-2024 00:04:46 JST Outfrost Outfrost
      in reply to

      @spritely Not to be a naysayer, because I may be excited for some things your thing eventually brings to life, but, as a rather technical person, I have no idea what your thing is actually trying to do. I like to support cool initiatives, but I can't know if I agree or don't agree with your view of the future of the Internet, if I don't materially understand what it entails.

      Imho you might be able to reach a few more folks in general if you make your messaging less buzzwordy.

      In conversation about 6 months ago permalink
    • Embed this notice
      Christine Lemmer-Webber (cwebber@social.coop)'s status on Tuesday, 24-Dec-2024 00:06:20 JST Christine Lemmer-Webber Christine Lemmer-Webber
      in reply to
      • Outfrost

      @outfrost @spritely The challenge is "what are those new layers", and we actually have a *lot* of information on that at lower levels of detail. Since you describe yourself as technical, this paper might be helpful to you: https://files.spritely.institute/papers/spritely-core.html

      In conversation about 6 months ago permalink

      Attachments

      1. Domain not in remote thumbnail source whitelist: files.spritely.institute
        The Heart of Spritely: Distributed Objects and Capability Security
        from Christine Lemmer-Webber, Randy Farmer, Juliana Sims
    • Embed this notice
      Outfrost (outfrost@mastodon.social)'s status on Tuesday, 24-Dec-2024 01:51:38 JST Outfrost Outfrost
      in reply to
      • Christine Lemmer-Webber

      @cwebber @spritely Or is the whole point "we're here to figure out the tech to answer our current unmet needs, and we're not yet sure what all that tech is going to be"? Because reading the posts I'm not sure how to interpret it.

      In conversation about 6 months ago permalink
    • Embed this notice
      Christine Lemmer-Webber (cwebber@social.coop)'s status on Tuesday, 24-Dec-2024 01:51:38 JST Christine Lemmer-Webber Christine Lemmer-Webber
      in reply to
      • Outfrost

      @outfrost @spritely We know what the tech is going to be. We have a roadmap, and the roadmap is what we're getting onto the website next. You can see an older version on the older website https://spritelyproject.org/

      If you read the document I sent before, it's very specific about what the tech is to meet said needs. If you want another doc about motivation, read OCapPub: https://gitlab.com/spritely/ocappub/blob/master/README.org

      In conversation about 6 months ago permalink

      Attachments



    • Embed this notice
      Outfrost (outfrost@mastodon.social)'s status on Tuesday, 24-Dec-2024 01:51:39 JST Outfrost Outfrost
      in reply to
      • Christine Lemmer-Webber

      @cwebber @spritely I'm wondering about the tl;dr of "what" (more than the "why"), so I know whether I want to look something up in the long doc. Is Spritely an object capability permission model to be integrated by an operating system kernel, and to begin porting all applications to? Is it an interface for a new user-level application runtime? Is the decentralised object thing a separate framework, or part of the same, and is that important?

      In conversation about 6 months ago permalink
    • Embed this notice
      Christine Lemmer-Webber (cwebber@social.coop)'s status on Tuesday, 24-Dec-2024 01:53:24 JST Christine Lemmer-Webber Christine Lemmer-Webber
      in reply to
      • Outfrost

      @outfrost @spritely However, it's very hard to explain these things sometimes by pointing at tech documents. It was incredibly hard to explain to people what ActivityPub was and why we were standardizing it when we were working on the standardization process. Once it gained major adoption, people "just got it"

      More on that: https://dustycloud.org/blog/if-you-cant-tell-people-anything/

      We have a lot of documentation and demos on our site. We'll be producing more high-level materials soon. I guess, how far do you *want* to dive?

      In conversation about 6 months ago permalink

      Attachments


    • Embed this notice
      Christine Lemmer-Webber (cwebber@social.coop)'s status on Tuesday, 24-Dec-2024 02:41:36 JST Christine Lemmer-Webber Christine Lemmer-Webber
      in reply to
      • Outfrost

      @outfrost @spritely Good feedback, thanks. More of the "features" from the old website have slowly been migrating onto the new one. It's good to hear that the things on the old website were very directly helpful in terms of what you felt you needed to see. Thank you!

      In conversation about 6 months ago permalink
    • Embed this notice
      Outfrost (outfrost@mastodon.social)'s status on Tuesday, 24-Dec-2024 02:41:37 JST Outfrost Outfrost
      in reply to
      • Christine Lemmer-Webber

      @cwebber @spritely Tech documents is exactly what I wanted to avoid. I was looking for the "imagine social media but it's many websites/services that talk to each other, and anyone can host their own and connect it to the whole network" of ActivityPub, but for Spritely.

      In conversation about 6 months ago permalink
    • Embed this notice
      Christine Lemmer-Webber (cwebber@social.coop)'s status on Tuesday, 24-Dec-2024 03:08:00 JST Christine Lemmer-Webber Christine Lemmer-Webber
      in reply to
      • Outfrost

      @outfrost @spritely You may appreciate today's value writeup, which begins to expand on the things you're asking about: https://social.coop/@spritely/113703378145858473

      In conversation about 6 months ago permalink

      Attachments

      1. No result found on File_thumbnail lookup.
        The Spritely Institute (@spritely@social.coop)
        from The Spritely Institute
        Hello! Continuing with our walk through Spritely's Technical Values and Design Goals, today's is "networks of consent": https://spritely.institute/about/ This one expands the vision of "secure collaboration", which we discussed yesterday, and ties together both social and technical goals! 🧵

Feeds

  • Activity Streams
  • RSS 2.0
  • Atom
  • Help
  • About
  • FAQ
  • TOS
  • Privacy
  • Source
  • Version
  • Contact

GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.

Creative Commons Attribution 3.0 All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.