filiwickers
OpenReview is building software for transparent scientific peer review, advanced review-paper matching systems, and knowledge bases for scientific communities. We are seeking an experienced full stack developer to join the dynamic team of software developers working across universities and nonprofits. We aim to revolutionize scientific peer review working with machine learning researchers, open access advocates, and a broad community of open source developers. Are you excited to build user-facing applications and inspired to develop new tools for research? Join us! Reviewing applications now!
OpenReview is a fiscally sponsored project of Code for Science & Society, a nonprofit supporting public interest technology. Read more about OpenReview + CS&S here: https://blog.codeforscience.org/welcome-and-contratuations-o...
To apply, please send a cover letter and resume to [email protected].
We created a protocol working group and spec are being updated at https://www.datprotocol.com/deps/. But definitely still some need to improve docs all around! We have an upcoming grant to support this :).
- joe hand, a dat person
Check out the first commit: https://github.com/datproject/dat/tree/464679267049899eafa34...
Bit more on the funding history, etc. : https://blog.datproject.org/2017/09/15/dat-funding-history/
Someone could built a storage that uses IPFS, similar to our dat-http storage [1].
Under the hood, there are two implementations: hyperdrive and hypercore. Hyperdrive is a filesystem for storing any kinds of files. Hypercore can store any kind of data and is really great for streaming data (hyperdrive is built on top of it).
The hosting provider is responsible for removing illegal content. Dat itself doesn't track any content. The datproject.org is more of a registry, not a host.
> Also, is your peer to peer network able to be attacked by nefarious users like a sybil attack? Is there a situation where I could alter or forge data?
No, only authorized people can write to each dat key (currently only the owner, but multi-writer is coming soon). All the writes are signed with the writers private key and then verified whenever content is downloaded.
First, we are working with libraries, universities, or other groups with large amounts of storage/bandwidth. They'd help provide hosting for datasets used inside their institutes or other essential datasets.
Second, we started to work on at-home data hosting with Project Svalbard[1]. This is kind of a SETI@home idea where people could donate server space at home to help backup "unhealthy" data (data that doesn't have many peers).
Finally, for "published" data (such as data on Zenodo or Dataverse), we can use those sites as a permanent HTTP peer. So if no data is available over p2p sites then you can get it directly from the published source.
As others said, decentralization is an approach but not a solution. It gives you the flexibility to centralize or distribute data as necessary without being tied to a specific service. But we still need to solve the problem!
[1] https://medium.com/@maxogden/project-svalbard-a-metadata-vau...
Underneath all the transfers in Globus use GridFTP. Using Dat could help distribute bandwidth and speed up transfers. It'll also add version control for free, which (I think) Globus does not have yet.
The core difference is in our approach. We're all open source and a non-profit. We're also really focused on the research data use case where BitTorrent is less easily deployed.
We hope that making an open and easy to use p2p protocol will enable other developers to build applications on top, and something like Resilio could be one.
The direct HTTP support is not fully supported yet. But we're excited for that because it'll allow you to use S3 or other static file servers as peers.
Dat works over any protocol, so it's just a matter of implementing it.
Dat is targeting similar users to Quilt. But we are also looking more broadly at libraries, labs, or other larger academic/gov't organizations managing data. There are a lot of data publishing tools in the sciences such as Zenodo. We'd love for it to be easier to download/publish data to those places. Dat is decentralized, so it really fits well in integrating other data tools.
You can use Dat to replace file transfer software like rsync, so it is a bit more general purpose.
Another difference not mentioned is that Dat really starts at the protocol level while Quilt is more software-focused. Dat protocol is a peer-to-peer protocol for syncing files, modeled off Git and BitTorrent. We built the data management software on top of the protocol.
Edit: I should mention we don't offer any hosting right now, all the data up there is temporarily cached. There is public hosting via Hashbase[1] from the Beaker team. The cool part about Dat being p2p is that it's really easy to switch hosts or use multiple hosts.
Dat Project started with a focus on increasing access to research & public data. To support the data tools we built a peer-to-peer protocol. People are doing some really cool stuff on top of Dat (such as Beaker Browser), we're really excited about it and want to make sure to support all the neat use cases.
We'll be launching an updated site soon to highlight more of the work around the protocol and what the community is building. Our main use case will still be data management but most of what you see on the current site will shift to a new domain.
This is especially important in fiction books where you are immersed in the experience of main characters. If the authors identity mirrors yours, then the experience of the main character will not build my understanding of how other people live. At this point, you are reading only for entertainment (which is fine, but you must acknowledge and accept that).
Books, whether fiction or nonfiction, are stories. They present information in a narrative. That narrative will be determined by who writes it and how they've lived their life.
Women are better writers.
=)
Historically, men were the only ones that had the opportunity to write, so any books from older centuries are going to be by men. But that doesn't have to be the case now.
ps. Love Jane Jacobs! After you read that, if you are interested, you may want to check out The Power Broker to see the other side. It is one of my top nonfiction books. (warning, white male author ;)).
* Twenty-Three Things They Don't Tell You about Capitalism [1]
* Bad Samaritans: The Myth of Free Trade and the Secret History of Capitalism [2]
[1] https://www.amazon.com/Things-They-Dont-About-Capitalism/dp/...
[2] https://www.amazon.com/Bad-Samaritans-Secret-History-Capital...
2 of 19 the books in the list are by female authors (both recommended by women). Looking for some good books from women? Check out these:
Nonfiction:
* Radical Acceptance, Tara Brach
* The Death and Life of Great American Cities, Jane Jacobs
* Freedom Is a Constant Struggle, Angela Davis
* Rising Strong, Brené Brown
* Cleopatra, Stacy Shiff
* The New Jim Crow, Michelle Alexander
Fiction:
* Anything by Ursula Le Guin
* Ancillary Justice, Ann Leckie
* Too Like the Lightning, Ada Palmer
* Citizen: An American Lyric, Claudia Rankine
... so many more
We do NAT traversal but also connect to local peers over multicast DNS. Command line client should have a local or offline option to restrict only to local peers soon.
Your points are spot on and things we've been thinking a lot about. I also wouldn't feel comfortable putting a Dat link in a paper yet, but that is an eventual goal because of the persistence properties of dat compared to http urls.
> Maybe Dat plus Zenodo could do the trick eventually.
Yes, exactly!! Dat supports http publishing right now, so you can run `dat sync --http` on a server and it'll live publish files from the source to an http site.
We are working on also supporting http downloads. The idea is you publish to Zenodo, including the SLEEP metadata, dat can then clone the files over http (including content verification) or via the peer network, i.e. `dat clone zenodo.org/record/439922`.
We are super excited for the http downloading because it'll allow dat to store files on any data repository with a good api and a http file backend. We've been talking with the Dataverse folks on how to accomplish this there and have an eye on others such as Zenodo.
However, Dat has put a lot of focus into developing an ecosystem to build applications on top of the protocol. This is making awesome things like Beaker Browser[0] and peer-npm possible [1].
[0] - https://beakerbrowser.com/ [1] - https://github.com/noffle/peer-npm
In progress paper - https://github.com/datproject/docs/blob/master/papers/dat-pa...
Dat protocol site - https://www.datprotocol.com/
However, we are concerned and thinking about how to improve reader privacy - which is the main need for anonymity in the Dat: https://datproject.org/blog/2016-12-18-p2p-reader-privacy.
Additionally, you have to explicitly opt-in to re-hosting another site. You'll never upload data unless you tell beaker to host a site.