peerreview VS Navidrome Music Server

Hey everyone, I'm an experienced software engineer from an academic family. I've been aware of the problems in academic publishing for most of my life, and for the last several years I've been running headlong into the paywalls as I work on municipal policy advocacy. I've been pondering software solutions to this problem for a long time. This is exactly the sort of problem internet based software is, in theory, best suited to solving: sharing and discussing information. It should be possible to build a web platform that allows academia to share work, collect feedback, organize review that maintains quality, and find relevant papers with out relying on private, for-profit journal publishers. It should be possible to build and run a web platform that handles all of academic publishing for 1% of the current cost of for-profit publishing or less - which would (in theory) allow the universities to keep it funded while allowing it to be free to publish and free to access. Hell, it could probably be run lean enough that individual academics could fund it through small dollar donations. There's really no good reason to allow the private publishers to charge academia $11 billion a year while keeping 80% of the work locked behind paywalls. I've had several ideas for how to approach the problem, and I spent the last year building out a beta of one of them as a side project. Software development is experimental and iterative. It only works when the developers are able to get active feedback from the people most effected by the problems they are trying to solve. So I'm reaching out for feedback on the beta, and on possible paths forward. The web platform that I've built enables crowdsourced peer review of academic papers. It uses a reputation system (similar to StackExchange) and ties reputation to a field/concept tagging system. Submitted papers must be tagged with 1 - n fields, and only peers who have passed a reputation threshold in one of the tagged fields may offer review. Review is also split into two phases: pre-publish and post-publish. Pre-publish review is author driven. It's focused on collaborative, constructive feedback and uses an interface heavily inspired by both Github Pull Requests and Google Docs. Post-publish review is much closer to traditional review, and is focused on maintaining the integrity of the literature by filtering out spam, misinformation, fraud, and poorly done work. Reputation is mostly gained and lost through voting that happens during post-publish review. Reputation can also be gained by offering particularly constructive pre-publish reviews. All reviews are open and published alongside the papers. Post-publish review is on-going. That's iteration one. As much as I believe review could be crowdsourced, it seems pretty clear that going straight from what we have to this platform would be a huge leap. So I have ideas for how to build a journal overlay on top of the crowdsourced review system that would allow editors to manage teams of reviewers and run their journals through the platform. This would allow them to take advantage of the review interface, and would still give authors the benefit of being able to have a conversation with their reviewers. Authors would then be able to choose to submit their papers to one or more journals, crowdsourced review, or both. Building that out is the next project. Right now I'm working on this as a side project and an experiment -- could a web platform like this work? Would people even use it? If the answer turns out be yes, I'd love for it to become a non-profit, multi-stakeholder cooperative. Essentially independent public infrastructure similar to Wikipedia, only more transparent and more clearly democratically governed. I would love feedback on all aspects of this project - both the current crowdsourcing iteration and the thought to build a generic, open platform for diamond open access journals to run their operations through. Could you ever see yourself using something like this to publish? What about to collect pre-print review? Could you see yourself reviewing through it? What about submitting to journals through it? Are there other approaches to building a web platform that might work better? Am I barking up the wrong tree? Should I press forward, abandon, or is there a better tree? You can find the beta platform here: https://peer-review.io The source here: https://github.com/danielbingham/peerreview And more details about exactly how it works (in its current iteration) here: https://peer-review.io/about Maintaining an open roadmap here: https://github.com/users/danielBingham/projects/6/views/1

And the source code here: https://github.com/danielbingham/peerreview

