guregu / intertube Goto Github PK

Need some UI improvements related to track selection in the web UI

• Be able to select multiple tracks
  • Edit multiple tracks simultaneously (the backend does support this)
  • Delete multiple tracks simultaneously
  • Select all
  • Keyboard shortcuts
• Select a track without playing it

Currently if you upload the same track in multiple encodings (e.g. mp3 and flac) it will show both of them in the web UI and subsonic APIs.
Let's deduplicate them. For Subsonic we might be able to pick based on the client's accepted types, for the web UI we can just pick the "better" format or make it a setting.

It will run without Stripe configured, but we should hide the subscription settings / nag message etc

The King Gizzard & The Wizard Lizard broke so many players with their long-ass album title :D On inter.tube, I've found this bad overflow.

Playing with the devtools of the browser, I saw that adding margin-left: 100px (more or less) to .player-title solves the problem.

(I can try to make a PR for this later, if it is okay for you.)

Let's add a flag that sets the server to "local mode" and instead of relying on Lambda / CF Workers to process/serve files, handles that stuff immediately.
I plan on adding this sometime this week, should help a lot.

Currently we return a subsonic API error when getCoverArt can't find any matching art, but some web-based clients such as Subplayer don't like this and display a broken image instead.

Instead, we should probably return an image always, but use a placeholder for missing art.

Example of brokenness:

Regression from migrating to R2. I tried to use <a download="filename"> for the download link but it only works in Safari, other browsers consider it cross-origin and ignore.

For some reason the tracks view seems to get stuck loading for me. Due to this, searching doesn't work because not every track gets indexed/cached.

Upon going to the music page, there is never any progress and it only ever says "loading..." with no percentage shown. If I switch to albums view, loading will show progress and eventually finish at which point everything can be searched. For my library it takes ~20 seconds to fully load. Then I can switch back to the tracks view to see and search all tracks.

OS: Linux
Browser: Firefox 120.0

I've tested it against R2 and it works nicely, but you need to set some CORS things in the admin panel, things like that.

Occurs when attempting to upload ~200 files

also:

error: Failed after retrying 5 times: {"message": "Internal server error"}

I'm thinking a potential issue is API rate limit exceeded, or perhaps something with Lambda function concurrency

Here's a rough idea...

Things that you need:

• B2 buckets
  • one for unprocessed uploads (intertube-upload)
  • one for processed tracks (directories split by user)
• AWS account for the Lambdas
• Cloudflare account for the Workers
• DynamoDB tables

Lambdas

• tube-web (env var MODE = WEB)
  • HTTP server (API gateway)
• tube-trigger (MODE = CHANGE)
  • DynamoDB Streams trigger on Tracks table
• tube-refresh (MODE = REFRESH)
  • Refreshes B2 API token and stores in Cloudflare KV

Workers

• workers/dl.js - file downloader
• workers/auth.js - maybe unused?

DynamoDB tables

• Tracks
• Sessions
• Users
• Files

I think this could be greatly simplified for self-hosting

You can run it locally like:

source env.sh # see README.md
go build && ./intertube

But there are a lot of things still hardcoded. Buckets, domains, Stripe IDs, ...

• https://github.com/guregu/intertube/blob/main/storage/s3.go
• https://github.com/guregu/intertube/blob/main/tube/plan.go
• https://github.com/guregu/intertube/blob/main/web/b2.go#L25-L28