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/

Outfrost

@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.

Christine Lemmer-Webber

@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

Christine Lemmer-Webber

@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

Outfrost

@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?

Outfrost

@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.

Christine Lemmer-Webber

@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

Christine Lemmer-Webber

@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?

Outfrost

@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.

Christine Lemmer-Webber

@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!

Christine Lemmer-Webber

@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