Comment by ssl-3
2 days ago
Thanks. From the FAQ, https://docs.rocksky.app/faq-918661m0
> What is Rocksky?
> Rocksky is a decentralized, open-source music tracking and discovery platform built on the AT Protocol. It works like Last.fm but publishes your listening history directly to your Bluesky account.
-
Can we start a trend where we tell people what the thing is and what it does without making them dig around to find it?
I don't use Bluesky and don't plan to start. Rocksky really isn't for me.
While it's not like it was on display in the bottom of a locked filing cabinet stuck in a disused lavatory with a sign on the door saying 'Beware of the Leopard,' this whole experience could have been concluded a lot faster if the project page simply described the function of the thing in a forthright fashion.
I thought "A decentralized music tracking and discovery platform" and the features list was plenty descriptive. I don't think you have to use Bluesky to use this, I think Bluesky is like the backend, and otherwise it's a Last.fm alternative?
Yeah. I don't know, either.
And that's kind of my point: The description of what the thing does is so brief that neither of us can figure it out.
Afterward, there's a ton of instruction on how to install it. Including a link to use it on...someone else's sandbox, I guess? Which sure is neat and that may be a platform that I want to play with for my own purposes, but... the point isn't a sandbox, is it?
Or is that the point? Who could tell?
Anyway, I'm not installing new-to-me software that is so detrimentally-vague about what it is actually meant to do as this is.
(I mean: I already know about last.fm -- I've known about last.fm for decades now and even used to give them a few dollars every month. I still don't know what this thing is supposed to be, or why it exists, or what real advantages it might have. I strongly suspect that it could all be summarized very well in one or two decently-written paragraphs, and it seems very lazy to not simply write them.)
No, sorry, I was saying I do know what it does based on the description.
Instead of a line by line command copypaste, they really could have used a single post where users can just copy the commands and paste the set to terminal.
This is better so you think about the commands that you're pasting into your terminal before you do it, rather than just one blob of who-knows-what.
However, what I don't understand is why there isn't just a single Dockerfile that does it all. `docker build` is step 4 or something.