News for hackers. Stuff that matters.
Re:Reviving Sandstorm by ocdtrekkie on Tuesday February 04, 2020 @12:06AM (#22232591)
Besides avoiding having to manage its own authentication system, one important future direction is federation. So ensuring you can associate accounts as being ‘the same person’ on multiple servers is a significant boon for the future.

As a community, many of our conversations and notes are spread across five or six servers in different people’s control. We’d like a better experience for that long term.

Email login is pretty good now though if you don’t want to deal with Google or GitHub, and now that LDAP and SAML is available for free, intranet is pretty doable with standard conventions known to most IT departments.

Re:Reviving Sandstorm by mathnmusic on Tuesday February 04, 2020 @12:25AM (#22232686)
Cloudron.io's approach seems far more easier for developers to adopt. Every webapp runs in a Docker container and auth/user management is delegated to a single-sign-on service. But it's not open-source.

Sandstorm explains why they don't use Docker: https://sandstorm.io/news/2014-08-19-why-not-run-docker-apps

But the problem with the ease of adoption remains.

Re:Reviving Sandstorm by ocdtrekkie on Tuesday February 04, 2020 @01:09AM (#22232876)
Cloudron is definitely easier to build and integrate apps for than Sandstorm. And it is open source now, although automatic updates require a license.

However, Sandstorm’s security model is a step beyone what something Docker based can offer.

Re:Reviving Sandstorm by polyglotnetwork on Tuesday February 04, 2020 @03:22AM (#22233478)
> And it is open source now

I don't think so. Here's their license: https://git.cloudron.io/cloudron/box/blob/master/LICENSE

Re:Reviving Sandstorm by ocdtrekkie on Tuesday February 04, 2020 @07:32AM (#22234798)
Oh, that’s unfortunate. It looks like they replaced the AGPL with that 11 months ago. It used to be open source!