You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been thinking recently about how we present the project. The current website is a lot better than it used to be, but it's still not great and doesn't do a good job of explaining the project.
I think we should focus on three main things that differentiate us from other ActivityStreams/(future) ActivityPub projects:
Great admin experience - it's dead-simple to install and set up because of npm and good MongoDB packaging (even easier than Wordpress' 5-minute install, which is only 5 minutes if you already have a database, web server, etc.). We're also always looking to make this better with things like zero-downtime restarts (Investigate zero-downtime upgrades pump.io#1295)
Flexibility through open standards - the pump.io project has historically been deeply involved in the standards community (specifically AP derives from the pump.io API). We also drive new standards and explicitly track useful protocol extensions in our issue tracker. We should focus on how this makes us open and flexible, such that we can go beyond just "social network" usecases (i.e. solid, high-performance, generic ActivityStreams distribution)
Thoughts?
The text was updated successfully, but these errors were encountered:
<e_s_p> So another strength I like is that we build on the Web
<e_s_p> Like, not with plugins or modules, but with other web sites
<e_s_p> bridges, apps, etc.
<strugee> e_s_p: yeah, good point. will include some language about that in the standards item
I've been thinking recently about how we present the project. The current website is a lot better than it used to be, but it's still not great and doesn't do a good job of explaining the project.
I think we should focus on three main things that differentiate us from other ActivityStreams/(future) ActivityPub projects:
Thoughts?
The text was updated successfully, but these errors were encountered: