Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Federation support #63

Open
yuvipanda opened this issue Jun 24, 2017 · 10 comments
Open

Federation support #63

yuvipanda opened this issue Jun 24, 2017 · 10 comments

Comments

@yuvipanda
Copy link
Collaborator

Me and @fperez came up with a pretty good (and really simple) federation scheme for binders late evening this friday.

I'll document that here in a day or two!

@choldgraf
Copy link
Member

did this ever get documented somewhere???

@yuvipanda
Copy link
Collaborator Author

yuvipanda commented Aug 15, 2017 via email

@choldgraf
Copy link
Member

choldgraf commented Aug 15, 2017 via email

@willingc
Copy link
Collaborator

How about 3 bullets to get it out of your head? @yuvipanda :-)

@Carreau
Copy link
Member

Carreau commented Oct 18, 2017

Summarizing for Yuvi – If I understood /inferred correctly

Have a hardcoded list of default alternative well know binder, and when hitting http://mybinder.org/ have a page asking:

Which binder to use ?
- binder.anaconda.org
- binder.microsoft.com
- binder.google.com
- custom url: 

The custom URL(s) and default chosen binder can be stored in a Cookie; so that when a user click a https://mybinder.org/path/to/repo they will be redirected to their chosen binder which may (or may not) be behind authentication.

Institutions can provide a link for their users tohttps://mybinder.org/add?https://binder.berkeley.edu that would be registered into users available binder (in the cookie). [Hidden iframe to set the cookie automatically ?]

If there is a known well defined URL scheme and API, mybinder.org can also poll known binders to see if they are up before redirecting.

We likely need a /settings/ page to allow people to change their default binder, or remove some if other binders are stopped.

@luizirber
Copy link
Contributor

This might be too random, but this last week this Rotonde social network showed up, and it has a super simple implementation: a file named portal.json inside a dat archive

  • the port field would be equivalent to your list of default alternatives, and you can also add more if you want.
  • all the posts are in the field 'feed'
    The benefit of this simple approach is that the client can be smarter (or even updated) without users losing their data.
    More info: https://github.com/Rotonde/Specs

@Carreau ideas are way more robust than this approach, but I thought it might be useful to leave this comment here.

@betatim
Copy link
Member

betatim commented Nov 21, 2017

Related work in #274

@Carreau
Copy link
Member

Carreau commented Dec 15, 2017

I'm happy with the current state of #274 and would likely like to get more reviews, and maybe get it in the wild to get limited feedback.

@choldgraf
Copy link
Member

Do you mean you'd "like to get" more reviews?

@Carreau
Copy link
Member

Carreau commented Dec 17, 2017

Do you mean you'd "like to get" more reviews?

Yeah, sorry, I was tired and speak french a lot these days my brain is confused.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants