19 ms·
Spritely – leveling up the federated social web
- and-hi 6y agoIt looks interesting but I do not really understand what it does. Could someone put this into context and summarize it, please?
- Shared404 6y agoIt appears to be a project with the goal of being a "killer app" that will push people onto the fediverse. It appears to be both a game and a messenger, sort of like a distributed MMO. Edit: Someone please correct me if I've misunderstood.
- TotempaaltJ 6y agoI think this is incorrect. It looks like it's intending to be a set of libraries or protocols(?) to support development in the distributed web. > Spritely consists of a number of modular components bringing new and rich features, from distributed programming, to decentralized storage, to virtual worlds. "Fantasary" in particular seems to match with your description. I'd guess it would be built on top of the other mentioned things.
- Shared404 6y agoAh, I missed that line. I had read it as all of the libraries/characters(?) being different parts of the same whole project, with the whole project being to achieve that goal. Thanks!
- scribu 6y agoIt's a collection of features meant to sit on top of ActivityPub. ActivityPub is a general protocol for decentralised social networking. Instead of Facebook or Twitter servers generating a feed for each user, user's servers send updates to each-other.
- TotempaaltJ 6y agoThis homepage doesn't do a great job at communicating this.
- SahAssar 6y agoI think the audience is expected to know about distributed systems and the fediverse. Think of it like being linked to https://luajit.org/ https://luajit.org/ without knowing anything about lua, programming and so on. Some links on HN are pulled from places where certain knowledge is pre-assumed.
- paroneayea 6y agoOkay, reply was long. tl;dr, just watch this video: https://conf.tube/videos/watch/18aa2f92-36cc-4424-9a4f-6f2de946fbd2 https://conf.tube/videos/watch/18aa2f92-36cc-4424-9a4f-6f2de... Hi! Spritely's main author here. Spritely is taking on quite a few things, so it's understandable that it might not be completely clear what from the tagline. Here's the short version: we'd like to bring better security, privacy, and rich interactions to the federated social web. I was one of the co-authors of the ActivityPub standard so I have some strong opinions about what it's capable of that isn't happening yet. If you want a friendly, semi-visual overview, here's a video I just recorded for the ActivityPub conference: https://conf.tube/videos/watch/18aa2f92-36cc-4424-9a4f-6f2de946fbd2 https://conf.tube/videos/watch/18aa2f92-36cc-4424-9a4f-6f2de... It goes over (most of) the layers in a fairly friendly way. Within all the subprojects listed, the most ambitious is the Fantasary one, which is distributed virtual worlds. Not as out there as it sounds, such a thing was built in the mid/late 90s: https://www.youtube.com/watch?v=KNiePoNiyvE https://www.youtube.com/watch?v=KNiePoNiyvE But in the dot-com crash, went up in flames. However many of the ideas were carried forward by the object capability community, particularly the E language, on which Spritely Goblins is heavily influenced: http://www.erights.org/ http://www.erights.org/ The distributed games goal then becomes a driver for the other components, so even if that fails we should hopefully still get cool stuff. Spritely Goblins, the foundational layer, already exists and has support for such features as time travel debugging: https://dustycloud.org/blog/goblins-time-travel-micropreview/ https://dustycloud.org/blog/goblins-time-travel-micropreview... and distributed networked programming, safe to run in a hostile network... here's a chat program where the "protocol" authenticates the users joining the channel and also that the messages came from them, with the chatroom and user "protocol" both written in 250 lines of code combined... and without being planned at all for networked interaction, it just worked over the network... here's a gif of it working over Tor Onion Services: https://dustycloud.org/misc/goblins-chat-captp-onion-services.gif https://dustycloud.org/misc/goblins-chat-captp-onion-service... No code was added to the "protocol" to expect network interactions; Goblins' CapTP (Capability Transport Protocol) took care of that for us. Already that should sound pretty cool, but that's just the foundation for the system. Look at the other subprojects to see where we're going from there. Happy to answer questions if anyone has them!
- paroneayea 6y ago
- Shared404 6y agoThis is actually a really cool idea. I saw someone mention that in order for people to use peer-to-peer tech it'll have to become easier, and more fun... It looks like this could be it.
- syllable_studio 6y agoThanks to paroneayea and team for doing this! It's so important that we move this technology forward. I'm looking forward to digging in and maybe getting involved.
- Hitton 6y agoWhat is it supposed to be? Blurb on the front page doesn't really say anything. It tells you to press "Start" to take back the net. There is no "Start" button or link...
- ryukafalz 6y agoI’ve been following this project over the last few years and it’s super exciting. There’s a lot going on here... the video and descriptions on the site are a good high-level overview, but if you want to really understand what’s going on you’ll want to click some of those links. Fair warning, rabbit holes abound. :)
- paroneayea 6y agoHi! Wow, the website just got up a couple days ago... that was fast for hitting the HN homepage... But the work has actually been happening for a couple of years, and the foundational layer, Spritely Goblins, is already something you can use: https://docs.racket-lang.org/goblins/index.html https://docs.racket-lang.org/goblins/index.html I think people don't tend to get very excited until they see the time travel demo, and then they say "whoa, something cool is going on here" https://dustycloud.org/blog/goblins-time-travel-micropreview/ https://dustycloud.org/blog/goblins-time-travel-micropreview... But that's not really the most interesting part of Spritely Goblins... the safe to run in a mutually suspicious network distributed programming environment is. Some background: I was one of the co-authors/co-editors of the ActivityPub social network standard... you might know it because it's the protocol used by Mastodon, but it's also used by Peertube, NextCloud, Write Freely, Funkwhale, Pixelfed, etc. I actually got involved in standardization because we needed it for the previous project I worked on, MediaGoblin. After standardization of ActivityPub ended, it turned out that a number of ActivityPub-using applications such as Peertube and Pixelfed and Funkwhale were using the protocol we worked on standardizing to do the kinds of things we meant to work on in MediaGoblin. So I asked myself, given the finite amount of time I have on this planet, what's the best use of my time? At this point I thought (and with a lot of feedback and phone calls with close friends): I should work on advancing the things that the federated social network can't do. And there are quite a few of those because ActivityPub left some gaps in the spec, especially around authentication and authorization, but also because people aren't building as rich of experiences as I think are interesting and possible yet... they're mostly mimicing contemporary social networks. So you can see in that long list of things on the Spritely website that one of them is Fantasary, which is the goal of bringing distributed virtual worlds to the fediverse. That may sound like a hyper-ambitious and also kind of strange goal, but consider that modern social networks are really degenerate versions of massively multiplayer games; you can chat in both, but most social networks don't have the sense of space and rich interaction that games do. But I also want to make more obscure peer-to-peer technologies available and in the hands of users without the usual "Oh no those are only for the bad people on the internet"... normalizing things can help. Those of us old enough remember when demanding https was similarly brought up with the "well, that's only for people who have something to hide". A use case of e-commerce changed that. Well, I want another use case... but one that involves fun. Hence the distributed game stuff. We can see how motivating building worlds together is by the success of minecraft. But what if the Fantasary component fails? It's the most ambitious piece! That's actually okay, because it's really a driver for all the other layers. Distributed programming that's safe to run in a hostile network, portable encrypted storage, the ability to safely run untrusted code... all of these are useful things, and useful things to bring to users generally, even if the game approach fails. But actually all of these layers are quite well researched and possible. Part of the reasons that Spritely development happened before two years before the launch of the Spritely website is because when we ran MediaGoblin, we opened up the project and within a couple of weeks had dozens of developers... but that was quite feasible to accomodate because MediaGoblin was a fairly "traditional" web application, easy enough to point to how it works by other similar web applications. Spritely is treading a lot of what appears to be "new ground" to most people, so I had to figure out how it works enough, and lay enough of the foundation, before I was comfortable making a public image for it and asking people to start looking at it. But with the last release of Goblins with the beginnings of distributed network programming and with a fairly reasonable tutorial, that's starting to change. But I said "new ground" to most people, but few of these are actually new ideas. Most of them are old, well researched ideas, from a somewhat obscure (but becoming quickly less so) branch of computer science called "object capability security". I've been very fortunate that the object capability security community has been willing to take the time to walk me through how many of these concepts work... Spritely wouldn't be possible without their help. If you want to hear more, the video embedded on the site is a good overview, but here's a direct link: https://conf.tube/videos/watch/18aa2f92-36cc-4424-9a4f-6f2de946fbd2 https://conf.tube/videos/watch/18aa2f92-36cc-4424-9a4f-6f2de... Anyway, happy to answer questions if anyone has any. And feel free to join our irc channel... we're #spritely on irc.freenode.net!
- vorpalhex 6y agoThis feels like.. too much. It's great to have all of these plans, but this is years of development at which point the original problem is likely to have changed. Especially when there is only a single very early alpha with no major product growth, this feels like Star Citizen but for ActivityPub.
- paroneayea 6y agoHi! I'm the lead author of Spritely here. Totally understand that sentiment, and you're not wrong that it's hugely ambitious. So, Spritely's approach to vaporware avoidance is to break things into subprojects and show how we're making progress with demos. If some of the subprojects fail, but the others still exist and are useful independently, that's a big win. Spritely Goblins is already quite usable, and does quite some interesting things: https://docs.racket-lang.org/goblins/index.html https://docs.racket-lang.org/goblins/index.html Even if that's all that succeeds from Spritely (and I don't think it will), I think that's a useful contribution. But seeing is believing, and skepticism is well warranted. All I can say is, I hope that in two years we can come back to this post and re-evaluate it and see how far Spritely is along. I hope we can prove ourselves. I'm working very hard to do so.
- Shared404 6y agoOff topic question. Is there a mailing list people could follow? I don't actively use anything on the fediverse and still avoid Twitter, but I would still like to follow the project.
- paroneayea 6y agoThere's no mailing list... right now just the fediverse and twitter accounts, irc, and the gitlab branches. I would be open to having a mailing list except that I'm aware the kind of maintenance burden involved in keeping them alive, and I have too much work to do on the core. Recommendations? (Also, I hope we can get to the point where we dogfood Spritely for Spritely communications, but I think that's ~1-1.5 years out from now.)
- deleted 6y ago[deleted]
- nottorp 6y agoActivityPub... fediverse. The project page doesn't mention those. Very self referential and someone from outside won't understand anything?
- paroneayea 6y agoI'm assuming what you meant is "the project page doesn't explain those" rather than it doesn't "mention" those. And it's true that it doesn't give a definition; presumably at this earlier stage, the people most interested in the website are people who are already interested in some way in the federated social web. The ActivityPub spec is linked to though, so it's not hard to find out more info about it.
- nottorp 6y agoHow about some high level overview of what they're trying to do instead of a spec? Not going to read the spec based on 'you're lazy, go read the spec'.
- ehutch79 6y agoI wish something like this would work, but there's no way this one will take off. I don't actually have any idea what it's for. Is it a twitter replacement? facebook competitor? Message board for fantasy nerds? There's no way mainstream users would go for this. It looks like an 90s fan site for some YA fantasy series. They're going to scoff at this if they stumble on this. As a technical user looking for something I could setup for small groups to use as an alternative to facebook, I can't even tell if this would work or not. I'm still not 100% this isn't some kind of cute indie mmo...
- ionforce 6y agoCompletely agree. It's like engineers consistently fail to recognize that users generally don't care about the internals. If it doesn't LOOK like FB why use it?
- eitland 6y agoIt is a careful balance isn't it? Maybe theya are just trying to recruit early techy users for now?
- egypturnash 6y agoYeah this does not do a good job of explaining itself. Maybe the video does but I haven't watched it. From what I can tell it seems to be a project with the long-term goal of building a federated VR world atop the Fediverse, with a bunch of building blocks for that split out as separate projects: running untrusted programs from federated sources, storing files on federated sources, transferring money via federated sources, etc. From a higher level I feel like, you know how there's a whole bunch of projects/companies/VC sinks whose description is "here is a familiar function but ON THE BLOCKCHAIN"? This is a bunch of those but ON THE FEDIVERSE instead. And with cute painterly mascots instead of weird little single-color abstract logos.
- paroneayea 6y agoWhen I started working on standardizing ActivityPub in the W3C Social Working Group, the main thing I heard from everyone (including here on Hacker News was): "You're wasting your time. There's no way you're going to get all these projects to talk to each other, everyone building distributed social software is too stubborn to do that." Now ActivityPub is the most widely adopted federated social network standard on the web ever, with dozens of projects using it, thousands of servers, and millions of users. I did sometimes feel like giving up when I heard that kind of feedback then, but I'm glad I didn't. I'm not going to give up here either. The project is ambitious. It's broken into many subprojects so that even if the larger goal doesn't succeed, we might still get a number of useful pieces out of it. But I've learned not to let comments like this dissuade me. If I had, ActivityPub wouldn't have happened. We might fail, but more likely, we'll have a partial success, which is still useful. And it's worth trying.
- megameter 6y agoI'm so glad this is being pursued. I'm aware of the context(I was around for early Mastodon, and have drifted away from the dev news but still have accounts I use), and the proposals sound "reasonably ambitious", in line with the idea I've daydreamed about for years that more of my online activity should go through personal AI agents, but with a sensitivity to making it work as a real distributed system. Driving things forward with demos is a good plan. The fairy cartoon aesthetic will filter out the people who don't "get" fedi, which is fine. It does fall a bit into the academic and AP-centric jargon. Some phrases that come to mind as alternate ways of defining the issues being addressed: "Quality of service" "Personalized service" "Features as services" "Self-healing" Or maybe go for the classic Unix reference and call them "daemons". Except that would have overlapping technical connotations.