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.

Sign up for GitHub

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

Jump to bottom

DatArchive API #5

Open
rjcorwin opened this issue Apr 7, 2018 · 5 comments
Open

DatArchive API #5

rjcorwin opened this issue Apr 7, 2018 · 5 comments

Comments

@rjcorwin
Copy link

rjcorwin commented Apr 7, 2018

dat-fox uses dat-gateway under the hood to bring support for dat to Firefox, we're considering the same for Bunsen browser. However, something hot on our todo list is to add support for DatArchive API and thinking through this I've been starting to think it might make sense as an HTTP API that a DatArchive API polyfill can fall back to if a proper DatArchive API is not available like it is in Beaker Browser. If dat-gateway offered this HTTP API for DatArchive API polyfill to fall back to, this could enable DatArchive API in both Firefox and Bunsen.

Is this crazy? Fraught with danger?
@rjcorwin
Copy link
Author

rjcorwin commented Apr 7, 2018

Aha! There is a conversation on this topic going on in the dat-fox issue queue sammacbeth/dat-fox#1

@rjcorwin rjcorwin mentioned this issue Apr 7, 2018
Closed
@RangerMauve
Copy link

Working on it today. :D Hopefully I'll have something done by next weekend.

sammacbeth pushed a commit to sammacbeth/dat-gateway that referenced this issue Apr 9, 2018
@garbados
Merge pull request pfrazee#5 from garbados/librarian
9048e4c 
[WIP] Librarian
@RangerMauve
Copy link

You can check out my progress DatArchive API using the dat-gateway websocket PR I've got open.

https://github.com/RangerMauve/dat-archive-web

Is Bunsen browser still being actively developed?

@rjcorwin
Copy link
Author

rjcorwin commented Apr 9, 2018

Is Bunsen browser still being actively developed?

@RangerMauve It is. We're incorporating some new node binaries at the moment in order to get broader device support across different chipsets. Also refactoring the server, considering using dat-gateway but probably not because of shared in browser memory access across all Dat archives. I'm experimenting with using subdomains of *.lvh.me to segment.

lvh-support

Discussion on security here.

@RangerMauve
Copy link

Awesome! I'm really excited to see it released in the playstore :D

I was thinking about setting up a public gateway that used dynamic subdomains which get proxies to the usual dat-gateway APIs.
I was thinking of just using NGINX with some rules and a wildcard DNS from letsencrypt.

Didn't the android webrequest API allow for writing arbitrary data as a response without redirecting? Maybe you can get data directly from the nodejs bridge instead of setting up a server and redirecting?

sammacbeth pushed a commit to sammacbeth/dat-gateway that referenced this issue Sep 1, 2018
@chrisekelley @RangerMauve
Add error handler for stream when refreshing browser (pfrazee#5)
86d93d4 
* added websocket peers test

* added axios to tests (supports promises)

* removed setTimeout

* commented out console.log

* removed the new Promise, since axios supports Promises

* added socket.end inside the socket.on

* added Promise and delay to 'feed' test

* added error handler for getWebsocketHandler stream

issue pfrazee#4
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rjcorwin @RangerMauve