Oh dear.
But usually you just read everything that is relevant to your research interests from the daily arxiv posting.
Love this idea.
It's routinely used for propagating smears:
https://odysee.com/@AlisonMorrow:6/how-wikipedia-decides-if-...
Even one of its co-founders says it's failing as an accurate source of information:
https://odysee.com/@TimcastIRL:8/former-founder-of-wikipedia...
Just like Jaron Lanier predicted in 2006:
https://www.edge.org/conversation/jaron_lanier-digital-maois...
I never understood why so many technologists vehemently defend a website that was obviously prone to a form of "regulatory capture" and groupthink.
If the files are cached and the services are up, it's plenty fast for static data but dynamic data (IPNS) is still very slow.
We've built a competitor called Skynet that is much faster (less than 200ms for files that aren't in the cache) and scales better. It's currently hosting tens of millions of files across 200+ TB of data.
We really like the vision that IPFS had and we think decentralized data is the future of the Internet. We're proud to have put in the legwork to make it practical.
Wait, is that a typo?? That seems incredibly generous. I guess that's where decentralization comes in.
Does it also mean that if for some reason the network comes down, the files all come down as well?
Do you have any plans to implement some search functionality to help find documents, or is it about permissionless publishing only?
In my opinion, indexing and ranking services work much better as ancillary services. The bundling of indexing and ranking with core protocol features is one of my main contentions with the Coinbase-backed "Research Hub" project/company (https://researchhub.org).
If you think about it, journals are important services, but they serve two functions right now:
1. Publication/information & data storage
2. Information indexing and ranking
Really, I think the whole contention about open/closed science is directed in the wrong place. Journals shouldn't be hosting information! They should be indexing and ranking information.
The information should be stored on an open, decentralized substrate where no one needs to go through authentication steps to view it. Then, journals can maintain their closed/open persuasions and offer bundled services and discovery and maintain their clout without really needing to change their core offering.
Also, the git repo link needs to be updated, and there's nothing there right now really, but https://github.com/scipubapp is the right link!
In my opinion, indexing and ranking services work much better as ancillary services. The bundling of indexing and ranking with core protocol features is one of my main contentions with the Coinbase-backed "Research Hub" project/company (https://researchhub.org).
If you think about it, journals are also important services
Also, git repo link needs to be updated, and there's nothing there right now really, but https://github.com/scipubapp is the right link!
Also at the time I was considering IPFS.
But I guess the real trick is implementing a WOT to implement peer review and filter out the inevitable junk that will be published
> jupyter-comment supports a number of commenting services [...]. In helping users decide which commenting and annotation services to include on their pages and commit to maintaining, could we discuss criteria for assessment and current features of services?
> Possible features for comparison:
> * Content author can delete / hide
> * Content author can report / block
> * Comments / annotations are screened by spam-fighting service
> * Content / author can label as e.g. toxic
> * Content author receives notification of new comments
> * Content author can require approval before user-contributed content is publicly-visible
> * Content author may allow comments for a limited amount of time (probably more relevant to BlogPostings)
> * Content author may simultaneously denounce censorship in all it's forms while allowing previously-published works to languish
#ForScience
> JupyterLite is a JupyterLab distribution that runs entirely in the browser built from the ground-up using JupyterLab components and extensions
With JupyterLite, you can build a static archive of a repo2docker-like environment so that the ScholarlyArticle notebook or computer modern latex css, its SoftwareRelease dependencies, and possibly also the Datasets can be run in a browser tab with WASM. HTML + JS + WASM
Furthermore, a user searching for “reviewed” data and papers would normally filter for items with enough “endorsement” metadata items signed by known WOT actors.
I haven’t figured a mechanism to prevent “review rings”, although being totally transparent it should be easy to spot them.
But overall, great idea!
arXiv does not accept papers from authors with no institutional affiliation and viXra was the only (and ugly) alternative. There is an opportunity there to fix both sites.
https://www.xirva.org/list/eess.IV/2011/2011.00052
Brings me to https://ipfs.io/ipfs/undefined/2011.00052.pdf
which says: invalid ipfs path: invalid path "/ipfs/undefined/2011.00052.pdf": invalid CID: expected 1 as the cid version number, got: 31965309853
"research publishing platform that is community based, transparent and censorship resistant" (my emphasis)
"Community members moderate the platform and can increase or decrease the visibility of the uploaded files" (again, my emphasis)
My emphasis.
invalid ipfs path: invalid path "/ipfs/undefined/2107.00648.pdf": invalid CID: expected 1 as the cid version number, got: 31965309853
Now the same for Sci-Hub?