Last summer I finally saved up enough runway to take some time off work and put a significant amount of time into building an MVP beta of it ( https://peer-review.io, https://github.com/danielbingham/peerreview ). I've been trying to find folks interested in trying it out and exploring whether it could work.

Hey HN,

I've been working on Peer Review for the past year. It's still in early beta (pre-0.1) but I'm looking for some early adopters to start putting it through its paces and help highlight areas I should focus on.

Peer Review is an idea I've had for years. You're probably well aware of the problems involved in academic, scientific, and scholarly publishing - HN certainly discusses them enough. Peer Review is my attempt to solve them (or a subset of them).

Peer Review combines features of Github and StackExchange to allow scholarly review to be crowd sourced to a trusted pool of peers. It does this by tying reputation to a hierarchical field tagging system. Reputation gained in children is also gained in the parents. Authors tag their papers with any fields they feel are relevant.

This means authors can tag their papers with fields higher up the hierarchy to cast a wider review net, or go lower down the hierarchy to cast a narrower one. It also enables cross-discipline review and collaboration very easily - authors simply tag their papers with the fields of both disciplines.

The review interface combines aspects of Github PRs and Google docs.

Review is split into two phases: pre-publish "review" focused on giving authors constructive critical feedback to help the improve their work and post-publish "refereeing" which looks more like traditional peer review and is the primary mechanism through which new authors gain reputation.

The whole site is built around the idea that scholars are working to collectively build the body of human knowledge and make it the best they can.

You can see the production site here: https://peer-review.io

You're welcome to explore the staging site and treat it as a sandbox, if you'd like: https://staging.peer-review.io

It's open source: https://github.com/danielbingham/peerreview

I'm doing all the development in the open as much as possible. If it gains traction, the plan is to form a non-profit around it and explore whether a web platform can be governed democratically as a multi-stakeholder cooperative and if we can solve some of the issues around large centralized platforms through that governance approach.

I'm working open source and would welcome contributions! (https://github.com/danielbingham/peerreview)

(Although, the first contribution would probably need to be getting the local working again in a new context... I've been going fast and taking on some techdebt that will need to be paid down soon.)

My primary way to play music is from my self-hosted navidrome[1] server with my collection of albums I've mostly purchased from bandcamp. I can stream it to many different devices at home or on the go.

But sitting next to my bed is a Walkman (actually a $10 Jensen version) with a few of my favorite cassettes in the nightstand drawer. Granted, I listen to raw black metal, so the format fits the music well, but I really enjoy just popping in a cassette and hitting play. When I "metaltate", I listen to full albums and do not want to ever be interrupted or have skipping audio due to bluetooth or anything else. It is a really simple and great experience.

Would I ever take my walkman with me or want to carry around a bunch of tapes on a trip? Of course not! But it does have a time and place that is valuable.

When friends come over, we use either vinyl or my custom built RFID cards. There is more of a ceremony to digging through a physical stack of albums and being forced to listen to the album front to back.

[1] https://www.navidrome.org/

Basically, you run a server on your Mac that scans your music collection and "broadcasts" it to the network (LAN or WAN) via either the venerable UPnP/DLNA[1] family of technologies or the newish Subsonic API[2]. Of course, there are others, like DAAP or AURA, etc..

From there, you need to point a compatible player to said server to play your music on any supported device.

If you want to listen to your music on the go, pairing a Subsonic-compatible server on your Mac and a Subsonic-compatible app on your iPhone is probably the way to go. On the server side, I have only used the original Subsonic[3], which was good, but Navidrome[4] seems to be OK. But be aware that the whole "scene" is super messy and fragmented, with the usual abandoned forks of open source alternatives of everything.

Note that this means opening your local network, which comes with its own complexity.

This r/selfhosted thread[5] should give you an idea.

My use case is slightly different. I only care about streaming to my Denon CEOL mini system, which only supports UPnP/DLNA, so my current setup is:

- All my music is stored on a 2011 Mac Mini,

- I use Kazoo Server[6] (not perfect but reliable) to stream it to my audio system,

- which I control via the HEOS app provided by Denon.

Whatever stack you choose, make sure your files are tagged correctly and consistently.

[1] https://en.wikipedia.org/wiki/DLNA

[2] http://www.subsonic.org/pages/api.jsp

[3] http://www.subsonic.org/pages/index.jsp

[4] https://www.navidrome.org/

[5] https://old.reddit.com/r/selfhosted/comments/pz9dpb/lets_mak...

[6] https://docs.linn.co.uk/wiki/index.php/Kazoo_Server_setup_Ma...

[Scanner] Fix Windows scanner (#2633). Thanks @caiocotts

EDIT: This version has a bug when running on Windows that breaks your database! I deleted the Windows binary from the download page and will publish a fix very soon. For details see: https://github.com/navidrome/navidrome/issues/2630

Jellyfin is great for movies & shows. As an anecdote, it's not so good for music if you're a collector. I personally use Navidrome for that[0].

Anyway, Sonarr[1] makes use of .NET, too. Very reliable software, in my experience.

[0]: https://github.com/navidrome/navidrome

I am running ND via the docker container (deluan/navidrome:latest which is 0.49.3 (8b93962f) at the time of this writing) and interact with ND using the web interface.